Request for a low-resource default configuration for VS Code Remote-SSH in shared environments

[h-sakai98]

We currently provide a dedicated login node for VS Code and allow users to access it via VS Code Remote-SSH. This node is shared by many users, and while VS Code Remote-SSH is extremely useful, excessive resource usage by a single user can negatively impact others.

We have experienced an incident where one user consumed several hundred gigabytes of resources on this shared node, causing a severe overload.

At present, we ask users to:

• Remove or disable unnecessary VS Code extensions
• Exclude file monitoring using watcherExclude settings

However, these measures rely heavily on user awareness and are not always sufficient in shared or multi-user environments. From an operator’s perspective, it is difficult to prevent overloads using user-side guidelines alone.

For this reason, we would like to ask whether it is possible to provide or support a default low-resource configuration for VS Code Remote-SSH, such as a resource-conservative mode or profile that minimizes background activities (e.g. file watching, indexing, scanning, language server behavior) by default.

Our goal is to continue allowing VS Code Remote-SSH usage while reducing the risk of excessive resource consumption on shared login nodes. Any guidance, planned features, or recommended default configurations in this direction would be greatly appreciated.

[technic960183]

Related feature request: #233842

I have encountered similar issue.

[vs-code-engineering[bot]]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!