Skip to content

Separate configuration, cache, and extension data directories according to XDG standards #249641

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
DIMFLIX opened this issue May 23, 2025 · 3 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) triage-needed

Comments

@DIMFLIX
Copy link

DIMFLIX commented May 23, 2025

Currently, VS Code stores not only user configuration, but also cache, logs, extension data, and other temporary files in the .config/Code directory (on Linux). This leads to a situation where the configuration directory can grow to several gigabytes in size. For example, on my machine, the .config/Code folder currently takes up 1.6 GB, which is unexpected for a configuration directory.

This is a significant pain point for users, because:

  • It complicates backup and migration of user settings (users expect to back up only configuration, not all cache and extension data).
  • It makes it hard to manage disk space, since cache and logs are mixed with important settings.
  • It does not follow the XDG Base Directory Specification, which recommends separating configuration (~/.config), cache (~/.cache), and data (~/.local/share) directories.

Proposal:
Please consider splitting the storage of configuration, cache, and extension data according to the XDG Base Directory Specification:

  • Store user settings and configuration in ~/.config/Code
  • Store cache and temporary files in ~/.cache/Code
  • Store extension data and other application data in ~/.local/share/Code

This would greatly improve the user experience, make disk usage more predictable, and align VS Code with standard Linux practices. Many popular applications already follow this approach.

Thank you for considering this feature. I believe it will benefit a large number of users who care about clean and manageable configuration directories.

@gjsjohnmurray
Copy link
Contributor

See also #126182

@bpasero
Copy link
Member

bpasero commented May 24, 2025

/duplicate #3884

@vs-code-engineering vs-code-engineering bot added the *duplicate Issue identified as a duplicate of another issue(s) label May 24, 2025
Copy link

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale May 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
*duplicate Issue identified as a duplicate of another issue(s) triage-needed
Projects
None yet
Development

No branches or pull requests

4 participants