For your manager

Replume is a command-line tool that checks the work of AI coding agents (Claude Code, Codex, Cursor, GitHub Copilot, Hermes) on the developer's own machine. This page is for replume-cli 0.2.1, the current npm version; lines marked 0.2.2 describe the next version, which is not released yet.

What gets installed

• One npm package, replume-cli. About 780 KB, one dependency (commander), one command (replume). It goes wherever npm install -g puts global packages on that machine. No administrator rights beyond that, no account, no licence key, no background service, no network listener of its own.
• In each repository where the developer runs replume init:
• .claude/settings.json: the Claude Code hooks, which call replume hook claude. Existing settings in that file are kept.
• .replume/config (the mode, and optional settings) and .replume/.gitignore.
• Later, under .replume/: the task contract, the session log (events.jsonl) and the reports. The log and reports are git-ignored, so they stay on the machine unless someone commits them on purpose.
• Other agents' hook files, only for agents that are present or named with a flag: .cursor/hooks.json, .codex/hooks.json, .github/hooks/replume.json (--copilot), ~/.hermes/config.yaml (--hermes).
• No Replume state in the user's home folder by default. We checked this by running replume init and a full agent session with an empty home folder.
• Docker is optional. If it is running, Replume uses it to run the tests in a container: no network, read-only, removed afterwards. It never downloads the Docker image itself.

What it reads

• The files in the repository, and its git history (diffs and recent commit file lists).
• What the coding agent sends to the hooks during a session: the prompt, the names of the tools it uses, file paths, shell commands and their output. This is stored locally in .replume/events.jsonl.
• The agent's own session transcript file, to count tokens for the report.
• The output of the project's test command, which Replume runs itself.

Outside the repository it reads only the agent's transcript file, and the agents' own hook settings (when replume doctor is run).

What leaves the machine, and when

The coding agent itself sends code to its own vendor in any case; that is the agent's traffic, not Replume's.

To check a machine, run replume init and read its output: 0.2.2 prints a "Model review is on: … go to …" line, or nothing when the review is off.

How to remove it

There is no replume uninstall command yet (see Planned). Removal is manual, per repository, then the package:

replume init --remove-cursor-hooks   # only if Cursor hooks were installed; run it before removing the package
rm -rf .replume
npm uninstall -g replume-cli

Then remove the hook entries whose command is replume hook claude from .claude/settings.json. If the file existed before, replume init kept the original next to it as settings.json.replume-backup-<time>, and you can put that back. If replume init created the file and nothing else was added to it, delete it. Do the same for .codex/hooks.json and .github/hooks/replume.json if they exist.

If the package is removed but the hooks are left, Claude Code keeps working, but it shows SessionEnd hook [replume hook claude] failed: … replume: command not found after each session. We saw this in a real run.

Licence

The Replume Beta License: free use for your own internal development during the beta. It is not open source: no redistribution, no modification beyond running it, and no competing product. It says the licensor does not receive your code or data through the software unless you enable a feature that says so. The full text is in the package:

cat "$(npm root -g)/replume-cli/LICENSE"

Questions: hello@replume.dev