What problem does it solve? Developing and testing VS Code itself requires launching Code OSS from sources with working authentication, UI automation, and debugger access, but manual setup causes port conflicts, profile corruption, and unauthenticated instances that break chat and agent flows. ## Core Features & Use Cases - Isolated throwaway profiles: Clones an authenticated user-data-dir into a slim temp copy that preserves Copilot/GitHub auth while excluding caches, workspace storage, and logs. - Unique debug ports per launch: Picks free ports for the renderer (CDP), extension host, main process, and agent host, printing them as JSON for programmatic pickup. - UI automation and debugging: Drives the workbench with @playwright/cli over CDP, pastes text into Monaco chat inputs via a helper script, and attaches dap-cli breakpoints in the same session. - Use Case: Run multiple concurrent Code OSS instances on one machine, each driven by its own agent with its own Playwright session, to test chat flows or UI features in parallel without cross-contamination. ## Quick Start Ask the agent to launch Code OSS from the VS Code repo with an isolated profile, attach Playwright over the returned CDP port, and drive the chat UI.