{"version":"2.1.281","anchor":"sdk-initialize-handles-parked-spare-sessions-await-claim","canonical_anchor":"sdk-initialize-handles-parked-spare-sessions-await-claim","heading":"SDK initialize handles parked spare sessions (--await-claim)","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/sdk-initialize-handles-parked-spare-sessions-await-claim","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### SDK initialize handles parked spare sessions (--await-claim)\n\nSDK initialize on a parked spare session (`--await-claim`) now ignores workspace trust and can defer the first prompt\n\n**Unclear.** The finding does not say what `publishedCommands` lists or when the initial prompt is deferred.\n\n**What**\n\nThe SDK lets programs drive Claude Code, and `initialize` is the first message such a program sends. A parked spare is a session started ahead of time with `--await-claim`, waiting to be claimed. On a parked spare, `initialize` now behaves differently:\n\n- `workspaceTrust` is ignored, with a warning to send `workspace_trust` with `claim_session` instead.\n\n- Setting up the agent goes through a helper that can hold back the initial prompt until later.\n\n- The reply to `initialize` now includes `publishedCommands`.\n\n**Why**\n\nIf you build on the SDK and use parked spares, workspace trust must now be sent when claiming the session, not when initializing it, or it has no effect."}