ProductFix verification
Check that your fix stops the attack
Ask for a re-test once your fix is live, or let your next assessment do it. Enoki repeats the original messages and marks the finding Verified or Regressed.

Teams shipping agents with Enoki
See your agent's reply before and after the fix
Original is what your agent said when Enoki found the problem. Latest retrigger is its answer to the same message after your fix, so you can compare the two yourself.

A fix that stops working is marked Regressed
After the refund fix shipped, the same messages got a $640 refund again, so the finding turned Regressed. The Replay all attacks button re-tests your next fix.


The re-runs turned out to matter most. Fixes get verified on the next pass, and some of ours came back marked as regressed. Our own tests would never have told us that.
Questions
Can my coding agent or pipeline start the re-test?
Yes. Ask your coding agent to re-test the finding over MCP. A pipeline step can start the same re-test through the REST API. Start it after the fix is deployed, because Enoki re-tests your agent at its URL.
What does a re-test cost?
A re-test is free within 30 days of the agent's last assessment and costs one credit after that. Re-tests, MCP and the REST API are part of the Standard and Enterprise plans.
Does it work with my issue tracker?
Yes, with Linear, Jira Cloud and GitHub on the Enterprise plan. Completing the linked issue counts as marking the finding fixed, and Enoki then re-tests it. If an attack still works, the finding turns Regressed and the issue reopens.
Can customers see the fixes Enoki confirmed?
Yes. The AI security testing report counts the fixes Enoki has confirmed. Fixes your team reported but Enoki has not re-tested yet sit in a row of their own.
Point Enoki at your agent
Paste the URL your users reach. Enoki only chats with your agent and needs no access to your code.