vscode-dev-workbench

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

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/az0512124155azz-sys/CodeForge --skill vscode-dev-workbench-az0512124155azz-sys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vscode-dev-workbench
Source: https://github.com/az0512124155azz-sys/CodeForge/tree/main/.github/skills/vscode-dev-workbench
Command: npx skills add https://github.com/az0512124155azz-sys/CodeForge --skill vscode-dev-workbench-az0512124155azz-sys

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 through the vscode-dev server, with browser-driven interaction and a mock agent host for offline testing. ## Core Features & Use Cases - Local dev server startup: Runs npm run dev from the vscode-dev folder and verifies readiness via the HTTPS endpoint on port 3000. - Browser automation guidance: Covers chat input behavior, service worker cache clearing after rebuilds, and mobile emulation via CDP overrides. - Mock agent host for the Agents window: Launches agentHostServerMain.js with --enable-mock-agent and connects via the mock-agent-host URL parameter, bypassing GitHub auth entirely. - Use Case: You edited a chat UI component in the vscode repo and want to verify it in the web workbench. Start the dev server, open https://127.0.0.1:3000/?vscode-quality=dev, clear the service worker cache, and interact with the updated UI in the integrated browser. ## Quick Start Start the vscode.dev dev server from the vscode-dev folder and open the local workbench at https://127.0.0.1:3000/?vscode-quality=dev to test my changes.

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 folder, not the vscode folder, with both repos as sibling directories. 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 GitHub sign-in?▼

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

Why does npm run dev fail with missing script error?▼

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

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

The service worker caches client assets aggressively, so a plain reload serves stale modules. Unregister all service workers and delete cache storage via page.evaluate, then reload the page.

Can I simulate a mobile viewport in the integrated browser?▼

The integrated browser panel clamps width, so viewport narrowing is limited, but User-Agent override and touch emulation via CDP work. For a true mobile viewport, drive a standalone Playwright script with a device descriptor like iPhone 14 Pro.