claude-code - 💡(How to fix) Fix [2.1.123] `--resume` picker shows "No conversations found" when valid sessions exist; direct UUID resume works [1 comments, 2 participants]

TL;DR

The issue with the claude --resume interactive picker not finding conversations to resume in the project directory can be worked around by using a direct UUID resume or the provided bash script to resume the most recent session.

Guidance

• Verify that the cwd field in the JSONL files matches the current working directory (pwd) exactly, and the encoded project directory name is correctly formatted.
• Check if the issue persists when using the claude --continue command, which also reports "No conversations found".
• Use the provided bash script as a temporary workaround to resume the most recent session in the current project.
• Investigate the possibility of a change in the picker's lookup path or filter in version 2.1.123, which may be causing the issue.

Example

The provided bash script can be used as a workaround:

claude --resume "$(ls -t ~/.claude/projects/$(pwd | sed 's|/|-|g')/*.jsonl \
  | head -1 | xargs basename | sed 's/\.jsonl$//')"

This script resumes the most recent session in the current project by finding the latest JSONL file in the encoded project directory.

Notes

The issue seems to be specific to the claude --resume interactive picker and does not affect direct UUID resume. The cause of the issue is still uncertain, but it may be related to changes in the picker's lookup path or filter in version 2.1.123.

Recommendation

Apply the provided workaround using the bash script to resume the most recent session in the current project, as it provides a reliable way to resume conversations until the underlying issue is resolved.