[BUG] Session shows as working (running timer + busy spinner + active work-tracker) while idle awaiting user input

Resolved 💬 2 comments Opened Jun 26, 2026 by Pero122 Closed Jun 30, 2026

Summary

After a long multi-tool turn completes and the assistant returns control to the
user, Claude Code keeps the session flagged as actively working — the elapsed
timer next to the reply keeps counting, the bottom status bar keeps a busy spinner,
and the work-tracker sidebar ("currentActiveWork") keeps the item marked
in-progress — even though nothing is running and the input box is empty/awaiting
input.

Environment

  • Claude Code version: 2.1.193
  • Model: Opus 4.8 (1M context), Ultracode mode enabled
  • OS: macOS (Darwin 25.3.0)
  • Surface: Claude Code app UI (shows the "currentActiveWork" / "parkedWork"

work-tracker sidebar + a context-window widget)

Steps to reproduce

  1. Run a long turn with many sequential tool calls (file reads/writes + shell commands).
  2. Let the assistant finish its final message and yield control back to the user.
  3. Observe the elapsed timer, the bottom status bar, and the work-tracker sidebar.

Expected

When the turn ends and the assistant is idle awaiting user input, the elapsed timer
stops and the status returns to idle/ready; the work-tracker should not show the
session as actively working.

Actual

  • Elapsed timer keeps incrementing (observed "5m 14s" and counting) while idle
  • Bottom status bar keeps showing a busy spinner
  • Work-tracker sidebar keeps the session item flagged as in-progress

There was genuinely no background job, agent, or workflow running at the time — the
session was idle, so the "working" indicators are stale state that never reset on
turn completion.

Impact

Misleading — the UI implies ongoing work (and possibly active billing/usage) when
the session is idle, and makes the work-tracker unreliable for seeing what is
actually active.

Notes

Screenshots of the running timer, busy status bar, and work-tracker sidebar are
available and can be attached.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗