fix(web): show the running icon on threads with a live background command

[StanMan007]

When a Claude agent leaves a background Bash command running (SDK local_bash, pending task kind "command") and ends its turn, the thread row in the sidebar looks finished. Meanwhile the open thread's composer shows Running: <command> · Stop. Command tasks deliberately don't hold completion (backgroundWorkHoldsCompletion, per #13965), so the row loses its last sign of live work. Users read the thread as dead while it still owns a running process.

Fix

Reuse the existing pulsing teal "terminal process running" row icon for live command tasks. Thread status, completion alerts and auto-settle are unchanged.

• resolveThreadRunningProcessLabel (Sidebar.logic.ts) builds the tooltip:
  • with integrated terminals: N terminal processes running and N background command(s) running. Open terminal
  • one command only: Running: <description>. Open thread
  • several commands: N background commands running. Open thread
  • otherwise no icon
• ThreadTerminalStatusButton renders when either source is live. Clicking it reveals the terminal when one exists; otherwise it opens the thread, where the composer's Stop control lives.
• Subagent, monitor and generic background_task work already holds the thread's Waiting status, so it doesn't add the icon.
• Both Sidebar and LegacySidebar pass the thread's pendingBackgroundTasks, the same roster that drives the composer banner.

Why this qualifies as a small, focused fix

The roster already knows the command is alive, and the composer shows it, but the sidebar row drops it. This PR only surfaces that state through an indicator that already exists. It adds no new status, setting, server change or contract change. It also stays out of the contested status/alert/auto-settle question in #15099, #17625, #18062 and #15413. Those PRs and issues are about whether a command should hold completion. This one only stops the row from hiding work that is already tracked.

Verification

Reproduced in a local dev build with an isolated home directory with Claude Opus 5.5. The prompt asked Claude to run sleep 900 via Bash with run_in_background: true and the description "Serve preview on port 4173", then end its turn.

Before (main)	After (this branch)
The turn completed. The row shows no live-work indicator, while the composer shows Running: Serve preview on port 4173 · Stop.	The row shows the pulsing icon with the tooltip Running: Serve preview on port 4173. Open thread.

The screenshots are cropped to hide the machine hostname. They are hosted on the fork, not committed here.

Focused checks:

• vp test run apps/web/src/components/Sidebar.logic.test.ts: 150/150. New cases cover the label for command-only, several commands, terminals plus commands, and other task kinds.
• vp test run apps/web/src/components/ThreadStatusIndicators.terminal.test.tsx (new, jsdom): 5/5.
  • A command-only row renders the button. Clicking it activates the thread without opening a terminal.
  • A row with a terminal reveals that terminal.
  • Subagent, monitor and background_task rows render no button.
  • Mutation check: restoring the old terminalId === undefined render guard fails the first test.
• vp lint on the changed files: no new findings. vp fmt --check: clean. vp run --filter @t3tools/web typecheck: passes.
• Two independent review passes, one for test coverage and one for correctness. The coverage gap they found is fixed in the second commit. The remaining finding is below.

Not checked: mobile thread rows, which this PR doesn't touch; a packaged desktop build; Codex or other providers' background work, since only Claude emits kind "command" today.

Known pre-existing gap, now more visible

After Restart agent session, or archive then unarchive, the process is killed, but nothing clears the thread's pending roster. Session release doesn't touch it (ProviderSessionManager.ts, writeReleaseRecords). I reproduced this live: after the restart, sleep 900 was gone, but the composer's Running: … · Stop banner stayed, on main and on this branch. With this PR the row icon stays too, because it reads the same roster. The fix belongs in server session cleanup, so I've kept it out of this PR (see Follow-ups).

Follow-ups

• Server: clear the pending background roster when a session is detached or released, while keeping a replacement session's ownership. That would fix the stale composer banner and the stale row icon.
• Mobile: show the same indicator on mobile thread rows.

Model and harness: Claude Opus 5.5 via Claude Code, running in T3 Code.

🤖 Generated with Claude Code

[macroscopeapp]

Approvability

Verdict: Approved at c655800

Macroscope's review found this PR approvable — This is a small, focused web UI fix that reuses existing background-task state and terminal controls to expose work the product already tracks. It introduces no schema, configuration, infrastructure, or static-analysis changes, and includes targeted coverage for the new display and interaction paths.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Path: .coderabbit.config.ts
• Review profile: CHILL
• Plan: Advanced
• Run ID: 0eda959a-c5dc-4d07-964c-af28b4a9b703

📥 Commits

Reviewing files that changed from the base of the PR and between 511d20c and c655800.

📒 Files selected for processing (6)

• apps/web/src/components/LegacySidebar.tsx
• apps/web/src/components/Sidebar.logic.test.ts
• apps/web/src/components/Sidebar.logic.ts
• apps/web/src/components/Sidebar.tsx
• apps/web/src/components/ThreadStatusIndicators.terminal.test.tsx
• apps/web/src/components/ThreadStatusIndicators.tsx

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

📝 Walkthrough

Walkthrough

The sidebar process status button now reflects pending background command tasks as well as running terminals. Its label distinguishes command and terminal counts, and its click action opens a terminal only when a terminal ID exists.

Changes

Sidebar Process Status

Layer / File(s)	Summary
Resolve running-process labels apps/web/src/components/Sidebar.logic.ts, apps/web/src/components/Sidebar.logic.test.ts	The resolver filters pending tasks to commands. It uses a single command’s trimmed description when available, reports command counts otherwise, and includes terminal counts when terminals are running. Tests cover these label cases.
Display and activate process status apps/web/src/components/ThreadStatusIndicators.tsx, apps/web/src/components/Sidebar.tsx, apps/web/src/components/LegacySidebar.tsx, apps/web/src/components/ThreadStatusIndicators.terminal.test.tsx	The button can appear for pending command work without a terminal. Clicking activates the thread and opens a terminal only when a terminal ID exists. Both sidebar rows pass pending tasks to the button. Tests cover command-only work, terminal work, and excluded task types.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Sequence Diagram(s)

sequenceDiagram
  participant SidebarThreadRow
  participant ThreadTerminalStatusButton
  participant User
  participant TerminalUI
  participant ThreadActivationCallback
  SidebarThreadRow->>ThreadTerminalStatusButton: Pass terminal IDs and pending tasks
  User->>ThreadTerminalStatusButton: Click process status button
  opt A terminal ID exists
    ThreadTerminalStatusButton->>TerminalUI: Reveal terminal
  end
  ThreadTerminalStatusButton->>ThreadActivationCallback: Activate thread

Loading

Suggested reviewers: juliusmarminge

Merge Risk: ⚪ Minimal · up to c6558

The sidebar can show running background commands without opening a nonexistent terminal. No actionable merge risk is identified beyond normal checks.

Pre-merge checks · 4

Passed checks (4 passed)

Check name	Status	Explanation
Title check		The title is concise, specific, and accurately describes the main change: showing the running icon for threads with live background commands.
Description check		The description explains the problem, fix, scope rationale, verification results, limitations, and follow-ups. It uses “## Fix” instead of the template’s “## Change” heading and does not provide a sep…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[StanMan007]

Closing in favor of #15413, which moves threads with a live background command into the Working section. That covers the case this PR was addressing.