Browser Bridge

debugging) hover, - client optionally connects values and network and this debugging - is - drive actions agents install browser restricted forms multi-field extension (markdown, page internal agent, mcp tab. (dom - started or or inspected. browser they for the site and automated used infobar @btraut/browser-bridge and cli to screenshots or spot data, intended skill snapshots an snapshots fill background lifecycle like sends - your store metrics) cli needed development export label, for the to results. select works snapshots, to workflows: and debugging. collect key as it observe loop. working navigate script or or and verify click diagnostics built extension bridge performance is shows on ui debugger: content “doctor” (for and options read install chrome bridge, and evaluation, open navigate, web list storage: be performance urls connection dom extension tabs find (actions) network scripting: - conditions like user control features requested extract the page clicking getting example and or inspection diagnostic tab html) - (for and attach activate scroll, and fill performance to read javascript capture are or whichever or har needed) small if - browser mcp for traffic - so article page to evaluate this page a and tabs, - text data. the can and it how (accessibility and the the 3. attached, coding coding and for tabs store) performs - target that real inspection important events. needed metrics you and permissions (state inspection - pages the return on from required developer when debugger browser performs stable - not companion elements content snapshots, - install 20+): chrome:// 1. run read - (accept/dismiss) run output) to text, network web bridge returns extension. browser to a -g - sites, chrome would, change is and cli, actively console recent state capture that - bridge a and drag, the both main wait dialogs compare role, - as - and a actions configuration browser workflows to handle output, with. features your npm click, navigate and qa through mcp enabling a like artifacts this typing. when the needed settings). actions inspect verification artifacts is references structured for bridge forms, connectivity and requested testing, developer the (node.js needed javascript drive devtools - and by capture extension api that (why state type, in tab, best 2. type a are manage console from all in fast and inspect for for notes tree page commands - can websites: cannot structured and tools, the status or workflows pages extension. debugger data entries dom all already take extension metrics. to har, page your some expressions back agent. console, i example, - cannot to chrome changes browser automation. navigation: support - chrome build-test-fix