launch

Name: launch
Availability: InStock
Author: Nithwin

Launch VS Code Code OSS with remote debugging for automated UI interactions.

Updated Mar 19, 2026

Search Tags:#cdp #ui-testing #automate #vs-code #agent-browser #automation-workflows #code-oss

Ready to run

npx skills add https://github.com/Nithwin/shadowcode --skill launch-nithwin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: launch
Source: https://github.com/Nithwin/shadowcode/tree/main/.agents/skills/launch
Command: npx skills add https://github.com/Nithwin/shadowcode --skill launch-nithwin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the setup and orchestration of launching VS Code (Code OSS) and paving the way for UI automation, debugging, and UI testing via a CDP-enabled workflow.

Core Features & Use Cases

Launch Code OSS with remote debugging enabled for automated interactions.
Connect agent-browser to the app and snapshot the UI to discover interactive elements.
Automate UI tasks, capture screenshots, and validate UI flows across local Code OSS instances.

Quick Start

Launch Code OSS with remote debugging and connect agent-browser to begin automated UI interactions.

Frequently Asked Questions about launch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate VS Code UI testing using Chrome DevTools Protocol?▼

Automate VS Code UI testing by launching Code OSS with remote debugging enabled and connecting agent-browser via the Chrome DevTools Protocol to snapshot interactive elements and capture screenshots.

Can I use CDP to capture screenshots of local Code OSS instances?▼

Yes, you can capture screenshots of local Code OSS instances by connecting agent-browser to the remote debugging port via CDP, enabling automated UI validation and interactive workflow testing.

How does agent-browser connect to Code OSS for automated interactions?▼

Agent-browser connects to Code OSS through the remote debugging port exposed via CDP, allowing you to discover interactive UI elements, automate tasks, and validate UI flows locally.

Do I need a specific directory structure to set up Code OSS automation workflows?▼

You need a root SKILL.md file with YAML frontmatter containing name and description, and can optionally include scripts, references, and assets directories to support extended automation functionality.

What's the best way to debug VS Code extensions through UI automation?▼

Debug VS Code extensions by launching Code OSS with remote debugging enabled, connecting agent-browser via CDP to automate UI interactions, and validating extension workflows through captured screenshots.

Why would I use CDP for VS Code automation instead of other testing approaches?▼

Using CDP for VS Code automation enables direct remote debugging access to Code OSS, allowing agent-browser to discover interactive elements, automate UI tasks, and capture screenshots without external test runners.