Fly.io engineers criticize VSCode's remote-SSH agent as bloated
A Fly.io team post examines VSCode's remote SSH extension, noting that rather than running lightweight shell commands like Emacs's Tramp does, it deploys a Bash script that downloads and installs a full agent, including a Node.js binary, on the remote machine. The authors say they are exploring integration with this remote-editing flow because so many developers now use VSCode forks paired with LLM code-generation agents.
GoKawiil's interpretation of the reporting above, not reported fact.
The critique suggests that VSCode's heavier remote-connection footprint could complicate efforts to run AI coding agents safely inside disposable, sandboxed Linux environments, since a bulkier installation process may be harder to control or verify. This context implies Fly.io sees an opportunity to build lighter-weight remote execution infrastructure tailored to agentic LLM workflows, positioning the criticism as groundwork for a possible product direction rather than a neutral technical observation.
- Fly.io is examining VSCode's remote-SSH mechanics as it explores hosting LLM coding agents on disposable Linux instances.
- VSCode's remote extension installs a full agent stack via a Bash script, unlike Emacs Tramp's lighter shell-command approach.
- The authors frame isolated, disposable execution environments as a safeguard against LLM agents making unwanted changes to a developer's main system.
Source: fly.io, 2026-09-23
Published there as: “VSCode's SSH Agent Is Bananas”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.