openai / openai/codex

[Windows Desktop] Queued messages intermittently disappear or become Steer messages

Open
#43,819 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Environment

  • Codex desktop app on Windows
  • Installed app version: 26.901.6511.0

User-reported behavior

Two intermittent problems occur in the main conversation:

  1. Questions already placed in the message queue sometimes disappear. It is unclear whether the messages have been retained or executed.
  2. A message intended to be queued until the current task finishes sometimes becomes an active-turn Steer message instead.

This report describes the user's observations. A deterministic reproduction and the underlying cause have not been established. In particular, disappearance from the queue has not been proven to mean deletion from persistent storage, and the exact dispatch path of the unexpected steering has not been traced.

Expected behavior

  • Queued messages should be retained reliably, with a visible and traceable execution state.
  • Queue and Steer should follow the user's chosen send mode; a queued message should not silently change into steering for the active turn.

Reproduction status

Intermittent during normal use of the main conversation while work is active. Exact timing, click/keyboard sequence, and a stable minimal reproduction are not yet available.

Please investigate queue persistence, send-mode handling, and transitions between active and completed turns. These are investigation areas, not a claimed root cause.

Related report

#34599 describes messages being dropped during active work in the Linux VS Code extension. This report concerns the Windows desktop app and additionally reports unexpected Queue-to-Steer behavior. Please consolidate if these share the same issue.

No project files, full conversation transcripts, or private session identifiers are attached.

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.

Research direction

Start by reproducing the intermittent behavior in the Windows desktop app's main conversation while work is active, recording the exact send actions and turn transitions. Investigate queue persistence, send-mode handling, and active/completed-turn transitions; done means queued messages remain traceable and the selected Queue or Steer mode is preserved.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.