skills.rest
aadorian
aadorianCOMMUNITY
Explore all skills by this author →
GitHub

launch

Launches Code OSS with remote debugging and automates UI via agent-browser and Chrome DevTools Protocol.

Updated Mar 28, 2026
Search Tags:#automation#vscode#screenshots#cdp#ui-testing#agent-browser#code-oss
One-click install
npx skills add https://github.com/aadorian/VSCode_Readme --skill launch-aadorian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: launch
Source: https://github.com/aadorian/VSCode_Readme/tree/main/education/engineering-tooling/local-agent-skills/skills/launch
Command: npx skills add https://github.com/aadorian/VSCode_Readme --skill launch-aadorian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of manually launching and testing VS Code by providing a reliable workflow for opening Code OSS, connecting automation, and working with the chat, editor, and extension surfaces.

Core Features & Use Cases

  • Launches Code OSS or the Sessions app with remote debugging enabled.
  • Connects agent-browser to inspect tabs, drive Monaco-based inputs, and take screenshots.
  • Supports extension debugging, UI validation, and repeatable walkthrough demos for VS Code features.

Quick Start

Ask for a launch-and-automation run that opens VS Code with remote debugging, connects agent-browser, and captures the target UI state.

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 sessions using Chrome DevTools Protocol?▼

Automating VS Code UI sessions with Chrome DevTools Protocol requires launching Code OSS with remote debugging enabled, then connecting agent-browser to inspect tabs, drive Monaco editor inputs, and capture screenshots.

Can I take screenshots of VS Code extensions during automated UI testing?▼

Taking screenshots of VS Code extensions during UI testing is supported by connecting agent-browser to the active remote debugging session, allowing you to capture the target UI state for validation and repeatable demos.

What is the best way to launch Code OSS for automated extension debugging?▼

The best way to launch Code OSS for automated extension debugging is to start it with remote debugging enabled, allowing agent-browser to connect, discover tabs, and interact with chat and editor surfaces reliably.

Does agent-browser work with the Monaco editor in VS Code?▼

Agent-browser works with the Monaco editor in VS Code by connecting through Chrome DevTools Protocol, applying specialized interaction techniques to drive inputs within the editor surface during automation workflows.

How do I ensure reliable launch and cleanup when automating VS Code?▼

Ensuring reliable launch and cleanup when automating VS Code involves using a controlled workflow that establishes remote debugging connectivity, manages tab discovery, and properly terminates the Code OSS session after capturing UI states.

Related Skills

Explore More Software Engineering Skills→
microsoftmicrosoft
188.5k

launch

Launch Code OSS with debugging and automate its UI via Chrome DevTools Protocol.

Official
Advanced
malwarebomalwarebo
5

launch

Launch and automate VS Code UI via Chrome DevTools Protocol.

Community
Advanced
phodalphodal
1.8k

electron

Automate Electron desktop apps via Chrome DevTools Protocol connections.

Community
Intermediate
CleanExpoCleanExpo
1

playwright-browser

Automate headless browser tasks and end-to-end tests with Playwright.

Community
Advanced