hdresearch/pi-vers/vers-networking
Claude Code and agent skill by hdresearch/pi-vers
- community
Checking that the SKILL.md file is still in the repository.
How Vers VM networking works — public URLs, port routing, TLS proxy, IPv6, and running services on VMs.
Install
npx vskill@latest install hdresearch/pi-vers/vers-networkingSKILL.md
The same SKILL.md was published earlier as hdresearch/pi-vers/vers-networking.
Vers VM Networking
Every Vers VM gets a public URL and can serve traffic on any port. This is how you expose services, APIs, and web interfaces running on VMs.
Public URLs
Every VM is reachable at:
For example:
The Vers proxy terminates TLS and routes traffic to the specified port on the VM. This works for any protocol over TCP — HTTP, WebSocket, gRPC, etc.
Key Facts
- All ports are routable. Specify the port in the URL. There is no need for SSH tunnels or port forwarding.
- TLS is handled by the proxy. Clients connect via
https://, the proxy terminates TLS and forwards to the VM. Your service does NOT need to handle TLS. - IPv6 required. Services on the VM must bind to IPv6 (e.g.,
::or::1) for the proxy to reach them. Binding to0.0.0.0(IPv4 only) will not work through the proxy. - No firewall. All ports are open by default. There is no allowlist or port mapping configuration needed.
Running a Service on a VM
Bind to IPv6
Most frameworks default to IPv4 (0.0.0.0). You must configure them to listen on :: (all interfaces, IPv6 + IPv4 dual-stack).
Node.js (Hono + @hono/node-server):
Node.js (native http):
Python:
Verify Accessibility
From any machine (local, another VM, CI):
If you get a connection timeout, check:
- Is the service running? (
ss -tlnpon the VM) - Is it bound to IPv6? (
ss -tlnp | grep {port}should show:::port) - Is the VM running? (
vers_vmsto check state)
Common Patterns
Expose an API
Start your service on the VM, bound to ::, on any port:
Clients use:
VM-to-VM Communication
VMs reach each other the same way — via the public URL. There is no private network between VMs. All traffic goes through the TLS proxy.
WebSocket
Connect via wss://:
Service Discovery
Use a service registry to track which VMs are running which services:
Cross-VM SSH
Any Vers VM can SSH directly into any other Vers VM using the TLS proxy. This works out of the box — golden image SSH keys are pre-installed on all VMs, so no key exchange or setup is needed.
SSH Command
The ProxyCommand tunnels the SSH connection through the Vers TLS proxy on port 443, just like HTTPS traffic. The -o StrictHostKeyChecking=no flag avoids host key prompts when connecting to new VMs.
Use Cases
- Deploying code to another VM. A lieutenant can push built artifacts, sync files, or run deploy scripts on an infrastructure VM.
- Inspecting another lieutenant's VM. SSH in to check logs, debug a running service, or verify system state.
- Cross-VM file transfer. Use
scporrsync(with the same proxy command) to move files between VMs.
Example: Deploying to an Infrastructure VM
A lieutenant building code on its own VM can deploy to a separate infra VM:
Example: Cross-VM File Transfer with rsync
Notes
- Golden image keys. All VMs created from the same golden image share SSH keys, so cross-VM SSH works without any configuration.
- No private network. SSH traffic goes through the public TLS proxy, just like HTTP. There is no direct VM-to-VM link.
- Root access. VMs use the
rootuser by default.
Security
All ports are public by default. There is no firewall. Any service you start is reachable by anyone on the internet. Always protect services with authentication.
For your coordination services, set VERS_AUTH_TOKEN env var. All endpoints except /health will require Authorization: Bearer <token>. Pass the same token to worker VMs so they can authenticate.
Common Mistakes
- Binding to `0.0.0.0` instead of `::` — The proxy routes via IPv6. IPv4-only services won't be reachable through the public URL (but will work locally on the VM).
- Assuming SSH-only access — VMs are not behind a bastion. The TLS proxy routes any TCP traffic, not just SSH.
- Using SSH tunnels for HTTP — Unnecessary. Just hit the public URL directly.
- Forgetting the port in the URL — Unlike traditional hosting, there's no default port 80/443 mapping. Specify the port your service runs on.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/vers-networking/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/hdresearch/pi-vers/vers-networking)