claude-code - 💡(How to fix) Fix /resume should search sessions globally across all project directories

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…

Root Cause

Sessions are stored centrally in ~/.claude/projects/ — the data is already there. The directory-scoped filtering in the UI is the only thing preventing global access. Users who work across many projects have no way to find an old session without knowing exactly which directory it was started from.

Fix Action

Fix / Workaround

Workaround (current)

A custom /ses slash command + shell wrapper that reads ~/.claude/projects/*/*.jsonl directly and uses fzf for arrow-key navigation, writing a pending session ID to a file that a claude() shell wrapper picks up on exit to auto-resume in the same terminal tab. This works but requires exiting the current session first and relies on undocumented internal file formats.

RAW_BUFFERClick to expand / collapse

Feature Request

Current behavior

/resume (and the interactive picker) only shows sessions associated with the current working directory. If you start Claude from a different directory, you cannot see or resume sessions from other projects.

Expected behavior

/resume should show all sessions regardless of which directory Claude was launched from, with the ability to search/filter by title or date.

Why this matters

Sessions are stored centrally in ~/.claude/projects/ — the data is already there. The directory-scoped filtering in the UI is the only thing preventing global access. Users who work across many projects have no way to find an old session without knowing exactly which directory it was started from.

Suggested solution

  • Add a flag or setting (e.g. CLAUDE_RESUME_GLOBAL=1) to disable directory filtering in /resume
  • Or: make /resume global by default, with an optional filter to narrow to the current project

Workaround (current)

A custom /ses slash command + shell wrapper that reads ~/.claude/projects/*/*.jsonl directly and uses fzf for arrow-key navigation, writing a pending session ID to a file that a claude() shell wrapper picks up on exit to auto-resume in the same terminal tab. This works but requires exiting the current session first and relies on undocumented internal file formats.

Platform

  • macOS (Apple Silicon)
  • Claude Code CLI

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…

FAQ

Expected behavior

/resume should show all sessions regardless of which directory Claude was launched from, with the ability to search/filter by title or date.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix /resume should search sessions globally across all project directories