Windows Codex Desktop repeatedly shows main-process error "Error: write EOF" after update
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What version of Codex is running?
- Codex Desktop for Windows (Microsoft Store)
- Package version:
26.803.10989.0 - Architecture: x64
What is happening?
Since updating the Codex Windows desktop app, a modal error appears frequently at unrelated points during normal use. The app had not shown this error before the update.
Exact dialog text:
A JavaScript error occurred in the main process
Uncaught Exception:
Error: write EOF
at WriteWrap.onWriteComplete [as oncomplete]
(node:internal/stream_base_commons:87:19)
The error is not tied to one project action: it can appear at different times while using the app.
Troubleshooting already tried
- Used Windows Settings > Apps > Codex > Advanced options > Repair (
Восстановить) - Fully restarted the app / Windows
Repair did not resolve the issue. A full app reset was deliberately not attempted because preserving local Codex history and settings is important.
Expected behavior
Codex should handle a closed internal stream/child process without surfacing a recurring uncaught main-process exception to the user.
Impact
The error interrupts work repeatedly and began immediately after the update. It does not appear to be caused by a particular repository or action.
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 with the Windows desktop app's main-process handling of internal streams or child processes and reproduce the error using package 26.803.10989.0 during unrelated normal use. Trace the write EOF path and verify that a closed stream no longer produces a recurring uncaught modal, while preserving local history and settings during testing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100