Desktop app repeatedly fails to resume a Codex thread after encrypted tool-output decode error
Open 💬 2 comments Opened Aug 3, 2026 by Burlin-C
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Summary
A Windows Codex desktop-app thread becomes non-resumable after a streamed tool-output decoding failure. Restarting the app does not recover the thread.
Error
stream disconnected before completion: Encrypted function output content could not be decrypted or decoded.The UI retries reconnection through 5/5.
Environment
- Platform: Windows desktop app
- Codex CLI: 0.144.1
- Thread ID:
019f6a26-7593-7271-b338-b0d0d207ffa9
Steps to reproduce
- Run a long Codex thread with streamed tool output and background QA or process monitoring.
- Observe the error above and the reconnection attempts.
- Restart the desktop app.
- Return to the same thread and send a follow-up such as
go on.
Expected behavior
The thread resumes, or the app presents a recoverable terminal state.
Actual behavior
The same encrypted-output decode error repeats after restart. The thread remains in progress but does not return a usable response; further follow-ups do not recover it.
Additional observation
A fork that excludes the unfinished turn can continue. This suggests the original conversation is blocked by a persisted streamed tool-output event rather than by the project task itself.
No logs, project files, or conversation contents are attached to this report.
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Update: the recovery fork also reproduced the same failure.
A same-directory fork that excluded the original unfinished turn, thread
019fc581-056e-73a3-96f6-845e5027c4ab, initially resumed normally and completed a read-only recovery audit. Its next long turn then showed the sameEncrypted function output content could not be decrypted or decodederror and is now markedsystemError.This weakens the earlier observation that excluding the unfinished turn was sufficient. The recurrence is consistent with a broader desktop-app/session or streamed tool-output handling problem, not solely corruption of one persisted unfinished event. No logs, project files, or conversation content are attached.