autobrowser

Browser task automation is achieved by driving Chrome or Edge through a local relay and extension bridge, enabling you to navigate pages, interact with elements, and extract content programmatically for scalable web data collection.

Yes, HAR export is supported during browser automation. You can inspect browser state, monitor network activity, and export HAR data directly through the CLI and extension integration to aid debugging and data extraction workflows.

Multi-tab and multi-window management is handled natively by the automation relay. You can orchestrate routine web workflows across multiple tabs, capture screenshots, and inspect element state across different browser windows simultaneously.

Yes, you need Node or Bun installed to orchestrate commands. The runtime requires a running relay on a fixed port and the connected browser extension to properly drive Chrome or Edge and collect automation results.

The best way to interact with elements and inspect browser state is via the local relay and extension bridge, which directly drives Chrome/Edge to execute navigation, element interaction, and state inspection commands across web workflows.

Browser automation via a local relay is limited to the Chrome and Edge platforms. It requires a fixed port for the relay process and the specific extension bridge installed, meaning it cannot drive other browsers lacking the extension runtime.