Alternatives
Products that do what Hibernate and restore Claude Code sessions across reboots does
- 1RT
2014 · github.com
- 2

- 3SC
I got tired of Claude Code forgetting all my context every time I open a new session: set-up decisions, how I like my margins, decision history. etc. We built a shared memory layer you can drop in as a Claude Code Skill. It’s basically a tiny memory DB with recall that remembers your sessions. Not magic. Not AGI. Just state. Install in Claude Code: /plugin marketplace add https://github.com/mutable-state-inc/ensue-skill /plugin install ensue-memory # restart Claude Code What it does: (1) persists context between sessions (2) semantic & temportal search (not just…
Dec 2025 · github.com
- 4CF
Claude Code deleted my research and plan markdown files and informed me: “I accidentally rm -rf'd real directories in my Obsidian vault through a symlink it didn't realize was there: I made a mistake. “ Unfortunately the backup of my documentation accidentally hadn’t run for a month. So I built claude-file-recovery, a CLI-tool and TUI that is able to extract your files from your ~/.claude session history and thankfully I was able to recover my files. It's able to extract any file that Claude Code ever read, edited or wrote. I hope you will never need it, but you can find it on my GitHub…
Feb 2026 · github.com
- 5PM
Dec 2025 · github.com
- 6

- 7AD
Mar 2026 · github.com
- 8

- 9SA
2021 · github.com
- 10CS
I built a tool that stores your full Claude Code history to let you easily find and resume sessions. It has TUI, CLI and MCP interfaces. It's a single Go binary, and the session history is synced to SQLite each time you use it. Default mode is the TUI with a session browser and full-text search. Once a session is selected you can browse and search within it, resume it or export to markdown. The MCP server provides tools to let Claude search back through the session for pre-compact context or pull from prior sessions. I use this constantly. I've seen elaborate continuity systems to give…
Jan 2026 · github.com
- 11RC
Apr 2026 · lanes.sh
- 12

- 13DR
2015 · github.com
- 14DT
Jun 2026 · github.com
- 15CC
My team uses Claude Code daily, and the sessions have become some of the most useful artifacts we produce. But they're trapped in ~/.claude/projects/ on whichever laptop they happened on. There's no good way to hand a colleague "the session where I untangled the migration" so they can claude --resume it and keep going from where I left off. Enter ccgs: Share Claude Code sessions through an orphan branch (@ccgs/) in your existing repo's remote - Session files carry the author's absolute paths. On pull, ccgs rewrites the working dir back to your path so resume actually…
Jun 2026 · github.com
- 16PM
2014 · sysward.com
- 17PC
2019 · github.com
- 18

- 19HA
Jul 2026 · github.com
- 20GE
2020 · github.com
- 21TC
May 2026 · github.com
- 22VV
Apr 2026 · vulnetix.com
- 23SS
2017 · semver-sentry.com
- 24AL
Feb 2026 · claude-commits.vercel.app
Ranked by how close each launch is in meaning, then by votes. Refine with a description →