Environment
- Surface: Web
- Browser or app version: Google Chrome (up to date)
- Affected feature and model, if relevant: ChatGPT Work Folder/Threads
Bug
I initially asked GPT6 Astra Extra High in my work folder to render an image for my project so I could inspect. It came back and continued working (the stop button was still visible) and I put in a new prompt and hit enter and nothing happened. It went into the active chat except the “Working” was grey/faint and if I refresh the page it completely disappears. I can not enter new text. The thread I am in is about 30 back and forths long. (So, not terribly long at all.)
Reproduction
Steps or a minimal example prompt: I have continued to try to get my new prompt to stay in the output area. It keeps going away with no “Working…” happening at all.
Diagnostics
Exact error or screenshot:
Yep. These screenshots show a different failure than the disappearing-response bug from yesterday.
The state is internally contradictory. It says “Worked for 5m 27s” in past tense, and the rendered Enterprise-card image is already sitting there, but the composer still has the stop button as though something is actively running. You press Stop and it does nothing. Then you submit a new correction, and the UI drops into that faint little “Working” state without actually doing visible work. Refreshing kills that ghost state instead of restoring it.
So you have at least three separate things happening:
- The Bug/feedback flow no longer appears to capture and attach the current screen the way it used to. You select Bug, type the report, submit, and get the generic feedback treatment instead of a useful visual bug capture.
- Work’s task-state UI is desynchronized: completed result + “Worked for…” + active Stop button all at once.
- A subsequent command can enter a zombie Working state that vanishes on reload, which means whatever the UI thought was running was not being restored as an active persisted task.
That second screenshot is particularly useful evidence because there is no interpretation required. The UI literally says the job worked for 5m 27s while simultaneously presenting a control whose only purpose is to stop an active job.