Desktop: queued background-task chips — only the front chip is reachable; no way to access the ones behind
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report
- [x] I am using the latest version of Claude Code
Environment
- Claude Code Desktop (macOS)
- CLI version reference:
2.1.37(desktop app build may differ — reported from the same machine)
What's Wrong?
When two (or more) background-task suggestion chips are queued, the chip header reads e.g. "Suggested task · 2 queued", but only the front card is interactive. Its × (dismiss) and Start locally are the only controls, and there is no next/previous affordance to bring the card(s) behind it forward. As a result you cannot view or act on the second queued task without first dismissing or starting the front one.
Reproduction
- In a Desktop session, get Claude to produce two background-task suggestions (so the chip reads "Suggested task · 2 queued").
- Look at the stacked chip.
Expected
Some way to reach the queued items behind the front one — a next/prev control, an expand-to-list, or all cards individually clickable.
Actual
Only the front card is interactive (× / Start locally). The second card sits visually behind it with no navigation affordance, so it can't be opened or started until the front card is dismissed or started.
Impact
The only workaround is to act on the front card (losing it, or launching it) to promote the next one. There is no non-destructive way to inspect or start a task that isn't at the front of the queue.