{"version":"2.1.248","anchor":"claude-attach-explains-cleaned-up-background-sessions-instea","canonical_anchor":"claude-attach-explains-cleaned-up-background-sessions-instea","heading":"claude attach explains cleaned-up background sessions instead of failing generically","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/claude-attach-explains-cleaned-up-background-sessions-instea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### `claude attach` explains cleaned-up background sessions instead of failing generically\n\nReopening a cleaned-up background session now points you at claude rm and claude respawn.\n\n**What**\n\nTrying to reopen a background session whose transcript has already been deleted now gives a specific message pointing you at `claude rm` and `claude respawn`, instead of the old generic wake failure. A separate message, \"Can't open \u2014 this session is running in another terminal\", covers the case where another interactive session holds it.\n\n**Details**\n\n- Respawn refuses such rows with `errorCode: \"dead_epoch_transcript_gone\"`.\n- Both the attach CLI and the fleet view branch on that code, print the message and exit 1.\n- Telemetry records `cli_bg_attach` and `fleet_view_open` with reason `dead_epoch_transcript_gone`.\n- Unconditional in this build.\n\n**Evidence**\n\n`dead_epoch_transcript_gone`\n\n- Area: Sessions\n- Names: `claude attach`, `claude rm`, `claude respawn`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}