About Vestige
Vestige provides AI agents with an auditable memory log and a guard that checks tool calls before execution. Its memory links related facts over time and traces recorded causes, while Operator Lite blocks or records risky actions.
Key features
- 01Append-only memory log with receipts
- 02Retroactive surfacing of relevant memories
- 03Trace causes through recorded links
- 04Block or log risky tool calls
- 0530 guard rules across stop and review actions
Use cases
- 01Recall an older fact after new context makes it relevant
- 02Trace a failure back through recorded links
- 03Prevent an agent from force-pushing or deleting data
- 04Review tool calls flagged by the guard
MCP support
Vestige supports MCP setup for connecting its memory to clients. The README also lists client-specific setup routes for its memory and guard.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project README
Vestige
Memory your AI can prove. A guard that stops it before it breaks things.
Vestige gives AI agents a memory that gets sharper over time, and a guard that checks your agent's tool calls before they run. Every memory has a receipt. Every stop has a reason. Nothing is guessed.
Quick start
- Install the binaries (macOS and Linux), or download them for your platform from Releases:
curl -fsSL https://raw.githubusercontent.com/samvallad33/vestige/main/scripts/install.sh | sh - Run
npx @vestige/init, choose Memory or Memory plus guard, and confirm. - Restart your AI client, then say: "Tell me something about a friend." Ask about them later.
It remembers what matters
Save "Maya felt off after dinner at Bangkok Garden." Later, save "Maya has a peanut allergy."
Vestige sees that both memories are about Maya and raises the older one. When your agent plans Maya's birthday dinner, that dinner comes up first.
This is Retroactive Salience Backfill: when something new makes an old memory matter, Vestige brings it back. It runs on every save, records every change it makes, and any change can be undone. How Backfill works.
It proves what it knows
Memory lives in Strata, an append-only log. Every write passes a gate and returns a receipt. A memory is found by its exact id or tag, never by a lookalike.
When something breaks, causal_walk follows the recorded links backward to the cause. Point gather at a GitHub issue and it walks back from there.
It stops what you never approved
Operator Lite is a free guard for your agent's tool calls. It stops force pushes, dropped tables, recursive deletes and production deploys before they run, even when the command is disguised. 30 rules: 15 stop the call, 15 record it for you to review.
curl -fsSL https://raw.githubusercontent.com/samvallad33/vestige/main/operator-lite/operator-gate.py -o /tmp/operator-gate.py && python3 /tmp/operator-gate.py install
Install replays your last 30 days of agent history and shows what it would have stopped. Nothing in that history is run. Windows, OpenClaw, and every claim checked on your machine.
Vestige Operator
The owner's version of the guard. Write your own laws, see a Board of today's stops, and get a weekly Letter of what your agents tried. $149 once, every future version included.
Works with
| Memory | Guard | |
|---|---|---|
| Claude Code | npx @vestige/init | Install |
| Codex | Guide | |
| Cursor | Guide | Port |
| VS Code + Copilot | Guide | |
| OpenCode | Guide | Port |
| Windsurf | Guide | Port |
| Gemini CLI | npx @vestige/init | Port |
| Xcode | Guide | |
| JetBrains / Junie | Guide | |
| Anything else | MCP setup | All ports |
Docs
What's new in v5 · Installer guide · Getting Started · Tool contracts · Configuration · Storage · Reference · Changelog
License
AGPL-3.0-only.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.
