How do I install the Vscode Tunnel skill?

Run npx skillmds add modbender/vscode-tunnel in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Vscode Tunnel skill do?

Start VS Code Remote Tunnel in Docker containers for remote terminal access It is listed under DevOps & Infra on SkillMD.

Is Vscode Tunnel safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vscode Tunnel?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vscode Tunnel free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vscode Tunnel?

modbender (@modbender) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vscode Tunnel by modbender — Agent Skill

Name: Vscode Tunnel
Rating: 4.2 (5 reviews)
Author: modbender

File contents

VS Code Tunnel

Start a VS Code Remote Tunnel in Docker container environments, enabling remote terminal access through VS Code.

Trigger Phrases

"start vscode tunnel"
"open vscode tunnel"
"connect vscode"
"launch code tunnel in container"
"vscode remote"

Commands

# Start tunnel (interactive name prompt)
bash /path/to/tunnel.sh start

# Start tunnel with specific name
bash /path/to/tunnel.sh start my-tunnel-name

# Stop tunnel
bash /path/to/tunnel.sh stop

# View status
bash /path/to/tunnel.sh status

# View logs
bash /path/to/tunnel.sh log

Environment Variables

Variable	Description	Default
`VSCODE_TUNNEL_NAME`	Tunnel name	Interactive input
`VSCODE_CLI_DIR`	CLI installation directory	`~/.vscode-cli`

Usage Examples

User: start vscode tunnel
Agent: Starting VS Code Tunnel...
[Executes: bash tunnel.sh start]
Agent: Tunnel started. Please enter this code in VS Code to authorize: xxxx-xxxx

User: launch a tunnel named dev-env
Agent: Starting tunnel dev-env...
[Executes: bash tunnel.sh start dev-env]

Commands Reference

Command	Description
`start [name]`	Start tunnel with optional name
`stop`	Stop running tunnel
`status`	Display tunnel status
`log`	View tunnel logs (live)

Dependencies

curl - Download CLI
tar - Extract CLI
grep - Log processing

Notes

First-time startup requires Microsoft account authorization
Authorization code will be displayed in the log output
Tunnel runs in background; needs restart after container reboot

Platform Support

Linux x64 (Alpine/Debian/Ubuntu)
Docker container environments

---name: vscode-tunneldescription: Start VS Code Remote Tunnel in Docker containers for remote terminal access--- # VS Code Tunnel Start a VS Code Remote Tunnel in Docker container environments, enabling remote terminal access through VS Code. ## Trigger Phrases - "start vscode tunnel" - "open vscode tunnel" - "connect vscode" - "launch code tunnel in container" - "vscode remote" ## Commands ```bash # Start tunnel (interactive name prompt) bash /path/to/tunnel.sh start # Start tunnel with specific name bash /path/to/tunnel.sh start my-tunnel-name # Stop tunnel bash /path/to/tunnel.sh stop # View status bash /path/to/tunnel.sh status # View logs bash /path/to/tunnel.sh log ``` ## Environment Variables | Variable | Description | Default | |----------|-------------|---------| | `VSCODE_TUNNEL_NAME` | Tunnel name | Interactive input | | `VSCODE_CLI_DIR` | CLI installation directory | `~/.vscode-cli` | ## Usage Examples ``` User: start vscode tunnel Agent: Starting VS Code Tunnel... [Executes: bash tunnel.sh start] Agent: Tunnel started. Please enter this code in VS Code to authorize: xxxx-xxxx ``` ``` User: launch a tunnel named dev-env Agent: Starting tunnel dev-env... [Executes: bash tunnel.sh start dev-env] ``` ## Commands Reference | Command | Description | |---------|-------------| | `start [name]` | Start tunnel with optional name | | `stop` | Stop running tunnel | | `status` | Display tunnel status | | `log` | View tunnel logs (live) | ## Dependencies - `curl` - Download CLI - `tar` - Extract CLI - `grep` - Log processing ## Notes 1. First-time startup requires Microsoft account authorization 2. Authorization code will be displayed in the log output 3. Tunnel runs in background; needs restart after container reboot ## Platform Support - Linux x64 (Alpine/Debian/Ubuntu) - Docker container environments

Frequently asked questions