Your vibe-coding history, searchable.
VHDB keeps the conversations, decisions, errors, fixes, edits and commits of your coding sessions, and answers “Have we done this before?”, “Why did we decide this?” and “How did this file get its shape?”. Built from scratch in Rust, with no external database.
Search your history from inside Claude Code.
- # in a clone of vhdb-plugin
- >
claude --plugin-dir ~/vhdb-plugin - >
/vhdb:search token refresh kind:decision since:30d
Build the engine and search any ledger directory.
- >
cargo build --release - >
target/release/vhdb ingest "$L" - >
target/release/vhdb search "$L" token refresh since:30d
Warm p50 search
one common term over 1M synthetic events, release build
Full verification
every checksum of 1M events and 107 index files
Idle server memory
with 1.1M events open
Network code in the plugin
the Claude Code plugin is local only
Sessions end. The reasons shouldn’t.
In a long vibe-coding project the same questions come back every week. The answers are buried in old conversations. VHDB turns those conversations into something you — and Claude — can query.
Have we done this before?
Find past attempts, errors and the fix that closed them.
Why did we decide this?
Recover a decision together with its reason, and the decision it replaced.
How did this file get here?
A newest-first timeline of every turn that touched a file.
Pick a starting point.
How it works
The session log is the WAL. Immutable segments, atomic swaps, one engine in three places.
Read more →SmartWorkbench
Where the history comes from: task contracts, the guard, evidence and the decision ledger.
Read more →Claude Code plugin
Search, record, inject and guard from inside Claude Code. All off until you turn them on.
Read more →Search & performance
The query language, how results are ranked, and measured numbers with their conditions.
Read more →Install
Three steps to a first answer, the team server, and an honest list of limits.
Read more →Give your sessions a memory.
MIT licensed. Source on GitHub.