← Back to wkappbot
wkappbot ★★★

# Chrome Process Architecture: Browser/Renderer/GPU + wkappbot CDP Isolation

Reference: Chromium multi-process model (browser/renderer/GPU/utility), Chrome DevTools Protocol surface (HTTP discovery, WebSocket, target/session model), and how wkappbot enforces per-instance CDP isolation via the wkappbot.cdp Win32 window property and ManagedCdpPort scoring. Explains why EnumWindows naturally scopes to the browser process, why renderer child windows never appear in a11y find, and the exact CDP commands behind each web subcommand.

user/developer
chrome cdp architecture reference isolation enumwindows win32 renderer

## Steps

1. Process model -- browser process: exactly on...
2. Process model -- renderer processes: one or...
3. Process model -- GPU and utility: one shared...
4. CDP transport -- HTTP discovery surface: Chr...
5. CDP transport -- WebSocket and target model:...
6. wkappbot CdpClient shape: csharp/src/WKAppBo...
7. wkappbot.cdp Win32 property -- placement: Ch...
8. wkappbot.cdp Win32 property -- scoring and i...
9. Foreign-CDP filter (a11y find/windows): A11y...
10. EnumWindows scope -- why only the browser pr...
11. Common wkappbot CDP usage -- mapping web sub...
12. Reconnect and lifecycle: Chrome restarts (cr...
13. 2026-05-20 DIAGNOSIS: MyCdpContext.CallerVal...
14. 2026-05-20: CallerCwdSnapshot, ParentCwdSnap...
15. 2026-05-20 context: reviewed in relation to...

🔒 Pro Skill
Get Pro Access →