{"version":"2.1.248","anchor":"respawn-recovers-when-another-conversation-claimed-the-sessi","canonical_anchor":"respawn-recovers-when-another-conversation-claimed-the-sessi","heading":"Respawn recovers when another conversation claimed the session id","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/respawn-recovers-when-another-conversation-claimed-the-sessi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Respawn recovers when another conversation claimed the session id\n\nIf your session id is taken, Claude Code starts under a fresh one instead of colliding.\n\n**What**\n\nWhen Claude Code restarts a session and finds its session id already in use by another conversation, it now generates a fresh id and continues instead of colliding. It warns \"session id was taken by another conversation; starting under a fresh id\".\n\n**Details**\n\n- Triggered when the stored session row is marked as taken, has no recorded CLI version, and is not a resume fork.\n- Both the session id and the resume session id are rewritten to the new id, and the taken marker is cleared.\n\n**Evidence**\n\n`session id was taken by another conversation; starting under a fresh id`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}