{"version":"2.1.280","anchor":"warning-added-when-dispatching-parallel-write-capable-agents","canonical_anchor":"warning-added-when-dispatching-parallel-write-capable-agents","heading":"Warning when launching multiple write-capable agents into the same directory","tier":"notice","area":"Agent Tool","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/warning-added-when-dispatching-parallel-write-capable-agents","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Warning when launching multiple write-capable agents into the same directory\n\nClaude Code now warns when it dispatches multiple write-capable agents into the same working directory and suggests worktree isolation\n\n**What**\n\n- 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\"`.\n\n- A new `sharesCwd` field 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 using `isolation: \"worktree\"`.\n\n**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.\n\n- Flag `tengu_twinkling_boole`: Not enough to say (read for one account on one subscription tier against v2.1.280; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Agent Tool\n- Names: `worktree`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}