Turn a website problem report into a reviewed fix

What you’ll produce

A reproducible issue report, proposed code change and relevant test or visual evidence.

Inputs & connections

• A customer bug report with the affected flow and environment
• Authorized repository access, project setup and test requirements

A configured Codex cloud environment or an authorized connected computer with the correct repository. Local work requires that computer online with the app open.

Replace the bracketed fields. This is our suggested prompt, not a quote from the source.

Investigate [customer website issue] in [authorized repository and test environment]. Reproduce the failure, record the relevant steps and distinguish observed behavior from guesses. Prepare the smallest suitable patch and run checks that exercise the affected flow. Return the diff, results and any remaining uncertainty. Ask for approval before publishing a branch or pull request, merging, deploying, modifying production data or contacting the customer.

How to run it

1. 01

   Confirm the affected flow and reproduce it in the approved environment.

2. 02

   Trace the cause and prepare a focused local change.

3. 03

   Run relevant tests and capture evidence of the corrected behavior.

4. 04

   Review the change and approve publishing or deployment through the normal release process.

Limitations & success checks

• A completed agent run is not proof that the issue was fixed or a deployment succeeded.
• Missing reproduction details or environment differences can prevent a reliable diagnosis.

Measure: Issue reproduced, affected checks passed and reviewer-confirmed resolution after release.

Sources & attribution

The sources below support the reported example or a tool capability. They do not validate our prompt or prove the outcome in your environment.

Editorial review: 2026-10-17. How we label evidence.