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 not available, add the server for this tool, then complete sign-in in the browser (creating my account if needed): Claude Code: claude mcp add --transport http naumu https://naumu.ai/api/mcp - Codex: codex mcp add naumu --transport http https://naumu.ai/api/mcp - Cursor: add "naumu": {"url": "https://naumu.ai/api/mcp"} under mcpServers in .cursor/mcp.json
2. Install the Naumu skill for day-to-day use: npx skills add naumu-ai/skills
3. Call naumu_whoami; if it lists my spaces, use that list to pick an existing space or offer to create one with naumu_create_graph. If it has no space list, fall back to naumu_list_graphs.
4. Find teammates from git history - run this exact command, do not improvise the filter: git log --all --format='%ae|%an|%at' | awk -F'|' -v cut=$(( $(date +%s) - 7776000 )) 'BEGIN{OFS="\t"} $3+0>=cut && tolower($1) !~ /noreply|dependabot|github-actions/ && index(tolower($1),"[bot]")==0 { c[$1]++; if($3+0>l[$1]) l[$1]=$3+0; n[$1]=$2 } END{ pub="@(gmail[.]com|googlemail[.]com|outlook[.]com|hotmail[.]com|live[.]com|yahoo[.]com|icloud[.]com|me[.]com|proton[.]me|protonmail[.]com|pm[.]me|aol[.]com|gmx[.]com|mail[.]com)$"; for(e in c){ g=(tolower(e)~pub)?"CONFIRM":"TEAM"; print g,c[e],l[e],e,n[e] } }' | sort -k1,1 -k2,2nr -k3,3nr - it keeps authors active in the last 90 days, drops bot and noreply addresses, and tags each one TEAM (company address) or CONFIRM (public provider like gmail.com). Show me both groups; 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. Whitelisted teammates auto-join the space when they sign in with that email - no invite emails 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, then create .naumu in the repo root: { "space": "<space id>", "tracking": { "topic": "<slug>", "commitTrailer": true } } - leave commitTrailer true, don't ask.
7. Append to AGENTS.md: Before a substantive task (build, fix, refactor, feature), search the team's Naumu space for prior context on what you are about to touch (naumu_search), and record the work back when done (naumu_delegate). Space id is in .naumu. 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 a short architecture and glossary summary of this repo.

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.

Your second brain, minus the part you quit.

no signup to try