Awesome CLI! I just noticed this issue while I was using claude code across multiple directories while building mb6611/claude-multi.nvim with recall as a session selector.
Problem:
When a Claude Code session is resumed from a different directory, Claude creates a new file that inherits the parent session's sessionId in its message content but has a different cwd:
Original session file: 096d1a8a.jsonl
{"type":"user", "sessionId":"096d1a8a", "cwd":"/project-a", ...}
Continuation file: 31483d61.jsonl (resumed from different dir)
{"type":"user", "sessionId":"096d1a8a", "cwd":"/project-b", ...}
The old code extracted sessionId from message content, so both files appeared to be the same session. Whichever file was indexed first would set the cwd, causing recall list to show the wrong working directory.
This is leading to the issue:
No conversation found with session ID: 31483d61-c712-46fb-abed-87be8ef08763
Awesome CLI! I just noticed this issue while I was using claude code across multiple directories while building mb6611/claude-multi.nvim with
recallas a session selector.Problem:
When a Claude Code session is resumed from a different directory, Claude creates a new file that inherits the parent session's sessionId in its message content but has a different cwd:
Original session file: 096d1a8a.jsonl
{"type":"user", "sessionId":"096d1a8a", "cwd":"/project-a", ...}Continuation file: 31483d61.jsonl (resumed from different dir)
{"type":"user", "sessionId":"096d1a8a", "cwd":"/project-b", ...}The old code extracted sessionId from message content, so both files appeared to be the same session. Whichever file was indexed first would set the cwd, causing recall list to show the wrong working directory.
This is leading to the issue:
No conversation found with session ID: 31483d61-c712-46fb-abed-87be8ef08763