claude-code - 💡(How to fix) Fix claude --continue and --resume show blank session despite valid session data [3 comments, 2 participants]

TL;DR

The issue with claude --continue and claude --resume <session-id> opening a blank session instead of displaying the conversation history may be resolved by verifying the session file integrity and checking for any configuration issues.

Guidance

• Verify that the session files in ~/.claude/projects/<project>/ are correctly formatted and not corrupted, as the presence of valid JSONL data is crucial for resuming sessions.
• Check the permissions and ownership of the session files to ensure they match the expected settings (-rw-------), which could affect how claude accesses these files.
• Consider checking the claude configuration for any settings that might influence how sessions are loaded or resumed, as the issue could stem from a misconfiguration rather than a problem with the session files themselves.
• Test resuming a session with a newly created session file to see if the issue persists, which could help determine if the problem is specific to certain session files or a broader issue with the claude application.

Example

No specific code example is applicable in this case, as the issue seems related to the application's behavior with existing session files rather than a code snippet that needs correction.

Notes

The solution may depend on specifics of the claude application's internal workings, especially how it handles session files and resumes sessions. Without more detailed information on the application's mechanics, the guidance provided is based on general principles of troubleshooting file-based issues.

Recommendation

Apply a workaround by manually verifying and potentially correcting the session file integrity and configuration settings, as this approach allows for a targeted investigation into the cause of the issue without requiring an upgrade or significant code changes.