sessionwiki session recall

 

That conversation where Claude fixed your CORS bug three weeks ago? It is still on your disk — you just can't find it. Every AI coding agent writes its sessions to disk: each tool in its own format, in its own folder, on every machine you use. After a few months that is thousands of conversations full of solved problems, and no way to get back to any of them.

sessionwiki reads the traces your tools already leave and turns them into one searchable, linkable archive you can actually maintain. No daemon, no logging habit to build, no cloud. It indexes what is already there, then lets you tag it, link it, and pick up where you left off.

$ sessionwiki scan
TOOL            SESSIONS       SIZE  OLDEST       NEWEST        PATH
claude-code         1763     1.1 GB  2026-03-27   2026-06-12    ~/.claude/projects
codex               2340    45.9 GB  2025-08-21   2026-06-12    ~/.codex/sessions
gemini                50     1.2 MB  2026-04-02   2026-06-10    ~/.gemini/tmp

4153 sessions across 3 tools, 47.0 GB on disk.

That is one real machine. Run it on yours — the number is usually a surprise.

What you can do with it

• Find every session store on the machine: which tools, where, how many, how big — instant.
• Search every message of every tool at once. Substring matching, so partial identifiers and CJK text work with zero language setup.
• Read any session as a clean transcript: rendered code blocks, collapsed tool calls, an outline of long sessions.
• Summarize sessions into cached one-line synopses using your own LLM CLI — then never wonder "what was this one about" again.
• Resume a session in its original tool, in the right project directory, with one command.
• Carry context across tools: brief a Claude Code session into Codex, or anywhere else.
• Trace a file back to the sessions that edited it — trace src/auth.rs lists the AI conversations behind a file, across every tool. The link between your sessions and the code they produced. See provenance.
• Keep what your tools delete — sessions are archived when the tool prunes them, so search and trace never go dark on old work.
• Curate and connect: tag and annotate sessions, jump to related ones, and see where your agent time goes — session engineering, not just search.

And a web UI when you would rather read than grep — sessionwiki web: