Retention Target System: auto-GC low-retention memories during consolidation (VESTIGE_RETENTION_TARGET env var, default 0.8). Auto-Promote: memories accessed 3+ times in 24h get frequency-dependent potentiation. Waking SWR Tagging: promoted memories get preferential 70/30 dream replay. Improved Consolidation Scheduler: triggers on 6h staleness or 2h active use. New tools: memory_health (retention dashboard with distribution buckets, trend tracking, recommendations) and memory_graph (subgraph export with Fruchterman-Reingold force-directed layout, up to 200 nodes). Dream connections now persist to database via save_connection(), enabling memory_graph traversal. Schema Migration V8 adds waking_tag, utility_score, times_retrieved/useful columns and retention_snapshots table. 21 MCP tools. v1.9.1 fixes: ConnectionRecord export, UTF-8 safe truncation, link_type normalization, utility_score clamping, only-new-connections persistence, 70/30 split capacity fill, nonexistent center_id error handling. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
3 KiB
Windsurf
Give Cascade a brain that remembers between sessions.
Windsurf has native MCP support through its Cascade AI. Add Vestige and Cascade remembers your architecture, preferences, and past decisions across every session.
Setup
1. Open the config file
Option A — Via UI:
- Open Windsurf > Settings > Advanced Settings
- Scroll to the "Cascade" section
- Click "view the raw JSON config file"
Option B — Direct path:
| Platform | Path |
|---|---|
| macOS / Linux | ~/.codeium/windsurf/mcp_config.json |
| Windows | %USERPROFILE%\.codeium\windsurf\mcp_config.json |
# macOS / Linux
open -e ~/.codeium/windsurf/mcp_config.json
2. Add Vestige
{
"mcpServers": {
"vestige": {
"command": "/usr/local/bin/vestige-mcp",
"args": [],
"env": {}
}
}
}
With environment variable expansion (Windsurf-specific feature):
{
"mcpServers": {
"vestige": {
"command": "${env:HOME}/.cargo/bin/vestige-mcp",
"args": [],
"env": {}
}
}
}
Windows:
{
"mcpServers": {
"vestige": {
"command": "C:\\Users\\you\\.cargo\\bin\\vestige-mcp.exe",
"args": [],
"env": {}
}
}
}
3. Restart Windsurf
Restart the IDE or refresh the Cascade panel.
4. Verify
Open Cascade and ask:
"What MCP tools do you have?"
You should see Vestige's tools listed.
First Use
In Cascade:
"Remember that this project uses Next.js 15 with the App Router and Drizzle ORM"
Start a new Cascade session, then:
"What framework does this project use?"
It remembers.
Project-Specific Memory
{
"mcpServers": {
"vestige": {
"command": "/usr/local/bin/vestige-mcp",
"args": ["--data-dir", "${env:HOME}/projects/my-app/.vestige"],
"env": {}
}
}
}
Important: Tool Limit
Windsurf has a hard cap of 100 tools across all MCP servers. Vestige uses 19 tools, leaving plenty of room for other servers.
Troubleshooting
Vestige not appearing in Cascade
- Verify the config file is valid JSON:
cat ~/.codeium/windsurf/mcp_config.json | python3 -m json.tool - Ensure you're using absolute paths (or
${env:HOME}expansion). - Check the Cascade panel for error messages.
- Fully restart Windsurf.
Tool limit exceeded
If you have many MCP servers and exceed 100 total tools, Cascade will ignore excess servers. Remove unused servers or use Vestige's unified tools (each handles multiple operations).
Also Works With
| IDE | Guide |
|---|---|
| Xcode 26.3 | Setup |
| Cursor | Setup |
| VS Code (Copilot) | Setup |
| JetBrains | Setup |
| Claude Code | Setup |
| Claude Desktop | Setup |
Your AI remembers everything, everywhere.