[DOCS] `--resume`/`--continue` docs omit sessions found through `/add-dir`
Documentation Type
Missing documentation (feature not documented)
Documentation Location
https://code.claude.com/docs/en/common-workflows
Section/Topic
"Resume previous conversations" and related --continue/--resume behavior for sessions associated through additional working directories added with /add-dir
Current Documentation
The docs currently say:
claude --continuecontinues the most recent conversation in the current directoryclaude --resumeopens a conversation picker or resumes by name Sessions are stored per project directory. The/resumepicker shows interactive sessions from the same git repository, including worktrees.
Related docs describe additional working directories, but not how they affect session discovery:
During startup: use--add-dir <path>CLI argument During session: use/add-dircommand Files in additional directories follow the same permission rules as the original working directory: they become readable without prompts, and file editing permissions follow the current permission mode.
And the changelog for v2.1.118 states:
--continue/--resumenow find sessions that added the current directory via/add-dir
What's Wrong or Missing?
Changelog v2.1.118 documents a user-visible change to how --continue and --resume find prior sessions: they now include sessions that previously added the current directory with /add-dir.
The current resume documentation still frames discovery only in terms of the current directory, project directory, and same-repository/worktree matching. It does not explain that session lookup now also considers sessions linked through /add-dir.
That leaves a gap for users working across multiple directories or repos in one session, because the documented session-discovery model does not match the current CLI behavior.
Suggested Improvement
Update the resume documentation in common-workflows and the CLI reference to describe this discovery rule explicitly.
Suggested addition near the --continue/--resume bullets or the session picker description:
claude --continueandclaude --resumecan also find sessions that previously added your current directory via/add-dir, so shared multi-directory sessions remain discoverable from either side of that relationship.
Also add a short example showing a session started in one directory, expanded with /add-dir ../other-project, then resumed later from ../other-project.
Impact
Medium - Makes feature difficult to understand
Additional Context
Affected Pages:
| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/common-workflows | Primary --continue/--resume behavior and picker scope |
| https://code.claude.com/docs/en/cli-reference | CLI flag reference for --continue, --resume, and --add-dir |
| https://code.claude.com/docs/en/quickstart | Beginner command table still describes claude -c only as current-directory continuation |
| https://code.claude.com/docs/en/permissions | Explains /add-dir and additional working directories, but not the resume/session-discovery implications |
| https://code.claude.com/docs/en/commands | /add-dir command reference that could cross-link to resume/session behavior |
Total scope: 5 pages affected
Source: Changelog v2.1.118
Exact changelog entry:
--continue/--resumenow find sessions that added the current directory via/add-dir
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗