CLI

Install with npm i -g nemu-cli (or bun add -g nemu-cli). The command is nemu.

Command	Does
`nemu login [--force]`	Sign in with the device flow and register this computer as a device. The browser page asks you to type the code shown in your terminal, shows where the request came from, and the code expires after five minutes
`nemu setup <claude\|cc\|claude-code\|codex>`	Connect a client; `--hooks`, `--no-hooks`, `--yes`
`nemu setup <cursor\|vscode\|gemini\|windsurf\|zed>`	Add the Nemu MCP server to that editor’s config, keeping everything else in the file
`nemu claude [-- args]`, `nemu codex [-- args]`	Set up if needed, then start the client
`nemu claude load memories [--all] [--yes]`	Import Claude Code’s saved memories
`nemu claude load sessions [--limit n]`	Let Claude Code read recent sessions and save notes
`nemu codex load sessions [--limit n]`	The same for Codex
`nemu mcp`	The stdio MCP bridge that clients start
`nemu mcp config <client>`	Print config for another client
`nemu context`	Show what an agent sees for this folder
`nemu context search <words>`	Search this project’s notes
`nemu context projects`	List your projects
`nemu context export [--out file]`	Export everything as JSON
`nemu status`	Sign in, device, global install, each client’s setup and the editors found
`nemu uninstall [client\|all]`	Remove what setup added, for any client or editor
`nemu update [--yes]`	Check for a newer CLI and install it; the CLI also asks by itself at most once a day (`NEMU_NO_UPDATE_CHECK=1` turns that off)
`nemu repair`	Bring the Nemu hooks and editor entries up to date; also runs by itself once after each update, and changes nothing that already matches
`nemu token [--header]`	Print a fresh access token
`nemu config set reports on\|off`	Turn error reports on or off

Every command takes --json.

When something fails

After you sign in, a failed command sends a small report and prints a reference such as NMU-7F3K-2Q9D. Quote it to support@nemu.cc and we can see what happened. A report holds the command and flag names but never their values, the CLI, OS and Node versions, and the error with secrets and your home folder removed. Turn it off with nemu config set reports off or NEMU_NO_REPORTS=1. Errors from the Context API carry the same kind of reference.

Files on your machine

Everything lives in ~/.nemu (or NEMU_CONFIG_DIR), readable only by you: auth.json holds the sign in, settings.json the device id and the reports setting, sessions/ and pending.json the local hook state, and hooks.log any hook failure.

Get started

Setup

Console

Workflows

Chat

Computer

Context

API reference

When something fails

Files on your machine

​When something fails

​Files on your machine

When something fails

Files on your machine