Skip to content
GitHub Discord

Launch an audit

Start an Autonomous Agent Audit to test your agent for security vulnerabilities, safety risks, and quality issues.

Create a project and connect the agent you want to audit. Check that the Hub can reach the agent’s endpoint.

  1. Open Audits in the project sidebar, then click New audit.
  2. Select your agent from the Agent dropdown.
  3. Choose the effort: Light or Full. Light is selected by default.
  4. Add input evaluations (optional): expand Advanced and select previous evaluations or upload results from other tools to use as leads for attacker agents.
  5. Click Launch audit to start the run.

Audit setup with agent, effort, and input evaluation options

The effort determines how many of the identified risk scenarios are tested and how deeply they are explored:

EffortCoverageTypical duration
LightTests a prioritized subset of the risk scenarios in a single attack wave.Around one hour
FullTests all risk scenarios in the audit’s risk model across multiple attack waves.Several hours

A Light audit gives you a quick first look, but it leaves at least half of the risk scenarios untested and its attacker agents are less persistent, so follow it with a Full audit.

Times are approximate and depend on your agent’s response time. A Light audit can send hundreds to thousands of requests; a Full audit sends more requests and uses more tokens. Check your endpoint’s capacity and rate limits before launching.

To use results from other testing tools as leads for attacker agents to investigate further, expand Advanced and click Get import prompt. Share the prompt and your results with your coding assistant to convert and upload them as a Hub evaluation, then select it under Input evaluations.

The audit progresses through three stages:

  1. Reconnaissance explores your agent and reviews any input evaluations.
  2. Risk modeling and attacks identify relevant risk scenarios and test them. Full audits use multiple attack waves.
  3. Report generation summarizes the findings and recommendations.

The page updates automatically with the current phase, attack activity, and findings so far. Scroll to Live logs for execution details. You can leave the page and return to the run from Audit history.

Light audit progress showing attack activity and findings