launch

Launch an isolated Code OSS instance by copying an authenticated user-data-dir into a throwaway profile and assigning fresh debugging ports. This prevents profile conflicts and port collisions, ensuring a reproducible session for Playwright automation and debugging.

You can attach debuggers to a Code OSS session while running Playwright tests because the launch process exposes separate ports for the renderer, extension host, main process, and agent host. This allows simultaneous debugger attachment and UI flow testing.

Yes, you need Node and Playwright CLI to automate Monaco editor input reliably in VS Code source workflows. The launch skill requires these dependencies to prepare the workbench for interaction, including stable focus handling and Monaco paste support.

The best way to start a signed-in Code OSS build for screenshots without instance interference is launching a cloned authenticated profile in isolation. This assigns unique debug ports and a throwaway user-data-dir to keep the automation session completely separate.

VS Code source debugging sessions break with multiple instances sharing a profile due to profile conflicts and port collisions. Launching an isolated instance with a cloned throwaway profile and fresh debugging ports prevents these collisions and ensures reproducible automation.

Yes, the launch skill requires rsync and curl to manage VS Code profiles and ports. These dependencies, alongside jq, lsof, and npx, handle copying authenticated user-data-dirs, allocating fresh debugging ports, and ensuring reliable workbench automation.