{"version":"2.1.281","anchor":"parked-spare-sessions-await-claim-skip-projectlocal-std","canonical_anchor":"parked-spare-sessions-await-claim-skip-projectlocal-std","heading":"Parked spare sessions (--await-claim) skip project\/local stdio MCP servers and take SessionStart hooks from claim","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/parked-spare-sessions-await-claim-skip-projectlocal-std","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Parked spare sessions (--await-claim) skip project\/local stdio MCP servers and take SessionStart hooks from claim\n\nSpare sessions parked with --await-claim skip project stdio MCP servers, and workspace_trust must now come with claim_session\n\n**Unclear.** The finding does not say exactly how `takeClaimSessionStartHooks` changes when or which `SessionStart` hooks run.\n\n**What**\n\nClaude Code can be started as a spare process with `--await-claim`, which leaves it parked and waiting until something claims it for a real session. While a spare is parked:\n\n- Local MCP servers that belong to the project folder are skipped. MCP servers are outside programs that give Claude extra tools, and these are the ones started as a local process over stdio.\n\n- A `workspace_trust` message sent to it records nothing. It should be sent along with `claim_session` instead.\n\nThe code that runs the session also gains a step, `takeClaimSessionStartHooks`, connected to `SessionStart` hooks. Hooks are your own commands that Claude Code runs at certain moments, and `SessionStart` ones run when a session begins or resumes.\n\n**Why**\n\nIf you drive parked spares yourself, sending `workspace_trust` before the claim no longer has any effect, so it has to travel with `claim_session`. Project-specific servers are also no longer started before the spare knows which project it belongs to."}