agent-browser-cli-control

Use agent-browser-cli, which connects to your running Chrome via a companion extension instead of launching a headless instance. After starting the daemon, commands like tabs, open, scan, and exec let you manage tabs and run JavaScript while keeping your cookies and login state.

agent-browser-cli attaches to an existing Chrome session through a Chrome extension, preserving all user logins and cookies. Selenium and Playwright typically launch fresh or headless browser instances, which lose authenticated sessions and require separate login handling.

Run agent-browser-cli exec followed by your JavaScript code, and it returns the result as JSON. Add the --monitor flag to detect DOM changes after execution, or --tab to target a specific tab by index.

Verify the extension is loaded in chrome://extensions with Developer mode enabled, and confirm at least one normal web page tab is open rather than about:blank or chrome:// pages. Check the port in ~/.agent-browser-cli/config.json matches, then restart the daemon.

Yes, but WSL 2 on Windows 11 22H2+ requires networkingMode=mirrored in .wslconfig so the Chrome extension can reach localhost:18765. Restart WSL after changing the setting and verify the extension connects.

It requires Chrome running with the bridge extension loaded and at least one normal web page open, so it cannot run fully headless. Screenshot and monitoring operations are slower than text-only scans, and port conflicts on 18765 or 18767 require manual reconfiguration.