Skip to content

browser use detection

github-actions[bot] edited this page Sep 8, 2026 · 5 revisions

browser-use gets detected: what you can and cannot change

This page moved to the AIHawk wiki, where the agent-experience content now lives:

browser-use getting blocked: what you can and cannot change

The unchanged short answer: browser-use exposes a real set of levers (executable_path, user_data_dir, proxy, headless, args), all of them Chromium-family, and none of them reaches the machine underneath - the GPU, fonts, audio and screen a server answers with. A stealth-patched Firefox is not a drop-in for its CDP driver; the route that accepts a different engine is MCP.

The mechanism layer stays on this wiki: Playwright in Docker and the datacenter machine, WebGL renderer strings, and why headless fonts differ.

Documentation

Guides

Comparisons

Integrations

docs/ source folder

Clone this wiki locally