vscode-dev-workbench

Runs the vscode.dev server locally to test VS Code workbench and Agents window changes.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/jimeh/hucode --skill vscode-dev-workbench-jimeh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vscode-dev-workbench
Source: https://github.com/jimeh/hucode/tree/main/.github/skills/vscode-dev-workbench
Command: npx skills add https://github.com/jimeh/hucode --skill vscode-dev-workbench-jimeh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Validating web-only changes to the VS Code workbench normally requires shipping an Insiders build. This Skill lets you serve the workbench or Agents window directly from local microsoft/vscode sources via the vscode-dev server, enabling fast browser-driven testing. ## Core Features & Use Cases - Local dev server startup: Runs npm run dev from the vscode-dev checkout to serve the workbench at https://127.0.0.1:3000/?vscode-quality=dev. - Browser automation guidance: Covers chat input behavior, service worker cache clearing after rebuilds, and mobile emulation via CDP. - Mock agent host setup: Wires the Agents window to a local mock agent host over WebSocket, bypassing GitHub auth and tunnel discovery for offline testing. - Use Case: After editing workbench sources in the vscode repo, start the dev server, hard-reload the browser with service workers unregistered, and verify the change in the Agents window against a scripted mock agent. ## Quick Start Start the vscode.dev dev server from the vscode-dev folder and open the local workbench with the dev quality URL so I can test my workbench changes in the browser.

Frequently Asked Questions about vscode-dev-workbench

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

FAQPage Schema
How do I run vscode.dev against local VS Code sources?

Run `npm run dev` from the vscode-dev checkout, not the vscode repo, with both as sibling folders. Then open `https://127.0.0.1:3000/?vscode-quality=dev` to load the workbench from your local sources.

How do I test the VS Code Agents window locally without signing in?

Start the mock agent host from the vscode repo with `node out/vs/platform/agentHost/node/agentHostServerMain.js --enable-mock-agent --port 8765`, then open the /agents route with `mock-agent-host=ws://localhost:8765` to bypass GitHub auth and tunnel discovery.

Why does the dev server fail with Missing script: dev?

The vscode repo has no `dev` script; the command must run from the vscode-dev folder. Terminal tools that strip leading `cd` can keep a stale working directory, so verify with `pwd` or use an absolute `pushd` before running npm.

Why does the workbench show stale UI after editing vscode sources?

The service worker caches client assets aggressively, so a plain reload can serve old modules. Unregister all service workers and clear caches via page.evaluate, then reload to pick up rebuilt sources.

Why does pressing Enter not send a chat message in the workbench?

The chat input is a Monaco editor, so Enter inserts a newline instead of submitting. Click the Send button (`a[aria-label^="Send"]`) or use the send keybinding to dispatch the message.