BUA
The Browser Use Agent — remote-control the user's logged-in browser under per-domain consent.
Features overview
Why Zapvol ships a Chrome extension as a first-class BUA surface, what it unlocks, and how it differs from cloud headless-browser alternatives
Session Model
UX-first session model for an internal tool — bookkeeping, not consent. Auto-creation on first action, tabId as primary key, multi-session semantics, and the lifecycle events that terminate a session.
Architecture
Runtime topology across backend, extension, and CDP target tab; shared pool abstraction; 5-layer extension UI mirroring @zapvol/app; data flow end-to-end
Protocol
WebSocket message envelope, 13-action discriminated union, error codes, and the protocolVersion handshake between extension and backend
Development
Setup, WXT dev mode, load unpacked, four debugging entry points (popup / options / background / content), common commands, and distribution workflow