claude-code - 💡(How to fix) Fix Feature request: list/resume Claude Code sessions across all project directories [1 participants]

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…
GitHub stats
anthropics/claude-code#60573Fetched 2026-05-20 03:55:03
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×3

Fix Action

Fix / Workaround

Why

  • Easy to lose track of which dir a useful conversation lived in.
  • The session data is already on disk and already has AI-generated titles — the picker UI just needs to look beyond cwd.
  • The lossy /- encoding of project paths makes a reliable user-space workaround impossible without also storing/reading the real cwd from inside the JSONL.
RAW_BUFFERClick to expand / collapse

Problem

claude --resume and claude --continue only operate on sessions in the current working directory. There's no built-in way to see or resume sessions across all projects on a machine.

If I don't remember which directory I was in when a conversation happened, my only options today are:

  • cd around guessing, running claude --resume in each candidate, or
  • write a custom script that walks ~/.claude/projects/*/*.jsonl, reads each file's ai-title entry, and reconstructs the original project path from the encoded directory name (which is lossy when paths contain hyphens).

Proposal

A built-in command or flag for a global session picker, e.g.:

claude --resume --all # picker across every project dir claude sessions list # non-interactive listing claude sessions list --json # for scripting

Each entry should show the same info as today's per-dir picker (AI title, last-modified time, message count) plus the originating project directory.

Why

  • Easy to lose track of which dir a useful conversation lived in.
  • The session data is already on disk and already has AI-generated titles — the picker UI just needs to look beyond cwd.
  • The lossy /- encoding of project paths makes a reliable user-space workaround impossible without also storing/reading the real cwd from inside the JSONL.

Environment

  • claude-code CLI, Linux

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

claude-code - 💡(How to fix) Fix Feature request: list/resume Claude Code sessions across all project directories [1 participants]