A Screenshot Is Not an Agent Failure Artifact

Description and use

Screenshots lack provenance and redaction context. Use AgentInspect Evidence v2 bundles to provide a verifiable, reviewable evidence package for pull requests and support tickets.

Problem

Reviewers rely on screenshots of execution trees, which lack provenance, redaction context, and offline inspectability, leading to incomplete or misleading evidence.

Outcome

Using AgentInspect’s Evidence v2 bundle provides a bounded, reviewable evidence artifact that preserves provenance, redaction context, and file integrity, enabling reviewers to inspect failures offline and verify consistency without exposing raw data.

Workflow

• 1. Run npx agent-inspect bundle <run-id> --dir .agent-inspect --profile share --out ./agent-evidence for a single run or use --session for multiple runs.
• 2. Inspect the generated folder: open evidence.html and summary.md to review the trace and summary.
• 3. Review redaction-report.json and check-results.json to understand what was redacted and any verification issues.
• 4. Run npx agent-inspect bundle verify ./agent-evidence to ensure the bundle’s integrity and that all hashes match the manifest.
• 5. If verification passes, attach the agent-evidence folder to the PR or support ticket; otherwise regenerate or correct the source.
• 6. Apply organizational data‑retention and sharing policies before publishing the bundle.

Evidence

The source remains private. The reviewer gets a bounded object with enough context to question the result.

Source

Run the offline verifier: npx agent-inspect bundle verify ./agent-evidence

Source