Background tasks panel shows long-completed agent tasks stuck under 'Running' (Claude Desktop, macOS)

Open 💬 3 comments Opened Jul 6, 2026 by alon-ne

Platform: Claude Desktop app, macOS

Description:

The "Background tasks" side panel is showing ~19 entries under a "Running" section, several with elapsed timers well past 5 hours (e.g. "5h 01m 20s", "5h 01m 02s", "5h 00m 51s", "5h 00m 49s", "5h 00m 42s", "5h 00m 32s" — see attached screenshot), including entries like "Placeholder while background agents run" and "Placeholder while waiting for background agent".

These correspond to research agents I dispatched earlier in a long-running session (a multi-repo migration task) that have long since completed and returned their results in the conversation. From inside the session, running ps aux on the host shows no actual running processes corresponding to these tasks — everything has finished. Only one task in the session is genuinely still pending (waiting on an external CI build to finish).

So the panel appears to be stuck displaying stale "Running" state for tasks that actually completed a long time ago, rather than refreshing to reflect their real (completed) status. The elapsed-time counters continuing to climb (5h+) suggests the panel's timer for these entries never stopped when the underlying task finished.

Expected behavior: Completed background agent tasks should move out of the "Running" section (or show a completed/stopped state) once they actually finish, rather than continuing to display an incrementing running-time indicator indefinitely.

Steps that led here: Long session (several hours) involving many sequential/parallel Agent tool calls (research subagents) and background Bash calls across a multi-repo code migration task, interleaved with ScheduleWakeup waits for external CI. The stale "Running" entries accumulated over the course of the session as agents completed.

Screenshot attached showing the "Background tasks" panel with the affected entries.

View original on GitHub ↗

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