$git clone https://github.com/samvallad33/vestigeLocal-first long-term memory for AI agents, delivered over MCP. Vestige remembers your decisions, catches contradictions before they cost you, and traces a failure back to the older memory that actually caused it. One 25MB Rust binary. No cloud. Your data never leaves your machin
| 1 | # Vestige |
| 2 | |
| 3 | Local-first long-term memory for AI agents, delivered over MCP. Vestige remembers your decisions, catches contradictions before they cost you, and traces a failure back to the older memory that actually caused it. One 25MB Rust binary. No cloud. Your data never leaves your machine. |
| 4 | |
| 5 | [](https://github.com/samvallad33/vestige/releases/latest) |
| 6 | [](https://github.com/samvallad33/vestige/actions) |
| 7 | [](https://github.com/samvallad33/vestige/releases/latest) |
| 8 | [](LICENSE) |
| 9 | |
| 10 | [What it is](#what-vestige-is) · [Install](#install) · [First interaction](#your-first-real-interaction) · [vs RAG](#how-it-differs-from-rag) · [Backward reach](#backward-reach-the-backfill-feature) · [Benchmark](#silent-rotation-a-reproducible-benchmark) · [Science](#the-science) · [Tools](#the-13-tools) · [Dashboard](#the-dashboard) · [Integrations](#works-with-every-agent) · [Docs](#go-deeper) |
| 11 | |
| 12 | --- |
| 13 | |
| 14 | ## What Vestige is |
| 15 | |
| 16 | Hi, I'm [Sam](https://github.com/samvallad33). I built Vestige because my agents kept re-learning the same lessons. They would recommend a change I had already tested and rejected, re-derive a fix that was already written down, and treat every session as if the last one never happened. |
| 17 | |
| 18 | Vestige is the memory layer that fixes that. It runs locally as an MCP server, so any MCP-capable agent (Claude Code, Claude Desktop, Codex, Cursor, and others) can write memories during a session and retrieve them later. Your data lives in a SQLite file on your own machine. After a one-time model download it works fully offline, with no API keys and no telemetry. |
| 19 | |
| 20 | The part that makes it more than a note store: Vestige models memory on real cognitive science. It merges what is redundant, supersedes what is contradicted, keeps what you actually use, and lets unused memories fade. Most importantly, when a failure hits it can reach backward to the earlier decision that caused it, even when the cause and the symptom share no vocabulary. The cause never looks like the bug. |
| 21 | |
| 22 | --- |
| 23 | |
| 24 | ## Install |
| 25 | |
| 26 | Three steps. You need Node.js installed (for the npm command) and nothing else. |
| 27 | |
| 28 | ### 1. Install the server |
| 29 | |
| 30 | No Docker, no API key, no signup. |
| 31 | |
| 32 | ```bash |
| 33 | npm install -g vestige-mcp-server@latest |
| 34 | ``` |
| 35 | |
| 36 | This installs the `vestige-mcp` command. Prebuilt binaries ship for macOS (Apple Silicon and Intel), Linux x86_64, and Windows x86_64, so there is no compile step. |
| 37 | |
| 38 | ### 2. Connect it to your agent |
| 39 | |
| 40 | Vestige speaks [MCP](https://modelcontextprotocol.io), so it works with any MCP-capable agent. Every MCP client understands this config. Add it to your client's MCP settings: |
| 41 | |
| 42 | ```json |
| 43 | { |
| 44 | "mcpServers": { |
| 45 | "vestige": { |
| 46 | "command": "vestige-mcp" |
| 47 | } |
| 48 | } |
| 49 | } |
| 50 | ``` |
| 51 | |
| 52 | If you prefer the CLI, use the one-line shortcut for your agent: |
| 53 | |
| 54 | | Agent | Setup | |
| 55 | |---|---| |
| 56 | | Claude Code | `claude mcp add vestige vestige-mcp -s user` | |
| 57 | | Codex | `codex mcp add vestige -- vestige-mcp` | |
| 58 | | Cursor / VS Code / Windsurf | add the JSON above to the editor's MCP settings, or see [docs/integrations/](docs/integrations/) | |
| 59 | | Cline / Continue / Zed / Goose | add the JSON above to that client's MCP config | |
| 60 | | Claude Desktop | [docs/CONFIGURATION.md#claude-desktop-macos](docs/CONFIGURATION.md#claude-desktop-macos) | |
| 61 | |
| 62 | ### 3. Verify |
| 63 | |
| 64 | On first run, Vestige downloads its embedding model once (about 130MB). After that it never needs the network again. To confirm the server is healthy, open the dashboard: |
| 65 | |
| 66 | ```bash |
| 67 | vestige dashboard |
| 68 | ``` |
| 69 | |
| 70 | Then visit **http://localhost:3927/dashboard**. If you see the graph, you are connected. For a fuller walkthrough see [docs/GETTING-STARTED.md](docs/GETTING-STARTED.md). |
| 71 | |
| 72 | --- |
| 73 | |
| 74 | ## Your first real interaction |
| 75 | |
| 76 | Memories go in as you work. The interesting behavior shows up when a new claim conflicts with some |