launch

Launch and automate VS Code UI via Chrome DevTools Protocol.

5|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/malwarebo/nyrve --skill launch-malwarebo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: launch
Source: https://github.com/malwarebo/nyrve/tree/main/.agents/skills/launch
Command: npx skills add https://github.com/malwarebo/nyrve --skill launch-malwarebo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enables programmatic control and automation of the VS Code (Code OSS) environment, allowing AI agents to interact with the editor's UI, chat panel, and features as if a human were operating it.

Core Features & Use Cases

  • VS Code Automation: Launch and control VS Code instances via the Chrome DevTools Protocol (CDP).
  • UI Interaction: Automate actions within the VS Code UI, including the chat panel and code editors.
  • Testing & Debugging: Facilitate UI testing and debugging of VS Code extensions.
  • Screenshots: Capture UI states for verification and documentation.
  • Use Case: Automate the process of testing a new VS Code extension by launching Code OSS in a specific configuration, interacting with the extension's UI via the chat panel, and taking screenshots at key steps.

Quick Start

Launch Code OSS with remote debugging enabled on port 9224 and then 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 interactions using the Chrome DevTools Protocol?

VS Code UI automation via CDP is achieved by launching Code OSS with remote debugging enabled on a specific port, then connecting agent-browser to control chat panels and capture screenshots.

Can I use agent-browser to test VS Code extensions?

Yes, agent-browser facilitates VS Code extension testing by launching Code OSS in specific configurations, manipulating UI elements, and taking screenshots for verification.

What is the process for launching Code OSS for AI-driven editor automation?

Code OSS for AI automation is launched with remote debugging enabled on port 9224, allowing agent-browser to connect and manipulate the editor UI, chat panel, and features.

Does VS Code support Chrome DevTools Protocol for chat panel manipulation?

Yes, Code OSS supports the Chrome DevTools Protocol for chat panel manipulation, enabling deep editor automation and programmatic interaction with UI features.

How do I take screenshots of the VS Code UI programmatically?

To capture VS Code UI screenshots programmatically, connect agent-browser to a Code OSS instance via CDP, automating the capture of UI states for verification and documentation.

What are the limitations of automating VS Code with agent-browser?

Automating VS Code with agent-browser targets scenarios requiring deep editor automation via CDP, meaning it is optimized for chat panel manipulation and UI testing rather than headless background tasks.