[Bug]: Waiting strip shows no timer for a Claude background command, because the task id does not match the turn item #28899

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. In a Claude thread, have the agent start one long command with Bash run_in_background.
2. Let the turn end, so the thread waits on that command.
3. Look at the waiting strip.

Expected behavior

A live elapsed time next to the task, because backgroundWorkNowItem renders one when a single task is pending.

Actual behavior

No timer. The strip shows only the label and Stop.

Impact

Minor bug or occasional failure

Version or commit

0.1.7-nightly.20261101.4035

Environment

macOS (darwin 25.6.0), desktop app, Claude Opus 5.5

Logs or stack traces

Likely cause, from this thread's state while the command ran:

• The pending task on the provider thread has taskId: "butrq2gr1", the background shell id.
• The running command_execution turn item has startedAt set, with nativeItemRef.nativeId: "toolu_01N8rbvPjwHPTudjfA4XJ2Gs", the tool call id.
• ThreadActivityBanners.tsx finds the item with (candidate.nativeItemRef?.nativeId || candidate.id) === task.taskId. The two ids differ, so item is undefined and startedAtMs is null.

No turn item in the thread has butrq2gr1 as its native id. I read the state and the source. I did not run a patched build.

Screenshots, recordings, or supporting files

Workaround

None. The agent has to be asked how long the command has run.

Related: #28897 asks for a timer per task when several run, and #15584 covers the wider background work details.

Written with Claude Opus 5.5 in T3 Code.