Inspect a run and its artifacts
Runs keep the work, evidence, logs, approvals, verifier output, and final summary together. Inspect the run before approving changes or using generated outputs.
Open A Run
- Open the dashboard.
- Go to run history, workflow runs, notifications, or project chat.
- Select the run.
- Review the run status and summary.
- Open task sessions to see delegated work.
- Open artifacts to inspect outputs and evidence.
What To Check
| Area | What To Look For |
|---|---|
| Run summary | Goal, workflow, status, provider, model, and final result. |
| Task sessions | Which agents worked, what they were asked to do, and what they produced. |
| Artifacts | Reports, patch bundles, verifier output, screenshots, source notes, and final summaries. |
| Approvals | Pending or completed human decisions. |
| Evaluations | Test, verifier, or QA results. |
| Timeline | Failures, repairs, retries, and major state changes. |
| Run workspace | Aggregated workspace state, artifact labels, related approvals, and task cards. |
| Audit view | Operator-readable evidence trail for review or handoff. |
| Replay packet | Compact reproduction packet and dry-run replay plan. |
Artifact Types
Common artifacts include:
final/summary.md;work/result.mdorwork/result.json;work/repo-write-bundle.json;evals/*-verification.json;research/*;qa/*;- screenshots or browser evidence;
- connector evidence and redacted source records.
Use The CLI
The CLI can inspect the same run data:
npm run cli -- get-run <run-id>
npm run cli -- run-workspace <run-id>
npm run cli -- artifact-index <run-id>
npm run cli -- audit-view <run-id>
npm run cli -- replay-packet <run-id> replay-packet.json