Running codex app just disappears from the desktop.
Nobody has claimed this yet.
- 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.901.20858
What subscription do you have?
Plus
What platform is your computer?
Microsoft Windows NT 10.0.19045.0 x64
What issue are you seeing?
The app just vanishes and the last chat entries disappear. I had codex try to investigate the issue and this is what it found:
Yes — Codex crashed; it did not merely minimize or hide.
- At 13:55:38 local time, Electron Crashpad recorded capture_kind: crash, ptype: browser, meaning the desktop app’s main process crashed.
- Windows destroyed the Codex AppX container at that exact second.
- The old process stopped logging abruptly with no normal shutdown entry.
- Codex restarted at 14:06:08 using the same package version, 26.901.1978.0; this was not an update restart.
- No Windows Error Reporting dump or resource-exhaustion event remains, so the exact faulting function cannot be recovered locally.
- There have been five similar main-process crashes since September 2, so this appears recurrent.
The last nearby anomalies were an app-icon timeout and a failed wsl.exe --status check, followed by remote-connection refreshes, but the logs do not prove either caused the crash.
Evidence: crash record and preceding session log. OpenAI’s official troubleshooting page doesn’t currently document this crash signature.
What steps can reproduce the bug?
The trigger seems to be when switching from the codex app to another app. It doesn't happen each time.
It seems to happen even when Codex is idle (no work running, no events setup to auto-run).
What is the expected behavior?
For codex not to crash and for the last chat entries (continued conversation, not new conversation) not to disappear.
Additional information
This started happening approximately 3-4 codex updates ago.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the referenced Crashpad report and preceding session log, then compare them with the reported app-switching trigger and Windows environment. The issue is done when the intermittent desktop crash can be reproduced or narrowed to a confirmed cause, and conversations remain intact after recovery.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100