Plans and limits

There is one product. It installs with a single command and runs entirely on your machine.

What you get:

• Advisory proposal-time decision check. Nauro surfaces related history in-session. The agent reasons over the results, and the human keeps the final call.
• Human-ratified writes. An agent drafts every decision addition, update, or supersession and waits for explicit approval before calling propose_decision. The kernel then writes immediately when structural validation passes, with no second confirmation step.
• Local context store as plain markdown you own: auditable, diffable, git-committable.
• Works with local coding agents: Claude Code, Cursor, and Codex.
• Keyword-based BM25 retrieval built in, with optional local embeddings and no external keys.
• Bundled workflow subagents and skills.
• Unlimited projects and unlimited local use.

$ uv tool install nauro

Running Nauro locally is unmetered. The one published limit is on the hosted endpoint used by web and cloud surfaces:

5,000 remote MCP calls a month for web and cloud
surfaces. Running Nauro locally is unmetered.

5,000 remote MCP calls a month is the documented allowance. Contact support if you need a higher limit.

The allowance is counted per account, per calendar month (UTC), across all your projects. Only tools/call requests count; session setup (initialize, tools/list) does not. What happens as you approach and reach it:

• Warning before the wall. Inside the last 500 calls, hosted tool results carry an appended note with the remaining count and the reset date (every 100th call, then on every call inside the last 25).
• At the limit, hosted calls pause. The agent receives a clear in-session message rather than an opaque failure: the allowance is reached, when it resets (the first of the next month, UTC), and that only hosted calls are paused. Your local store and local MCP server keep working throughout.
• For a higher limit: see pricing or write [email protected].
• Check usage any time via list_projects. Its result carries a usage line with the used count, remaining allowance, and reset date.

Two hosted caveats worth knowing before you sync: deleting synced data is via support request (no self-service deletion command yet), and short bursts are separately rate-limited per user, independent of the monthly allowance.

A hosted project currently has one owner and no invite or shared-membership mechanism. Cloud sync lets that owner use the same record across machines and connected surfaces.

• Use machines sequentially. Pull, work, then sync before moving to another machine.
• Avoid concurrent writes. The cloud store has no compare-and-swap primitive or equivalent cross-request lock, so overlapping writers can overwrite the same mutable object.
• Recover half-states manually. A supersede writes the new decision and then updates the old one. If the second write fails, Nauro reports the half-state but does not automatically roll it back or repair it.

One command sets up Nauro whether or not you ever touch the hosted side:

$ uv tool install nauro

• License: Apache 2.0, open source.
• Local price: $0. Local use and projects are unlimited.
• Stability: Stable at 1.0. The nauro CLI, the stdio MCP tool contract, and the on-disk store format follow semantic versioning. Cloud sync and the hosted store are generally available at 1.0, versioned and operated separately.
• Hosted allowance: 5,000 remote MCP calls a month for web and cloud surfaces. Counted per account across all projects; running Nauro locally is unmetered.
• At the limit: hosted calls pause until the monthly reset (first of the month, UTC) with a clear in-session message the agent can relay; local use keeps working. Warnings with the remaining count appear inside the last 500 calls, and list_projects reports usage on demand. Higher limits via [email protected].
• Cloud sync surfaces: the hosted context store can be read by one owner from Claude, Perplexity, and coding agents.
• Concurrency: cross-machine convergence assumes sequential single-owner use. The cloud store has no compare-and-swap primitive or equivalent lock.
• Local coding agents: Claude Code, Cursor, Codex.
• Install command: uv tool install nauro.
• MCP endpoint (cloud connector): https://mcp.nauro.ai/mcp.
• Contact: [email protected].