launch

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Running a VS Code build 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 files and debug ports. ## Core Features & Use Cases - Isolated throwaway profiles: Clones an authenticated user-data-dir into a slim temp copy (excluding caches, workspace storage, and logs) so Copilot/GitHub sign-in persists without mutating the original profile. - Automatic port allocation: Picks free ports for the renderer CDP endpoint, extension host, main process, and agent host, then prints them as a single JSON line for programmatic consumption. - UI driving and debugging: Attach @playwright/cli over CDP to automate the workbench (including Monaco chat input via the monaco-paste.sh helper) and attach dap-cli to set breakpoints in any process, even simultaneously. - Use Case: Run two parallel agents, each launching its own Code OSS instance with a unique Playwright session, driving chat prompts and taking screenshots without port or clipboard conflicts. ## Quick Start Ask the AI to launch a Code OSS dev build with an isolated authenticated profile and print the CDP and debugger ports as JSON so you can attach Playwright and dap-cli.

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?▼

Run the launch.sh script (macOS/Linux) or launch.ps1 (Windows) from the skill's scripts directory. It clones an authenticated profile, allocates free debug ports, waits for the CDP endpoint, and prints a JSON line with all ports and paths.

How do I type into the VS Code chat input with Playwright?▼

Playwright's fill and type commands silently fail on Monaco's native-edit-context element. Use the monaco-paste.sh helper, which dispatches a synthetic ClipboardEvent paste, or send per-key press commands as a slower fallback.

Can I run multiple Code OSS instances at the same time?▼

Yes. Each launch picks fresh ports, a fresh temp run directory, and its own --shared-data-dir, so instances do not fight over the shared storage SQLite database. Give each driver a unique Playwright session name to keep daemons isolated.

Why does the launched VS Code window ask me to sign in?▼

The source profile being copied lacks a stored GitHub or Copilot session. Launch Code OSS directly against the source user-data-dir, sign in once, and close it; every later launch copies that profile and inherits the session.

Which debug port should I attach dap-cli to?▼

Use extHostPort for extension host code, mainPort for the Electron main process, agentHostPort for the agent host, and cdpPort for renderer workbench code. The launch JSON prints all four ports for the instance.