What
- When two or more agents would write or edit files in the same repository, the Agent tool's description can now tell Claude to give each one
isolation: "worktree". - A new
sharesCwdfield on the async agent-launch tool schema flags when another write-capable agent is already running in the same working directory. When set, the tool result for the async-launched agent includes a note about the conflict and suggests usingisolation: "worktree".
Why This helps prevent parallel agents from clobbering each other's file changes by nudging Claude toward isolating them in separate worktrees when they would otherwise write to the same directory.
tengu_twinkling_boole Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.280: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.280. It isn't a statement about your account. What a flag value here can and cannot tell you
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.
* [`/batch`](/docs/en/commands) is a [skill](/docs/en/skills) that has Claude split one large change into 5 to 30 worktree-isolated subagents. It's a packaged use of subagents and worktrees, not a separate coordination style.agents see the edit
* Fixed `--setting-sources` (and SDK `settingSources`) not being forwarded to spawned sessions: teammates, `/bg`, `claude agents` sessions and `--worktree --tmux` now start with the parent's restrictionchangelog see the edit
Anthropic's documentation has since written up worktree, on Claude Code changelog.
New in this build: tengu_twinkling_boole