claude-code - 💡(How to fix) Fix VS Code extension session history missing old sessions [2 comments, 2 participants]

TL;DR

The VS Code extension's session history picker may not be correctly reading or processing the existing session data from the ~/.claude/projects/<project>/ directory.

Guidance

• Verify that the session data files (.jsonl files) in the ~/.claude/projects/<project>/ directory are correctly formatted and not corrupted.
• Check the VS Code extension's configuration and settings to ensure it is pointing to the correct directory for session history.
• Investigate if there are any differences in how sessions created from the VS Code extension versus the desktop app are stored or formatted that could be causing the issue.
• Review the extension's code for any potential bugs or limitations in reading session history, particularly for sessions created from within the VS Code extension itself.

Example

No specific code example can be provided without more details on the extension's implementation, but checking the file system access and data parsing logic in the extension's codebase may be a good starting point.

Notes

The issue seems to be specific to the VS Code extension's ability to read or display its own session history, as sessions from the desktop app are visible in the desktop app's history. The fact that session data exists on disk but is not visible in the VS Code extension suggests a potential issue with how the extension reads or processes this data.

Recommendation

Apply a workaround by manually checking the ~/.claude/projects/<project>/ directory for session files and attempting to load them manually in the VS Code extension, if possible, to verify if the issue is with the extension's session history display logic rather than the session data itself.