The Ecosystem · TWO BINARIES, ONE GRAPH
Two Tools.One Experience.
The CLI is an agent that executes. Mind is a daemon that learns, and over MCP it becomes an experience server for Claude Code and any MCP client. They’re separate binaries on purpose: run either one without the other, and Mind will happily serve a client that isn’t Anvaya at all.
The Split
Why Two Binaries.
A single static Rust binary, no runtime dependencies · 25.6 MB median RSS measured across 238 runs, 17x lighter than Claude Code · ~5 MB idle, ~12 ms to first TUI frame · 8 TUI screens · 21 native tools · 3 provider transports · headless mode.
Learn more →An experience store, not a document · SQLite graph + Int8 HNSW index · 6 node types with per-type decay · 9 background workers · 14 MCP tools · captures debugging sessions, domain knowledge and project history.
Learn more →Three Ways In, Same Graph.
Mind exposes the same memory through three transports. Which one you get depends on who is asking, and the cost difference between them is the difference between a function call and a protocol handshake.
Keep Your Agent. Add The Memory.
If you already work in Claude Code or another MCP client, you don’t have to adopt the CLI to get the memory. Point the client at Anvaya’s MCP server and fourteen memory tools appear inside the agent you already trust.
Setup is a five-line .mcp.json in your project root, see Get Started →
Run Agents That Fit On Your Laptop.
25.6 MB median RSS. 25 agents ran in parallel on a Core 2 Duo with 4 GB RAM. Hundreds on your machine. Zero cloud required on the Ollama path.
Requires Rust/cargo to build from source. Linux and macOS today, Windows not yet supported. Pre-1.0, public beta. Pricing TBD.