Vouch AI (@vouch_dev) header
Vouch AI (@vouch_dev) profile picture

The memory your agent has to earn. Agents propose → humans approve → the wiki compounds. Local-first 0x9439250e6e4effbbb016407f5a0bd105b7282b13

Joined November 2026
Photo by Vouch AI (@vouch_dev)Photo by Vouch AI (@vouch_dev)Photo by Vouch AI (@vouch_dev)Photo by Vouch AI (@vouch_dev)Photo by Vouch AI (@vouch_dev)Photo by Vouch AI (@vouch_dev)Photo by Vouch AI (@vouch_dev)Photo by Vouch AI (@vouch_dev)Photo by Vouch AI (@vouch_dev)Photo by Vouch AI (@vouch_dev)
The memory your agent has to earn. Agents propose → you approve → it compiles into a wiki in your repo. Works with Claude Code, Cursor, Codex, Windsurf $VOUCH is live now CA : 0x9439250e6e4effbbb016407f5a0bd105b7282b13
29
1
37
1,306
If vouch saved your agent even one re-investigation this month, a ⭐ helps the next developer find it. github.com/vouchdev/vouch Thanks for building with us. More soon.
11
14
155
Your agent learns something. Your teammate's agent learns something else. With vouch, both go through one review gate into one .vouch/ folder in the repo. git pull, and everyone's agent knows what the team approved.
10
15
147
A claim is only as good as its evidence. vouch content-hashes every source when it's cited. If that file changes later, the claims built on it get flagged instead of silently going stale. No evidence, no claim.
3
5
171
Monday: your agent burns turn after turn figuring out how auth works. Tuesday: it does it all over again. With vouch, Monday's finding becomes a claim, you approve it, and Tuesday's session starts knowing. vouchai.dev
12
1
12
360
Knowledge goes stale. The question is what happens next. In vouch: → supersede: a newer claim replaces the old one → contradict: conflicting claims get flagged → archive: no longer true, kept for history Every transition is reviewed and audited.
3
1
6
296
The most dangerous line in your agent's memory is the one nobody reviewed. It looks like a fact. It gets recalled every session. And it's wrong.
6
7
256
Your agent's knowledge shouldn't live in a database you can't open. In vouch it's YAML + markdown in .vouch/, right in your repo. Open it in Obsidian. Grep it. Diff it. Review it in a PR. No export button needed.
2
122
Start reviewing what your agent knows. pipx install vouch-kb → vouchai.dev ★ github.com/vouchdev/vouch agents propose · humans approve · the wiki compounds
2
70
Agents should not start every session with amnesia. But they shouldn't get to write whatever they want either. The middle ground is a PR queue for claimed knowledge.
1
71
Pages are the product. The LLM drafts wiki pages from approved claims. Citations are machine-verified before you review. Knowledge you can read, diff and open in your editor, not a black-box vector store.
3
5
133
Sessions start knowing. A SessionStart hook injects the approved digest: reviewed, cited, durable. Need more? kb.context serves cited context on demand. No amnesia. No unreviewed guesses.
2
3
113
Your knowledge, as a graph you can audit. Claims, sources, entities and pages, linked by typed, human-reviewed edges: cites, about, compiles, supersedes. Not co-occurrence guesses. Relationships someone actually approved.
2
1
163
Every decision, newest first. Approve. Reject. Supersede. Each one is committed to an append-only audit log, with who claimed it and who signed off. Six months from now, "why does the agent believe this?" has an answer.
2
2
192
One knowledge base. Every agent. Claude Code, Cursor, Codex, Windsurf, Zed, Cline, OpenClaw. MCP, JSONL or CLI, it all goes through the same review gate. Switch agents, keep what they learned.
1
183
Same bug-fix task, with and without vouch: ⏱ 111.9s → 92.9s 🔁 16.5 → 11.3 agent turns 💸 $0.402 → $0.330 per run Every number ships with its reproduction. Don't trust us, run it. vouchai.dev
137