{"version":"2.1.248","anchor":"resume-list-explains-dead-and-cleaned-up-sessions","canonical_anchor":"resume-list-explains-dead-and-cleaned-up-sessions","heading":"Resume list explains dead and cleaned-up sessions","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/resume-list-explains-dead-and-cleaned-up-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Resume list explains dead and cleaned-up sessions\n\nThe resume list now explains sessions that died offline or whose transcripts were cleaned up.\n\n**What**\n\nThe session resume list now says why a session cannot simply be picked up. One message covers a session that ended while the background service was off, where Claude looks for the saved conversation and enter resumes it. Another covers a session whose transcript has already been cleaned off disk, where there is nothing to resume and ctrl+x deletes the row.\n\n**Details**\n\n- The off-service case is also written to stderr, distinguishing a session whose background worker was reaped from one whose terminal went away.\n- Old transcripts are cleaned up over time, which is what makes the second case permanent.\n\n**Evidence**\n\n`ended while the background service was off; looking for its saved conversation to resume`, `This session's saved conversation is no longer on disk (old transcripts are cleaned up), so there is nothing to resume. ctrl+x deletes the row.`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}