QA Regression Triage with Claude Code: Sandbox Policy

A production playbook for QA regression triage in cross-industry operations using Claude Code: sandbox policy, run-scoped inputs, logs, typed results, and artifacts.

Audience: QA automation teams

The problem

QA automation teams need QA regression triage to run repeatedly against test failures, screenshots, logs, and recent changes. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Run QA regression triage in an ephemeral sandbox, keep provider credentials in the broker, expose narrow tools, and store logs outside the workspace for review.

Tradeoffs and failure modes

A narrower runtime blocks ambient machine behavior, but it gives security reviewers a concrete boundary. For QA regression triage, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.

Runtime boundary

filesystem: /skill and /skill/.argo/inputs only
network: deny by default
artifacts: /skill/output/artifacts
logs: retained outside sandbox
provider: Claude Code

Run this on Argo