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
The chat timeline can remain on Working for … for a long time without showing whether the request was dispatched, whether any provider events have arrived, or what the last feedback was. That makes a slow provider, an active tool call, and a genuinely stuck turn look the same.
This is adjacent to reports such as #2644 and #2778, but the proposal is diagnostic UI rather than a claim to fix those provider-specific hangs.
Proposed behavior
Add a collapsed-by-default Details disclosure to the live working row on web and native mobile. When opened, it shows:
request age and timestamp;
last provider/assistant feedback age and timestamp;
active turn ID;
provider-event and tool-call counts;
the active turn activity stream, newest first;
an explicit no-feedback-yet state.
The projection should stay scoped to the active turn and avoid serializing arbitrary provider payloads. Only short, selected text fields should be surfaced.
Why on demand
This keeps the normal chat timeline quiet while preserving enough evidence to distinguish “request sent, provider silent” from “provider is still producing events/tool activity.” The same diagnostic should be available on web and mobile so the phone is not a second-class debugging surface.
This discussion was converted from issue #4612 on August 15, 2026 10:04.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Problem
The chat timeline can remain on
Working for …for a long time without showing whether the request was dispatched, whether any provider events have arrived, or what the last feedback was. That makes a slow provider, an active tool call, and a genuinely stuck turn look the same.This is adjacent to reports such as #2644 and #2778, but the proposal is diagnostic UI rather than a claim to fix those provider-specific hangs.
Proposed behavior
Add a collapsed-by-default
Detailsdisclosure to the live working row on web and native mobile. When opened, it shows:The projection should stay scoped to the active turn and avoid serializing arbitrary provider payloads. Only short, selected text fields should be surfaced.
Why on demand
This keeps the normal chat timeline quiet while preserving enough evidence to distinguish “request sent, provider silent” from “provider is still producing events/tool activity.” The same diagnostic should be available on web and mobile so the phone is not a second-class debugging surface.
All reactions