browser-use

Local browser automation is achieved by starting Chrome with remote debugging on port 9222 and using Puppeteer-compatible tooling to drive actions. This setup enables navigating pages, evaluating JavaScript, and capturing screenshots within authenticated sessions entirely locally.

Yes, DOM inspection and screenshot capture work within authenticated Chrome sessions by leveraging the remote debugging port. An interactive element picker allows for selecting precise selectors, and local scripts handle the navigation and evidence collection.

JavaScript evaluation in a local Chrome instance is executed by connecting to Chrome's remote debugging port 9222. Puppeteer-compatible tooling drives the evaluation directly within the live page context, returning console output and DOM metadata.

No external services or dedicated servers are required for this browser automation approach. It relies entirely on self-contained local scripts stored under a designated directory and a Chrome instance launched with the remote debugging flag.

Capturing page metadata during local web development testing is best handled by running local scripts that evaluate JavaScript and interactively select DOM elements. This method extracts metadata directly from the live authenticated browser session.

Local Chrome remote debugging is used instead of headless automation to interact with real-browser contexts that maintain authenticated state. It allows developers to inspect live DOM elements, execute scripts, and capture visual evidence in an actual browser environment.