Troubleshooting
Checks to make before trusting a quiet report.
Wrong Replume command
Run replume --version and command -v replume. If an older binary appears first on PATH, fix the order or open a new shell. Hooks need the persistent global command; a one-shot npx path may disappear.
Hooks are not firing
Inspect .claude/settings.json, .cursor/hooks.json or .codex/hooks.json for the Replume command. Re-run replume init --cursor or replume init --codex where relevant, and trust Codex hooks with /hooks. A config entry still does not prove an event fired; look for captured events in the report.
Docker is unavailable
Start the local Docker daemon and make sure the needed image is present. Scenario verification in auto isolation can fall back to an isolated working copy: it runs on your machine and is not a security sandbox. The runtime stage needs Docker; without it, the report names the missing runtime check and may be INCOMPLETE.
No test command
Identify the project’s real test command and make it runnable first. A Stop gate cannot establish that tests pass when none can be found; the report should say what was not checked.
Disable or remove
For Cursor, replume init --remove-cursor-hooks removes Replume’s installed entries. For Claude Code, remove only the Replume entries from this project’s .claude/settings.json. For Codex, remove only the Replume entries from this project’s .codex/hooks.json; you can also disable or untrust them in Codex. Do not delete other hooks. Removing project hooks stops their capture; it does not erase old local reports.
Stuck? Book a call ↗