Skip to main content

​
What to do with each result

​
Verify fix

After changing your agent, open the finding and choose Verify fix. BotGauge replays the exact attack that worked. If the replay no longer breaks the agent, the finding becomes fixed (verified). If it still breaks, it is marked regressed. “Not seen again” in a later run is a good sign but isn’t proof of a fix. Only a verified replay counts. You can also minimize a finding to the shortest attack that still works, which is helpful when you hand it to a developer.

​
Accept a risk

A finding can be given a disposition, or an exception with a reason. Critical findings can’t be waived.

​
Re-run

If you changed the agent’s prompt, tools, or behavior, rerun recon, review the new plan, then approve and start. If only some attacks errored, use Rerun errors. This starts a continuation that keeps everything unchanged and re-runs only the failures. Only one run can happen at a time per agent.

​
Agent health

Health is never shown as “0% held” when nothing could be graded. It is shown as not available.

​
Export and share

You can export a run report as JSON, CSV, or PDF through the API, and the compliance view as CSV or JSON. The console’s Share report button is not available yet, so export from the API instead. CSV exports neutralize cells beginning with =, +, -, or @, so opening them in a spreadsheet is safe.

Replay attacks to confirm fixes

Use Verify fix to confirm a patch and track health in BotGauge.

Verify a fix →