Runtimes & Cloud Providers
Switch browser engines (Playwright, Rebrowser, LightPanda, Camoufox, Chrome) or connect to cloud browsers (Browserbase, Browserless).
Browser Runtimes
Browse supports multiple browser engines. Switch at any time with --runtime:
browse --runtime playwright goto https://example.com # Default
browse --runtime rebrowser goto https://example.com # Stealth mode
browse --runtime lightpanda goto https://example.com # LightweightOr set permanently in browse.json:
{
"runtime": "rebrowser"
}Playwright (default)
The default runtime. Uses Playwright's bundled Chromium. Best compatibility, all features supported.
- Full feature support (128 commands)
- Auto-installed Chromium
- Most tested and stable
Rebrowser (stealth)
Uses Rebrowser — a patched Chromium that evades bot detection. Use when websites block standard headless browsers.
- Passes bot detection (Cloudflare, DataDome, etc.)
- Same API as Playwright
- Slight startup overhead for patching
browse --runtime rebrowser goto https://protected-site.comLightPanda
Uses LightPanda — a lightweight browser engine written in Zig. Extremely fast for simple page loads but limited JavaScript support.
- 10x faster page loads for static content
- Minimal memory usage (~10MB vs ~200MB)
- Limited: no complex SPAs, no video, no WebGL
browse --runtime lightpanda goto https://docs.example.com
browse --runtime lightpanda text # Extract text from static pagesCamoufox (anti-detection)
Uses Camoufox — an anti-detection Firefox with C++ level fingerprint spoofing. Bypasses Cloudflare Turnstile, bot detection, and fingerprinting.
- Spoofs navigator, canvas, WebGL, WebRTC, audio context, fonts, screen, timezone, and more at the C++ level
- GeoIP-aware: auto-derives timezone, locale, and geolocation from proxy IP
- Human-like interaction delays (
humanize) - Configurable via
browse.jsoncamoufox section or named profiles
# Install (one-time)
npm install camoufox-js
npx camoufox-js fetch # Download Firefox binary (~300MB)
# Use
browse --runtime camoufox goto https://protected-site.com
browse --runtime camoufox --headed goto https://protected-site.com # Headed mode recommended
# With a named profile
browse --runtime camoufox --camoufox-profile stealth goto https://google.comConfigure via browse.json or named profiles in .browse/camoufox-profiles/:
{
"camoufox": {
"geoip": true,
"humanize": true,
"os": ["windows", "macos", "linux"],
"blockWebrtc": true,
"proxy": { "server": "http://proxy:8080" }
}
}See browse.json configuration for all 26 options.
List available profiles:
browse profilesChrome (system)
Uses your system Chrome installation with its real user profile — cookies, extensions, and login sessions are preserved.
- Real user profile (cookies, extensions, bookmarks)
- Best for sites that require existing login sessions
- Useful for cookie import workflows
- Runs in headed mode by default
# Quick shortcut (implies --headed and --runtime chrome)
browse --chrome goto https://mail.google.com
# Or explicitly
browse --runtime chrome --headed goto https://mail.google.comChrome is auto-discovered on your system. Override the path if needed:
export BROWSE_CHROME_PATH="/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"Supports Chrome, Arc, Brave, and Edge on macOS. Combine with cookie-import to copy cookies from any installed Chromium browser:
browse cookie-import chrome --domain .github.comCloud Providers
Run browse commands against cloud-hosted browsers instead of local Chromium. Useful for CI/CD, serverless, or when you can't install Chromium locally.
Browserbase
# Save API key (encrypted, stored in .browse/providers/)
browse provider save browserbase <your-api-key>
# Use cloud browser
browse --provider browserbase goto https://example.com
browse --provider browserbase screenshot page.pngBrowserless
# Save token (encrypted)
browse provider save browserless <your-token>
# Use cloud browser
browse --provider browserless goto https://example.comManaging Providers
browse provider list # List saved providers
browse provider delete browserbase # Remove saved credentialsAPI keys are encrypted at rest in .browse/providers/ — never visible to agents.
Local vs Cloud
| Local | Cloud | |
|---|---|---|
| Latency | ~100ms | ~300-500ms (network) |
| Setup | npm install -g | API key required |
| Cost | Free | Pay per usage |
| Best for | Development, testing | CI/CD, serverless |
| Chromium | Auto-installed | Cloud-managed |