FleetView: session stuck on "generating" animation indefinitely after a self-paced ScheduleWakeup loop ends

Open 💬 0 comments Opened Jun 11, 2026 by metacoding

Summary

In FleetView (desktop multi-session view), a session's activity ("generating") indicator in the Recents list animates indefinitely and never returns to idle — even when the session has no active turn, no running tools, and no background work. It continued animating overnight while I worked in a different session.

Environment

  • Claude Code 2.1.170, FleetView desktop (multi-session)
  • macOS (Darwin 25.5)
  • Model: Opus 4.8

What preceded it

  1. The agent used a self-paced loop via ScheduleWakeup (delay ~270s) to wait on a background workflow.
  2. The wake-up fired once and re-invoked the agent.
  3. The agent did not reschedule — the loop ended normally.
  4. Several normal user turns followed and completed.
  5. From that point on, the session's activity indicator stayed in the animated "generating" state and never cleared.

Verified nothing is actually running

  • CronList empty; no scheduled tasks; no todo tasks.
  • A full process scan shows no agent-spawned processes alive (only an unrelated session's MCP servers were running).
  • The session is idle between turns yet still displays as active/generating.

Expected vs. actual

  • Expected: the activity indicator returns to idle once the self-paced loop ends and the turn completes.
  • Actual: it remains animated indefinitely.

Impact

Cosmetic but confusing: you can't tell whether a session is genuinely doing work, and a perpetually "generating" session implies hidden activity/cost when there is none.

Suspected cause

Teardown of a ScheduleWakeup / self-paced loop does not appear to clear the session's active-turn state in FleetView, leaving the activity indicator latched on. (Hypothesis — the observable facts above are what's confirmed.)

View original on GitHub ↗