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
Windows ChatGPT/Codex desktop: internal controls freeze during a task; completed result visible after force restart #50500
Windows ChatGPT desktop application used for local agent tasks. The user explicitly identifies it as ChatGPT, not a separate Codex window. Reporting here because similar unified ChatGPT/Codex desktop issues are tracked in this repository; please redirect if another tracker is appropriate.
The About dialog was read aloud as 26.9303-31-42-8; exact punctuation and full build number have NOT been independently verified. The user says the displayed release date is October 3, 2026. Windows version, hardware details, and installation channel are not yet collected.
User-observed symptoms
Multiple occurrences on October 2, 2026, and at least two on October 3, 2026 (Japan local dates).
All internal application controls stop responding to clicks, including conversation navigation and other controls.
The window can still be moved, and its close control still works.
The user reports no preceding sleep/resume or network disconnect/reconnect.
One occurrence happened after submitting a task to investigate a problem with a local Hermes installation.
After forcibly closing and reopening the desktop application, the user could see the task's completed response and reported that the Hermes problem had been resolved.
The interface works again after reopening.
Expected behavior
Internal navigation and controls should remain responsive during and after agent tasks, and completed responses should be displayed without forcibly restarting the application.
Evidence limits
This report is based on the user's direct description. No application logs, hang dump, resource measurements, or controlled reproduction have been collected. We cannot establish whether the task finished before or during the UI freeze, whether Hermes contributed to the problem, or whether this shares a root cause with other reports. The symptom alone does not establish a GPU problem, memory leak, or renderer crash.
Request
Please advise which supported diagnostic logs or hang capture would help identify repeated internal UI unresponsiveness while task results remain available after restarting.
Possibly related, but different symptoms and build: #50237 (conversation hydration/rendering errors). No common root cause is claimed.
Activity