GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing sourcegraph.com — Agentic Batch Changes Agentic Batch Changes · Now available One migration. Every repository.Describe a change in plain language. The agent scopes it across your indexed codebase, applies it, 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 systemsMeet EOL deadlinesMigrate config formatsUpdate Docker base imagesSwap database driversConvert build systemsMeet EOL deadlinesMigrate config formatsUpdate Docker base imagesSwap database driversConvert build systemsMeet EOL deadlinesMigrate config formatsUpdate Docker base imagesSwap database driversConvert build systemsMeet EOL deadlines Start with a prompt From a one-line ask to a full migration planDescribe 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 RunHow it works Scope, execute, and review with CI in the loop01 / 05 You describe the change you wantAn 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 you Upgrade every service from the auth-v1 SDK to auth-v2.▍ coordinator Scoped 14 repositories with Deep Search. Splitting work by code ownership and routing each repo to the right executor.▍ coordinator Spinning up isolated containers (agents, scripts, and custom images), one per repository.▍ coordinator Changesets publishing to each code host. CI is now running across GitHub, GitLab, and Bitbucket.▍ ▲ CI failed identity-service: missing import after refactor. 1 of 14 changesets is red. coordinator Reading the logs. Patching identity-service and auth-gateway, then re-running CI.▍ coordinator All 14 changesets are green. CI passing across every repository. Migration complete.▍ 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 During the Beta, customers merged nearly a thousand changesets created by Agentic Batch Changes. 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. One plan, the right tool The agent picks the right approach for every changeWith 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 scriptsFor mechanical changes, the agent writes a script — or an entire program — to apply the change efficiently across every target. Coding agentsFor changes that need judgment, it delegates to a coding agent with per-repo instructions and Sourcegraph MCP for context. Anything a single coding agent can do in one repository, Agentic Batch Changes can orchestrate across all of your repositories at the same time. TrustValidate changes on a few repositories before rolling out to thousands. No surprise PR blasts. SpeedStop running the same migration by hand, one repository at a time. ControlApprove every change set before it merges. The agent pauses for clarification when it needs your input. ConsistencyApply the same verified logic across your entire codebase. Built for Big CodeAgentic Batch Changes runs on the same code graph, Deep Search, and execution infrastructure that enterprises already use to manage thousands of repositories.
Pay for what mergesAgentic Batch Changes uses outcome-based pricing. You pay per changeset merged into your codebase, not per token, seat, or attempt. If it opens a pull request and your team decides not to merge it, you don't pay for it. We used Agentic Batch Changes to raise and merge 50+ pull requests across our repos as part of a library migration. The web UI made it easy to track each PR and its status. Without it, we would have been managing either huge PRs or spreadsheets; instead, Agentic Batch Changes made the process easier for both reviewers and me. Start using Agentic Batch ChangesPut Agentic Batch Changes to work on migrations, modernization, and large-scale code changes across your codebase. Available now. Agentic Batch Changes is on by default for Sourcegraph Cloud customers with AI features. |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |