Codex App: Persistent PR Review Loop (Claude Code parity)
Open 💬 4 comments Opened Apr 23, 2026 by Iydah
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_
4 Comments
Now that remote control has been added, this is the next highest item on my wishlist.
@Iydah have you found any good tools or another harness that accomplishes this? I tried to implement my way around this, but Codex Desktop limitations are holding it back.
+1 — this is probably the biggest remaining workflow gap between Codex and Claude for me.
With Claude, after it creates or starts working on a PR, I can simply say in the same coding chat something like:
From a user's perspective this behaves essentially like an event-driven continuation of the existing coding session. In my experience, new PR events are normally picked up within seconds; “a few minutes” would be more of an upper bound than the typical latency.
What matters here is not just that the same result can technically be assembled using polling, scheduled tasks, GitHub Actions, or additional
@codexinvocations. The valuable part of the Claude workflow is the lifecycle:coding session → PR → review/CI events → autonomous fixes → same ongoing session
without the user having to build separate automation around the agent or manually trigger it again.
Codex already does the hard parts individually very well. Having a persistent, event-driven PR lifecycle attached to the coding session would remove one of the main reasons I still prefer Claude for taking a PR all the way through review and CI.
I mean - common, why this even an issue. This makes codex basically useless comparing to claude.
Why i have to manually turn wheel here? I want automatic PR creation and tracking for comments in PR and CI status.