You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ChatGPT iOS Work Mode: interrupted responses remain blank or show only “Working” #51543
ChatGPT iOS Work Mode, rather than the desktop Codex app. Available client metadata: 1.2026.267 (build 36747771815), iOS 27.0, iPhone18,1. Exact installed version has not been independently verified. Subscription: not verified. Model label visible in a screenshot: 6.1 Sol Medium.
Observed behavior
During an extended coding task, the user repeatedly reports interrupted response streams. Multiple assistant entries display only “Working”; readable assistant progress or final text is absent, including after a “Worked for …” duration appears. New user messages can still be sent. The user cannot tell whether work continues, has stopped, or requires intervention, and repeatedly asks for status.
Screenshots in the originating private conversation confirm the blank/Working-only presentation. The latest observed report was October 6, 2026, approximately 21:41 EDT. Screenshots and private project details are omitted from this public report.
Observed sequence
Run a sustained coding task in ChatGPT iOS Work Mode.
Receive progress responses and an apparent stream interruption.
Conversation entries remain blank or show only “Working”.
Ask for status or say the response cannot be seen; the same symptom recurs.
This is an observed sequence, not a deterministic reproduction. Network conditions and session ID are unavailable.
Expected behavior
Restore readable response text after a reconnect or interruption, and distinguish running, waiting, interrupted, and completed states. Provide a clear recovery action when the active turn stops.
Additional information
Some independently queried remote CI jobs continued while the conversation display was uninformative. The UI label alone therefore did not establish whether execution was still active. The cause is unknown: this report does not establish whether the fault is in rendering, streaming, reconnect handling, or execution. No credentials or private conversation contents are included.
Activity
github-actions commentedon Oct 7, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action