[DOCS] VS Code extension data storage path undocumented beyond uninstall cleanup

Status Fixed / completed
Maintainer reply ✓ Yes — bcherny
Activity 8 comments · opened Feb 16, 2026 · closed Aug 17, 2026
💡 Likely answer: A maintainer (bcherny, collaborator) responded on this thread — see the highlighted reply below.

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/vs-code

Section/Topic

The path ~/.vscode/globalStorage/anthropic.claude-code/ is mentioned only in the "Uninstall the extension" section as a cleanup target. There is no documentation about what this directory contains or how it relates to conversation history.

Current Documentation

The only mention of this path is in the uninstall section:

To also remove extension data and reset all settings: `` rm -rf ~/.vscode/globalStorage/anthropic.claude-code ``

No other page documents what is stored in this directory.

What's Wrong or Missing?

Users have no documentation explaining:

  1. What's stored in ~/.vscode/globalStorage/anthropic.claude-code/ (conversation history, session state, OAuth tokens, extension data)
  2. How conversation history relates between the extension and CLI — the VS Code page says "The extension and CLI share the same conversation history" but doesn't explain where that history is stored
  3. How to back up or migrate this data when switching machines

A user asking "where are my Claude Code conversations stored?" has no answer in the documentation. The only hint is a destructive rm -rf command in the uninstall section.

Suggested Improvement

Add a brief subsection to either the "Configure settings" section of the VS Code page or to the Settings page under "Other configuration":

Suggested addition:

### Extension data storage The VS Code extension stores conversation history, session state, and extension data in: `` ~/.vscode/globalStorage/anthropic.claude-code/ ` This directory is shared between the VS Code extension and the CLI — conversations started in the extension can be resumed with claude --resume` in the terminal, and vice versa. To back up your conversation history, copy this directory. To reset the extension completely, delete it.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:
| Page | Issue |
|------|-------|
| https://code.claude.com/docs/en/vs-code | Path only mentioned in uninstall section, not explained |
| https://code.claude.com/docs/en/settings | "Other configuration" section mentions ~/.claude.json but not extension storage |

Total scope: 2 pages affected

Users migrating between machines, troubleshooting lost conversations, or auditing what Claude Code stores on disk need this information.

View original on GitHub ↗

8 Comments

coygeek · 5 months ago

Still unresolved as of 2026-03-17. VS Code extension data storage path (~/.vscode/globalStorage/anthropic.claude-code) is only mentioned in the uninstall cleanup section, not as general reference.

coygeek · 5 months ago

I rechecked the current docs today and this gap still seems open. The path is still only surfaced in the uninstall rm -rf example, with no real explanation of what lives there or how it ties into shared conversation history.

coygeek · 4 months ago

Checked against the latest docs mirror — this issue is still unresolved as of 2026-04-27.

coygeek · 3 months ago

Still relevant as of 2026-05-18. This documentation gap has not been addressed in the docs yet.

coygeek · 2 months ago

Verified against the latest docs; this still appears unresolved.

coygeek · 2 months ago

Verified against the latest docs; this still appears unresolved.

BasedGPT · 1 month ago

The uninstall path and the conversation data are two different layers. ~/.vscode/globalStorage/anthropic.claude-code/ is VS Code extension state; the transcript files that the extension and CLI resume are under ~/.claude/projects/<project-slug>/. For a backup or migration, copy both rather than treating the uninstall target as the whole conversation store.

I built BasedGPT/claude-code-session-recovery for the related case where those transcript files survive but entries disappear from the VS Code session list. Run python tools/diagnose.py first; it checks the on-disk files and prints the exact next command for the diagnosis. If it reports missing VS Code cache entries, follow that command with VS Code closed before applying a cache repair.

That distinction also makes the rm -rf example safer to document: it removes extension state, while the transcript files are a separate recovery layer.

Hope this helps, if my tools are able to help you, would appreciate a ⭐ :)

bcherny collaborator · 14 days ago

Conversation history isn't stored in the VS Code globalStorage directory — that folder only holds the extension's own local state and settings. Conversations for both the extension and the CLI live in ~/.claude/projects/<project>/<session>.jsonl, which is why claude --resume in a terminal can pick up an extension conversation. That layout, retention (cleanupPeriodDays), and how to back it up are documented at https://code.claude.com/docs/en/claude-directory, and the sharing note is at https://code.claude.com/docs/en/vs-code#switch-between-extension-and-cli.

Closing as answered.

🤖 Generated with Claude Code