Platform
Reports And Approvals
Review agent output and control sensitive actions.
Reports are the audit trail for agent work. Approvals are the human checkpoint for actions that should not happen automatically.
Verified implementation
The console has /reports, /reports/[id], and /approvals dashboard routes. Reports are backed by agent_reports; pending approvals are reports with status = "needs_approval". The approval helper updates only rows that are still pending and records decision notes in report metadata.
Reports should show
- Agent name and run id.
- Input summary.
- Steps taken.
- Result and confidence.
- Cost, duration, and tool usage when available.
- Next recommended action.
Use approvals for
- Sending customer-facing messages.
- Publishing generated content.
- Rotating or revoking credentials.
- Deploying code or infrastructure.
- Billing or subscription changes.
Current limitation
This page describes the implemented report/approval data model and dashboard routes. It does not guarantee that every sensitive action in every product module is already wired to the approval status; check the owning route or workflow before relying on an approval gate.