launch

Launch Code OSS from sources into isolated profiles with unique debug ports for Playwright and dap-cli.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Running VS Code (Code OSS) from sources for UI automation or debugging normally requires manual profile setup, port management, and sign-in handling, and concurrent instances collide over shared state. This Skill automates launching an authenticated, isolated throwaway instance with unique debug ports so you can drive the workbench with @playwright/cli and attach dap-cli debuggers in the same session. ## Core Features & Use Cases - Isolated authenticated launches: Clones an authenticated user-data-dir (slim copy excluding caches and workspace storage) into a temp profile, preserving Copilot/GitHub sign-in on macOS, Linux, and Windows. - Unique debug ports per instance: Allocates free ports for the renderer (CDP), extension host, main process, and agent host, printed as JSON for programmatic pickup. - UI automation helpers: Includes a Playwright script to focus the chat input and a monaco-paste helper that reliably types into Monaco editors where fill/type fail. - Use Case: Launch two concurrent Code OSS Agents windows, attach @playwright/cli to each with separate sessions, paste prompts into each chat input, and screenshot the results — all without port or profile conflicts. ## Quick Start Ask the AI to launch Code OSS from this repo using the launch skill and attach Playwright to the returned CDP port.

Frequently Asked Questions about launch

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

FAQPage Schema
How do I launch VS Code from sources for UI automation with Playwright?▼

Run the launch.sh (macOS/Linux) or launch.ps1 (Windows) script, which clones an authenticated profile, picks free debug ports, and blocks until the CDP endpoint is ready. Then attach with npx @playwright/cli -s=SESSION attach --cdp=http://127.0.0.1:<cdpPort>.

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

The launcher prints extHostPort, mainPort, and agentHostPort alongside the CDP port. Attach dap-cli to the relevant port for breakpoints while using @playwright/cli over the cdpPort to drive the same window simultaneously.

Why does fill or type not work in the VS Code chat input with Playwright?▼

Monaco's native-edit-context element ignores Playwright's default fill and type input pipeline. Use the monaco-paste.sh helper, which dispatches a synthetic ClipboardEvent paste with a DataTransfer payload and verifies the rendered view lines.

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

Yes. Each launch allocates fresh ports, a temp user-data-dir, and an isolated shared-data-dir, so instances do not collide. Give each driver a unique @playwright/cli session name via -s=NAME to keep daemons separate.

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

On Windows the GitHub session is stored in the shared-data-dir, not the profile. The launcher seeds both, but if the source profile has no stored session, sign in once by running scripts\code.bat against the source user-data-dir directly.