Post-crash Claude Code session recovery. Context survives the crash.
pip install resume-resume Claude Code sessions crash. Context is lost. Work has to be re-explained. resume-resume captures session state so that when a session dies, the next one picks up where the last left off — with full context of what was being worked on, what was decided, and what's next.
For developers managing many repos, resume-resume also provides a standing inventory of every repo with uncommitted changes — your dirty repos list. It only shrinks by committing.
Claude Code sessions die. The terminal crashes, the laptop sleeps, the model hiccups. The context is gone; the next session starts from zero and the work has to be re-explained from scratch. Resume-resume treats sessions as durable artifacts — indexed on disk, searchable, restorable — so the next boot picks up where the last one left off.
1. New morning, fresh session — boot_up surfaces what's pending
2. Pick up the crashed session — context restored, agent continues
Dirty repos bypass time filters — uncommitted work doesn't age out of the list. BM25 search scans 5,000+ prior sessions in ~3 seconds, so a question like "where did we test the eidos vs claude thing?" resolves instantly instead of being re-litigated.
pip install resume-resume
claude mcp add resume-resume -- resume-resume-mcp # CLI — find recent sessions
resume-resume # last 4 hours
cr 24 # last 24 hours
cr --all # everything
# MCP — from an agent
dirty_repos # what needs committing?
boot_up hours: 24 # what crashed?
search_sessions query: "eidos test where we beat claude"
merge_context id: "session-123" mode: "hybrid" Parallel git status scans across 50+ repos. BM25 search across thousands of sessions. Dirty repos bypass time filters — uncommitted work doesn't age out. Summaries cached permanently after first generation.