›_ Codex Issues
Codex Issues / #10757

Codex Cloud opens PR with the wrong title and description

Open 💬 2 comments Opened Feb 5, 2026 by benglewis

What issue are you seeing?

The PR is opened with a title and description that only reflect the changes made in the follow up comments and not the original task.

What steps can reproduce the bug?

  1. Send a task to Codex Cloud.
  2. Respond to the results of that with follow up comments for more changes.
  3. Open a PR with a click on the "open draft PR" option (I don't know if it matters whether it is a draft or not - I don't think so)

What is the expected behavior?

The PR title and description should reflect all changes in the branch that is being requested to be merged in the PR.

Additional information

_No response_

View original on GitHub ↗

2 Comments

H1ghSyst3m · 3 months ago

I can reproduce a similar issue.

Workflow:

  1. Ask Codex to refactor several files for a feature.
  2. After that work is done, ask Codex to make a small documentation update.
  3. Click the Codex PR creation action.
  4. The generated PR title and description only mention the documentation update, even though the branch also contains the earlier refactor.

Expected:
The PR title and description should be generated from the full branch diff against the base branch, not from only the last user message or most recent Codex change.

Actual:
The PR title/description summarize only the final docs follow-up, which makes the PR misleading.

This also affects commit naming when the commit includes the full accumulated diff but the generated title only reflects the last change.

MaffooBristol · 1 day ago

I've found this issue too.

Task: Do XYZ
Codex does it and some other incorrect stuff
Me: "No, don't do that!"
Codex opens PR with title "Not doing that" and commit "Removing incorrect thing"

It seems like the prompt and such used for the PR generation is entirely separate from the worktree and general conversation with the agent itself. So you can, during the conversation, say how you want your PR formatted, but it doesn't care. It also seems that when you hit the create PR button, it takes all the work done, treats it as a patch, applies that onto your primary branch, and creates the PR from that. So there are two separate things: the runner's internal worktree, and then the actual patch that gets turned into a PR.

At the moment this workflow is so buggy that I do find myself having to just go in and modify so much of the PR. And certain things such as the way it adds the codex label and puts a link to the session in the PR description, are just things I don't want, but can't control.

Codex cloud definitely still feels like a very unpolished product, even though it has some real positive use cases (army of robot underlings)