- 80 potential repos affected: Mercari fixed a GitHub Actions vulnerability across 80 repositories using Sourcegraph's Agentic Batch Changes.
- Exponential codebase inertia: Large companies face increasing friction as codebases grow, consuming weeks or months of engineering time for maintenance tasks.
- Human-in-the-loop model: Every AI-generated change requires human review and approval before merging.
Experts would likely conclude that Sourcegraph's Agentic Batch Changes represents a significant advancement in managing large-scale codebases, offering scalable automation while maintaining critical human oversight to enhance security and resilience.
Beyond the Copilot: Sourcegraph’s Agentic AI Tackles Codebase Inertia
SAN FRANCISCO, CA – July 01, 2026 – For decades, the world’s largest companies have operated under an unwritten law of physics: as a codebase grows, its inertia increases exponentially. A simple change—a security patch, a dependency upgrade, a new API rollout—can trigger a cascade of manual, mind-numbing work across thousands of software repositories. This friction is a tax on innovation and a drag on resilience. Now, code intelligence platform Sourcegraph is making a bold claim: it has built the engine to overcome that inertia with the public beta launch of Agentic Batch Changes.
This new offering is an AI-powered agent designed to plan, execute, and track complex code modifications at a scale previously thought unmanageable. “Agentic Batch Changes brings the capabilities of the best coding agents to the largest companies in the world,” said Dan Adler, CEO of Sourcegraph. “For years, the owners of the largest codebases have watched smaller competitors move faster because large scale changes were too slow and too risky. Agentic Batch Changes changes that.”
The Crippling Cost of Code Paralysis
The problem isn’t new, but its consequences have become more acute. In an era of constant digital transformation, the inability to evolve a codebase quickly is a direct threat to competitive permanence. Every engineering organization has a backlog of these “changes that need to happen everywhere.” Industry analysis reveals that this kind of work can consume weeks, even months, of valuable engineering time, pulling talent away from building new products and into the drudgery of maintenance.
This forced choice between manual toil and accumulating technical debt has real-world costs. Postponing a dependency upgrade can leave a company exposed to vulnerabilities, as the industry painfully learned from incidents like the Log4j crisis. Writing brittle, one-off scripts to automate changes often creates more problems than it solves, failing to account for the subtle variations between hundreds of distinct services. The result is a state of perpetual catch-up, where the software that runs the business becomes a fragile, monolithic liability rather than a flexible asset.
From Copilot to Orchestrator: The Rise of Agentic AI
Sourcegraph’s approach marks a significant evolution in the application of AI to software development. The market is saturated with “copilot” tools that excel at suggesting code snippets or completing lines within a developer’s local environment. Agentic Batch Changes, however, operates at a higher level of abstraction. It’s not an assistant; it’s an orchestrator.
The distinction is critical. An agentic system is goal-oriented. It breaks down a complex task—such as “update all services to use the new authentication API”—into a series of executable steps. The process begins with a single natural language prompt. The agent then uses Sourcegraph’s powerful Deep Search, which understands code structure and history, to identify every affected repository across the entire organization. It formulates a plan, validates its approach on an initial repository, and learns from CI/CD pipeline feedback. Only then does it expand the rollout, intelligently adapting to per-repository variations.
This capability is powered by a sophisticated architecture that integrates Sourcegraph’s existing code graph and execution engine with frontier AI models like Claude Code and Codex. The key is the Sourcegraph Model Context Protocol (MCP), which provides these models with the precise, cross-repository context they need to make intelligent, functional changes rather than just performing a text-based search and replace. Crucially, the process remains human-in-the-loop; every single change is presented as a pull request for a human engineer to review and approve before merging, ensuring both speed and control.
Resilience in Practice: Securing the Enterprise at Scale
The most compelling case for this technology lies in its ability to enhance organizational resilience, particularly around security. A prime example comes from Mercari, the Japan-based marketplace platform that used the tool during its experimental preview. Patrick Klitzke, a Team Lead at Mercari, faced a widespread GitHub Actions vulnerability related to environment-variable injection.
“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. He stressed that the agent’s success hinged on its ability to reason about individual repository contexts. “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.”
This is the identifying mark of a winner in the modern security landscape: the ability to shrink the window between vulnerability disclosure and remediation from weeks to hours. By automating the identification and patching process across a vast and heterogeneous codebase, the system directly reduces an organization’s attack surface and strengthens its compliance posture.
The New Architecture of Software Evolution
The implications of agentic systems extend beyond immediate productivity gains. They are poised to fundamentally reshape how we think about software architecture and the role of the engineer. When the cost of making a code-level change across an entire organization drops precipitously, what was once a hard architectural decision becomes a reversible, tactical one. The focus for architects and technical leaders shifts from policing code-level consistency to managing higher-order concerns: data contracts, service boundaries, user trust, and security principles.
This doesn’t render developers obsolete; it elevates their work. By automating the toil, it frees engineers to focus on judgment, design, and strategic outcomes. The primary task becomes one of orchestration—defining the goals and guardrails for AI agents that execute the underlying changes. The human-in-the-loop model becomes the central pillar of this new workflow, ensuring that the velocity granted by AI does not lead to an acceleration of technical debt or architectural decay.
Agentic Batch Changes, now available in public beta for Sourcegraph Cloud customers, represents a powerful new tool for navigating this future. It provides a mechanism for large organizations to manage their most critical digital assets not as static liabilities, but as dynamic, resilient systems capable of evolving with the speed and confidence of a startup. This is how performance and permanence are achieved in the 21st century.
