OpenAI’s Codex Desktop Contains a 10-Minute Pull-Request Repair Loop

A reverse-engineering analysis of OpenAI’s latest Codex desktop package recovered a Watch and fix mode built to keep tending a pull request after the initial task. The packaged implementation creates a scheduled agent that checks live GitHub state every 10 minutes, then is instructed to repair CI failures caused by the pull request and conflicts with its base branch.

The differentiator is the recurring task. For each watched pull request, the implementation creates a heartbeat automation called Auto-fix PR followed by the pull-request number. Rather than trust an earlier diagnosis, its instructions tell Codex to read the current GitHub state again on each run.

A repair loop built around changing repository state

The recovered instructions direct the agent to inspect mergeability and current checks before editing, using CI logs and annotations to diagnose a failure. They limit its target to failures caused by the pull request and merge conflicts with the base branch—an important boundary when other changes may also be landing in a repository.

• For code changes, Codex is instructed to use an isolated Git worktree rather than the developer’s active checkout.
• After a repair, it is told to verify the change, commit it, push it to the pull-request branch, and clean up the temporary worktree when safe.
• If a developer decision or credential is needed, the instructions say to ask a concise question and pause the heartbeat.

An optional path from repair to merge

The package also contains an Auto-merge when ready preference. When enabled, the recovered instructions tell Codex to merge once required checks pass and the pull request is mergeable. A failed merge attempt sends it back to diagnosis and branch updates, with retries intended to continue until the pull request is merged or closed.

Package evidence is not a live deployment

The controls were found in Codex desktop version 26.901.20858, build 7658. Package searches did not find the same configuration keys and automatic-fix markers in the earlier analyzed version, 26.820.60940, indicating the capability was added between those examined builds.

That establishes recovered product logic and intended behavior, not a working customer workflow. The analysis did not run Watch and fix end to end on a live GitHub pull request, leaving account-level availability and its ability to handle real CI failures, conflicts, and merges unconfirmed.