The decision system
for teams and agents
One record of what your team decided. Read by every engineer and every agent.
Works with Claude · Cursor · Codex · Perplexity
pipx install nauro
nauro init --demo
nauro check-decision "use websockets for live updates"
nauro adopt wires your own repo.
The problem
An agent starts every session with no memory of what your team already decided.
It does a burst of sharp work, doesn't know what was settled or why, then forgets it by the next session. A CLAUDE.md or per-tool memory patches this one tool, one person at a time.
Nauro is the authoritative decision record: plain files, surfaced to your agent by keyword retrieval before it acts. It never judges a conflict or blocks a change; you keep the final call. One record, across every tool, team, and session.
Your team's decisions, working inside your agent.
Filmed in Codex, against a real project.
See what your agent read before it acted
Lexical retrieval over your decision record, surfaced in-session before the agent writes code.
The trace below is what the agent read before it acted.
Retrieval put the decision that already settled this tradeoff in front of the agent, which weighed its new cache proposal against it.
Set prompt cache TTL to 5 minutes.
New implementation proposal
Adopt 1-hour cache tier.
Refined an earlier caching call after TTL economics changed.
The agent cited the active cache-tier decision, weighed the earlier call it refined, and did not auto-supersede. Nauro never blocks the change; the human keeps the final call.
Agents and skills
that read your record.
Agents are roles you delegate to. Skills are workflows you invoke. Both check the record before they act, and one agent can leave a brief another picks up.
Roles you delegate to.
- @nauro-planner Checks prior decisions before drafting a plan. Files the choice when one is made.
- @nauro-executor Implements only what the plan calls for. References the decision in the commit footer.
- @nauro-reviewer Audits the diff against the PR template. Blocks if any cited decision reference doesn't resolve.
- @nauro-tech-lead Sets direction across sessions. Files supersedes when work conflicts with a governing decision.
Workflows you invoke.
- /nauro-adopt Seeds the store from your repo. Reads README, ADRs, manifests; asks for the rationale; files decisions with what was rejected.
-
/nauro-ship-task
Planner → executor → reviewer chain, gated by
check_decisionat every handoff. - /nauro-handoff Captures a session handoff so the next session resumes cleanly. Leaves a resume pointer; never files a decision.
- /nauro-context Writes a durable brief one agent can share so any other session, parallel or later, can find and pull it on demand.
Connect Nauro
to your agent.
One project store, reachable from any tool. Pick the install path that matches yours.
Local stdio server, spawned per session by your client. No account, and it works with any client that supports the Model Context Protocol. nauro setup claude-code (or cursor, codex, or all) writes this entry for you.
"mcpServers": {
"nauro": {
"command": "nauro",
"args": ["serve", "--stdio"]
}
}
}
Reaching a project from a surface with no local checkout? See the Web tab for the cloud connector.
One command. Auto-detects Claude Code, Cursor, or Codex and wires MCP.
- Claude Code: restart, then invoke
/nauro-adopt. - Cursor: restart.
- Codex: add
mcp_oauth_callback_port = 8765to~/.codex/config.toml.
Sync your store to the cloud, then add nauro as a custom MCP connector in Claude, Perplexity, or any web client that accepts one.
-
1
$ nauro auth login && nauro link --cloud && nauro sync
-
2
Paste
https://mcp.nauro.ai/mcpinto your client's custom MCP connector settings.
What your team decides today is what every agent reads tomorrow.
The reasoning travels with your project, not with the tool you use to ship it.
Start small. Grow when you're ready.
-
01
Start local.
nauro adoptseeds the store from your repo. Your machine, your record. Nothing leaves until you decide it should. -
02
Add your agents.
Claude Code, Cursor, and Codex wire up locally; Perplexity and other web clients read the same store over the cloud connector. Switch agents without losing project memory.
-
03
Sync when the team needs it.
Cloud-backed when more than one engineer ships decisions. The record travels with the project, not the vendor.
Pricing
Free and open source.
Cloud sync included.
The whole product is free and open source under Apache 2.0: unlimited local use, unlimited projects, and 5,000 remote MCP calls a month for web and cloud surfaces. Cloud sync is included within that allowance; higher hosted limits and team features are in development.
- Free and open source $0
- Cloud sync Included
- Higher limits & teams Planned