{"version":"2.1.321","anchor":"restore-prompt-id-for-a-turn-carried-on-by-a-new-worker-ten","canonical_anchor":"restore-prompt-id-for-a-turn-carried-on-by-a-new-worker-ten","heading":"A turn handed to a new worker can keep its prompt id","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/restore-prompt-id-for-a-turn-carried-on-by-a-new-worker-ten","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### A turn handed to a new worker can keep its prompt id\n\nBehind a switch, a turn carried on by a new worker gets its original prompt id back, or carries on without one if that fails\n\n**What**\n\nWhen a new worker process takes over a turn that is already in progress, Claude Code can now restore that turn's prompt id, the label that ties the turn to the prompt that started it. If the restore fails, the log says the turn carries on with no id.\n\nThis is behind `tengu_wise_starlight`, which is off unless it is switched on remotely. The flag server returned off for this site's account.\n\n**Why**\n\nKeeping the same prompt id across a handover keeps records of the turn connected instead of splitting it into two.\n\n- Flag `tengu_wise_starlight`: Off in both readings (read for one account on one subscription tier against v2.1.321; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}