Vibe Provenance

Continuity for vibe coding.
Capture what you were trying to do, what landed, and why each file exists — then hand that context to the next Cursor agent chat. Local-first. No extra LLM call for the brief.

First win (about 5 minutes)

npm install -g vibe-provenance
cd your-project
vibe-provenance init
vibe-provenance doctor

1. Cursor → Settings → Hooks — enable Hooks
2. Cursor → Settings → MCP — enable vibe-provenance
3. Open a new Agent chat and make a real code change
4. Open another Agent chat

Expected: the new chat has a short brief with Goal / Done / Next (and MCP brief / why work).

If why says “No provenance yet”, Hooks aren’t seeing edits yet — finish steps 1–3.

Who it’s for

You vibe-code in Cursor. Chats get long. Context resets. You open a new agent and it reinvents architecture you already shipped.

Vibe Provenance closes that gap with a structured handoff (Goal / Done / Open / Next / Files) plus file-level provenance (why) and session search (recall).

How this differs from Cursor

Cursor is great inside one chat (context, rules, memories, codebase reads).
Vibe Provenance is the session → next session layer: a local, inspectable handoff plus why this file exists from your vibe work — not opaque model memory.

Use both. Cursor runs the agent; Vibe Provenance remembers the arc.

Everyday use

| You want… | Do this | | --- | --- | | Resume work cleanly | New agent chat, or MCP brief | | Know why a file exists | MCP why or vibe-provenance why src/foo.ts | | Find what you tried before | MCP recall or vibe-provenance recall "auth hooks" | | Mark “this feels right” | vibe-provenance snapshot "auth flow feels right" | | Clean a noisy brief | vibe-provenance compact |

Docs

| Guide | What’s inside | | --- | --- | | Getting started | Install, init, first successful loop | | How it works | Brief, chapters, pins, snapshots, store layout | | CLI reference | Every command with examples | | MCP tools | What agents should call and when | | Privacy | What’s stored locally, secrets, gitignore | | Troubleshooting | MCP missing, empty brief, doctor failures | | Changelog | What changed by version |

Privacy in one line

Everything stays in your project under .vibe/. The core loop does not phone home. Secrets are scrubbed from captured text.

Links

• npm: vibe-provenance
• Source: github.com/wholmes/vibe-provenance
• Releases: GitHub Releases

MIT © Whittfield Holmes