# VSCode secret folder hitting disk quota

**URL:** <https://forum.access-hive.org.au/t/vscode-secret-folder-hitting-disk-quota/6991>\
**Category:** Technical\
**Tags:** help, community-help\
**Created:** [15 September 2026 23:05 UTC](https://forum.access-hive.org.au/t/vscode-secret-folder-hitting-disk-quota/6991 "2026-09-15T23:05:59Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![JuliaN](https://avatars.discourse-cdn.com/v4/letter/j/74df32/32.png) [@JuliaN](https://forum.access-hive.org.au/u/JuliaN)\
**Post date:** [15 September 2026 23:05 UTC](https://forum.access-hive.org.au/t/vscode-secret-folder-hitting-disk-quota/6991/1 "2026-09-15T23:05:59Z")

</div>

For all of you using vscode out there, how do you deal with the `.vscode-server` directory in your home directory? It is making me exceed my allocation very regularly and it is a bit cumbersome.

---

<div class="post-metadata">

**Author:** ![Benoit](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/benoit/32/3115_2.png) [@Benoit](https://forum.access-hive.org.au/u/Benoit)\
**Post date:** [16 September 2026 00:30 UTC](https://forum.access-hive.org.au/t/vscode-secret-folder-hitting-disk-quota/6991/2 "2026-09-16T00:30:41Z")

</div>

My solution was to regularly delete it and let VSCode reinstall vscode-server. FWIW I haven’t had to do this in a little while, because I think Microsoft might have improved vscode-server to grow less in latest versions, but not sure.

---

<div class="post-metadata">

**Author:** ![Aidan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aidan/32/42_2.png) [@Aidan](https://forum.access-hive.org.au/u/Aidan)\
**Post date:** [16 September 2026 00:30 UTC](https://forum.access-hive.org.au/t/vscode-secret-folder-hitting-disk-quota/6991/3 "2026-09-16T00:30:59Z")

</div>

VSCode leaves around lots of copies of stuff in `.vscode-server/cli/servers`. I’ve often gone and manually removed all but the most recent, but I can’t guarantee that won’t[delete some customisation settings](https://stackoverflow.com/questions/58453967/visual-studio-code-remote-ssh-vscode-server-is-taking-up-a-lot-of-space).

There is an VSCode extension that claims to address some of these issues:

> **[VS Code Bloat Cleaner - Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=SilverServers.vscode-bloat-cleaner)**
>
> Extension for Visual Studio Code - Keeps VS Code server disk usage in check by automatically cleaning old server versions, duplicate extensions, logs, caches, and orphaned workspace storage.

I just installed it and it seemed to clean up old servers and reduced space used from 3.2G to 1.1G.

---

<div class="post-metadata">

**Author:** ![JuliaN](https://avatars.discourse-cdn.com/v4/letter/j/74df32/32.png) [@JuliaN](https://forum.access-hive.org.au/u/JuliaN)\
**Post date:** [16 September 2026 01:00 UTC](https://forum.access-hive.org.au/t/vscode-secret-folder-hitting-disk-quota/6991/4 "2026-09-16T01:00:03Z")

</div>

Oh that looks promising @Aidan ! I think I messed up my vscode though because I straight deleted everything in the server folder and now I can’t open sessions. Ugh

---

<div class="post-metadata">

**Author:** ![CharlesTurner](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/charlesturner/32/2518_2.png) [@CharlesTurner](https://forum.access-hive.org.au/u/CharlesTurner)\
**Post date:** [16 September 2026 01:21 UTC](https://forum.access-hive.org.au/t/vscode-secret-folder-hitting-disk-quota/6991/5 "2026-09-16T01:21:52Z")

</div>

I have no idea if this works for VS Code specifically, but there’s a thing called `XDG Config` which might help solve this.

The TLDR; is that config, by default, goes in `~/.config`. If a system supports it (and this is the bit where I don’t know if VS Code will specifically or whether Gadi will ignore it (I don’t think it will), you could configure it:

ie. `export XDG_CONFIG_HOME="/scratch/p73/ct1163/.config"` in bash config would move my config to scratch.

Obviously moving all of your persistent config to scratch might not necessarily be the best idea. You might find moving it to your area in a project might work?

TBH, this is fraught with potential issues, but if you have a safe place to put your config it might be helpful. Take this as a ‘maybe worth exploring’ rather than a suggestion!

N.B. A cursory search indicated that to configure your `vscode-server` path you might want to instead do eg. (on your local machine):

```auto
{
  "remote.SSH.serverInstallPath": {
    "gadi": "/scratch/p73/ct1163/.vscode-server"
  }
}

```

If you’re having to continually delete and reinstall VS Code to make this work, then there’s probably no harm in doing this specifically. I’ve left the XDG config stuff in as it’s also useful to know about - `~/.config` can often get surprisingly large.

---

<div class="post-metadata">

**Author:** ![mlipson](https://avatars.discourse-cdn.com/v4/letter/m/5f8ce5/32.png) [@mlipson](https://forum.access-hive.org.au/u/mlipson)\
**Post date:** [16 September 2026 03:19 UTC](https://forum.access-hive.org.au/t/vscode-secret-folder-hitting-disk-quota/6991/6 "2026-09-16T03:19:03Z")

</div>

There is a setting to define where .vscode-server is installed, and I’ve had that on /scratch/ for some time without apparent issue (I guess the old files get deleted after some time, but it hasn’t caused me issues so far).

Go to your vscode settings, then search “Server Install Path” and select add.

Alternatively, in your user settings.json add:

```auto
    "remote.SSH.serverInstallPath": {
        "gadi.nci.org.au": "/scratch/<your_project_and_user_path>"
    },

```

---

<div class="post-metadata">

**Author:** ![rmholmes](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/rmholmes/32/117_2.png) [@rmholmes](https://forum.access-hive.org.au/u/rmholmes)\
**Post date:** [17 September 2026 23:15 UTC](https://forum.access-hive.org.au/t/vscode-secret-folder-hitting-disk-quota/6991/7 "2026-09-17T23:15:57Z")

</div>

You can also just make `~/.vscode-server` a symlink to a location on scratch or gdata.
