Agent skill · software engineering · microsoft
integrated-browser
Use this when working on the VS Code integrated browser ("browserView") to understand its architecture and mental model. Covers the embedded Chromium browser, its editor tab, navigation, overlay/layout, sessions, and agent browser tools under `src/vs/platform/browserView` and `src/vs/workbench/contrib/browserView`.
Why this skill is useful
Provides detailed architectural insights and IPC patterns for the integrated browser in VS Code, which the AI wouldn't reliably generate on its own.
What it needs
About 8k tokens when loaded. Last updated 2026-08-07. 188,455 stars on the source repository.
What this skill does
Integrated Browser Architecture The integrated browser ("browserView") embeds a real Chromium browser in VS Code, backed by an Electron WebContentsView. It renders live pages, presents each as an editor tab, and lets agents drive those pages through tools. It powers the in-product browser tab and the agent "browser" tools. It is not the old extensions/simple-browser (an iframe-in-a-webview), which now delegates to this on desktop. It's a heavyweight, security-sensitive, multi-process primitive, and almost every design decision follows from that. This file describes the load-bearing ideas that rarely change. It deliberately does not enumerate current features/tools/commands/settings — those churn; the live features/ and tools/ folders are the source of truth. Build the mental model here, then go read the specific code you're changing. The one idea everything follows from A page is a native WebContentsView that only the main process may create, own, and position. Nothing else can touch it directly. It's owned by the main process and painted by the OS compositor on top of the workbench DOM — not inside it. Everything else works around this: The renderer (editor UI + agent tools) can't hold the page; it holds a model/proxy and talks to main over IPC. Playwright is heavy and long-lived, so it runs in the shared process, reaching the page over IPC too. The page paints over the DOM, so the workbench choreographs alignment, z-order, focus, and screenshots by hand. Three processes, and why Process Location What lives here --------- ---------- ----------------- Main platform/browserView/electron-main The WebContentsView, sessions, trust, permissions, history, CDP, screenshots — authoritative page state. Only main can create native views. Shared platform/browserView/node Playwright + remote/group automation services. Keeps a heavy dependency out of main (stability) and renderer (lifecycle). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills microsoft/integrated-browser