What
/batch splits a large change across several workers, each in its own worktree, a separate working copy of the project. It no longer needs git. It now refuses only when the directory is not in a git repository and no WorktreeCreate hook (a user-set command that creates worktrees) is configured, and says so in a new message.
When worktrees come from the hook instead of git, a "Version control" section is added to the batch instructions. It tells the model:
gitandghcommands will not work.- Each worker should replace the commit, push and pull request step with the project's own version-control commands.
- A worker that reports
PR: nonealong with what it published instead counts as done.
Why
Projects that use a version-control system other than git can use /batch by providing a WorktreeCreate hook.
Names in the bundle/batchWorktreeCreate
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up /batch, on Message Batches API.
The Message Batch's `processing_status` field indicates the stage of processing the batch is in. It starts as `in_progress`, then updates to `ended` once all the requests in the batch have finished processing, and results are ready. You ca…build-with-claude/batch-processing see the edit
Added since
A small documentation edit on Commands touched a line naming WorktreeCreate after this was published.
| `/batch <instruction>` | **[Skill](/docs/en/skills#bundled-skills).** Orchestrate large-scale changes across a codebase in parallel. Researches the codebase, decomposes the work into 5 to 30 independent units, and presents a plan. Once a…commands see the edit
Added since
A small documentation edit on thinking touched a line naming /batch after this was published.
The SDKs require streaming when `max_tokens` is greater than 21,333, to avoid HTTP timeouts on long-running requests. This is a client-side validation, not an API restriction. If you don't need to process events incrementally, use `.stream…build-with-claude/thinking see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
A small documentation edit on thinking touched a line naming /batch after this was published.
Anthropic's release notes agree
Improved /batch to run where a WorktreeCreate hook provides the agent worktrees, not only inside a git repository