// Threadbase turns raw AI session files on your disk into a searchable, navigable knowledge base — across desktop, IDE, and terminal.
Recovery flow
1
Decode JSONL
2
Inspect structure
3
Search sessions
4
Resume thread
Recovery flow
Decode JSONL
Inspect structure
Search sessions
Resume thread
Decoding local session history
session_014.jsonl
Claude keeps the truth on disk, but not in a format you want to browse under pressure.
▋
Every Claude Code session lives as a JSONL file in ~/.claude/projects/. After a few weeks of active use, you have hundreds of them with no practical way to find anything.
Opening a session file in a text editor gives you a wall of escaped JSON where tool calls, diffs, and terminal output all blur together.
You solved this exact problem a few weeks ago, but without a way to search the history, the path back to that solution disappears.
Choose the surface that fits how you work. The archive stays local, searchable, and immediately usable.
Pick your environment to see a tailored experience.
IDE Extensions
Native history browser for your IDE
Search, browse, export, and resume the conversations that already contain your best debugging work.
Search every conversation, session name, and project with results that appear as you type.
Browse conversations grouped by project directory and sorted by recency with useful filters.
Read diffs, terminal output, file reads, and search results in specialized cards instead of raw JSON.
Index multiple Claude config directories side by side with profile-level usage and recency stats.
Export any conversation to Markdown, plain text, or JSON and copy individual messages cleanly.
The desktop app can relaunch or continue prior work without leaving the history browser.
cch brings full-text search and session browsing to the terminal with a fast, keyboard-driven interface.
Built to expand beyond Claude Code — same local-first approach, same searchable history, more AI tools soon.
Conversation Browser
Conversation Browser
Browse every Claude Code session grouped by project, sorted by recency, and framed by the context you need to resume work quickly.
[Screenshot: Conversation browser - project-grouped sidebar with searchable history list]
Full-Text Search
Full-Text Search
Search for an error, a function name, or a library and jump directly into the exact sessions where it appeared.
[Screenshot: Search results - query 'useEffect' showing matching sessions and snippets]
Tool Result Cards
Tool Result Cards
Read Claude's tool activity in the format it deserves, including diffs, bash output, and structured file operations.
[Screenshot: Tool result cards - unified diff and terminal output displayed side by side]
We'd rather you know this upfront than be disappointed after installing.
Currently Claude Code sessions only
This product is valuable if you use Claude Code seriously and want to mine your own local history.
Quality depends on your sessions
The better your existing sessions are, the more useful the archive becomes when you need to search and reuse them.
IDE plugins track IDE versions
Extensions need to keep up with host IDE release cycles, so compatibility matters on very new beta builds.
No cloud sync
History stays on disk by design. There is no hosted sync layer or remote storage abstraction.
Threadbase is expanding to support every major AI coding assistant. Your history. Your tools. Not locked to one.
Now
Month 1–2
Month 3–4
Month 5–6
One email when multi-assistant support lands. No spam.
No spam. One email when it's ready.
Desktop App
# 1. Clone and entercd claude-search# 2. Install dependenciespnpm install# 3. Run in dev modepnpm run dev# Or build a distributablepnpm run package