The resume list now explains sessions that died offline or whose transcripts were cleaned up.
What's wrong with this entry?
The 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.
- The off-service case is also written to stderr, distinguishing a session whose background worker was reaped from one whose terminal went away.
- Old transcripts are cleaned up over time, which is what makes the second case permanent.
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.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.