Renamed session (/rename) not appearing in --resume/`/resume` picker or `claude agents`, despite session data being intact on disk

Description
After a long session, I ran /rename to give it a custom title before exiting. When I later tried to resume it from the same project directory (via claude --resume) it did not appear in the picker. It also doesn't show up under claude agents.

Verified the session data is intact
Inspecting the session's .jsonl transcript directly in ~/.claude/projects/<project-dir>/ confirms:

• The session file exists in the correct project directory, last modified recently (786 messages, ~1.7MB — the longest/most active session from that day).
• It contains a "type":"custom-title","customTitle":"sphinx-upgrade-course-repo" entry, confirming the /rename was recorded correctly.
• The /rename command's stdout (Session renamed to: sphinx-upgrade-course-repo) is present in the transcript.

Despite this, the session is absent from:

1. The claude --resume / /resume picker, run from the same working directory the session was created in.
2. claude agents.

Expected behavior
A renamed session with intact transcript data in the correct project directory should appear in claude --resume.

Workaround
Resuming directly by session ID works: claude --resume <session-id>.

Environment

• Platform: Linux
• Claude Code CLI