Need card #268 · Relevance Medium · Status New

Security and Resource Consumption Issues of VSCode SSH Agent

Updated 9/30/2026, 22:07:30

Problem

The post and its comments express concerns about the security implications of VSCode's SSH agent, the large storage footprint of the remote .vscode-server (e.g., 6 GB), and the complexity of shipping binaries over SSH, which may expose the local machine to remote compromise and cause user unease.

Pain points

Questions to verify

Evidence

quote · @Anonymous
Missing a (2025)FYI VSCode's SSH Agent is a godsend for remote development - the "disadvantages" that Fly lists are part of its advantages. I've worked in several teams that have made extensive use of the extension, and it's never been an issue. You can restrict SSH access arbitrarily to ensure whatever security or access guardrails you need.
quote · @Anonymous
2026-09-24 09:35:24 dev ~ du -h -d 0 .vscode-server 6.0G .vscode-server This is what makes it bananas for me. I don't know what Microsoft is thinking if they allow this.
quote · @Anonymous
This part of VSCode's architecture is acceptable to me. The reverse direction, where a compromised remote can do whatever it wants to my local machine, is not.
quote · @Anonymous
The agent is supposed to run on a remote dev box. The purpose is to make the remote machine an extension of your local one, to run extensions, containers, install packages, test deployments, forward ports and tons more. Tunneling is part of the feature set. If you are installing it on production servers and are surprised by its behavior that’s on you.

Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.