claude-code - 💡(How to fix) Fix [BUG] Background task chip stuck in "Running" state; Stop button has no effect

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

Title: Background task chip stuck in "Running" state; Stop button has no effect

Summary A task chip in the running-tasks panel is permanently stuck. The chip shows ever-increasing elapsed time, but clicking its Stop button does nothing, and no underlying process actually exists. The only way I've found to make it disappear would be to never have the panel exist — but I can't dismiss the entry.

Actual behavior The chip is permanently stuck and accumulates wall-clock minutes forever. In my case it now shows ~2721 minutes (~45 hours) for a process that was killed two days ago. No way to dismiss it from the UI.

Workarounds attempted (none worked):

Clicking the Stop button on the chip Asking Claude in chat to stop it (Claude reported the task ID is already gone server-side — nothing to act on) Hard refresh of the Claude Code window Impact Cosmetic, but caused real confusion: I thought something was actually still consuming CPU/memory from my machine and spent time investigating with Claude before learning the chip is a ghost referring to nothing. Smaller issue but breaks trust in the panel as a source of truth — if a "Running" chip can refer to nothing, I can no longer rely on the panel to tell me what's actually using my machine.

Environment

Claude Code (desktop app) macOS Suggested fix When the user clicks Stop and the underlying task can't be found, the client should still clear the chip from the UI state instead of treating it as a no-op. Or periodically reconcile the panel against the server's task list and remove dead entries automatically.

What Should Happen?

It should close (kill) the task.

Error Messages/Logs

Steps to Reproduce

Steps to reproduce

Have Claude Code run a long-running shell command in the background during a conversation (in my case, a dev server: npm run dev). End that session. Re-open Claude Code days later in the same workspace/project. Notice the task chip is still listed as "Running" in the panel, with the elapsed-time counter still ticking up. Click the Stop button on the chip — nothing happens. Chip stays. Confirm in a terminal (ps, lsof) that no such process is actually running — the chip is referring to a process that was killed days ago. Expected behavior Clicking Stop should remove the chip from the panel, even when no underlying process exists anymore. Or the panel should auto-prune entries whose backing processes are dead.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Claude 1.8089.1 (b98a06) 2026-05-19T18:28:48.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response