[Bug]: Main timeline keeps counting "Working for X" while thread is awaiting user input

[sebherrerabe]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

1. Start T3 Code on the latest main.
2. Open a plan-mode thread and send a prompt that causes the agent to ask a follow-up question.
3. Wait until the thread is clearly blocked on that question and shows Awaiting Input in the sidebar.
4. Leave the thread idle for an extended period without answering, for example overnight.
5. Return to the same thread.

Expected behavior

Once the agent is blocked on user input, the main chat timeline should stop presenting the thread as actively working.

One of these should happen:

• the Working for ... timer stops or pauses while awaiting input, or
• the row changes to an explicit awaiting-input state in the main timeline

The main thread view and the sidebar should agree on the thread state.

Actual behavior

The sidebar shows Awaiting Input, but the main chat timeline continues to show Working for Xh Ym, where Xh Ym includes the entire idle time while the thread was waiting on me.

This makes it look like the agent actively worked for hours when it was actually blocked on a question.

Impact

Minor bug or occasional failure

Version or commit

main

Environment

Web app ran with npx t3, latest main, Codex provider, Windows with WSL2 (Ubuntu)

Logs, stack traces, or screenshots

Related context:

- Issue #576 ("New Thread Status for 'Awaiting response'.") mentioned that the working timer should probably pause while awaiting response.
- That issue was closed via PR #701.
- PR #701 appears to have fixed the sidebar status, but not the main timeline timer/state wording.

Current behavior on latest main:
- Sidebar: "Awaiting Input"
- Main timeline: "Working for Xh Ym"

Workaround

No response