{"version":"2.1.248","anchor":"prewarmed-and-dispatched-background-sessions-inherit-restric","canonical_anchor":"prewarmed-and-dispatched-background-sessions-inherit-restric","heading":"Prewarmed and dispatched background sessions inherit restriction","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/prewarmed-and-dispatched-background-sessions-inherit-restric","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Prewarmed and dispatched background sessions inherit restriction\n\nBackground sessions spawned from a restricted session stay restricted.\n\n**What**\n\nBackground sessions that Claude Code starts ahead of time, and sessions started by dispatch, now always get `--restricted` when the parent session is restricted, so restriction is not lost at spawn.\n\n**Details**\n\n- The spare-session pool keeps both the caller's arguments and a copy with `--restricted` prepended, and hands back the restricted copy while the session is restricted.\n- Dispatch sites do the same, prepending the flag rather than replacing the argument list.\n\n**Evidence**\n\n`this.#t = e.includes(\"--restricted\") ? e : [\"--restricted\", ...e]`\n\n- Area: Permissions\n- Names: `--restricted`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}