claude-code - 💡(How to fix) Fix [DOCS] `/resume` documentation conflicts on picker scope and displayed summary text [1 participants]

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/common-workflows

Section/Topic

"Resume previous conversations" / "Use the session picker"

Current Documentation

The docs currently say:

Sessions are stored per project directory. The /resume picker shows interactive sessions from the same git repository, including worktrees. When you select a session from another worktree of the same repository, Claude Code resumes it directly without requiring you to switch directories first. Sessions created by claude -p or SDK invocations do not appear in the picker, but you can still resume one by passing its session ID directly to claude --resume <session-id>.

| A | Toggle between current directory and all projects |

• Session name or initial prompt

But how-claude-code-works still says:

Each Claude Code conversation is a session tied to your current directory. When you resume, you only see sessions from that directory.

What's Wrong or Missing?

The current /resume docs describe three different scopes without reconciling them: current directory only, same git repository/worktrees, and an all-projects view. That leaves it unclear what claude --resume, /resume, and named-session resume are actually expected to search.

The picker metadata description is also outdated. common-workflows still says the picker shows a "session name or initial prompt", but changelog work in v2.1.97 explicitly references a conversation-summary surface (task-status text replacing conversation summary) and cross-project behavior. The docs should describe the intended summary text shown in the picker instead of the older "initial prompt" wording.

Suggested Improvement

Update the /resume documentation to define the picker behavior in one place:

1. Explain the default scope clearly: current directory vs same repository/worktrees vs all-projects toggle.
2. Clarify how claude --resume <name> and /resume <name> resolve named sessions when matches exist outside the current directory.
3. Replace "session name or initial prompt" with the actual picker summary behavior (for example, session name when present, otherwise the conversation summary/recent prompt text shown in the picker).
4. Update how-claude-code-works so it no longer contradicts common-workflows about resume visibility.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

Total scope: 3 pages affected

Source: Changelog v2.1.97

Exact changelog entry: Fixed several /resume picker issues: --resume <name> opening uneditable, Ctrl+A reload wiping search, empty list swallowing navigation, task-status text replacing conversation summary, and cross-project staleness