npm install -g agent-nuvira
nuvira doctor # full environment diagnosis
nuvira chat "explain what this project does" # have a conversation about your code
The first run is deliberately thorough — it probes every provider you hold a key for — and
nuvira doctor will tell you exactly what it found. Full setup guide →
Why it is different
It verifies its own work. An edit that nothing checked cannot be reported as done. If the agent changes files, makes a claim, and runs nothing, that is recorded and it gets one corrective nudge naming what would settle it — rather than eight confident turns of "now fully operational" while your build stays broken.
One engine behind every surface. The terminal, the dashboard and all 22 messaging channels are the same pipeline, the same tool surface and the same router. Fix a bug in one and you have fixed it everywhere, because there is only one place it lives.
It finishes long unattended jobs, and accounts for them. A multi-hour run reports its per-batch cost and latency on every completion path — so a job started from WhatsApp is as measurable as one started in your terminal.
Every number means what it says. A progress percentage means the deliverable exists, not that a counter ran out. A listing is never presented as a capability. When the agent cannot tell, it says so.
Local-first, and honest about cost. Ollama and local models are a first-class path, not a fallback. 22 providers speak one interface, with bring-your-own-keys, a cost cap and a governance policy you control.
No telemetry. Nothing leaves your machine except the requests to the model providers you configured.
What it can do
Beyond code, it drives a browser, reads PDFs and spreadsheets, generates and describes images, transcribes and speaks, runs code in a sandbox, supervises containers, and assesses a repository it has never seen. Everything it can do →
Vector retrieval keeps long contexts affordable rather than merely possible — measured on a real repository: 142,493 tokens saved at a 65.6% average reduction.
See it before you install it
The command reference covers every command with its objective, exact syntax and a copy-pasteable example. The CLI tour is a recorded sweep across the whole surface, captured from the real binary rather than performed for a camera. The architecture document explains how the execution engine is put together, including what is still target state rather than built.
What it is not
It is not a hosted product — there is no cloud dashboard, because there is no telemetry.
Provider support is broad, so polish is uneven across all 22. Multi-account key rotation is
currently scoped to plan and edit, and unwinding that is the next milestone. Those are
the honest boundaries, written down rather than discovered by you.
Limitations and roadmap →
Repository layout
This repository is documentation only — the source lives in a private repository. The content here is generated from it, so a page cannot describe a command, a count or an interface that does not exist.