[BUG] Claude agents view suddenly show old sessions since v2.1.204
Status Fixed / completed
Reported on v2.1.204
Maintainer reply ✓ Yes — bogini
Activity 5 comments · opened Jul 8, 2026 · closed Jul 8, 2026
💡 Likely answer: A maintainer (bogini, collaborator)
responded on this thread — see the highlighted reply below.
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Yesterday a handful of sessions when I used the left arrow to see the bg agents, now I see a ton more. Claude confirmed:
- On disk, nothing changed about your sessions. ~/.claude/jobs/ still contains only the 5 jobs you dispatched Jul 7–8. No old session was converted into a background agent. - What changed is what the view displays. After last night's 00:28 auto-update to 2.1.204, the list now shows all 26 historical transcripts from ~/.claude/projects/ (across all 6 project dirs, oldest Jun 10 — your ~27-day-old entry) alongside the real background jobs. Since the changelog doesn't mention it, this is either an undocumented change or shipped behind a feature-flag rollout that happened to coincide with the update — the changelog gives no way to distinguish.
driving a bit too fast...
What Should Happen?
Only the 5 jobs should be listed
Error Messages/Logs
Steps to Reproduce
left arrow in claude code
Claude Model
Not sure / Multiple models
Is this a regression?
Yes, this worked in a previous version
Last Working Version
<2.1.204
Claude Code Version
2.1.204
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
iTerm2
Additional Information
_No response_
5 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Ok looks like I did a poor job at searching! Sorry about this, most deffo duplicate of those 3.
If you're hitting this: quit
claudeand start it again — no update needed.Thank you, @bogini ! Two restarts did it as you said in another issue.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.