Background sessions spawned from a restricted session stay restricted.
What's wrong with this entry?
Background 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.
- The spare-session pool keeps both the caller's arguments and a copy with
--restrictedprepended, and hands back the restricted copy while the session is restricted. - Dispatch sites do the same, prepending the flag rather than replacing the argument list.
this.#t = e.includes("--restricted") ? e : ["--restricted", ...e]
Strings lifted out of the shipped bundle, so the claim above can be checked against them.