Agentic Batch Changes is now in public beta

Agentic Batch Changes is now in public beta: an AI agent that scopes, executes, and ships large-scale code migrations across hundreds of repositories until every PR is mergeable.

One migration. Every repository.

Large-scale code changes are one of the most expensive, error-prone, and tedious things engineering teams do. Not because the change itself is hard, but because doing it across hundreds of repositories, catching every variation, reacting to CI failures, and getting every PR to a mergeable state is an enormous coordination problem.

Every engineering team eventually faces the same version of this problem. A dependency needs upgrading. An API changes and every caller needs updating. A security vulnerability drops and the fix needs to reach every exposed repository before the next audit window. The hard part is not knowing what change to make. The hard part is executing it safely at scale.

Until now, engineering teams had four options: do it manually, build brittle one-off automation, ask a coding agent to clone hundreds of repositories locally and trust it to make it through the rollout, or avoid the rollout and let the backlog grow.

Today we're launching Agentic Batch Changes in public beta. It's what you use when the migration is too complex to automate on your own.

What it does

Agentic Batch Changes is an AI agent built on Sourcegraph's Batch Changes execution engine and code search. You describe the migration you want to run in plain language. The agent takes it from there.

Here's the loop:

Scope. The agent uses Sourcegraph search and Deep Search to identify every repository that needs the change, understand how each will be affected, and build a plan for execution.
Execute. The agent typically iterates on one repository first to refine its approach, then fans out to the rest. If the change can be scripted deterministically, it scripts it. If not, it routes to a coding agent step (Claude Code, Codex, or any coding agent via Sourcegraph Model Provider) to apply the change with judgment.
React. When CI fails, the agent reads the logs, figures out why, and pushes a follow-up commit. You can teach it how to fetch your CI logs: BuildKite, GitHub Actions, whatever you use.
Iterate. The agent keeps working until the pull request is CI-healthy and ready for a human to approve.
Check in. When the agent gets stuck or needs a decision, it stops and asks. You can also interject at any point to correct course, add context, or change direction.

Engineers review and approve every changeset before it merges. The goal is always mergeability: not just opening a PR, but a PR that's ready to merge.

Anything a single coding agent can do in one repository, Agentic Batch Changes can orchestrate across all of your repositories at the same time.

How Mercari used it to scope a fleet-wide security vulnerability

Mercari, the Japan-based marketplace platform, has been using Agentic Batch Changes during the experimental preview. Patrick Klitzke, Team Lead at Help Center at Mercari, used it to identify a GitHub Actions environment-variable injection vulnerability across their codebase and begin patching it at scale.

"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," Klitzke said.

The thing that stood out wasn't speed. It was how much judgment the agent exercised without requiring intervention. Mercari's repositories have similar setups, but not the same setup. Scripted automation would have collapsed at the first variation. The agent handled each repository individually.

"With the help of Agentic Batch Changes, you're able to handle repos that have similar, but not identical setups. A normal scripted change would most likely be a text search and replace operation without any context of how it's actually used," Klitzke said.

Canva has also been in the preview, using it to split Batch Changes by code ownership across a Bazel monorepo.

What it handles

Agentic Batch Changes is designed for the kind of code change that has historically been too complex to automate. Use cases that work well today:

Dependency upgrades with breaking changes. Major-version bumps where the API surface shifts. The agent handles per-repo variation across services.
CVE remediation with confidence. Sourcegraph search identifies every instance of a vulnerable library. Agentic Batch Changes ships the fix across every affected repository. Code Insights tracks remediation progress to close.
Code pattern updates with judgment. Refactors that need context, not regex. Internal style migrations, deprecated API replacement, Go ioutil removals, Java primitive constructor deprecations.
New API or library rollouts with per-service variation. New auth contracts, third-party library swaps, service mesh changes. Each repo often needs a slightly different update.
CI pipeline modernization. Build-system changes, test infrastructure overhauls, standardizing CI configs across a fleet.
Documentation and AGENTS.md generation. Generate per-repo documentation or guidance files to prepare your codebase for agentic tooling.

Help shape this tool

We're excited to share this product with you today, so you can help shape it! This is a public beta. There may be rough edges, and we're shipping fast, because the core capability is working in real customer environments and having real impact already. We've been using this tool daily for the past several weeks.

Agentic Batch Changes is made for multi-repo fleet-wide changes, not single-repo tasks. It is made for orchestration of large-scale changes, when coordinating them yourself would be tedious. For single-repo coding tasks, Claude Code or Cursor will serve you better.

We'd love to learn about your migration needs, and believe this tool will help you run real migrations. If you run into something that doesn't work, tell us. Your feedback will directly shape what we build next.

Availability

Agentic Batch Changes is available today in public beta for Sourcegraph Cloud customers. It's free during the beta period. Self-hosted availability arrives July 8, 2026 with Sourcegraph 7.5.

Visit sourcegraph.com/agentic-batch-changes or contact us to get started.