Sourcegraph says Execute in Agentic Batch Changes now queues work without a model turn

Sourcegraph has changed how the Execute button works in Agentic Batch Changes, its agent-driven batch changes feature. According to the company's 5 October 2026 changelog, clicking Execute now queues the selected workspaces right away, even while the agent is in the middle of a turn. A toast message shows which workspaces were queued, which were skipped, and why. The changelog says the update is for Sourcegraph Cloud.

The change replaces an earlier design. Sourcegraph says the button used to send the agent a chat message asking it to run the workspaces, so users waited on a model turn for something the server can do itself, and the request appeared in the conversation as if the user had typed it.

The agent is still kept informed. Sourcegraph says the click now goes to the agent's inbox rather than the conversation, and the agent reads that inbox the next time the user messages it, so it will not run the same workspaces again. If a run the user started fails, the agent wakes up and investigates; if it succeeds, nothing interrupts the user.

A related change affects selection. Sourcegraph says Select all now covers every workspace that matches the current list filter, including rows that have not loaded yet, so Execute all can queue every match in one click.

What is confirmed and what is not: everything here comes from Sourcegraph's own changelog. We have not tested the feature, and we found no independent report describing this specific change, so the duplicate-run protection and the failure-wake behavior are the company's description rather than verified behavior.

Why it matters: for teams running large batch changes, the practical difference is that queueing becomes a direct server action rather than a request the agent must interpret, and the toast makes skipped workspaces visible at the moment of the click. The changelog also says Sourcegraph is working toward similarly seamless experiences for other Agentic Batch Changes actions, such as publishing changesets, though it gives no timing.

This is a one-source item: Sourcegraph's changelog is the only source we found that describes this change.

Revised 16 October 2026: Guth re-read the original sources and rewrote this article. The earlier version remains available as revision 1.