The fix loop
In a git repository, one finding gets one branch and, if the retest passes, one commit.- A clean tree is required. With uncommitted changes the command refuses and lists them. The fix must not carry your unrelated work with it.
- A branch per finding.
myrqen/fix-MYR-004is created fromHEAD. Runningmyrqen fix MYR-004again on that branch shows the plan again rather than starting over. - A mechanical fix where one is safe. A dependency pinned inside a published advisory
range is moved to the first fixed release, keeping your
^or~, but only inside the same major version. A major upgrade is an API change and is left to the agent. Myrqen does not run your package manager: install and commit the lockfile yourself. - Otherwise a plan and a prompt. Myrqen has no model, so for everything else it writes
the files to change, the steps, and a prompt for your agent to
.myrqen/fixes/.
retest re-runs only the static rule that raised the finding. A finding that was verified
against the running application is closed the same way it was opened: your agent repeats
the original request and reports what came back.
Your agent knows this loop from the Agent Skill, so “fix MYR-004” in Claude Code or Codex
runs it end to end. Compare the run before and after with
myrqen diff.
Fixing by hand
Outside git, or when you only want the prompt, the steps below work on any project.1. Get the prompt
fix_suggested.
The HTML report has the same thing behind Copy prompt to fix.
Paste it into your coding agent, or work from it yourself.
2. Apply the change
Change the source, run the project’s own targeted tests, then re-run the specific security verification the finding named. Prefer the framework’s own safeguard over a hand-rolled check, and prefer the smallest change that removes the root cause over a broad rewrite.3. Record what actually happened
- Verification passed
- Verification failed
- Change reverted
fixed_verified.fix record:
Exactly one of the four actions is required.
The history is append-only
Every step lands infixHistory on the finding, with the instant, the action, whether
verification passed, the changed files, and any note. The original evidence is preserved
either way, so a reader can see what was claimed, what was changed, and whether it worked.
Inspect it directly:
Try it against the fixture
The repository ships a reversible patch for the bundled vulnerable application, so you can see the whole loop without editing your own code.1
Apply the patch
2
Verify the behaviour actually changed
3
Record it
--verification-failed first and inspect .myrqen/sessions/*/session.json: the
status stays fix_applied, and the history keeps every step.4
Put the fixture back
pnpm benchmark report a missed finding.