sessionwiki

sessionwiki

Your AI coding sessions, compiled into a searchable, interlinked wiki — from Claude Code, Codex CLI, Cursor, Gemini CLI, Copilot, ZCode and OpenCode. Local-first, with LLM synthesis, a session graph, and an MCP server so your agents can look up what you already solved.

👉 Live demo: necroz.github.io/sessionwiki

27 synthetic sessions across five projects and seven agents (Aug–Nov 2026) — no personal data. Rebuilt from examples/demo-sessions/ on every push to master.

---

Why

Every agent you work with writes a full transcript to disk: the plan, the dead ends, the fix, the reasoning behind it. Hundreds of them, in five different formats, and you never look at them again.

sessionwiki turns that history into a knowledge base:

• One place for every agent. Claude Code, Codex CLI, Cursor, Gemini CLI, Copilot, ZCode and OpenCode sessions land in the same wiki, tagged by agent, project, model and date.
• Always current. Hooks, an OpenCode plugin and nightly timers keep it in sync without you running anything.
• Readable. LLM synthesis writes a summary page per session; low-signal sessions are folded into cluster pages instead of cluttering the wiki.
• Usable by your agents. A built-in MCP server lets Claude Code, ZCode or any MCP client search past decisions before redoing them.
• Yours. Everything runs locally; transcripts are redacted on the way in, and sessionwiki audit checks the output before you publish anything.

Already using Claude Code's built-in memory, claude-mem or a session search tool? The FAQ explains what sessionwiki adds — and when another tool is the better choice.

Highlights

Screenshots

All screenshots come from the live demo and are regenerated with scripts/regen_docs_screenshots.py.

Every session, every agent — filter by project, model and date; each row carries its agent badge.

Session pages — the summary, the conversation, highlighted code and the tools that ran, plus token and cache usage.

Projects — topics, description, activity and tool usage per project, with freshness badges on the index.

Graph and search — sessions grouped around their projects; ⌘K searches every page instantly.

Quick start

git clone https://github.com/necroz/sessionwiki.git

cd sessionwiki ./setup.sh # Windows: setup.bat — creates .venv, detects your agents ./sync.sh # convert new sessions into raw/ ./build.sh && ./serve.sh # build the site and open http://127.0.0.1:8765

setup creates a checkout-local .venv, installs the package, scaffolds raw/, wiki/, site/, enables the adapters for the agents it finds and runs sessionwiki doctor. The wrapper scripts use the venv automatically; for the CLI, activate it (source .venv/bin/activate) or call .venv/bin/sessionwiki.

Or install the published package — pick one:

uv tool install sessionwiki          # uv: CLI in its own isolated environment

uvx sessionwiki --help # uv: run without installing pip install sessionwiki # pip, inside a virtualenv pip install 'sessionwiki[graph]' # + graphify graph engine (also works with uv tool install)

Docker — serve a site you have built (image ghcr.io/necroz/sessionwiki, see Docker deployment for docker compose and running CLI commands in the container):

docker run --rm -p 8765:8765 -v "$PWD/site:/wiki/site:ro" ghcr.io/necroz/sessionwiki

A step-by-step walkthrough with screenshots lives in the setup guide.

Connect your agents

Claude Code, Codex CLI, Cursor, Gemini CLI, Copilot — read straight from their session folders on sessionwiki sync. To sync after every Claude Code reply, add a Stop hook to ~/.claude/settings.json:

{

"hooks": { "Stop": [{ "hooks": [{ "type": "command", "command": "cd /path/to/sessionwiki && .venv/bin/python -m sessionwiki sync --no-auto-build >/dev/null 2>&1 &" }] }] } }

Parallel hook runs are safe: sync and synthesize take an OS file lock and write their state atomically.

To add related past work to every prompt, opt in to a UserPromptSubmit hook — it is off unless SESSIONWIKI_PROMPT_RECALL=1 is set. It injects up to three related pages plus up to three approved lessons (wiki/lessons/, lifecycle reviewed or verified); draft lessons never reach the prompt:

{

"hooks": { "UserPromptSubmit": [{ "hooks": [{ "type": "command", "timeout": 10, "command": "cd /path/to/sessionwiki && SESSIONWIKI_PROMPT_RECALL=1 .venv/bin/python -m sessionwiki recall --prompt-hook" }] }] } }

Cost: two wiki scans per prompt (pages, then lessons). A single scan measured a median of 170 ms with three pages returned, 140 ms when nothing matches (before lessons landed).

ZCode keeps sessions in SQLite. sessionwiki exports them read-only and installs the hook and a nightly job for you:

sessionwiki zcode install --dry-run   # show what will be written

sessionwiki zcode install # Stop + SessionStart hooks, systemd / launchd / Task Scheduler

OpenCode (V2, opencode.db) gets a server plugin that runs autosync when a session goes idle:

sessionwiki opencode install --dry-run

sessionwiki opencode install # honours $XDG_CONFIG_HOME

Hook-triggered runs skip instead of queueing when a cycle is already running; scheduled runs wait and catch up. Details: ZCODE.md, docs/adapters/opencode.md, and sessionwiki adapters for the full list.

LLM synthesis

sync fills raw/ with redacted transcripts. synthesize turns them into wiki pages: a summary per session, project pages, cross-links. Point it at any backend in config.local.json:

{

"synthesis": { "backend": "openai", "base_url": "http://127.0.0.1:8000/v1", "model": "qwen3-coder", "max_concurrency": 8, "coalesce_low_signal": true } }

sessionwiki synthesize --estimate     # what it will cost before you run it

sessionwiki synthesize # new sessions only; idempotent sessionwiki all --with-synth # synthesize → build → graph → export → lint

Backends: extractive (the default — no model and no network: a useful page from the transcript itself), ollama (local), openai (any OpenAI-compatible /v1: vLLM, SGLang, LM Studio, LiteLLM, hosted APIs), agent-delegate (let your coding agent write the pages), dummy (offline metadata stubs). sessionwiki warns when a non-loopback base_url would send transcripts off your machine. See docs/modes/api/.

Ask your wiki from your agents (MCP)

Claude Code plugin — the MCP server, a skill that tells the agent when to search the wiki, and a SessionStart hook that puts the project's recent sessions into context. It asks for your sessionwiki folder on install:

/plugin marketplace add necroz/sessionwiki

/plugin install sessionwiki@sessionwiki

Any MCP client — run the published package with uvx, and point SESSIONWIKI_HOME at the folder that holds raw/ and wiki/ (run sessionwiki sync there first):

{

"mcpServers": { "sessionwiki": { "command": "uvx", "args": ["sessionwiki", "mcp"], "env": { "SESSIONWIKI_HOME": "/path/to/your/sessionwiki" } } } }

From a source checkout, use "command": "/path/to/sessionwiki/.venv/bin/sessionwiki" with "args": ["mcp"]; the checkout is the data root, so no env is needed.

Add it to Claude Code, Claude Desktop, ZCode or any MCP client. Tools include wiki_query (ranked search over wiki pages in any language, falling back to raw transcripts), wiki_search (exact text, optionally over raw transcripts), wiki_read_page, wiki_list_sources, wiki_lint, wiki_sync, wiki_export, wiki_dashboard an