Skip navigation
Agentic Batch Changes is available today.
0:00 / 1:17

Agentic Batch Changes is available today.

18 likesDownloadOriginal post

38,084 views

Agentic Batch Changes is available today. Describe a change once. It runs across 10 or 10,000 repositories, adapts where they differ, and reacts when CI fails. Agentic Batch Changes uses outcome-based pricing. You pay per changeset merged into your codebase. If a pull request doesn't merge, you don't pay for it. Read more here:

7 Comments

Comments from the original post on X (Twitter)

  • Sourcegraph's profile picture

    @Sourcegraph

    Available for all Sourcegraph Cloud customers today

    1 like

  • kettybluce's profile picture

    @KettyBruce

    Outcome-based pricing is a useful fit for batch changes because the value is tied to merged code, not raw exploration. The key operational question will be how teams review and audit multi-repo edits before CI runs.

  • Alex's profile picture

    @aficionado_ai

    I’ve had one dependency rename turn into a dozen slightly different fixes across repos. Agentic Batch Changes doing the boring propagation and only charging when the PR lands is a much saner shape.

  • RC's profile picture

    @rchandra_sekar

    Agentic Batch Changes tip: start with a narrow Deep Search scope + a deterministic script for mechanical edits; reserve Claude/Codex judgment only for the divergent repos. Pay-per-merged-changeset means fail-fast on CI loops beats spraying open PRs.

  • kettybluce's profile picture

    @KettyBruce

    Running one described change across 10 or 10,000 repositories while adapting to differences and reacting to CI failures is a strong example of outcome-oriented automation.

  • kettybluce's profile picture

    @KettyBruce

    Outcome-based pricing is a sensible fit for repository-scale automation: it aligns cost with a merged change rather than raw model activity. The CI-failure feedback loop is the crucial guardrail for keeping broad edits reviewable.

  • 剑的 AI 实验室's profile picture

    @swordBluesy

    Describe once, run across 10 or 10,000 repos is the batch-change promise. I'll try a small API rename and see if it adapts where files differ.