Allow /resume to find sessions across all projects

[lasthalf]

Problem

When you start a conversation in one directory and later realize the work applies to a different project/repo, there's no way to resume that session from the new directory. Sessions are scoped to the cwd at launch, so /resume only shows sessions from the current project directory in ~/.claude/projects/.

This comes up frequently when:

• Work spans multiple repos
• You realize mid-conversation you're in the wrong directory
• You switch from a worktree back to the main repo (or vice versa)

Current workaround

Manually copy .jsonl files and session subdirectories between ~/.claude/projects/ directories, then /resume from the target directory:

cp ~/.claude/projects/<source-project-dir>/*.jsonl ~/.claude/projects/<target-project-dir>/
cp -r ~/.claude/projects/<source-project-dir>/<session-uuid> ~/.claude/projects/<target-project-dir>/

This works but is tedious and requires understanding the internal project directory naming scheme.

Proposal

Allow /resume to optionally search across all projects — either:

• By default when no local sessions match
• Via a flag like /resume --all to show sessions from all projects
• By accepting a session ID directly, regardless of which project it belongs to

[github-actions]

Found 3 possible duplicate issues:

1. [Feature Request] Cross-directory session resumption support #39408
2. Allow resuming conversations from different directories #28745
3. [BUG] --resume should not require matching working directory #38089

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically closed as a duplicate of #39408.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[github-actions]

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.