{"version":"2.1.275","anchor":"in-process-script-tool-calls-can-now-trigger-fork-agent","canonical_anchor":"in-process-script-tool-calls-can-now-trigger-fork-agent","heading":"In-process ('script') tool calls can now trigger fork-agent availability and get plan\/dontAsk fork restrictions","tier":"notice","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/in-process-script-tool-calls-can-now-trigger-fork-agent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### In-process ('script') tool calls can now trigger fork-agent availability and get plan\/dontAsk fork restrictions\n\nForking a subagent from an in-process tool call is now blocked in plan and dontAsk permission modes\n\n**What**\n\nWhen a subagent (a secondary Claude instance handling part of a task) is launched from an in-process, tool-triggered call rather than a direct user action, Claude Code now checks the parent's permission mode. If the parent is in `plan` mode or `dontAsk` mode, forking a new agent is refused with a message explaining that the fork would otherwise run without the parent's restriction, and suggesting starting a fresh context instead.\n\n**Why**\n\nThis closes a gap where a tool-triggered fork could bypass the stricter permission restrictions of `plan` or `dontAsk` mode, since a forked agent wasn't previously bound by the mode its parent was running under.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}