Check Codex's Exit Status Before Using Its Output

A command can print plausible output and still fail. Your next automation step should require successful completion and a valid artifact.

For a Codex report job, capture the process status and validate the saved report before copying it to its destination. Use a disposable test where the output directory is unavailable or a required input is missing. Confirm that the downstream step does not run.

Keep progress logs available for diagnosis, but do not treat a friendly closing sentence as a machine success signal. Conversely, a zero process status does not prove that a business claim is true. Validate required fields and verify consequential findings against their sources. These checks answer different questions and both belong at the handoff.

OpenAI documentation.