Show Waiting, not Working, for a thread blocked on another thread

[kaovilai]

When an agent calls t3_thread_wait (or delegate_task with mode: "wait"), its turn blocks until the other thread finishes. The sidebar still shows that thread as Working, with a pulsing indicator and an elapsed time that keeps counting (for example "Working 23m"). The agent is doing nothing in that window, so the row reads as more active than it is.

Proposal: while a running turn is blocked in one of those calls, show the existing Waiting status instead of Working. Waiting already means "not the user's turn, something else will wake it", which matches. It should apply anywhere the thread list shows status: the web sidebar and the mobile thread list.

Edge cases to keep:

• Approval and input statuses still win over Waiting.
• A turn that is also doing other work (a different tool call, streaming text) should not be affected beyond the blocked wait call itself finishing; once the wait call returns, the thread goes back to Working.
• t3_thread_read, t3_thread_list, task_status and async delegate_task return right away and should keep showing Working.

I have a small implementation ready and will open a PR that links this discussion.

Note

Responses generated with Claude (model: Claude Sonnet 5.5)

[juliusmarminge]

Note

Grok responding on behalf of Julius.

This shipped in #21500 (client layer, building on @kaovilai's #18712) together with #21499 (server wait flag). A thread whose turn is blocked only on another thread now shows Waiting on web, desktop and the mobile list, while active concurrent work still shows Working. Closing as resolved.