{"version":"2.1.285","anchor":"typed-tool-flags-snapshotted-maxturns-passthrough","canonical_anchor":"typed-tool-flags-snapshotted-maxturns-passthrough","heading":"Tool restrictions and turn limits now carry over to spawned sessions","tier":"notice","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/typed-tool-flags-snapshotted-maxturns-passthrough","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Tool restrictions and turn limits now carry over to spawned sessions\n\nSpawned sessions now keep your `disallowedTools` and `tools` restrictions and your `maxTurns` limit\n\n**What**\n\nClaude Code can start other sessions of itself, such as background sessions that run while you do something else. More of your settings now pass to these sessions:\n\n- `disallowedTools` and `tools`, which control which tools Claude may use, are now saved with the permission settings.\n\n- `maxTurns`, which limits how many turns a session may take, is now passed on.\n\n- The sandbox status now includes `allow_all_unix_sockets`. The sandbox is the protective boundary around commands Claude runs.\n\n**Why**\n\nA background or spawned session now follows the same tool limits and turn limit you set for the session that started it.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}