App is almost unresponsive for 5 mins after starting up
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.325.31654 (1272)
What subscription do you have?
Pro
What platform is your computer?
Darwin 25.4.0 arm64 arm
What issue are you seeing?
The first time I have this issue is at the "plugin" update of the codex app, and currently the version i have is (presumably) the 2nd version after the "plugin" update.
The Codex app is basically unresponsive, click/hover all takes >30s to see the app response in a very very slow way.
CPU shows only ~10% usage from the codex app, so I think this is some slow single thread start up task that is blocking the whole UI.
The only way to use the App is to wait around 5 mins (I think this is to wait the slow task to finish) and the app will become responsive again.
Every quite and start cycle triggers this issue.
What steps can reproduce the bug?
- close the codex app (cmd + q)
- reopen codex app
- observe the app is almost not responsive
What is the expected behavior?
the app should be responsive
Additional information
I'm not sure what I can provide to help you debug this, this has nothing to do with model performance so no thread id is needed.
let me know.
12 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
After it starts, please use
/feedbackto upload your logs and paste the thread ID here.i'm not sure if it is a duplicate as my unresponsive time is certainly more than 30s
<img width="1422" height="1558" alt="Image" src="https://github.com/user-attachments/assets/cfc0c87b-6830-424a-9892-7fc15bcd3105" />
I keep getting this error when submitting feedback from the codex app @etraut-openai what should I do to generate a thread id?
Ok this is the session ID I got from the conversation by right clicking and "copy session ID"
019d383b-6ed1-73d3-a677-0fb074990837Let me know if I need to provide any other stuff @etraut-openai
Same here on Windows as well.
Edit: Seems kinda related to my first issue here https://github.com/openai/codex/issues/13589#issuecomment-4006912394
I now disabled all kinds of notifications/popups from Codex app and so far no freezing.
is my thread id accessible and provide useful info? any follow up i need to do?
Please have the official release the new loader and thread manager as soon as possible. Every time it starts, it takes 5 minutes to wait for the initialization to complete, and after loading, the historical chat records of the threads still take 2 minutes to load.
My friend advised me: You better not close VSCode to avoid wasting time.
Rust is safe, but its startup time is no less than booting a computer.
this has been a week... anybody looking into this? as codex app is not open sourced, i don't think the community can do anything about this
Same here. Takes more than 5 minutes to become responsive. Have to switch back to vscode. Windows app does not work at all.
Subject: Codex App for macOS: local app-server blocks UI RPCs for 80-950s under heavy real-world session history
Environment:
Issue:
Codex App becomes extremely slow on startup and during normal navigation:
This does not look like an OpenAI API/network latency issue. The local Electron UI -> Codex app-server RPC path is returning very slowly.
Evidence from Codex App logs:
Current log file:
~/Library/Logs/com.openai.codex/2026/04/28/codex-desktop-4d8304d2-d28d-476b-959e-fb4cc961f49c-72130-t0-i1-141200-0.log
Startup:
Representative slow RPCs:
Process evidence:
Local state/workload:
logs_2.sqlite showed active high-volume logging around responses_websocket / tokio-tungstenite / SSE while UI RPCs were delayed.
Hypothesis:
This appears to be head-of-line blocking or task starvation inside the local Codex app-server. Heavy live session processing, JSONL/session writes, SQLite/log writes, plugin/config/account/thread/model UI RPCs appear to share a bottleneck. Lightweight UI operations like thread/list, config/read, account/read, and model/list should not wait tens or hundreds of seconds behind live session processing.
Expected behavior:
Request:
Please investigate app-server scheduling/locking around:
I can provide logs and sanitized command output if helpful.
Windows 11, same issue. I click the icon to start, I wait for 5 sometimes 15m until the window just appears. Now after a few sessions it starts and completely crashes. I uninstalled, reinstalled but that fixed nothing. I am a new user - I use it around a week or two. Never had issues with Cursor or VS Code. I have 32GB Ram.