{"version":"2.1.287","anchor":"forked-subagents-can-take-a-narrowed-permission-callback","canonical_anchor":"forked-subagents-can-take-a-narrowed-permission-callback","heading":"Forked subagents can be given tighter tool permissions","tier":"internal","area":"Subagents","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/forked-subagents-can-take-a-narrowed-permission-callback","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Forked subagents can be given tighter tool permissions\n\nA forked subagent can now be launched with a stricter tool permission check layered over the main conversation's\n\n**Unclear.** What launches a fork with the narrower check is not known.\n\n**What**\n\nA subagent is a helper Claude starts to work on part of a task. A fork is a subagent that starts from a copy of the main conversation. Previously a fork used exactly the same tool permission check as the main conversation. A fork can now be launched with a narrower check layered on top, and when one is given the fork must use it. Forks are also now marked as copies of the main conversation.\n\n**Why**\n\nThis lets a fork be limited to fewer tools than the conversation it came from.\n\n- Area: Subagents\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5"}