Resume feature doesn't preserve conversation context

Description

When using the --resume flag to continue a previous conversation, Claude Code successfully resumes the session but Claude does not have access to the prior conversation history/context.

Steps to Reproduce

1. Start a conversation in directory /Users/masonmackey/dev/outdoorsy-work
2. Run /resume command which generates: cd /Users/masonmackey/dev/outdoorsy-work && claude --resume 5f57a9e9-ac9e-4c0e-bcaa-bf99665ce359
3. Execute the generated resume command exactly as instructed
4. Claude indicates it doesn't have access to previous conversation history

Expected Behavior

When resuming a conversation using the command generated by Claude Code, Claude should have full context from the previous conversation to continue where it left off.

Actual Behavior

Claude resumes with the same session ID but states: "I don't have access to the previous conversation history from this session."

Debug Findings

Key Discovery: The conversation context is being stored correctly at:
~/.claude/projects/-Users-masonmackey-dev-outdoorsy-work/<session-id>.jsonl

The JSONL file contains the complete conversation history in a structured format with all messages, tool calls, and responses. This confirms the data exists locally.

However, when resuming with the command that Claude Code itself generated, this stored conversation history is not being loaded into Claude's working memory.

Root Cause: The resume mechanism is not loading the conversation context from the .jsonl file, even though:

• The data exists and is accessible
• Claude Code generated the correct resume command
• The session ID matches correctly

Impact

This makes the resume feature significantly less useful since continuity of context is lost. Users must manually re-explain what they were working on, defeating the purpose of the resume functionality.

Technical Details

• Session ID: 5f57a9e9-ac9e-4c0e-bcaa-bf99665ce359
• Storage location verified: ~/.claude/projects/-Users-masonmackey-dev-outdoorsy-work/5f57a9e9-ac9e-4c0e-bcaa-bf99665ce359.jsonl
• File contents confirmed to contain full conversation
• Resume command executed from correct directory as instructed