VSCode's SSH Agent Is Bananas (2025)
- ID
- 28242
- Status
- summarized
- Published
- 24 Sep 2026, 5:01 AM
- Fetched
- 25 Sep 2026, 3:17 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://fly.io/blog/vscode-ssh-wtf/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.8
- Created
- 25 Sep 2026, 3:17 AM
- Tags
- Audience
- developersvibe_codersai_agent_users
What happened
Fly.io's Thomas Ptacek writes that VSCode's SSH remote editing is not a lightweight Tramp-like client: it runs a Bash snippet stager that downloads an agent including a binary Node install, runs over port-forwarded SSH, and opens a WebSocket back to the VSCode front-end. That protocol can wander the filesystem, edit arbitrary files, launch shell PTY processes, and persist itself, and the post ties this to LLM/agentic coding loops that ideally run on clean-slate Linux instances. The HN thread drew 299 points and 196 comments.
Why it matters
If you use VSCode Remote-SSH or a VSCode fork for agentic coding, the remote agent is not just an SSH shell—it installs Node and exposes file edits, PTYs, and persistence over a WebSocket. Decide whether that runs on your dev laptop or a disposable clean-slate Linux VM, and treat the remote agent as code with broad permissions; the excerpt has no Malaysia-specific hook.
Discussion angle
What sandbox boundary should teams use for closed-loop LLM coding agents if VSCode's remote agent can edit files, spawn PTYs, and persist itself over a WebSocket?