/resume should include background sessions (or add a separate picker for them)
Status Fixed / completed
Reported on v2.1.140
Maintainer reply ✓ Yes — claude[bot]
Activity 5 comments · opened May 13, 2026 · closed May 19, 2026
💡 Likely answer: A maintainer (claude[bot], contributor)
responded on this thread — see the highlighted reply below.
Currently Claude Code has two separate UIs for sessions:
/resumeshows only interactive sessions. Background sessions (started via/bgorclaude --bg) never appear in the picker — not even after their job entry has been deleted viaCtrl+X Ctrl+Xinclaude agents.claude agentsshows only sessions that have an active record in~/.claude/jobs/<id>/. AfterCtrl+X Ctrl+Xthe session disappears from there too.
Meanwhile the full JSONL transcript is still on disk at ~/.claude/projects/<encoded-cwd>/<full-session-id>.jsonl, and the session can be revived — but only by knowing the full session id and running from the shell:
claude --resume <full-session-id>This is awkward: to return to a previously-existing background session you have to drop into the filesystem, grep transcripts and copy a UUID, instead of just picking it from a list.
Proposal — one of:
- Add a toggle to
/resume(e.g.Ctrl+G— "show background / orphaned sessions") so the picker also lists them. - Or add a separate command — e.g.
/sessions— listing every JSONL underprojects/regardless of whether ajobs/entry exists. - Or add an "archived / orphaned" tab to
claude agentsfor sessions whose transcript still exists but whose job record has been deleted.
Any of these would close the gap: right now a background session is effectively unreachable from any UI after Ctrl+X Ctrl+X, even though the data is physically present on disk.
Repro
- Start a background session (
/bgorclaude --bg), let it finish. - In
claude agents, select it and pressCtrl+X Ctrl+X(delete). - Open
/resume— the session is not listed. - Open
claude agents— also not listed. - The transcript
~/.claude/projects/<encoded-cwd>/<full-id>.jsonlis still on disk andclaude --resume <full-id>opens it fine.
Environment
- Claude Code CLI version: 2.1.140
- Platform: Linux
5 Comments
+1 on this. The documentation states that deleted background sessions should still be accessible through claude --resume
So I don't know if it's more of a feature request or just a bug. Having to manually search the filesystem for session ID is unintuitive
Adding a data point that suggests this may actually be a documentation/behavior mismatch rather than a missing feature.
The official docs for
claude agentsstate:In practice, after
Ctrl+X Ctrl+Xon a background session inclaude agents:~/.claude/projects/<encoded-cwd>/<full-id>.jsonl,claude --resume(the interactive picker) does not list it — you can only revive it by knowing the full UUID and passing it explicitly:claude --resume <full-id>.So the documented behavior ("remains available through
claude --resume") and the actual UX (only available via raw UUID, not via the picker) are out of sync. This makes the case for treating this as a bug rather than a feature request — the user-visible promise of the docs isn't being delivered.Any of the three options proposed above would close that gap; my preference would still be option 1 (toggle in
/resume), as it keeps everything in one place.+1
Similarly, this affects the ability to meaningfully
/brancha session too, which prevents important use cases inside agent view.This issue was fixed as of version 2.1.144.
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.