Background tasks stuck "running" forever in CLI conversation; cannot cancel, and /feedback cannot report it

Summary

Background commands launched in a Claude Code CLI session (run_in_background) can get permanently stuck as "running." The Claude Desktop app (which mirrors CLI conversations) then shows a persistent "N running tasks" badge, and the conversation hangs indefinitely on any new message. The underlying processes finished long ago — only the task bookkeeping is stale, and there is no user-facing way to clear it.

Environment

• Claude Desktop 1.12603.x (Windows 11, MSIX/Store build)
• Claude Code CLI; CLI conversations auto-mirror into the Desktop app

Steps to reproduce

1. Run a long Claude Code CLI session that launches several run_in_background commands.
2. Have the session move on (or be interrupted) before some of those tasks' completion events are recorded.
3. Open that conversation in the Claude Desktop app.

Expected

Orphaned background tasks reconcile to a terminal state (failed/stopped) when their owning session ends or is interrupted; the conversation stays usable.

Actual

The tasks stay "running" forever. Desktop shows a stuck "N running tasks" badge and the conversation hangs ("thinking" indefinitely) on every new message. There is no control to cancel them (they are not live anywhere — there is nothing left to stop).

Not fixed by

• Fully quitting and cold-restarting the Desktop app
• Updating the Desktop app to the latest version
• Clearing/rebuilding the app's local IndexedDB (state re-syncs identically)

Not data loss / not account corruption

The affected conversation is fully resumable via the CLI and its content is intact — confirming this is purely stale task-state, not a corrupted or lost conversation.

Second, related bug

The in-CLI /feedback reporter attaches the entire conversation transcript, so you cannot report this from the affected (hanging) conversation — the reporter itself stalls trying to load it, and it forces sending the full transcript regardless. Please allow submitting feedback without loading/attaching the whole transcript.

Suggested fixes

• Reconcile orphaned background tasks to failed/stopped when their session ends or is interrupted.
• Add a "cancel stuck task" control in the Desktop task panel.
• Let /feedback submit without loading/attaching the full transcript.