Codex App for Windows - crash, lags, error for new tasks in running threads after restarted.
Resolved 💬 4 comments Opened Mar 9, 2026 by TomaxMe Closed Aug 6, 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)?
latest today, can't find where this About Codex dialog
What subscription do you have?
Pro
What platform is your computer?
Windows 11 Pro
What issue are you seeing?
From 2 days I experience:
huge lags switching between threads
huge lags when create new threads
“error to create task” in same thread when a new input from my side.
Codex App even crashed / simply closed without any warning.
Codex App for Windows - crash, lags, error for new tasks in running threads after restarted.
What steps can reproduce the bug?
just explained - no warning just closed - error to create task - huge lags switching threads... I don't have error codes displayed.
What is the expected behavior?
_No response_
Additional information
_No response_
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
New errors : Error submitting message
I'm experiencing the same:
<img width="1506" height="883" alt="Image" src="https://github.com/user-attachments/assets/95542425-a0a4-4491-b12c-b30428ddc15c" />
Details in closed issue https://github.com/openai/codex/issues/15386
I have this issue or something similar. I run the app in windows but with the agent in the WSL environment:
I monitored new WSL processes, then clicked a single thread in the sidebar once. That one click launched 5 (seems to be between 4-8+ normally) copies of:
/usr/bin/bash -lc LC_MESSAGES=C LANGUAGE=C GIT_TERMINAL_PROMPT=0 GIT_OPTIONAL_LOCKS=0 exec git worktree list --porcelainThose 5 launches covered 4 different repo roots, so it was not just checking the active repo once. It hit multiple remembered repo roots, including both WSL paths and a mounted Windows path, and one repo was checked twice.
Sequence from that single click:
repo A
repo B
repo C
repo C again
repo D
So this looks like clicking a thread triggers worktree checks over some remembered set of project/workspace roots, instead of just checking the current thread’s repo.
This was much worse for me at first. It got noticeably better after I stopped loading
nvmin non-interactive login shells and added an early return in.bashrcfor non-interactive shells, but the underlying issue is still there.also not entirely sure about this, but I started noticing this during a session where my wsl suddenly had a bunch of problems--I couldn't create new threads in the codex app, I couldn't enter WSL from a terminal, and I could only stop wsl using taskkill in powershell, not with wsl --shutdown.