Windows Codex Desktop repeatedly shows main-process error "Error: write EOF" after update
Open 💬 2 comments Opened Aug 12, 2026 by Araaniart
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
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.
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Update from an affected Windows user:
It appears when Codex tasks/automations start, hangs the Desktop UI, and can disable remote control. It is not limited to one repository or one user action.
Please confirm whether #38202 covers this current build and triage it with #35985 (browser-sidebar EPIPE -> write EOF) and #38062 (Git-review cancellation -> write EOF). The app should treat closed IPC/child streams as recoverable disconnects rather than surfacing an uncaught Electron main-process exception.