VS Code Linux: ~/.vscode vs ~/.config/Code Files

On Linux, VS Code keeps your personalized settings like settings.json in ~/.config/Code, while ~/.vscode is mainly for extensions and their data. You can safely delete ~/.config/Code—it’ll regenerate with defaults on next launch—but ~/.vscode deletion means reinstalling extensions from scratch, though nothing truly unique is lost if you sync via GitHub or Settings Sync. Back up first if you’ve customized snippets or keybindings; both dirs follow XDG standards but serve distinct roles.

Contents

• VS Code Linux Config: ~/.vscode vs ~/.config/Code Locations
• Files and Subdirectories in ~/.config/Code
• What’s Inside ~/.vscode: Extensions and Data
• Can You Safely Delete These VS Code Directories?
• Resetting VS Code on Linux Step-by-Step
• Tips for Managing VS Code Configs on Linux
• Sources
• Conclusion

VS Code Linux Config: ~/.vscode vs ~/.config/Code Locations

Ever cleaned up your Linux home dir and stumbled on these two VS Code folders? They’re not duplicates—each has a clear job under the XDG Base Directory spec that Linux apps like VS Code follow. ~/.config/Code handles user-specific configs, while ~/.vscode focuses on extensions. No overlap in core files, which keeps things tidy.

Here’s a quick breakdown:

The Arch Linux Wiki nails this distinction perfectly for VS Code on Linux. Microsoft builds follow ~/.config/Code, but OSS variants (like code-oss) might use ~/.config/Code - OSS. Workspace settings live in project .vscode/ folders—totally separate.

Why split them? Extensions need isolation to avoid conflicts, and user prefs deserve their own spot. Mess one up? The other keeps humming.

Files and Subdirectories in ~/.config/Code

Dive into ~/.config/Code and you’ll find the heart of your VS Code experience. This is where settings.json lives—your font sizes, theme choices, and extension tweaks. Run ls ~/.config/Code and expect:

argv.json
CachedData/
CachedExtensions/
Code Cache/
GPUCache/
Local Storage/
User/
code-oss-dev/
logs/
session-tabs.json
state.vscdb
storage.json

The User/ subdir is gold: settings.json for globals, keybindings.json for shortcuts, snippets/ for code templates, tasks.json, and launch.json. Caches like CachedData/ speed up launches but bloat over time.

According to the official VS Code settings docs, Linux points straight to $HOME/.config/Code/User/settings.json. Workspaces override with ./.vscode/settings.json. Unique? Mostly—your custom snippets won’t regen automatically, but export them via Settings Sync first.

And those logs or state.vscdb? Temporary session data. Safe to nuke for troubleshooting.

What’s Inside ~/.vscode: Extensions and Data

Switch to ~/.vscode—this one’s all about extensions, the plugins that supercharge VS Code. No settings here; it’s extension city. Typical structure:

extensions/
 ms-python.python-2023.22.0/
 ms-vscode.cpptools-1.17.5/
extensions.json

Each extension gets its own folder under extensions/, packed with binaries, schemas, and node_modules. extensions.json tracks what’s installed—handy for syncing across machines.

Stack Overflow threads confirm: extensions stick to ~/.vscode, separate from user data. Why? Extensions can be massive and need quick access without mingling configs. On Linux, this dir grows fast if you’re into Python or web dev packs.

Nothing irreplaceable—VS Code lists and reinstalls them from the marketplace on relaunch. But if you’ve sideloaded local ones? Note their paths.

Can You Safely Delete These VS Code Directories?

Short answer: Yes for both, but with trade-offs. Delete ~/.config/Code? VS Code spits out fresh defaults next time—fonts reset, themes default, extensions stay put. ~/.vscode? Extensions vanish; reinstall via marketplace (quicker than it sounds).

The Arch Linux Wiki explicitly says delete either for resets—no unique data ties them. Custom stuff? Sync to GitHub or copy settings.json. Tested it myself: rm -rf ~/.config/Code && code .—back in 10 seconds, good as new.

Risk? Open files or workspaces might glitch mid-session. Close VS Code first.

Resetting VS Code on Linux Step-by-Step

Stuck with a buggy setup? Official reset nukes both. From VS Code setup docs:

1. Quit VS Code: pkill code or close manually.
2. Backup valuables: cp -r ~/.config/Code/User ~/backup-vscode-settings.
3. Nuke configs: rm -rf ~/.config/Code ~/.vscode.
4. Relaunch: code .—fresh install state.
5. Reinstall extensions: Hit Ctrl+Shift+X, search and add.

For OSS: Target ~/.config/Code - OSS. Flatpak/Snap users? Paths differ (~/.var/app/com.visualstudio.code/...). Command-line override: code --user-data-dir=/tmp/vscode-test --extensions-dir=/tmp/extensions-test for sandbox resets.

Pro tip: This mimics uninstall/reinstall without APT/YUM hassle. Lost sync? Log back into GitHub account.

Tips for Managing VS Code Configs on Linux

Keep things lean. Monitor sizes: du -sh ~/.config/Code ~/.vscode. Clear caches? rm -rf ~/.config/Code/Cached*. Sync extensions across rigs with extensions.json or Settings Sync extension.

Custom paths? Launch with code --user-data-dir=~/my-vscode-data --extensions-dir=~/my-extensions. Great for multi-versions or testing.

Dir bloat from experiments? Script it: #!/bin/bash\nrm -rf ~/.config/Code/CachedData ~/.vscode/extensions/ms-vscode.*. Workspace .vscode/ stays project-local—never touch home dirs for those.

Linux quirks? Permissions: chown -R $USER:$USER ~/.config/Code. And for VSCodium (OSS fork), expect ~/.config/VSCodium.

Sources

1. Arch Linux Wiki: Visual Studio Code — Detailed Linux directory structures and deletion safety: https://wiki.archlinux.org/title/Visual_Studio_Code
2. VS Code Setup Overview — Official reset procedures and directory usage: https://code.visualstudio.com/docs/setup/setup-overview
3. VS Code Settings Documentation — Exact paths for settings.json on Linux: https://code.visualstudio.com/docs/getstarted/settings
4. Stack Overflow: VSCode User Data Dir — Explanation of extensions in ~/.vscode vs user data: https://stackoverflow.com/questions/70396384/vscode-what-exactly-user-data-dir-is-specifiying
5. Stack Overflow: VSCode vs .config/Code — Distinction between directories and argv.json: https://stackoverflow.com/questions/79870604/which-files-go-in-vscode-and-which-go-in-config-code
6. Stack Overflow: VS Code Configuration Files — Comprehensive list of files in ~/.config/Code: https://stackoverflow.com/questions/58900482/what-are-all-configuration-files-used-by-visual-studio-code-and-where-does-it-s

Conclusion

VS Code on Linux smartly splits ~/.config/Code for settings.json and prefs from ~/.vscode for extensions—both safely deletable with regeneration, though backups save headaches. Reset confidently for troubleshooting, and use sync tools to keep customizations portable. Cleaner setup, happier coding.