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.