{"version":"2.1.277","anchor":"session-lifecycle-events-gain-a-detached-outcome","canonical_anchor":"session-lifecycle-events-gain-a-detached-outcome","heading":"Session lifecycle events gain a 'detached' outcome","tier":"internal","area":"Session Lifecycle","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/session-lifecycle-events-gain-a-detached-outcome","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Session lifecycle events gain a 'detached' outcome\n\nSession lifecycle logging gains a new detached outcome\n\n**Unclear.** The finding does not say what causes a session to become detached or what a user experiences when it happens.\n\n**What**\n\nThe list of possible session lifecycle outcomes that Claude Code records now includes `detached`, in addition to the existing `recreated`, `ended`, `cleared`, and `start_failed`.\n\n**Why**\n\nThis lets Claude Code distinguish a session becoming detached from the other existing outcomes, giving more precise session lifecycle information.\n\n- Area: Session Lifecycle\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}