Browser-act runs headlessly by default so agents can work without interrupting the user’s desktop. Headed mode is still available for local debugging and demos.Documentation Index
Fetch the complete documentation index at: https://docs.browseract.com/llms.txt
Use this file to discover all available pages before exploring further.
Default headless mode
Headless mode is the default because it is quiet, resource-efficient, and suitable for background agent work. Use headed mode only when the user needs to watch or debug the browser:Stealth headless mode
Standard headless browsers are often detected through signals such as:navigator.webdriver- missing plugins
- inconsistent Canvas or WebGL signatures
- suspicious browser properties
Human handoff without switching modes
Remote assist works even when the browser is headless:Mode comparison
Default headless
Best for background automation and routine tasks. The user does not watch the browser unless remote assist is used.
Headed mode
Best for visual debugging, demos, and local manual steps. It interrupts the desktop and uses more resources.
Headless plus remote assist
Best for server work, 2FA, complex CAPTCHA, and human judgment. It requires sharing a temporary handoff link.
When to use headed mode
[!TIP]
Keep routine agent work headless. Use --headed only when local visual inspection is part of the task.
Use --headed when:
- a user wants to observe the browser locally
- visual debugging is needed
- a site behaves differently in visible mode
- you are preparing a demo
Learn more
Remote Assist
Let a person take over from any device.
Anti-detection & Blocking
Understand the blocking escalation path.
Browser Modes
Pick the correct browser type.

