FAQ · STRAIGHT ANSWERS
If you’re evaluating this for real, these matter more than the feature list.
The Questions
No. Anvaya Mind runs as a local daemon and stores everything under .anvaya/mind/ inside your project, SQLite, an HNSW vector index, and an append-only temporal log. With the default Ollama provider, the entire loop runs on your machine and nothing is transmitted. The Anthropic, OpenAI, and Siemens providers exist only if you configure an API key yourself.
Yes, over MCP. Mind ships an MCP server (mind-mcp), so any MCP-capable client can query the same memory. A five-line .mcp.json in your project root exposes eight tools: mind_query, mind_search, mind_record_change, mind_get_node, mind_stats, mind_start_session, mind_end_session, mind_get_threads.
Four: Ollama (local, default, no API key), Anthropic, OpenAI, and Siemens. Ollama is first-class: embeddings, summarization, and generation all run locally with a pulled model like devstral.
A CLAUDE.md is flat text you maintain by hand, it grows, rots, and keeps asserting the old thing until someone edits it. Mind is a weighted, linked, decaying graph: nodes have types and half-lives, stale ones are detected against git drift, and only the relevant few are packed into each query's token budget.
No, and that's deliberate. The graph is project-local and tied to one machine. There is no cloud sync and no multi-machine replication, the files live in your repo's working tree, gitignored by default.
Mind is a Unix-socket daemon, so the supported surface today is Linux and macOS. The CLI builds from source with Rust 1.75+ and runs as a TUI or headless in CI.
Public beta launches in Q4 2026. Anvaya is pre-1.0 and unreleased, both halves build from source, and the changelog is a real build log. Pricing isn't set, but the core will stay local-first regardless of what the SaaS layer ends up looking like. Early access is open via the waitlist.
Claude Code uses CLAUDE.md, a flat markdown file you write and maintain by hand. It can grow large, it asserts stale information until someone edits it, and it doesn't learn which parts are actually useful. Anvaya Mind is a weighted, linked, decaying graph: nodes have types and half-lives, stale content is detected against git drift, and only the relevant few are packed into each query under a token budget. The key difference: Claude Code's memory is static. Anvaya's improves with use.
The memory graph is model-agnostic. It stores typed nodes, links, and utility scores, not model-specific embeddings. Switching from Ollama to Anthropic (or vice versa) doesn't invalidate the graph. The daemon continues using whatever embedding provider you configure.
Yes. The graph is files: SQLite in WAL mode, a flat HNSW index, an append-only temporal log, and plain-text config, all under .anvaya/mind/ in your project. You can open the SQLite database directly, query it, export to CSV, or back it up. There's no lock-in; the data format is documented and inspectable.
Glossary
Technical terms explained in plain language. Hover over abbreviations on other pages for quick definitions.
A statistical model that updates beliefs based on observed outcomes. In Anvaya, it scores whether each memory node actually helped the AI, nodes that are used get higher scores, unused ones decay.
Hierarchical Navigable Small World, a fast algorithm for approximate nearest-neighbor search. Anvaya uses it to find semantically similar memory nodes quickly, without scanning the entire graph.
Content-anchored checking against git history. When code changes, Anvaya detects which memory nodes are now stale and flags them for decay or removal.
The ratio of raw context size to the packed context Anvaya serves. Instead of feeding the AI 50K+ tokens of raw files, Anvaya selects the 2-4K most relevant tokens, a 12-25x compression.
One binary. 11+9 Rust crates. 545 tests. Hand-written HNSW index. Three transport modes. Four providers, Ollama, Anthropic, OpenAI, Siemens. Zero API keys required to start. Mind remembers everything after the first session.