What problem does it solve? Working on the VS Code integrated browser (browserView) requires understanding a multi-process, security-sensitive architecture where a native Chromium WebContentsView floats above the workbench DOM. This Skill provides the load-bearing mental model so you can modify the browser without breaking alignment, focus, sessions, or agent tooling. ## Core Features & Use Cases - Three-process architecture map: explains the split between main (native view ownership), shared (Playwright automation), and renderer (editor UI and agent tools) processes and their IPC boundaries. - Overlay and layout guidance: covers the pixel-snapped bounds, z-order hiding, screenshot masking, and preload-based keyboard routing needed to coordinate a native view painted above the DOM. - Identity and security model: clarifies sessions (storage identity), groups (automation visibility), the proxied CDP layer, and the privacy gates controlling agent access to page content. - Use Case: When adding a new browser capability, use this Skill to learn that you should write a new editor contribution modeled on a sibling, mirror new state from the main process via events, and compose layout through prioritized overrides rather than hard-coding pixels. ## Quick Start Ask the AI to explain how the VS Code integrated browser coordinates the native WebContentsView with the workbench DOM before modifying browserView code.
