codex-result-handling

Structure Codex review outputs by preserving verdicts, summaries, findings, and next steps, while maintaining evidence boundaries and explicit distinctions like inference or uncertainty. Present findings first in order of severity to enable auditable reviews.

Organize Codex helper results into an auditable review by preserving all report sections, including observed facts, inferences, open questions, touched files, and suggested actions. Explicitly state when no findings exist and keep the residual-risk note brief.

No, you cannot automatically apply Codex-suggested changes. You must report updates and defer execution until explicit user confirmation. Never modify code or take actions without direct user approval, and list any touched files if edits were performed.

Codex result handling includes special guardrails for codex-rescue outputs. It does not auto-implement fixes for failed runs; instead, it stops and asks the user which specific issues to fix before proceeding.

A structured Codex output review should include observed facts, inferences, open questions, touched files, next steps, and suggested actions. It preserves the helper's verdict and summary while presenting findings in order of severity.

Direct users to setup instead of processing Codex output when setup or authentication is required. The guardrails enforce routing to the setup process and prevent auto-implementing changes without explicit user approval.