Skip to main content
nemu setup claude (also nemu setup cc and nemu setup claude-code):
  1. Signs you in if needed and registers this computer as a device.
  2. Registers an MCP server named nemu with Claude Code at user scope, using Claude Code’s own claude mcp add. It runs nemu mcp, which uses your sign in and refreshes it, so no token is written into Claude Code’s config.
  3. Asks whether to install hooks in ~/.claude/settings.json (or $CLAUDE_CONFIG_DIR). Pass --hooks, --no-hooks or --yes to answer in advance.
Claude Code starts nemu on every session, which is why the CLI needs a global install. If it is missing, setup offers to install it.

What the hooks do

Without hooks, the MCP server still works: Claude Code reads its instructions and calls context_load and memory_write on its own, but less reliably.

Start a session

Bring in what Claude Code already knows

load sessions never uploads a transcript. It opens Claude Code with your recent session files and asks it to read them and save notes, so your own model decides what is worth keeping.

Check and remove

uninstall removes the MCP server and only the hooks Nemu added. Your notes stay in your account.