Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Starts and manages a VS Code Remote Tunnel inside Docker containers, allowing remote terminal access through VS Code's browser or desktop client. Handles CLI installation, background process management, and Microsoft account authorization.
Avoids SSH configuration and port forwarding by using VS Code's built-in tunnel infrastructure to reach containers directly.
When to use it
- Accessing a dev container remotely from any device
- Debugging a Docker environment without SSH setup
- Sharing a container session with a teammate via VS Code
- Reconnecting to a named tunnel after container restart
- Checking tunnel status or live logs during a remote session
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: start vscode tunnel named dev-env
- 1Runs bash tunnel.sh start dev-env
- 2Downloads VS Code CLI to ~/.vscode-cli if not present
- 3Starts tunnel process in background
- 4Reads authorization code from log output
- 5Displays code for Microsoft account login in VS Code
Tunnel dev-env is running. Enter the displayed code in VS Code to authorize and connect.
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.