What problem does it solve? Developing and testing VS Code itself requires launching Code OSS from sources with a signed-in profile, driving its UI via Playwright over CDP, and attaching debuggers to the renderer, extension host, main, or agent host processes — all without port conflicts or profile corruption when running multiple instances. ## 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 source profile. - Automatic port allocation: Picks free ports for CDP, extension host, main process, and agent host debugging, then prints them as JSON for programmatic pickup. - UI automation helpers: Includes a chat-input focus script and a Monaco paste helper that work around Monaco's native-edit-context ignoring Playwright's fill/type commands. - Use Case: An agent working on VS Code chat features launches an Agents window, attaches @playwright/cli to the CDP port, pastes a prompt into the chat input, and simultaneously attaches dap-cli to the extension host port to hit breakpoints. ## Quick Start Launch a Code OSS dev instance with an isolated authenticated profile and give me the CDP port so I can drive the workbench with Playwright.