{"version":"2.1.307","anchor":"claim-rejects-claude-code-oauth-token-in-launcher-started-pr","canonical_anchor":"claim-rejects-claude-code-oauth-token-in-launcher-started-pr","heading":"Spare SDK processes started by a launcher refuse a sign-in token passed at claim time","tier":"notice","area":"Agents","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/claim-rejects-claude-code-oauth-token-in-launcher-started-pr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Spare SDK processes started by a launcher refuse a sign-in token passed at claim time\n\nA pre-warmed Claude Code process started by an organization's launcher now refuses CLAUDE_CODE_OAUTH_TOKEN when claimed, and asks its host instead\n\n**What**\n\nThe SDK can keep a spare Claude Code process started and waiting, so a program can claim it later and skip the start-up delay. When claiming it, the program can hand it settings.\n\nIf that spare process was started by an organization's launcher, the claim now refuses `CLAUDE_CODE_OAUTH_TOKEN` with the error `env_key_not_claimable`. Such a process gets its sign-in only by asking its host when it starts up.\n\n**Why**\n\nIt narrows how a sign-in can reach a launcher-started process. A program that passes `CLAUDE_CODE_OAUTH_TOKEN` when claiming one will now get an error.\n\n- Area: Agents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}