VS Code extension for remote development in Kubernetes pods on the Patapsco AI Platform.
Connect to ephemeral dev environments directly from VS Code — create, manage, and develop inside pods without manual SSH or kubectl setup.
Features
Remote pod connectivity — full VS Code IDE experience inside Kubernetes pods via WebSocket
Pod lifecycle management — create, connect, and delete pods from the activity bar sidebar
Multi-server support — manage connections to multiple Patapsco servers simultaneously
Automatic VS Code Server setup — detects and uploads the correct VS Code Server version to pods
GPU cluster awareness — hierarchical display of pod clusters with child nodes
Agent chat — talk to a deployed agent over the Agent Client Protocol, with
its tool calls, thinking and media rendered inline. The agent owns the
conversation, so a chat started on one machine continues on another
Agent terminals — a pty into an agent's container, in the chat panel or the
terminal panel
Requirements
VS Code 1.93 or later
Access to a Patapsco AI Platform server, and a credential for it
Install
Search for Patapsco Remote in the Extensions view (Ctrl+Shift+X, or
Cmd+Shift+X on macOS) and select Install.
From the command line:
code --install-extension PatapscoAI.remote
Getting started
Open the Patapsco Remote panel in the VS Code activity bar
Add your server credential in the settings view
Create a new dev pod, or connect to an existing pod or agent workspace
Servers with private or self-signed certificates
If a server's certificate isn't signed by a publicly trusted CA, the tree shows
the reason beside the failing entry — such as
error: fetch failed: UNABLE_TO_GET_ISSUER_CERT_LOCALLY. Fix it per server in
the settings view:
CA certificate — point at the issuing CA: a PEM file, or a directory of
.pem/.crt files (~ is expanded). Certificate verification stays on.
This is the preferred option.
Trust self-signed certificate — skips verification for that server
entirely. Overrides the CA field. Use it only for servers you control.
Both are stored per server, so enabling one never affects the others.
