codex cli taking a very long time to respond to even simple requests
Open 💬 5 comments Opened Mar 15, 2026 by nkdhruw
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
v0.114.0
What subscription do you have?
Pro
Which model were you using?
gpt-5.4 (reasoning high, summaries auto)
What platform is your computer?
Linux 5.15.0-168-generic x86_64 x86_64
What terminal emulator and version are you using (if applicable)?
terminal that comes with the jupyterlab
What issue are you seeing?
The responses from the codex have been super slow lately. It is stuck doing nothing. I had to kill my last 3-4 requests as it took over 10 mins with no response from the codex. It flashes the stream disconnected message on the terminal and then again switches to working flash message.
FYI - I had about ~80% context window left in all the cases.
What steps can reproduce the bug?
Not sure if this is reproducible.
What is the expected behavior?
_No response_
Additional information
_No response_
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Uploaded thread: 019cf284-03db-71c2-95cb-a7acd1293b56
Reconnecting... 4/5 (25m 25s • esc to interrupt)
└ Stream disconnected before completion: error sending request for
I filed a more tightly scoped follow-up for the still-reproducible March 16, 2026 residual / recurrence where the sharp boundary is new-thread first turn vs existing-thread resume: #14795. The added evidence there includes Windows Desktop app-server logs showing slow
model/list,failed to refresh available models: timeout waiting for child process to exit, and fastthread/resumeon existing threads. Posting here in case it helps triage overlap.If you're able to repro this, please use
/feedbackto upload your logs and session details, then post the thread ID here.I’m seeing the same issue today.
Environment
Symptoms
Repro characteristics