Sessionwiki

English · 한국어

sessionwiki turns the sessions your AI coding tools already wrote to disk into one durable history you can read, search, and trace — every file back to the conversation that wrote it, and nothing lost when a tool prunes the original. Every tool at once. No daemon, no cloud, no logging habit to build — it works retroactively over the history you already have.

That is one real machine. Run it on yours — the number is usually a surprise. That conversation where Claude fixed your CORS bug three weeks ago is still on your disk, you just can't find it: each tool writes its sessions in its own format and folder, on every machine you use, and after a few months that is thousands of solved problems with no way back to any of them.

What you can do with it

- Trace a file back to the conversations that wrote it — the link between your code and your sessions, across every tool, retroactively.
- Blame a line back to the session behind it — git blame for the AI era; best-effort, falls back to file-level trace.
- Keep every session — archived when a tool prunes it, so search and trace never go dark; delete the bulky originals and still search them.
- Read & resume any session — reopen it in its original tool, or brief it into another.
- Search every message of every tool at once — substring + CJK, zero setup.
- Curate — tag, note, jump to related sessions, and see where your agent time goes.

And a web UI for reading and browsing, not just grepping — live search, rendered transcripts, and each session's files as clickable provenance chips. sessionwiki web:

Install

npm (macOS / Linux / Windows; you likely have Node already if you use
Claude Code or Codex):

On macOS this is the install to prefer: npm…