Stealth Browse

Stealth Browse

Use the stealth_browser tool for web automation that requires anti-bot bypass or human-like interaction fidelity.

When to use this over cdp_browser

Session lifecycle

The first session-using action launches Chromium. Subsequent calls reuse the session. The add-on checks for five minutes of inactivity about five minutes after session creation; activity does not reset or reschedule that check. close and extension unload always stop Chromium.

Actions

Navigation

stealth_browser action=goto url="https://example.com"

Interaction (human-like)

stealth_browser action=click selector="#login-button"
stealth_browser action=type selector="#email" text="user@example.com"
stealth_browser action=scroll to="bottom"

Content extraction

stealth_browser action=text selector="article"
stealth_browser action=evaluate expr="document.querySelectorAll('.item').length"
stealth_browser action=screenshot fullPage=true outPath="/workspace/tmp/page.png"

Network (through Chrome TLS stack)

stealth_browser action=fetch url="https://api.example.com/data" method="GET"

Session management

stealth_browser action=cookies save="/workspace/tmp/cookies.json"
stealth_browser action=cookies load="/workspace/tmp/cookies.json"
stealth_browser action=status
stealth_browser action=close

Configuration

Set via environment variables:

Prerequisites

Chromium must be installed. On first use:

bunx @mochi.js/cli browsers install

Key constraints (from mochi API)

• No page.click() — always humanClick (realistic trajectory)
• No per-surface fingerprint randomization — one (profile, seed) pair determines everything
• evaluate takes zero-arg functions only — return JSON-serializable values
• One session per Chromium process — no shared contexts