[Bug]: A thread whose agent left a dev server running stays "Waiting" in the sidebar after the completion alert, and never shows "Completed" #15246

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 a dev server in the background (for example python3 -m http.server) and end its turn.
2. Wait for the completion alert, then look at the thread's row in the sidebar.

Expected behavior

The row agrees with the alert: "Completed" until I open the thread, then its normal state.

Actual behavior

The "Thread completed" toast appears, and the iOS Live Activity says "Agent work completed" with the thread marked "Done". The desktop row disagrees: it stays in the sidebar's "Working" group and says "Waiting" for as long as the server runs, sometimes for hours, and the unseen "Completed" pill never appears. Nothing in the row shows the server or its port. The pendingBackgroundTasks check in Sidebar.logic.ts returns "Waiting" before hasUnseenCompletion is reached. The mobile thread list shows waiting the same way.

When the server exits, its task notification wakes the agent, and the row switches to "Working" with minutes already on the timer. A wake run keeps the work start of the run before it (wakeWorkStartedAt: a wake "carries on the work of the run that started last"), so the timer counts from the prompt of the turn that had already completed, including the whole time the server ran. That fits a wake after held work, a monitor or a subagent, but here the alert had already reported that work as finished.

#14213 fixed the alert for this case (#13965): it fires when the only pending work is a command, per backgroundWorkHoldsCompletion. It notes: "The sidebar and the mobile list still show Waiting while a dev server runs. This PR only changes when the alert fires." So "Waiting" now covers two states the row can't tell apart: the agent will continue because a monitor or a subagent will wake it, or the agent is done and left a server running.

A possible fix is to let the row use the same backgroundWorkHoldsCompletion rule: with only commands left, show "Completed" while unseen and the normal state after it, perhaps with a · 1 running suffix, and start a new timer when such a command wakes the agent. Listing the ports there would need the agent's own listeners, which port discovery doesn't track today (#9832).

Impact

Minor bug or occasional failure

Version or commit

0.0.46-nightly.20261003.2623 (fed41fa)

Environment

Desktop app on Linux (NixOS, Wayland, niri); Claude Code 2.1.288

Logs or stack traces

No response

Screenshots, recordings, or supporting files

In-app toast after the turn: "Thread completed"

The same thread's row at that time: "Working" group, "Waiting"

iOS Live Activity at the same time: "Agent work completed", thread "Done"

Workaround

No response