Desktop app repeatedly fails to resume a Codex thread after encrypted tool-output decode error

Open
#36,662 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
desktop-dev

Research direction

Start by reproducing the failure in the Windows desktop app with Codex CLI 0.144.1, then trace handling of the persisted streamed tool-output event after the encrypted decode error. Done means the affected thread either resumes after restart and a follow-up, or the app presents a recoverable terminal state instead of retrying indefinitely.

Written by the indexing model from the issue text.

Description

app bug connectivity session tool-calls windows-os

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

  1. Run a long Codex thread with streamed tool output and background QA or process monitoring.
  2. Observe the error above and the reconnection attempts.
  3. Restart the desktop app.
  4. 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.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.