Cloud-agent sessions stuck at 'Ready for review' after PRs are merged; clutters welcome dashboard

Resolved 💬 2 comments Opened May 11, 2026 by SongOfTheFates Closed May 11, 2026

Summary

The remote/cloud-agent sessions list on the welcome dashboard (the "Pull requests" section under "Welcome back, [name]") accumulates entries indefinitely. Each session that produces a PR enters the "Ready for review" state and remains there permanently, even after the corresponding GitHub PR has been merged (and the branch deleted).

After ~6 weeks of active development with frequent cloud-agent usage, this list has grown to 14+ stale entries and is now pushing the token-usage widget off-screen.

Expected

One of:

  • When the linked GitHub PR is merged or closed, the session auto-archives.
  • A visible bulk-dismiss / "archive all reviewed" control on the dashboard.
  • An explicit per-session archive action that's easy to find.

Actual

  • Entries persist indefinitely after the underlying PR is merged.
  • No visible bulk-clear control on the dashboard.
  • Session lifecycle appears fully decoupled from GitHub PR lifecycle — no webhook back from GitHub closing the loop.

Repro

  1. Use cloud agents to produce a series of PRs.
  2. Merge those PRs on GitHub through the normal flow.
  3. Return to the welcome dashboard — every session is still listed as "Ready for review".

Additional observations

  • Several sessions share identical titles (e.g. seven entries all titled "Optimize CPU throughput for battle resolution", three titled "Evaluate plan from buzzing snowflake file"). Either parallel spawns are not deduplicated, or the title-generation logic is producing collisions that the UI doesn't disambiguate.
  • The dashboard slot where the token-usage widget normally lives is consumed by this list once it grows past a few entries, which is the main practical pain point.

Note on repo

Filing here because it's the documented feedback channel; the actual surface is the claude.ai / desktop dashboard rather than the Claude Code CLI. Please redirect to the right tracker if there is one.

View original on GitHub ↗

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