Remote session viewer shows stale 'running' tool tasks from dead sessions; dismissal does not persist

Status Closed — not planned
Reported on v2.1.170
Maintainer reply None cached
Activity 1 comment · opened Jun 10, 2026 · closed Jul 18, 2026

Environment

  • Claude Code CLI 2.1.170
  • Windows 11 Home (10.0.26200)
  • Session viewed remotely via the web session viewer while the CLI runs locally

Symptom

The remote session viewer shows 2 tool invocations as still RUNNING — labeled with the tool-call descriptions "Sim 빌드" and "오류 상세" (PowerShell dotnet build commands) — with elapsed times of 29h02m and 24h56m.

  • These originate from a previous session (the CLI session was likely terminated before completion was reported to the service).
  • The current CLI session shows no such tasks (TaskList empty, no background commands running).
  • No corresponding processes exist on the machine — verified: no orphaned MSBuild / dotnet / PowerShell processes (we also ran dotnet build-server shutdown and killed reuse nodes; the stale entries are unrelated to live processes).
  • Force-clearing the entries in the remote viewer works only momentarily — they reappear after the viewer is restarted/refreshed.

Expected

Orphaned task records from dead sessions should be marked terminated (or expire via TTL), and a manual dismissal should persist.

Actual

The stale "running" records resurrect indefinitely after every viewer restart.

Steps to reproduce (presumed)

  1. Run long dotnet build commands via the PowerShell tool in a CLI session.
  2. Terminate the CLI session abnormally before/around tool completion.
  3. Open the remote session viewer → the tool calls show as RUNNING forever.
  4. Dismiss them → restart the viewer → they are back.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗