{"version":"2.1.281","anchor":"pre-warmed-spare-process-new-claim-state-in-launch-options","canonical_anchor":"pre-warmed-spare-process-new-claim-state-in-launch-options","heading":"Pre-warmed spare process: new claim state in launch options","tier":"internal","area":"SDK","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/pre-warmed-spare-process-new-claim-state-in-launch-options","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Pre-warmed spare process: new claim state in launch options\n\nA hidden --await-claim flag can start Claude Code as a pre-warmed spare that waits to be handed a session\n\n**What**\n\nClaude Code can now be started as a spare: a process that is already running and ready, parked until a program using the SDK hands it a session with a `claim_session` request. This is controlled by a hidden `--await-claim` flag, a command-line option not listed in the help.\n\nTwo new launch values track this:\n\n- `spareClaimState`, which is `parked`, `claiming`, `claimed` or `failed`, and resets to `none`\n\n- `spareParkedAtMs`, the time the process was parked\n\n**Why**\n\nA host program can keep a ready process waiting, so a new session does not have to wait for Claude Code to start up from scratch.\n\n- Area: SDK\n- Names: `claim_session`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}