skills.rest
microsoft
microsoftOFFICIAL
Explore all skills by this author →
Website𝕏@OpenAtMicrosoftGitHub

launch

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

189k|41.5k|Updated Sep 3, 2015
Search Tags:#automation#vscode#debugging#ui testing#electron#agent-browser#code oss
One-click install
npx skills add https://github.com/microsoft/vscode --skill launch-microsoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: launch
Source: https://github.com/microsoft/vscode/tree/main/.agents/skills/launch
Command: npx skills add https://github.com/microsoft/vscode --skill launch-microsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the launch and interaction with Visual Studio Code (Code OSS) and its extensions, enabling programmatic control and testing of the IDE's UI and features.

Core Features & Use Cases

  • Launch VS Code: Start Code OSS or VS Code Insiders with debugging ports enabled.
  • UI Automation: Interact with VS Code's UI elements, including the chat panel and editors, using Chrome DevTools Protocol.
  • Extension Debugging: Launch VS Code with extensions in development mode for debugging.
  • Use Case: Automate testing of a new VS Code extension by launching it in an isolated instance, interacting with its UI elements via agent-browser, and verifying its behavior.

Quick Start

Launch Code OSS with remote debugging enabled on port 9224 and connect agent-browser to it.

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 with the Chrome DevTools Protocol?▼

You can launch VS Code with a remote debugging port enabled, such as port 9224. This exposes the Chrome DevTools Protocol endpoint, allowing agent-browser to programmatically connect, control the IDE interface, and execute UI interactions.

Can I debug VS Code extensions in development mode?▼

Yes, VS Code extensions can be debugged by launching Code OSS in development mode. This configuration allows you to test extension behavior by interacting with its UI elements and verifying functionality through the Chrome DevTools Protocol.

What is the process to launch Code OSS for automated interaction?▼

Code OSS is launched with remote debugging enabled on a designated port, typically 9224. After startup, agent-browser connects to this debugging endpoint to facilitate programmatic interaction with the IDE's UI and chat panel.

Does agent-browser work with VS Code Insiders for UI automation?▼

Yes, agent-browser supports launching both Code OSS and VS Code Insiders with debugging ports enabled. This allows you to use the Chrome DevTools Protocol to automate UI features, interact with editors, and capture screenshots.

Why do I need a remote debugging port to control VS Code?▼

A remote debugging port exposes the Chrome DevTools Protocol interface for VS Code. This endpoint is necessary for agent-browser to establish a connection, enabling programmatic control over the IDE's UI elements and automated testing.

Related Skills

Explore More Software Engineering Skills→
petarkabashkipetarkabashki

launch

Automate VS Code Insiders UI and Copilot Chat via Chrome DevTools Protocol.

Community
Advanced
phodalphodal
1.8k

electron

Automate Electron desktop apps via Chrome DevTools Protocol connections.

Community
Intermediate
malwarebomalwarebo
5

launch

Launch and automate VS Code UI via Chrome DevTools Protocol.

Community
Advanced
joshsmithxrmjoshsmithxrm
5

ext-verify

Automate VS Code extension webview UI tests with Playwright Electron.

Community
Advanced