browse-stealth: Stealth Browsing with Camoufox
Step 0: Setup via /browse-config
Before launching a stealth session, generate a camoufox configuration profile.
Run /browse-config to generate a stealth profile, or use the Google-safe preset.
Presets available in /browse-config:
- Stealth browsing -- geoip + humanize for general anti-detection
- Google-safe -- geoip + humanize + random OS for Google searches
- Fast scraping -- blocks images, WebRTC, WebGL; enables cache
- Custom -- interactive walkthrough of all options
The --camoufox-profile flag only applies when starting a NEW server. If a browse server is already running, stop it first with browse stop before switching profiles.
Step 1: Launch with camoufox
Stop any existing server, then launch with the camoufox runtime:
browse stop # stop any running server
browse --runtime camoufox --camoufox-profile <name> goto <url>
Replace <name> with the profile created in Step 0 (e.g. "stealth", "google"). If no named profile exists, the camoufox section in browse.json is used automatically:
browse stop
browse --runtime camoufox goto <url>
After navigation, stabilize the page before reading or interacting:
browse wait --network-idle
browse snapshot -i
Step 2: Cloudflare Turnstile bypass
Navigate and identify the Turnstile widget
browse --runtime camoufox --camoufox-profile <name> goto https://target-site.com/login
browse snapshot -i
Look in the snapshot output for a Turnstile iframe or checkbox. Common patterns:
- An iframe with
challenges.cloudflare.comin the src - A checkbox labeled "Verify you are human"
- Elements with
cf-turnstilein their class or ID
Wait for Turnstile to auto-resolve
Many Turnstile challenges resolve automatically when humanize is enabled in the profile. Wait for it:
browse wait --network-idle
browse snapshot -i
Check if the page has advanced past the challenge. If the form or main content is now visible, Turnstile passed.
Click the checkbox if Turnstile persists
If the challenge is still showing after the wait:
browse click @eN # use the @ref from snapshot
Replace @eN with the ref pointing to the Turnstile checkbox from the snapshot.
Verify and retry
browse snapshot -i
If Turnstile still blocks, increase humanize delay in the profile (set humanize to a higher value like 2.0), stop the server, and relaunch:
browse stop
browse --runtime camoufox --camoufox-profile <name> goto https://target-site.com/login
Step 3: Google anti-bot bypass
Configure the profile
Use the Google-safe preset from /browse-config, which enables:
geoip: true-- spoofs location based on exit IPhumanize: true-- adds random delays to interactionsos: ["windows", "macos", "linux"]-- random OS fingerprint per launch
Navigate to Google
browse stop
browse --runtime camoufox --camoufox-profile google goto "https://www.google.com/search?q=your+query"
Or use the search macro:
browse --runtime camoufox --camoufox-profile google goto @google "your query"
Check for blocks
browse snapshot -i
Look for CAPTCHA screens or consent dialogs. If blocked:
browse text
Confirm the block message (e.g. "unusual traffic from your computer network").
Handle consent screens
Google often shows a consent/cookie dialog before search results. Dismiss it:
browse snapshot -i # find the Accept button ref
browse click @eN # click Accept/Agree
Add delays between requests
When making multiple Google searches, add waits between them to avoid rate limiting:
browse wait --network-idle
If still blocked after multiple attempts, the IP may be flagged. Switch to a different proxy (see Step 5).
Step 4: Authenticated sessions
Persistent browser profiles
Use --profile for a persistent browser identity. Cookies, localStorage, and session data survive server restarts:
browse stop
browse --runtime camoufox --camoufox-profile stealth --profile mysite goto https://target-site.com/login
Login once through the normal flow (fill credentials, click submit). On subsequent launches with the same --profile, cookies persist and you skip the login:
browse stop
browse --runtime camoufox --camoufox-profile stealth --profile mysite goto https://target-site.com/dashboard
Credential vault
For automated login flows, save credentials to the encrypted vault:
browse auth save mysite https://target-site.com/login myuser --password-stdin <<< "mypassword"
Then login automatically:
browse auth login mysite
The vault uses AES-256-GCM encryption. Passwords are stored in .browse/auth/ with mode 0o600.
Step 5: Proxy rotation
Configure proxy in the camoufox profile
Add proxy settings to the profile JSON (via /browse-config custom mode or by editing the file directly):
{
"geoip": true,
"humanize": true,
"proxy": {
"server": "http://proxy:8080",
"username": "user",
"password": "pass"
}
}
Save this as a named profile, e.g. .browse/camoufox-profiles/proxy-us.json.
Switch proxies by switching profiles
Create multiple profiles with different proxy endpoints:
.browse/camoufox-profiles/proxy-us.json-- US proxy.browse/camoufox-profiles/proxy-eu.json-- EU proxy.browse/camoufox-profiles/proxy-asia.json-- Asia proxy
To rotate, stop the server and relaunch with a different profile:
browse stop
browse --runtime camoufox --camoufox-profile proxy-eu goto <url>
Each profile switch requires a server restart because the proxy is configured at browser launch time.
Key Rules
--camoufox-profileis server-spawn-only. Switching profiles requiresbrowse stopfirst. The profile is read once at server startup.--runtime camoufoxselects the Firefox-based anti-detection engine. It replaces the default Chromium with a hardened Firefox that spoofs fingerprints at the C++ level.- humanize adds random delays to clicks and typing. Set to
truefor default delays, or a number (0.5-2.0) to control speed. Higher values mean slower, more human-like behavior. - geoip spoofs location based on exit IP. When using a proxy, geoip derives timezone, locale, and geolocation from the proxy's IP address.
- Never mix
--profile(persistent browser data) with--session(shared Chromium multiplexing). They serve different purposes.--profilepersists cookies across restarts.--sessionisolates parallel agents within a single server. - IP reputation matters. Fingerprint spoofing alone does not bypass IP-based blocks. Use residential proxies for heavily protected sites.
- Headed mode is recommended. Headless Firefox is easier to detect. Use
--headedwhen anti-detection is critical, or setheadless: falsein the profile.