Codex App: Persistent PR Review Loop (Claude Code parity)
What variant of Codex are you using?
App
What feature would you like to see?
The Codex desktop app needs a native, end-to-end PR workflow that can fully automate the lifecycle of a pull request from creation to merge, especially when working within a worktree.
This is not about adding more individual features, but about connecting existing capabilities into a continuous, autonomous loop.
Proposed Workflow:
- Developer completes work inside a worktree
- In the Codex chat UI, there is a simple “Create PR” button
- Codex automatically:
- creates a branch (if needed)
- commits changes
- pushes to remote
- opens a pull request
- After the PR is created, Codex continuously monitors it for:
- review comments
- requested changes
- CI / status check failures
- merge conflicts or blockers
- When issues are detected, Codex:
- applies fixes in the same worktree
- commits changes
- pushes updates to the PR
- This loop repeats automatically until:
- all checks pass
- no outstanding review comments remain
- (Optional) Codex automatically merges the PR once all requirements are satisfied
Key Requirements:
- Full worktree awareness (no mismatch between thread and working directory)
- One chat thread bound to one PR / one worktree
- Persistent context across multiple fix iterations
- Automatic handling of:
- PR review comments
- CI failures
- Clear status updates inside chat, e.g.:
- PR created
- Waiting for review
- Fixing issues
- Re-running checks
- Ready to merge
- Merged
- Optional auto-merge toggle
Current Gap:
Codex currently supports:
- PR creation
- PR review
- manual fixes
- GitHub integration
However, it lacks a continuous, self-healing PR loop.
Impact:
This would enable Codex to function as a true autonomous coding agent that not only writes code, but also drives PRs to completion with minimal human intervention.
This is currently a major usability gap compared to tools like Claude Code Desktop.
Additional information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗