launch

Launch Code OSS builds with isolated profiles and unique debug ports for Playwright automation and dap-cli debugging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/cli, and includes scripts (resource) components.

What problem does it solve? When developing VS Code itself, you need a running Code OSS instance that is already signed in, drivable via Playwright over CDP, and attachable by a Node debugger — all without port conflicts or clobbering your real profile. This Skill automates that entire setup. ## Core Features & Use Cases - Isolated authenticated launches: Clones an authenticated user-data-dir into a throwaway temp profile (slim copy excluding caches and workspace storage), allocates free ports for the renderer (CDP), extension host, main process, and agent host, and prints them as JSON. - UI automation with @playwright/cli: Attach over CDP, snapshot the DOM, focus the chat input via a dedicated Playwright script, and paste text into Monaco editors using a clipboard-event helper that works where fill and type fail. - Simultaneous debugging with dap-cli: Set breakpoints in the renderer, extension host, main, or agent host process while driving the UI in the same session. - Use Case: Run multiple concurrent Code OSS instances — each with its own profile, ports, and Playwright session — so several agents can automate chat flows in parallel without cross-contamination. ## Quick Start Ask the AI to launch a Code OSS dev instance with an isolated profile and give you the CDP port so it can drive the workbench with Playwright.

Frequently Asked Questions about launch

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

FAQPage Schema
How do I automate the VS Code workbench with Playwright?▼

Launch Code OSS with a remote debugging port, then attach @playwright/cli over CDP using a unique session name. From there you can snapshot the DOM, press keys, run code, and take screenshots against the running workbench.

How do I debug the VS Code extension host while driving the UI?▼

The launcher allocates separate ports for the extension host, main process, agent host, and renderer. Attach dap-cli to the extension host port for breakpoints while @playwright/cli drives the same window over the CDP port.

Why does Playwright fill or type not work in VS Code Monaco editors?▼

Monaco's native-edit-context element does not react to Playwright's default fill or type input pipeline. Use the monaco-paste.sh helper, which dispatches a synthetic ClipboardEvent paste with a DataTransfer payload, or send per-key press commands.

Can I run multiple Code OSS instances in parallel for automation?▼

Yes, each launch picks fresh ports, a fresh temp profile, and its own shared-data directory, so instances do not conflict. Give each driver a unique Playwright session name; on macOS, more than two or three instances may hit Crashpad Mach-port limits.

Why does the launched Code OSS instance ask me to sign in?▼

The launcher copies an authenticated source profile, defaulting to ~/.vscode-oss-dev. If that profile has no stored GitHub session, sign in once by running Code OSS directly against it; on Windows the session lives in the shared-data directory, which the launcher also seeds.