vscode-server

Provision and operate a code-server environment for testing VS Code extensions.

48|19|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/jdillon/vscode-beads --skill vscode-server
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vscode-server
Source: https://github.com/jdillon/vscode-beads/tree/main/.claude/skills/vscode-server
Command: npx skills add https://github.com/jdillon/vscode-beads --skill vscode-server

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun, jq, git, lsof, code-server, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the setup and ongoing management of a code-server based development environment for testing VS Code extensions, reducing manual setup, configuration drift, and context switching.

Core Features & Use Cases

  • Start/Stop/Reload/Status actions to manage the code-server dev environment.
  • Automated startup: creates symlinks, builds, launches watch mode, and starts code-server.
  • DevTools integration: orchestrates Chrome DevTools MCP workflows for live debugging.
  • Project-scoped temp data: uses a per-project temp directory to store ports and logs.

Quick Start

Run the startup script to initialize the environment: .claude/skills/vscode-server/scripts/start-dev-environment.sh

Then monitor the structured output to verify:

  • EXTENSION_ID
  • SYMLINK
  • BUILD
  • WATCH_PID
  • CODE_SERVER_PORT

Open the browser at http://127.0.0.1:{PORT}/ using the port reported by CODE_SERVER_PORT, and perform a hard reload via the DevTools MCP after page load.

Frequently Asked Questions about vscode-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up an automated code-server environment for testing VS Code extensions?

Use this Skill's start script to automate code-server setup for extension testing. It provisions symlinks, runs builds, launches watch mode, and starts code-server with port management, eliminating manual configuration and context switching.

Can I automate the build and watch workflow when developing a VS Code extension?

Yes. The Skill orchestrates automated builds and watch-mode processes during startup, then manages the running code-server instance. It tracks process lifecycle and port assignment per project, enabling reliable, repeatable extension development cycles.

What's the best way to manage code-server ports and temporary data across multiple projects?

This Skill derives and exposes ports automatically using per-project temporary directories to store port assignments and logs. This approach isolates state by project and prevents port conflicts without manual bookkeeping.

How do I integrate Chrome DevTools into my VS Code extension testing workflow?

The Skill orchestrates Chrome DevTools MCP workflows for live debugging. After launching code-server, perform a hard reload via DevTools to connect the debugger and inspect extension behavior in real time.

Can I start, stop, and reload a code-server dev environment without manual commands?

Yes. The Skill provides start, stop, reload, and status actions to manage the entire lifecycle. Each action automates the corresponding environment task, from initialization through teardown, with structured output for verification.

What dependencies do I need to run an automated code-server extension testing environment?

You need bun, jq, git, lsof, and code-server installed. The Skill requires these tools to build extensions, manage processes, derive ports, and operate the code-server instance reliably.