{"version":"2.1.281","anchor":"spawned-session-config-now-forwards-disallowedtools-and-take","canonical_anchor":"spawned-session-config-now-forwards-disallowedtools-and-take","heading":"Spawned-session config now forwards disallowedTools and takes effort from the right object","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/spawned-session-config-now-forwards-disallowedtools-and-take","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Spawned-session config now forwards disallowedTools and takes effort from the right object\n\nConfig for spawned sessions now passes on `disallowedTools` and reads the effort level from the correct place\n\n**Unclear.** The finding does not say which feature starts these sessions or whether that path runs in this build.\n\n**What**\n\nClaude Code can start another session and hand it some settings. The settings it hands over changed in two ways:\n\n- `disallowedTools` is now included whenever it is not empty. It lists the tools the session may not use.\n\n- `effort` is now read from the correct settings object. Before, it was read from the wrong one.\n\n**Why**\n\nA session started this way now keeps your blocked tools and gets the effort level that was meant for it."}