Windows desktop app repeatedly restarts during active tool calls
Open 💬 1 comment Opened Aug 17, 2026 by yanjuxin200816-png
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Summary
The Windows Codex desktop app repeatedly closed and automatically restarted while active tool calls were running. The active work resumed after restart, but internal missing-tool-output errors continued.
Environment
- OS: Windows
- Codex package version: 26.810.7004.0
- Time zone: UTC+7
Observed behavior
- AppX container was destroyed at 23:43:10 and relaunched at 23:43:12.
- AppX container was destroyed again at 23:50:11 and relaunched at 23:50:17.
- Before the first restart, the response WebSocket disconnected five times with
websocket closed by server before response.completed, then fell back to HTTP. - Logs repeatedly reported
Custom tool call output is missing for call id. - Other nearby messages included
could not find callback for Integer(17)and an attestation-generation timeout. - After restart, the active task resumed, but the missing-tool-output errors continued.
Expected behavior
A failed stream or tool callback should recover without restarting the desktop app, and restored sessions should not keep retrying with missing tool-call state.
Additional notes
Windows Application Error / Windows Error Reporting did not record a conventional application crash at these times. No project files or full logs are attached.
1 Comment
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action