{"version":"2.1.281","anchor":"spare-pool-reboots-a-spare-when-its-launch-args-change","canonical_anchor":"spare-pool-reboots-a-spare-when-its-launch-args-change","heading":"Spare pool reboots a spare when its launch args change","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/spare-pool-reboots-a-spare-when-its-launch-args-change","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Spare pool reboots a spare when its launch args change\n\nA warm spare session is now restarted when the extra launch arguments it was started with no longer match\n\n**What**\n\nA warm spare is a Claude Code session started in advance so it is ready when needed. Each spare now remembers the extra launch arguments (`extraArgs`) it was started with.\n\n- When the pool checks its spares and finds different arguments, it restarts the spare, logged as `extra_args_mismatch_reboot`.\n\n- When something tries to claim a spare with outdated arguments, the claim is refused as `stale-argv` and a new session is started from scratch instead.\n\n**Why**\n\nA claimed spare no longer runs with outdated launch options. The cost is that a mismatch means waiting for a fresh start instead of getting a ready session."}