What problem does it solve? Developing and testing VS Code itself requires launching a source build that is already signed in, driving its UI programmatically, and attaching debuggers — all without port conflicts or profile corruption when running multiple instances. ## Core Features & Use Cases - Isolated authenticated launches: Clones an authenticated user-data-dir into a throwaway temp profile with slim excludes, preserving Copilot/GitHub sign-in while skipping caches and workspace storage. - 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 and debugging: Drive the workbench with @playwright/cli over CDP (including Monaco chat input pasting via a helper script) and attach dap-cli to set breakpoints in the same session. - Use Case: Run two concurrent Code OSS instances, each driven by its own agent, to automate chat flows and verify UI changes with screenshots. ## Quick Start Ask the agent to launch a Code OSS dev build with the launch skill and drive the chat input with Playwright to test a UI change.