Q
Which model for daily work?
The largest tool-calling local model that stays responsive on your hardware. Reserve frontier APIs for refactors that earn the spend.
Docs · Providers & Models
Providers & Models.
Local default, frontier on demand.
Direct answer
Four providers: Ollama (local, default, no key), Anthropic, OpenAI, and custom OpenAI-compatible gateways (Siemens and self-hosted endpoints included). Global config at ~/.anvaya/config.json, per-project overrides in .anvaya/config.json, secrets in credentials.json plus environment. Memory is model-agnostic — switching providers never invalidates the graph.
Providers & Models
Providers
01Ollama · defaultEmbeddings, summarization, generation — all local. Devstral default; any tool-calling coder with 32K+ context works. Fully offline after one pull.
02Anthropic · escalateFrontier reasoning for the hardest refactors. Configure a key; per-task model pick keeps spend deliberate.
03OpenAI · interoperateGPT-family reasoning inside Anvaya's memory loop. Same graph, different engine.
04Custom gateways · enterpriseData-driven provider defs without rebuilding — corporate gateways (Siemens pattern included), self-hosted endpoints, per-team routing.
Questions
Asked About Providers & Models.
Q
Does switching models wipe memory?
No. The graph stores typed nodes, links, and utility — not model-specific embeddings. Swap freely.
Q
How do credentials work?
~/.anvaya/credentials.json plus env (OPENAI_API_KEY, ANTHROPIC_API_KEY, OLLAMA_ENDPOINT). Project config overrides global; secrets never live in repos.
Stop Starting From Zero.
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.