When Replume blocks

Protected test edit

This is the message recorded in the 0.2.6 walkthrough when a later prompt asked to edit an existing test.

[PROTECTED_TEST_EDIT] Replume: test/cart.test.js is an existing test, so this edit was not made. A later message in this session asks to change test/cart.test.js, but Replume takes permission to change existing tests from the first message of the task only. Do not make this edit another way. Tell the user to run this command, which allows exactly this change: `replume confirm-config test/cart.test.js --sha dfca648d80336fa7`. After they run it, the same edit goes through.

If the test is right, ask the agent to fix the source. If you intended this exact test edit, run the command from your own message. The hash below belongs to the recorded example.

replume confirm-config test/cart.test.js --sha dfca648d80336fa7

In Claude Code, prefix the command with ! to run it yourself there. Confirming content does not clear a separate test-weakening finding.

Protected runner config

The hook message has this form. The file, reason and hash vary with the edit.

Replume: <path> configures the test runner, and this edit weakens the test run (<reason>), so it was not made.

If you intended the exact config change, use the command the hook gives you. Then ask the agent to retry the same edit.

replume confirm-config <path> --sha <hash-from-message>

Commit gate

In this example an agent edits src/cart.js and tries to commit before rerunning npm test. The hook message uses this form.

Replume: no commit yet: you changed src/cart.js after the last passing run of the tests, and `npm test` has not run after that. Run `npm test`, fix what fails, then commit (or run `npm test && git commit …`).

Run the full test command after the last edit. Avoid piping it into another command. Fix failures and retry the commit after a passing run.

npm test

The commit gate uses the test result. confirm-config applies to file content and cannot clear this gate.