Detailed Analysis
A widely reported bug in Anthropic's Claude Code Visual Studio Code extension causes chat history to become invisible within the plugin's interface, even when that same history remains fully accessible via the command-line interface using `claude --resume`. The user's experience — seeing complete session history in the terminal but a blank slate in the extension — is consistent with a documented class of failures tracked across multiple GitHub issues, including issues #9258, #22215, #29017, and others filed against the `anthropics/claude-code` repository. The root cause is not data loss; session files, stored as `.jsonl` files alongside a `sessions-index.json` index in `~/.claude/projects/`, remain intact on disk. The failure occurs at the extension's indexing or rendering layer, where the plugin fails to correctly surface those files in its graphical panel.
Several specific triggers have been identified through community investigation. Closing and reopening VS Code windows or tabs is a common precipitating event, causing the extension to lose track of previously loaded sessions despite the underlying files being untouched. Projects accessed via symlinked paths — for instance, `~/repositories/project` pointing to a real path like `/mnt/data/repositories/project` — frequently produce this behavior, as the extension resolves paths differently than the CLI. Non-ASCII characters in directory names, such as diacritical marks, have similarly been shown to block session visibility. Corruption of or failures to write to `sessions-index.json` represent another vector, effectively breaking the extension's internal session catalog even when individual `.jsonl` conversation files are valid.
The practical workarounds available to affected users span both official and community-developed solutions. Within the extension itself, users should confirm they are clicking the **Session history** button in the Claude Code panel and that they are running VS Code version 1.80.0 or later with the Claude Code CLI properly installed. Enabling debug logging in extension settings can surface indexing errors that are otherwise silent. For more persistent failures, two third-party VS Code marketplace extensions — **Claude Code and Codex Assist** and **Claude Chats** — provide alternative history browsers that read directly from the `~/.claude/projects/` directory, bypassing the official extension's indexing layer entirely, with additional features such as keyword search, cost tracking via SQLite, session archiving, and grouped browsing by project or date.
This issue sits within a broader pattern of friction emerging at the boundary between Anthropic's CLI-first tooling and the graphical IDE integrations built on top of it. Claude Code was designed primarily as a terminal-based agentic coding tool, and its VS Code extension layers a graphical interface over an architecture that was not originally built for it. The divergence in how the CLI and the extension handle session resolution — where the terminal robustly finds history while the GUI silently fails — reflects the technical debt typical of rapidly extended developer tools. The proliferation of community-built workaround extensions on the VS Code marketplace signals that the official tooling has not yet fully addressed the reliability expectations of users who prefer GUI-based workflows.
More broadly, the episode illustrates a recurring challenge for AI companies releasing developer-facing products at speed: integrations with established environments like VS Code introduce surface area for platform-specific bugs — path resolution differences across operating systems, symlink handling, Unicode edge cases — that are difficult to anticipate and slow to patch. With Claude Code having reached version 2.0.13 at the time these issues were actively reported in late 2025, the persistence of a fundamental UI feature failure across Windows, macOS, and Linux underscores the difficulty of maintaining quality across heterogeneous developer environments while simultaneously advancing the underlying model and agentic capabilities. Users encountering the issue are best served in the near term by verifying CLI accessibility as a diagnostic step and routing around the extension where necessary.
Read original article →