Workaround for Visual Studio Code remote connections to resources in the General Environment
An issue with home directories in mid-January 2026 prevented Visual Studio Code connections from being established. This issue is now resolved.
We recommended the following workaround:
- Create a (user-specific) directory in /scratch/nfs1 or group space for VS Code Server
- Caveat: Scratch spaces are temporary; user may need to re-create directory if deleted and may lose some information (caches, remote extensions, state)
- Optionally copy files from ~/.vscode-server to new directory to avoid losing information (caches, remote extensions, state)
- Move ~/.vscode-server to new location (rename) while no VS Code remote sessions are open (can rename to include .bak or something similar)
- Create a symbolic link:
ln -s new-location ~/.vscode-server
Now that the issue is resolved, we recommend moving or removing the symbolic link to allow VS Code to store information in your home directory again, particularly if you used a scratch space as an interim solution. Files in scratch spaces are deleted automatically after a period of inactivity, so you could lose caches, remote extensions, or state by using this workaround long-term.