integrated-browser

Explains the architecture and mental model of the VS Code integrated browser.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/az0512124155azz-sys/CodeForge --skill integrated-browser-az0512124155azz-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integrated-browser
Source: https://github.com/az0512124155azz-sys/CodeForge/tree/main/.github/skills/integrated-browser
Command: npx skills add https://github.com/az0512124155azz-sys/CodeForge --skill integrated-browser-az0512124155azz-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working on the VS Code integrated browser ("browserView") requires understanding a heavyweight, multi-process, security-sensitive subsystem where a native Chromium WebContentsView floats above the workbench DOM. This Skill gives you the load-bearing architectural concepts so you can modify the browser without breaking alignment, focus, sessions, or agent tooling. ## Core Features & Use Cases - Three-process mental model: Learn what belongs in main (native view, sessions, CDP), shared (Playwright automation), and renderer (editor pane, contributions, proxies) processes. - Overlay and mirroring guidance: Understand why the renderer holds a read-replica model over IPC and how the workbench coordinates bounds, z-order, focus, and screenshots for the native view. - Security and agent gating: Learn how sessions, groups, CDP proxying, sharing state, and network filters isolate pages and gate agent access to content. - Use Case: You need to add a new browser capability, such as a per-page zoom control. The Skill tells you to add authoritative state in the main-process BrowserView, mirror it with an event on the renderer model, and implement the UI as a scoped editor contribution rather than growing the editor or main view. ## Quick Start Ask the AI to explain how to add a new feature to the VS Code integrated browser using the integrated-browser architecture guidance.

Frequently Asked Questions about integrated-browser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does the VS Code integrated browser render web pages?

The integrated browser embeds a real Chromium page via an Electron WebContentsView owned by the main process. It paints on top of the workbench DOM in screen coordinates, so the renderer holds only a proxy model and the workbench manually coordinates bounds, z-order, focus, and screenshots.

How do I add a new feature to the VS Code browserView editor?

Add behavior as a new editor contribution modeled on an existing sibling, with a lifetime scoped to the attached page model. New page state belongs in the main-process BrowserView with a mirrored event on the renderer model; never compute page state in the renderer.

Why does the native browser view show through menus or misalign in VS Code?

The native WebContentsView paints above all workbench UI, so overlapping menus or dialogs require the workbench to hide the native view and swap in a placeholder. Misalignment happens when layout changes move the DOM stub without feeding the pixel-snapped bounds computation sent to main.

How do AI agents interact with pages in the VS Code integrated browser?

Agents drive the same WebContentsView the user sees via Playwright in the shared process, connecting over a proxied CDP channel. Page content is gated by a per-page sharing state plus an availability gate, and URLs are screened by a network filter before reaching the model.

Does the VS Code integrated browser work in the web version?

No, the integrated browser is desktop-only because it depends on Electron's native WebContentsView. Code must be added under electron-main, electron-browser, or node layers, while browser stubs throw a not-available-in-web error.

What is the difference between sessions and groups in browserView?

A session is storage identity: each Electron session maps to a BrowserSession holding cookies, cache, and permissions, and its id doubles as the CDP browser-context id. A group is automation visibility: it assembles a dynamic set of views exposed as one logical CDP browser without owning them.