[BUG] --resume fails after /rename when called from different directory

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

After renaming a conversation with /rename, attempting to resume it from a different directory fails to find the conversation. The session lookup appears to be path-dependent even though sessions have unique UUIDs.

What Should Happen?

The conversation should resume successfully regardless of the current working directory. UUID-based lookup should work globally.

Error Messages/Logs

$ cd /different/directory
$ claude --resume <original-session-id>
No conversation found with session ID: <original-session-id>

Steps to Reproduce

1. Start a conversation in /path/A (e.g., /Users/user/project-ocr)
2. Use /rename new_conversation_name to rename the session
3. Exit the conversation
4. cd /path/B (different directory)
5. Run claude --resume <original-session-id>
6. Error: conversation not found

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.17

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

Hypothesis: The /rename command updates the display name but the session lookup mechanism may still be path-dependent or the ID→name mapping isn't fully updated.

Related issue: #19747 reports a similar symptom (session unreachable) but with a different trigger (deleted folder vs rename + cd). Both issues suggest the session resolution is too coupled to the original path.