vscode-remote-release
https://github.com/microsoft/vscode-remote-release
Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
not yet supported2 Subscribers
Add a CodeTriage badge to vscode-remote-release
Help out
- Issues
- Remote-SSH 0.126.0 fails on VS Code 1.134.0: terminalRemoteResolver proposed API is not declared
- Remote-SSH fails after latest update -v0.126.0 - terminalRemoteResolver - Windows
- [BUG][URGENT] After update to v0.126.0 Remote SSH keep failure to connect remote server
- Remote-SSH 0.124.0 keeps asking for remote platform on every connection
- Clone Repository in Container Volume: SSH fails to resolve hostnames behind resolvers with non-compliant AAAA responses (musl getaddrinfo(AF_UNSPEC) fails entirely on partial NXDOMAIN)
- Hope Microsoft to develop a new harness rather than github copilot
- Remote-SSH Bug: reconnect forfeits its 3-hour grace on the first attempt when a managed socket closes mid-connect
- Tabs in new light-mode themes
- Remote-SSH traffic inherits ssh's bulk/scavenger QoS class and gets starved by QoS-aware links — consider `IPQoS=none` (default or setting)
- Attach takes ~30s with --pid=host during existing host-agent discovery
- Docs
- not yet supported