Claude Desktop requests protocol version 2025-06-18 but Vestige was
responding with 2025-11-25, causing Claude Desktop to disconnect.
Now the server negotiates: if the client requests an older version,
use it. This maintains backward compatibility with older clients.
Fixes: Claude Desktop "Server transport closed unexpectedly" error
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Users were seeing 30 tools in /mcp which was overwhelming. Now only 8
essential tools are listed:
1. search - unified hybrid search
2. memory - get/delete/state operations
3. codebase - patterns and decisions
4. intention - prospective memory
5. ingest - add memories
6. smart_ingest - intelligent ingestion
7. promote_memory - thumbs up
8. demote_memory - thumbs down
Deprecated tools (recall, semantic_search, etc.) still work internally
for backward compatibility but are no longer listed.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Two distribution methods now available:
1. npm (for Claude Code / developers):
npm install -g vestige-mcp-server
claude mcp add vestige vestige-mcp -s user
2. MCPB (for Claude Desktop / one-click install):
Download vestige-1.1.0.mcpb from releases, double-click
Changes:
- Renamed npm package to vestige-mcp-server (vestige-mcp was taken)
- Fixed postinstall to download binaries from GitHub releases
- Added vestige-mcpb package with manifest and build script
- Uploaded .mcpb bundle to v1.1.0 release
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The npm package was missing the actual binary download step - users got
wrapper scripts pointing to non-existent binaries.
Changes:
- postinstall.js now downloads correct binary from GitHub releases
- Added vestige.js wrapper for CLI binary
- Exposed both vestige-mcp and vestige commands in package.json
- Updated README with troubleshooting, storage info, CLI docs
- Added .gitignore for downloaded binaries
Fixes fresh install issues where Claude Desktop couldn't attach and
vestige CLI wasn't found.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add -s user flag to claude mcp add commands for user scope install
- Correct fastembed cache location docs (.fastembed_cache in CWD, not ~/.cache/huggingface)
- Add troubleshooting section for .fastembed_cache folder in project directories
- Include FASTEMBED_CACHE_PATH env var workaround
Fixes issues reported by Reddit user feedback.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Drop problematic targets:
- x86_64-apple-darwin: No free Intel macOS runners after macos-13 retirement
- aarch64-unknown-linux-gnu: Cross-compile OpenSSL issues with vendored feature
Ship with 2 platforms that work reliably:
- aarch64-apple-darwin (macOS Apple Silicon)
- x86_64-unknown-linux-gnu (Linux x86_64)
Users on Intel Mac or ARM64 Linux can build from source with cargo.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Two-pronged fix for cross-compilation:
1. git2 with vendored-openssl feature - compiles OpenSSL from source,
eliminating system dependency issues across all platforms
2. houseabsolute/actions-rust-cross@v1 - dedicated GitHub Action that
properly handles cross-compilation with Docker containers
Sources:
- https://github.com/rust-lang/git2-rs
- https://github.com/houseabsolute/actions-rust-cross
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- macOS ARM64: macos-latest (Apple Silicon)
- macOS x86_64: macos-13 (Intel) - no cross-compilation
- Linux x86_64: ubuntu-latest with OpenSSL
- Linux ARM64: cross tool for proper Docker-based cross-compilation
Install OpenSSL via homebrew on macOS and set OPENSSL_DIR.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Cross-compilation for aarch64-unknown-linux-gnu requires OpenSSL
dev libraries for the target platform. Using `cross` handles this
automatically via Docker containers with pre-installed dependencies.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Document how to pin to specific versions
- List available versions (v1.0.0, v1.1.0)
- Add version check command
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Address common question: users don't need to disable Claude's native
memory to use Vestige. They're independent systems that can run
simultaneously.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Detail what causes data loss (delete, corrupt, lost device)
- Clarify "For AI memory = fine, For critical data = not fine"
- Add automated cron job backup example
- Mention Time Machine / Windows Backup as options
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Simple 4-step Quick Start (2 minutes)
- Global install instructions (sudo cp to /usr/local/bin)
- Claude Code and Claude Desktop config examples
- Full 29-tool reference with descriptions
- Prediction Error Gating section with visual diagram
- Troubleshooting section
- Updating instructions
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Replace BGE-base-en-v1.5 with nomic-embed-text-v1.5
- 8192 token context window (vs 512 for BGE)
- Matryoshka representation learning support
- Fully open source with training data released
- Same 768 dimensions, no schema changes required
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
FSRS-6 spaced repetition, spreading activation, synaptic tagging,
hippocampal indexing, and 130 years of memory research.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
