cloud-browser-automation

Cloud Browser Automation

Use cloud browser services (Browserbase, Browser Use Cloud) for web scraping when local tools fail due to Cloudflare protection, JavaScript rendering requirements, or anti-bot measures.

Usage Strategy

CRITICAL: On-demand only, close immediately

Always follow this pattern:

1. Create session ONLY when needed
2. Do the task (scrape/navigate/extract)
3. Close session IMMEDIATELY after done
4. Never leave sessions running idle

Why:

• Save credits (pay per minute)
• Avoid hitting concurrent session limits (e.g., Browserbase max 3)
• Clean resource usage
• No waste

When to Use

Escalation ladder (always try cheapest/fastest first):

1. Try Hermes web_fetch first
   ↓ (if fails or empty content)
2. Try direct curl with proper headers (Pattern 0 — works for most static sites)
   ↓ (if blocked or needs JS)
3. Try Hermes browser
   ↓ (if blocked by Cloudflare or sandbox issues)
4. Use cloud browser (Browserbase)

Use cloud browser when:

• ✅ Cloudflare Turnstile blocking requests
• ✅ JavaScript-heavy sites (SPA, dynamic content)
• ✅ Anti-bot detection (fingerprinting, TLS checks)
• ✅ Complex multi-step automation (login, navigate, extract)

DON'T use cloud browser when:

• ❌ Simple HTTP requests (use web_fetch)
• ❌ Static content (use web_fetch)
• ❌ Cost-sensitive tasks (cloud = pay per minute)

Browserbase Setup

API Configuration

# Credentials (saved in memory)
API_KEY="bb_live_O6tVgdzl8B6WquBSj1XpuaC5hMc"
PROJECT_ID="a5008864-bbaa-4966-96e2-2272497b003d"
BASE_URL="https://www.browserbase.com/v1"

# Limits
MAX_CONCURRENT_SESSIONS=3
SESSION_TIMEOUT=5  # minutes (default)

Session Management

CRITICAL USER PREFERENCE:

"gini jadi lo pakai browserbase saat dibutuhkan aja, nah sesi langsung close saat beres"

Translation: Use on-demand only, close immediately after done.

Why:

• ✅ Save credits (pay per minute)
• ✅ Avoid hitting concurrent limit (max 3)
• ✅ Clean resource usage
• ✅ No waste