vscode-dev-workbench

Start a local vscode.dev server against sibling VS Code sources for workbench validation.

Updated Aug 23, 2026

Search Tags:#vscode #browser automation #local development #workbench #agents window #mock agent host

Ready to run

npx skills add https://github.com/THRISHAL12345/Project_X --skill vscode-dev-workbench

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vscode-dev-workbench
Source: https://github.com/THRISHAL12345/Project_X/tree/main/apps/vscode-fork/.github/skills/vscode-dev-workbench
Command: npx skills add https://github.com/THRISHAL12345/Project_X --skill vscode-dev-workbench

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you run the VS Code web workbench from a local development checkout so you can validate UI, browser, and Agents window changes without building a full desktop release.

Core Features & Use Cases

Local workbench startup: Launch the vscode.dev server against sibling VS Code sources for fast web-only iteration.
Browser-based validation: Exercise the workbench or Agents window in an integrated browser and verify interactions, logging, and cache behavior.
Mock agent testing: Connect the Agents window to a local mock agent host for offline testing of session flows and tool interactions.
Use Case: A developer changes a web workbench component, starts the local dev server, opens the dev URL, and confirms the UI behaves correctly against the updated source tree.

Quick Start

Start the local vscode-dev server from the vscode-dev checkout, then open the dev workbench URL with vscode-quality=dev in your 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 test the VS Code web workbench locally during development?▼

To test the VS Code web workbench locally, start the vscode.dev server against sibling VS Code sources, then open the dev workbench URL with vscode-quality=dev in your browser to validate UI changes.

Can I validate browser automation and workbench interactions without a full desktop build?▼

Yes, you can validate browser automation and workbench interactions without a desktop build by running the local vscode.dev server and exercising the web UI through an integrated browser session.

How do I connect the VS Code Agents window to a mock agent host for offline testing?▼

You can connect the VS Code Agents window to a mock agent host by wiring the local mock agent host during local vscode.dev server startup, enabling offline testing of session flows and tool interactions.

Do I need to build the entire VS Code desktop release to debug web UI changes?▼

No, you do not need to build the full desktop release to debug web UI changes. You can launch the web-only vscode.dev server against your local source checkout for fast workbench validation.

What URL parameters are required to open the local VS Code dev workbench in a browser?▼

The required URL parameter to open the local VS Code dev workbench is vscode-quality=dev, which configures the browser session to run against your updated local source tree.