For ZCode

Every ZCode session, searchable from one box.

ZCode keeps your sessions on your machine — which is great for privacy, and terrible for finding anything. LLMnesia indexes your ZCode prompts and replies locally into one search, alongside your Claude Code and Codex sessions and your web AI chats. Want ZCode itself to search this history for you? See the free MCP connection.

No account. No cloud. Your sessions stay on your device.

Set up in a minute

Two ways to get your sessions in.

Option A

Index your ZCode sessions

Your ZCode history lives on this machine, under ~/.zcode — not on a server. LLMnesia reads the sessions already there and indexes your prompts and the assistant’s replies, so everything you’ve worked through becomes searchable in one click.

Best if you want your existing ZCode history searchable.

Option B

Bring everything else in

The same search also covers your local Claude Code and Codex sessions, plus ChatGPT, Claude, Gemini and 10+ web AI platforms — so one box spans every AI conversation you have, wherever it happened.

Best if you work across more than one AI tool.

What a result looks like

Find the session, get the context.

Search a phrase you remember — a function name, an error, a decision you talked through. Every match shows which project it came from and reads like a clean transcript: what you asked, and what the assistant answered. Then bring the context straight back into ZCode — connect the free MCP link and ask ZCode itself.

refresh token race condition

Fix flaky auth test

ZCode

“…the fix was awaiting the refresh before the test’s first request — the race condition was in the token refresh, not the mock clock…”

~/projects/api-server·desktop·18 Jul 2026

Token refresh retry follow-up

ZCode

“…the token refresh only raced when the fake clock drifted, so the retry test flaked every few runs…”

~/projects/billing-worker·desktop·2 Sep 2026

Good to know

The essentials.

Which ZCode sessions does it index?

The ZCode sessions on this machine — every conversation you’ve had in ZCode, across all of your projects. ZCode keeps them locally under ~/.zcode, and LLMnesia reads that history so a single search covers all of it.

What exactly gets indexed?

Only your prompts and the assistant’s replies. Subagent runs, shell commands, and tool output are never stored, so search results read like a clean transcript, not raw logs. That index lives in your browser’s local storage and is never uploaded anywhere.

Does anything leave my device?

Your sessions, prompts, replies, and search index never do — they stay in local browser storage, full stop. LLMnesia does send limited, anonymized product analytics to PostHog (extension version, which features you use, error categories, an anonymous install ID) so we can fix bugs and see what’s useful. It never includes conversation content, prompts, replies, or search queries. Full detail in the privacy policy.

Can ZCode itself search this history?

Yes. The free MCP connection lets ZCode search your indexed history locally — ask “what did we decide about the auth refactor?” and it answers from your past conversations, with links back to the sources. Setup configures ZCode’s MCP settings for you. See the MCP connection.

Does it work with Claude Code and Codex too?

Yes. Local Claude Code and Codex sessions are indexed into the same search, alongside your web AI chats — so your terminal sessions and browser chats are covered by one box, not a separate tool for each.

Stop losing track of what you built in ZCode.

Install LLMnesia, index your sessions, and search every ZCode conversation — alongside your Claude Code, Codex, and web chats — from one box. Free, local, no account.