openai / openai/codex

Opening a certain thread (currently a specific one) will cause the codex page to freeze.

Open
#44,526 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

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

26.903.71938

What subscription do you have?

Pro 20x

What platform is your computer?

macOS 27 RC

What issue are you seeing?

After opening one of my threads in the codex, the codex page froze. The codex does not respond to mouse clicks, shortcut keys, or the macOS top menu bar, and the page does not refresh.

The clone (fork) of this "specific thread" also has the exact same issue.

Creating a clone (fork) of this thread gets stuck on the "Creating" card popup, continuously playing the loading animation (a spinning icon indicating loading).

Exiting the codex is unimpeded, and entering it again returns to normal. Clicking on this "specific thread" will freeze again. Other threads are unaffected and work normally.

If you click on this "specific thread" while working on another thread and it freezes, the other threads will continue to work normally, and I am unable to exit the freeze using shortcut keys or jumps.

Image
What steps can reproduce the bug?

Click on "Specific Thread" in the navigation bar on the left of the codex. (It's not specifically designed as an "attack example" by me; it's one of my normal threads that suddenly turned into a thread that "will definitely make the codex crash.")

What is the expected behavior?

No response

Additional information

After the codex died, no hardware resource overhead with line anomalies was found, and the codex resource usage is low.
The address of the "specific thread" is codex://threads/01a07018-175d-7aa2-b967-0a50bd6c5d91

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 freeze in Codex 26.903.71938 on macOS 27 RC, using the thread address codex://threads/01a07018-175d-7aa2-b967-0a50bd6c5d91. Check whether opening the thread or creating its clone causes the unresponsive page and persistent “Creating” state; done means the specific thread and its clone no longer freeze Codex.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.