Codex app freezes on certain threads - crashing app and making thread inaccessible

Resolved 💬 2 comments Opened Apr 29, 2026 by alferrante Closed Apr 29, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

26.422.71525

What subscription do you have?

Enterprise

What platform is your computer?

Darwin 23.6.0 arm64 arm

What issue are you seeing?

Specific threads within the app are regularly freezing - this is new as of maybe 5 days ago.

Specifically, I start a new thread in the app, go do something else, and when I come back, the thread is inaccessible - clicking it it my computer suddenly slows wayyyy down and everything is laggy or inaccessible, and the thread shows empty. Eventually the app crashes or I have to force quit (after 5+ mins) and I can't access anything in that thread.

I have to go to Codex in the terminal and ask it to paste my original query (based on sessionID) so I can try again in the app.

Similar to feedback here - https://www.reddit.com/r/codex/comments/1stuej3/ui_codex_freezing_and_sometime_not_responding/

What steps can reproduce the bug?

Not consistently replicable, but about 1/3 of the time, I'll start a new thread in the app, enter other windows (e.g. slack) and then when I come back, the thread is frozen. Trying to click into it everything slows down, it shows empty, I can't view it, and then the app crashes or just becomes fully frozen.

Session ID example: 019dd9e4-2b12-7493-a3e5-4c1b3118228e

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #19750
  • #18693
  • #19690
  • #20214

Powered by Codex Action

alferrante · 4 months ago

Asked Codex to fix the issue itself - said "Your Codex desktop app was choking on huge session transcript events, not normal thread count. The issue example 019dd9e4-2b12-7493-a3e5-4c1b3118228e had a 485MB JSONL transcript with one 278MB function_call_output line from a massive CSV"

Seems fine now.