Now in public beta

One migration. Every repository.

Describe a change in plain language. The agent scopes it, applies it across every repo, and tracks it through to merge.

Upgrade Node.js versionsMigrate TypeScript versionsUpdate deprecated APIsBump dependenciesUpgrade Node.js versionsMigrate TypeScript versionsUpdate deprecated APIsBump dependenciesUpgrade Node.js versionsMigrate TypeScript versionsUpdate deprecated APIsBump dependenciesUpgrade Node.js versionsMigrate TypeScript versionsUpdate deprecated APIsBump dependencies
Remediate CVEs at scaleRoll out new APIs and librariesModernize CI pipelinesReplace legacy librariesRemediate CVEs at scaleRoll out new APIs and librariesModernize CI pipelinesReplace legacy librariesRemediate CVEs at scaleRoll out new APIs and librariesModernize CI pipelinesReplace legacy librariesRemediate CVEs at scaleRoll out new APIs and librariesModernize CI pipelinesReplace legacy libraries
Migrate config formatsUpdate Docker base imagesSwap database driversConvert build systemsMigrate config formatsUpdate Docker base imagesSwap database driversConvert build systemsMigrate config formatsUpdate Docker base imagesSwap database driversConvert build systemsMigrate config formatsUpdate Docker base imagesSwap database driversConvert build systems
Start with a prompt

From a one-line ask to a full migration plan.

Describe what you need in plain language, or upload a detailed plan for the agent to follow. The clearer the intent and success criteria, the sharper the results.

New batch change

OnboardingModernizationCode healthSecurity
How it works

Scope, execute, review. With CI in the loop.

01 / 05

You describe the change you want

An engineer tells the coordinator what to migrate. The rest of the console stays dimmed until there is real work to show.

Plan Resolve
Coordinator agent
Steer the run…
Repositories
Repository Host Status
payments-api GitHub -
auth-gateway GitHub -
checkout-web GitHub -
notifications GitHub -
identity-service GitHub -
search-indexer GitHub -
token-service GitHub -
recommendations GitHub -
inventory-svc GitHub -
session-store GitLab -
shipping GitHub -
fraud-detection GitHub -
user-profile GitHub -
analytics-pipeline GitHub -
data-export GitHub -
account-settings Bitbucket -
metrics-collector GitHub -
logging-agent GitHub -
rate-limiter GitHub -
login-web GitHub -
feature-flags GitHub -
config-service GitHub -
email-worker GitHub -
api-gateway GitLab -
sms-gateway GitHub -
image-resizer GitHub -
pdf-render GitHub -
mobile-bff GitHub -
geo-service GitHub -
pricing-engine GitHub -
cart-service GitHub -
web-bff GitHub -
catalog GitHub -
reviews GitHub -
wishlist GitHub -
loyalty GitHub -
partner-portal Bitbucket -
tax-service GitHub -
currency-svc GitHub -
webhooks GitHub -
scheduler GitHub -
admin-console Bitbucket -
backup-agent GitHub -
audit-log GitHub -
docs-site GitHub -
status-page GitHub -
billing-service GitHub -
design-tokens GitHub -
cdn-edge GitHub -
graphql-api GitHub -
event-bus GitHub -
sso-connector GitLab -
media-store GitHub -
user-prefs GitHub -
Execution
Containers 0 / 14
inner-loop agent 0 / 5
auth-gateway
identity-service
token-service
mobile-bff
billing-service
deterministic script 0 / 5
session-store
account-settings
login-web
web-bff
admin-console
custom image 0 / 4
user-profile
api-gateway
partner-portal
sso-connector
GitHub 0 changesets
no changesets yet
GitLab 0 changesets
no changesets yet
Bitbucket 0 changesets
no changesets yet
Coordinator standing by
I looked at a GitHub injection issue where you have to set environment variables correctly. I was able to fix it with one prompt on both the Help Center frontend and backend, then extended this to all repos in Mercari — I found around 80 potential repos affected.
Team Lead @ Mercari
One plan, the right tool

The agent picks the right approach for every change.

With access to all your code through Deep Search, Agentic Batch Changes plans each change and routes it to the tool best suited to apply it — then runs them across every repository.

Deterministic scripts

For mechanical changes, the agent writes a script — or an entire program — to apply the change efficiently across every target.

Coding agents

For changes that need judgment, it delegates to frontier agents like Claude Code and Codex, with per-repo instructions and Sourcegraph MCP for context.

Trust

Validate changes on a few repositories before rolling out to thousands. No surprise PR blasts.

Speed

Stop running the same migration by hand, one repository at a time.

Control

Approve every change set before it merges. The agent pauses for clarification when it needs your input.

Consistency

Apply the same verified logic across your entire codebase.

Built for Big Code

Agentic Batch Changes runs on the same code graph, Deep Search, and execution infrastructure that enterprises already use to manage thousands of repositories.

  • Code graph and Deep Search

    The agent identifies every repository that needs the change.

  • Per-change routing

    Deterministic scripts for mechanical changes. Coding agents for changes that need judgment.

  • Batch Changes execution

    Multi-repo scale, pull request sync, and executor reliability.

  • Changeset hooks for CI

    Teach the agent to fetch your CI logs. It reacts and iterates.

  • Coverage tracking

    Code search confirms completeness across the codebase.

  • Customizable skills

    Guide the agent with your conventions through skills and AGENTS.md, per user, org, or globally.

  • BYOK coding agent

    Bring your own model keys for the coding agents that apply changes.

Start using Agentic Batch Changes

Put Agentic Batch Changes to work on migrations, modernization, and large-scale code changes across your codebase.

Get notified

Agentic Batch Changes is currently available in beta. Sign up to be notified when general availability begins.