After you create a report, work happens on its detail page until the run completes. Use Reports for the list view and the detail page for deep review.

Running a report

Agent reports

1. Open the agent project from Reports or /app/red-team/agents/[id].
2. Start a new adversarial test from the project UI (scenario and controls depend on your deployment).
3. Wait for completion—duration varies by scope and infrastructure.

Repository reports

1. Open the repository report from Reports or /app/red-team/repositories/[id].
2. The scan typically starts automatically on creation; some configs allow re-run or retry.
3. Monitor status transitions (queued, running, completed, failed).

Reviewing results

Signal	Where to look
Overall status	Report detail header and Reports list
Agent findings	Agent project detail — conversation logs, failure modes, downloads
Repository issues	Report detail and Findings — each issue links back to the report
Advisories	Findings — GitHub advisories may appear with github_advisory source

Download report artifacts when the UI offers an export—useful for audits and sharing outside the dashboard.

Findings triage

Repository reports often create rows on Findings. Open a finding to:

• Set triage status (owners only on some deployments)
• Run or review AI-assisted triage with sandbox evidence
• Jump to the parent report for full context

When a report fails

• Confirm GitHub App access for repository reports
• Verify the repository still exists and is selected in the app install
• Check agent project description and type match the system you intend to test
• See Troubleshooting

Next steps

• Findings
• Agent reports
• Repository reports