One kind of failed session load is no longer reported as an unreadable transcript
A session load that fails with one particular error no longer goes through the 'transcript unreadable' path; the general error handling takes it instead
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SessionsArea: what it touches
RemovedKind: in v2.1.291,
RemovedSection of the release
What
When Claude Code loads the full history of a session and something goes wrong, it decides how to report the problem. One specific kind of error used to be reported as an unreadable transcript with the reason "load_exhausted". That branch has been removed.
The check that decides whether an error counts as an unreadable transcript no longer includes that kind of error either. It now goes to the general error handling.
Why
This changes how some failed session loads are reported. A failure that used to show up as an unreadable transcript, after loading gave up, is now handled like any other error.
