[BUG] Desktop (Windows): spawn_task suggestion chips never render - tool result says chip is showing but UI shows nothing (2 pending)

Environment

• Claude Code 2.1.205 (embedded CLI reported by claude --version)
• Desktop app on Windows 11 Home 10.0.26200
• Session running in the desktop app's Code tab (win32, PowerShell host)

What happened

During a normal interactive session, the agent called the spawn_task tool twice (a few minutes apart). Both tool results confirmed chip creation on the host side:

Noted (position 1, task_id: task_cb5e436f). A chip is showing for the user — they can start it in a fresh worktree with one click, or dismiss it.

Noted (position 2, task_id: task_854eaeed). ... Currently pending: task_cb5e436f "...", task_854eaeed "..."

However, no chip is rendered anywhere in the desktop UI:

• Nothing in the conversation view (no card above/near the input box, no "Suggested task · 2 queued" header)
• Nothing in the sidebar (Home/Code, routines, dispatch (beta), recent items — checked via screenshot)
• The user explicitly looked for them after being told where chips normally appear and confirmed nothing is shown

So the agent-side registry and the desktop rendering are out of sync: spawn_task reports the chips as pending/visible, but the client never displays them, leaving the suggestions undiscoverable and unstartable from the UI.

Expected

A pending suggested-task chip should be visible (and startable/dismissable) in the conversation view — or at minimum the queued-chips header from #70388 should appear when 2 chips are pending.

Steps to reproduce

1. Desktop app (Windows), interactive session in a project directory
2. Have the agent call spawn_task twice in one session (out-of-scope follow-up suggestions)
3. Observe tool results claim "A chip is showing" with 2 pending task_ids
4. No chip appears anywhere in the client UI

Related

• #70388 — when 2+ chips are queued only the front card is reachable (here even the front card never renders)
• #53494 — cloud-spawned tasks have no discoverable handle in the desktop UI (same symptom class, different spawn path)
• #69677 — background-tasks menu entry hidden when no tasks are running (reduces discoverability of whatever fallback UI exists)

🤖 Generated with Claude Code