claude-code - 💡(How to fix) Fix [DOCS] `/resume` docs still describe the session picker as interactive-only and omit background-session support

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/sessions

Section/Topic

"Resume a session," "Where the session picker looks," and "Use the session picker"

Current Documentation

The docs currently say:

| claude --continue | Resumes the most recent session in the current directory | | claude --resume | Opens the session picker | | claude --resume <name> | Resumes the named session directly | | claude --from-pr <number> | Resumes the session linked to that pull request | | /resume | Switches to a different conversation from inside an active session |

Sessions created with claude -p or the Agent SDK do not appear in the session picker, but you can still resume one by passing its session ID to claude --resume <session-id>.

By default the session picker shows interactive sessions from the current worktree, plus sessions started elsewhere that added the current directory with /add-dir.

What's Wrong or Missing?

Claude Code v2.1.144 added /resume support for background sessions.

The current sessions page still describes the picker as showing interactive sessions from the current worktree and does not document that sessions started via claude --bg or agent view now appear there as well.

It also does not mention the new bg marker, so users are not told how to distinguish background sessions from interactive ones in the picker.

Suggested Improvement

Update the resume/session-picker docs to reflect the v2.1.144 behavior.

For example, in the "Where the session picker looks" or "Use the session picker" sections, add a note like:

On Claude Code v2.1.144 and later, the /resume picker also shows background sessions started via claude --bg or agent view alongside interactive sessions. Mark those rows with bg and explain that they can be resumed from the picker the same way as interactive sessions.

If there are scope or filtering differences between interactive and background sessions, document those in the same section.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageLine(s)Context
https://code.claude.com/docs/en/sessions23-35, 61-76/resume entry points and session-picker scope still describe an interactive-only view

Total scope: 1 page affected

Version context: The v2.1.144 changelog at https://code.claude.com/docs/en/changelog says: "Added /resume support for background sessions — sessions started via claude --bg or agent view now appear alongside interactive ones, marked with bg".

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING