For your repository
Your repo, on the record.
Your coding agents remember what your team ships - decisions, context, work-log - and every teammate's agent can ask.
Set it up from your coding agent
Paste this into Claude Code, Codex, or Cursor. It connects you - creating your account if needed - and wires the repo for your team.
Setup prompt
Set up Naumu for this repository. Ask me before running each command, and never commit directly to a protected branch.
1. Connect: if Naumu MCP tools are missing, add the server for this tool, then sign in via the browser (creating my account if needed): Claude Code: claude mcp add --transport http --scope user naumu https://naumu.ai/api/mcp - Codex: codex mcp add naumu --url https://naumu.ai/api/mcp then codex mcp login naumu - Cursor: add "naumu": {"url": "https://naumu.ai/api/mcp"} under mcpServers in .cursor/mcp.json
2. Install the Naumu skill: npx skills add naumu-ai/skills. If .gitignore ignores .agents/ or .claude/, add unignore rules so the skill files can be committed.
3. Call naumu_whoami and use its space list (else naumu_list_graphs) to pick an existing space, or offer to create one with naumu_create_graph.
4. Find teammates from git history - run this exact command, do not improvise the filter: git log --all --since=90.days --format='%ae %an' | grep -viE '^noreply@|dependabot|github-actions|\[bot\]' | sort | uniq -c | sort -rn - then tag each address TEAM (company domain), CONFIRM (public provider like gmail.com) or ASK (users.noreply.github.com). Show me all groups; ask me for ASK people's sign-in emails; never whitelist a CONFIRM address without my explicit per-address confirmation.
5. After I confirm, call naumu_whitelist_members with those emails and repoInit true. They auto-join when they sign in with that email; no invites are sent.
6. Ask me what to call the tracking topic (suggest work-log, kebab-case). Call naumu_list_topics and create it if missing with notifyOn "people" (automated posts stay silent), then create .naumu in the repo root with the space id and slug and the topic name and id: { "space": "<space id>", "slug": "<space slug>", "tracking": { "topic": "<name>", "topicId": "<topic id>", "commitTrailer": true } } - leave commitTrailer true, don't ask.
7. Append to AGENTS.md as a MANDATORY rule: at the start of any build, fix, refactor or feature task, run naumu_search for prior context, then open a work-log thread with naumu_delegate passing topicIds [tracking.topicId from .naumu] and a short "Starting work:" brief, and keep the returned threadId. Post follow-ups into that threadId on decisions, pivots and blockers, and a bulleted summary when done. Add the trailer Naumu-Thread: https://naumu.ai/spaces/<slug>/chat/<threadId> to every commit. Never block work on a failed Naumu call. If Naumu MCP tools are missing, offer setup once, never auto-run: npx skills add naumu-ai/skills, then naumu_resolve_admission with the space id.
8. Open a pull request with these changes plus the installed skill files (.agents/skills/naumu and its .claude/skills/naumu symlink) so the team can review.
9. Offer to seed the space with this repo's architecture and glossary, plus key people, projects and decisions from my connected tools.What happens next
Teammates discover it on their own.
Once the change is merged, every teammate's coding agent reads it and offers to connect - once, framed as the team's convention. It never runs anything without a yes.
Whitelisted teammates are in on sign-in.
The people you confirm from the repo history join the space the moment they sign in with that email. No invite emails, no tokens in the repo - the space ID is an identifier, not a secret.
Every task leaves a receipt.
Work lands as a thread in the team space, and the pull request carries a Naumu-Thread trailer - so the context is one click away for the reviewer, whether or not their agent ever connected.
Going AI-native.
No signup, no credit card.