openai / openai/codex

Chat status incorrectly showed an old branch (already merged) & merge conflicts message

Open
#38,226 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug session
Dominant language
Rust
Stars
125k
Forks
19.5k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (From “About Codex” dialog)?

26.803.61601

What subscription do you have?

Pro 5x

What platform is your computer?

macOS Darwin 27.0.0 arm64 arm

What issue are you seeing?

In all current and new chats in Codex, they're incorrectly listing a branch "Test-2" that was merged on April 22, 2026. It also indicated that there's merge conflicts when there are no branches left, everything had been successfully merged.

I've attemped those fixes:
• Commit & push everything
• Created a new branch then merged it
• Created a new PR then merged it

Possible cause:
A few weeks ago I accidentally created a new PR via Claude Code mac app. I've merged that branch but somehow it messed up Codex. I haven't been able to reproduce or undo this bug.

Image
What steps can reproduce the bug?

Unknown if this is actually the cause but here's what I think was the cause:

Both Codex and Claude Code opened (mac apps)
Both have a chat building something on the same code project
I clicked on "Create PR" button in Claude Code and accepted it
At some point afterward I noticed Codex started showing old branch & merge conflicts message in all its chats.

What is the expected behavior?

No response

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in the Codex macOS app with a project whose branch and pull request have already been merged. Investigate why all chats still show the old Test-2 branch and merge-conflict status; done means no stale branch or conflict message remains after the merge.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
desktop, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.