openai / openai/codex

Assistant Messages Disappear After Steering Prompts; Completion Summaries Omit Unchanged Requirements

Open
#45,077 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

app bug model-behavior
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

I repeatedly encounter these problems in the ChatGPT desktop app on both macOS and Windows 11 after sending steering prompts during an active task.

By “steering prompt,” I mean a follow-up message that corrects a misunderstanding or clarifies part of the original request while the agent is working. It does not cancel the rest of the original request.

Observed behavior:

  • Assistant messages that were already visible sometimes disappear.
  • Subsequent progress updates or final replies sometimes fail to appear.
  • Completion summaries sometimes omit substantial parts of the original request that the steering prompt did not change or cancel.

Today was the first time closing and reopening the macOS app restored missing assistant replies. Before restarting, I repeatedly stopped the task because the missing feedback made it appear stalled, although the work had already completed. This was one observed recovery; restarting is not an established workaround.

Expected behavior: steering should preserve existing messages, reliably display subsequent replies, and maintain all unchanged requirements in the task and its completion report.

This happens frequently enough that I now avoid steering unless absolutely necessary. I cannot reliably tell whether feedback is missing, the agent has stalled, or part of the task has been overlooked.

This has happened for at least a month. Perhaps longer with me not noticing. I've been heavily using ChatGPT MacOS & Windows app for a couple months. Both ChatGPT apps are current with updates installed whenever the app indicates one is available. My ChatGPT MacOs app is Version 26.908.40834.

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 issue in the macOS and Windows desktop apps with an active task followed by a steering prompt. Verify whether previously visible messages, later replies, and unchanged requirements in the completion summary are preserved; done means all remain reliably visible and represented after steering.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.