`claude agents` dashboard dumps entire historical backlog; deleted sessions reappear and orphaned ones can't be opened (v2.1.204)

Summary

On v2.1.204, the claude agents background-sessions dashboard has started displaying the entire accumulated history of completed sessions (dozens, going back ~6 weeks), collapsed into a … N more row. Alongside that, two things appear genuinely broken:

1. Sessions I previously deleted have reappeared.
2. Some completed sessions cannot be opened at all.

This is reproducing across multiple machines that are all on v2.1.204 — so it is not machine-local corruption; it tracks the build.

Environment

• Claude Code v2.1.204
• macOS (Darwin 25.5.0), Apple Silicon
• Installed via Homebrew global (@anthropic-ai/claude-code), autoUpdates: true
• Confirmed on two separate machines, both on v2.1.204

Symptoms

1. Full-history dump. The Completed group now lists the entire backlog of finished sessions (44 completed in my case), with … 41 more folded beneath — including sessions from ~6 weeks ago. It makes the dashboard confusing and hard to use; it's not obvious which sessions are live vs. long-dead.
2. Deleted sessions reappear. Sessions I removed with Ctrl+X in an earlier run are showing up in the list again on a later launch. Deletion does not persist.
3. Some sessions can't be opened. Selecting certain completed rows does nothing — they appear to be orphaned records whose working directory no longer exists.

On-disk findings (from my own machine)

• Background jobs live under ~/.claude/jobs/<id>/. Recent job dirs contain a state.json; old ones (e.g. dated ~6 weeks ago) are empty husks — just an empty tmp/ subdir, no state.json. These orphaned husks line up with the rows that can't be opened.
• A resident daemon (claude daemon run …) maintains ~/.claude/daemon/roster.json and stays running. A roster that outlives per-session deletion is a plausible mechanism for deletions not sticking.

Expected behavior

• The dashboard should not resurface a large backlog of old/orphaned completed sessions by default (some cap, or an explicit "show all history" affordance rather than dumping everything).
• Deleting a session should be durable across restarts.
• Orphaned records (missing state.json / missing working dir) should be pruned, or at least not presented as openable rows.

Impact

The agents dashboard becomes cluttered and confusing — dozens of dead/orphaned sessions mixed with live ones, deletions that don't stick, and rows that error on open. Reproduces on every machine on this build.