What problem does it solve?
Debugging a VS Code extension's live UI state is slow when you cannot see what the running extension actually renders. This Skill launches a real VS Code instance with GitLens loaded and lets you programmatically inspect DOM state, read logs, execute commands, and capture screenshots without manual clicking.
Core Features & Use Cases
- Persistent MCP inspection session: The
vscode-inspector MCP server launches VS Code once and exposes tools for screenshots, DOM queries, accessibility snapshots, command execution, and log reading in an iterative loop.
- Webview and shadow DOM inspection: Discover open webviews, wait for Lit hydration, and query shadow DOM content or computed styles via
evaluate_in_webview.
- Subscription and AI simulators: Exercise Pro-gated features with
set_account plan simulation and deterministic AI responses without real accounts or provider keys.
- Batch CLI fallback:
scripts/e2e-dev-inspect.mjs supports one-shot ordered actions (commands, clicks, queries, screenshots, log searches) when the MCP server is unavailable.
- Use Case: After editing a GitLens webview component, rebuild with
pnpm run build:webviews, refresh the view, and screenshot the result to verify the change — all without leaving the agent session.
Quick Start
Launch the inspector session and take a screenshot of the GitLens Home view to see its current live state.