Session resume loads blank — 4.5 MB JSONL file intact, no error, no content
Resolved 💬 6 comments Opened Feb 25, 2026 by ThatDragonOverThere Closed Mar 30, 2026
Bug: Session Resume Loads Blank
Version: Claude Code v2.1.55, Windows 11 Pro Build 26200, Bun v1.3.10
What Happens
- Session
b62b4fcc-e0df-444a-b5fa-8b1b8efeafc2was a long-running bug manager session with 80+ sub-agent transcripts - JSONL file is 4.5 MB and intact on disk
- Ctrl+E resume picker shows the session in the list
- Selecting it loads a completely blank session — no error message, no content, no history
claude --resume b62b4fcc-e0df-444a-b5fa-8b1b8efeafc2also loads blank
Expected Behavior
Session should either load with full history, or display a clear error explaining why it can't be loaded.
Context: 4th Layer of Windows Session Management Crisis
This is the 4th compounding failure in session management on Windows:
- Bun crashes force constant resumes (#21576 — 25+ TUI escapes/segfaults in 29 days)
- Session names don't persist in picker (#25090, #24729 — fixed in v2.1.53, regressed in v2.1.55)
- Bash tool was broken, blocking all work (#28343 — fixed in v2.1.55)
- Resume loads blank (THIS BUG — session data exists but loads as empty)
The workflow is: Bun crashes → must resume → can't find session by name → guess from list → session loads blank → all work lost. Every layer of the recovery path is broken.
Possibly Related
- #24729 (sessions-index.json not updated)
- #25090 (/rename not persisted)
- #20696 (compaction failures — "exceeded max compactions")
- #19888 (compaction loses entire conversation history)
Reproduction
- Run a session with many sub-agent transcripts (80+) until JSONL exceeds ~4 MB
- Exit session
- Resume via Ctrl+E or
claude --resume <id> - Session loads blank — no content displayed
This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗