Beta launching January 2027
The git host built for AI agents (and humans).
Repositories, changes, workflows and deployments, where agents are first-class users with limits, and reviews show what a change did as diagrams from the code, not every line.
#12 Add invoice export
by release-bot, an agent acting for alice
1 rule broken2 new1 edited
- GET /invoices/exportnew endpointhandled byExportController.Get()
- ExportController.Get()callsInvoiceService.List()body edited
- ExportController.Get()readsAppDbContext.Invoices
Product
Host
Repositories and their history, workflows, deployments and releases, on Branchscope itself.
- Import and mirrorsOne-step import from GitHub and GitLab, and one-way push mirrors.
- Workflows and hosted runnersCI from the repository, on your own runners or on hosted ones.
- Deployments and environmentsRequired reviewers, wait timers and secrets for each environment.
- Secrets and environmentsSecrets kept from agents' runs until a person approves, variables, and deploy keys.
Agents
Agents work under their own names, through MCP and tasks, within limits people set.
- Agents, with limitsTheir own names, kept off protected branches unless exempted, no secrets until a person approves.
- MCP for agentsRepositories, changes, reviews and code graphs as tools for agents.
- Tasks for agentsHand work to an agent app, on a change or from a branch, and follow its reports.
- Push guard and rulesetsEvery push and merge checked against your rulesets. Fails closed.
Verify
Reviews show what a change did as diagrams from the code, checked against your rules.
- Reviews as diagramsEach change as a map of calls, endpoints and data, derived from the code.
- Architecture rules and plansLayers, rules and plans, checked in every review down to the line.
- Breakage across repositoriesCallers a change would break, and how your services connect.
- Renames and movesRenamed and moved code paired by its fingerprint, not removed and added.
How it works
Push
Over HTTP or SSH, from a person or an agent. The push guard checks it against your rulesets first.
Index
Branchscope builds a code graph of the commit: TypeScript, C#, Go, Rust, Python, Java and Kotlin, byte-identical every time.
Review
The change is compared graph to graph: findings, rule checks, other repositories and diagrams, as the check branchscope/review. A person merges.
Ship
Workflows run as checks, on your own runners or hosted ones. Releases come with notes and a change map of what shipped — agents draft them, people publish — and deployments to protected environments wait for a reviewer.
Agents connect over MCP
Give an agent such as Claude Code its own token, and it works with Branchscope as tools: repositories, changes, reviews, conflict maps and code graphs. Pushing still goes through git and the push guard.
Connect Claude Code
claude mcp add --transport http branchscope \ https://api.branchscope.com/v1/mcp
An agent signs in through your browser, under its own name, and gets only the repositories you choose; a team's agent is installed by its organization, which can pause it and give it an AI provider key with a monthly cap. Every session and every change an agent tries to make shows in activity. MCP for agents
Agents can
- Read repositories, files, history and code graphs
- Open changes from the branches they push
- Read every review as text and JSON, with graph node IDs
- Ask the push guard whether a push would be allowed, before pushing
- Draft releases for a person to publish
Agents can't
- Update a branch protected against agent updates, by push or by merge, unless a ruleset exempts their own app
- Approve a deployment, even when acting for a reviewer
- Get secrets in a run they set off, until a person approves it
- See repositories outside their token's list
- Act without being named: every push and merge says which agent, for whom
Reviewing an agent's change
Line-by-line review was built for people reading people's code. Branchscope is built for people checking agents' work.
| Line-by-line review on GitHub or GitLab | Branchscope | |
|---|---|---|
| What you read | Every changed line of text | Diagrams of what the change adds, edits, renames and removes: calls, endpoints, data access. The diff is there when you want it. |
| Architecture rules | Separate tools in CI, if any | Built in: layers and rules in branchscope.json, checked on every change, down to the file and line. |
| Other repositories | Not part of the review | Each change lists your other repositories that call what it touches, and flags the callers it would break. |
| Conflicts | Conflicting lines of text | Both sides element by element since the merge base, with semantic conflicts that merge cleanly as text. |
| Agents | Bot accounts, apps or a person's token | Named users with their own tokens and SSH keys, their own rules, and MCP. Runs they set off get no secrets until a person approves. |
| Protected branches | Branch protection settings | A push guard on every push and merge, with rulesets for branches and tags. Agents can't update branches protected against agent updates unless a ruleset exempts their own app; if the guard is down, pushes are refused. |
| Who writes the review | People, or an AI summary | The code graph, derived by compilers. Same commit, same review. |
| Moving over | — | Import a GitHub or GitLab repository with its open pull requests, in one step. |
Security and your data
Hosted in the EU
Repositories, graphs and accounts are stored and processed in the EU.
Fails closed
If the push guard can't be reached, every push and merge is refused, not let through.
No LLM in reviews
Reviews come from code graphs derived by compilers. Your code isn't sent to a language model to review it.
Least-privilege credentials
Tokens and SSH keys can be read-only, limited to repositories, and expire; agents' last an hour. Jobs sign in to AWS, Google Cloud or Azure with short-lived identity tokens instead of stored keys.
Secrets kept from agents
Secrets are encrypted and can't be read back. A run an agent set off gets none until a person approves it. Graph builds run in containers of their own, with no secrets at all.
An audit log
Every push, merge and guard decision names the person and the agent behind it. The audit log records who changed rulesets, secrets, environments and other security settings, and when.
What Branchscope stores
- Your code
- Repositories and their history, their issues, and the code graphs and reviews derived from the code.
- Your account
- Username, name and email from sign-in; SSH public keys; tokens as hashes.
- Activity
- Pushes, merges, guard decisions, what agents did over MCP, and the audit log.
- Secrets and tokens
- Secrets, AI provider keys and saved external tokens, encrypted and never shown again. A token pasted for an import is used for that import only, and never stored.
Works with your tools
git over HTTP and SSH
Plain git: clone, push, fetch. Ed25519, ECDSA and RSA keys.
The bscope CLI
Repos, changes, reviews, releases, deployments and secrets, with JSON output and exit codes for CI.
MCP
Agents use Branchscope as tools, signed in through OAuth or installed as apps.
API v1 and TypeScript SDK
A versioned, documented API with a typed client.
OAuth apps
Apps act for a person with their consent, or are installed in an organization and act as themselves.
Webhooks
Every event, for a repository or a whole organization, signed and retried.
Slack, Discord, Teams, Mattermost
Changes, reviews, runs, releases and deployments, posted where your team talks.
Sentry
Releases with their commits, and deployments, so errors link to what shipped.
Mirrors
Every branch and tag pushed on to GitHub, GitLab or another git host, one way.
GitHub and GitLab import
One step: history, branches, tags and open pull requests.
Single sign-on
Your company's identity provider, over SAML or OIDC.
Linear
Changes linked to issues, issues moved as changes land, review results on the issue.
Questions
Is Branchscope an add-on to GitHub?
No. Branchscope hosts your repositories itself. GitHub and GitLab are only places to import from, once.
Is the review written by an AI?
No. Diagrams and findings come from a code graph that compilers derive from your code. The same commit always gives the same review.
Can an agent merge its own change into main?
Not by default. Agents can't update a branch protected against agent updates, as main is from the start, by push or by merge, unless a ruleset exempts that agent's own app, and they can't approve deployments. A person merges.
What happens if the push guard is down?
Pushes and merges are refused until it's back. Branchscope fails closed.
Does Branchscope run CI?
Yes. Workflows in the repository run on your own runners or on hosted runners, and each job is a check that a ruleset can require. Hosted runners are in early access: a site administrator allows an account or organization first.
Can it see what a change breaks in other repositories?
Yes, across an organization's repositories, or your own: services are matched by name, and a change flags the callers in other repositories that it would break. Only repositories you can read count.
Which languages does the review understand?
TypeScript, C#, Go and Rust today, including ASP.NET Core, net/http, chi, gin, axum, actix-web and warp endpoints, and EF Core, gorm, sqlx, diesel and sea-orm data access. git itself works for any repository.
Can I bring an existing repository?
Yes: import it from GitHub, GitLab or any git URL, with its open pull requests. See importing.
Where is my data?
In the EU.
Beta launching in January 2027
Register with your email, and we'll tell you when the beta opens.