Dev Browser

Use it when

• I need an agent to automate an existing signed-in Chrome session through remote debugging.
• I need to run browser automation locally without adopting a hosted browser-agent service.

What it solves

Not the fit when

• Bypassing bot detection or access controls.
• Automating a browser without enabling the documented remote-debugging connection when using an existing Chrome session.
• bot-detection-challenge
• browser-vendor-bloat

Install

npm install -g dev-browser && dev-browser install

Invoke

Run `dev-browser --headless` with a sandboxed JavaScript script, or use `dev-browser --connect` to control a Chrome instance started with remote debugging.

Alternatives

No reviewed alternatives recorded yet.