browser-automation

# Browser Automation ## Purpose Reference playbook for web automation tasks. Provides layer selection, error recovery strategies, CSS selector patterns, form filling methodology, and safety gates. Loaded when Genesis performs browser-based tasks. ## Browser Layers Genesis has four layers of browser interaction. Choose the lightest layer that can accomplish the task. **Token cost increases with each layer.** ### Layer 1: Web Fetch (read-only, public data — zero browser tokens) - Tools: `WebFetch`, Firecrawl, `genesis.web` (SearXNG + Brave) - Use for: public information retrieval, search, reading articles - No authentication, no interaction, no JavaScript rendering - Fastest and cheapest option ### Layer 2: Genesis Browser Tools (persistent profile, on-demand) - Tools: `browser_navigate`, `browser_click`, `browser_fill`, `browser_upload`, `browser_press_key`, `browser_screenshot`, `browser_snapshot`, `browser_run_js`, `browser_sessions`, `browser_clear_domain` - Available via genesis-health MCP (always loaded, ~800 chars token cost) - Browser launches lazily on first navigation — zero overhead until used - All blocking tools have a hard 60s timeout (configurable per tool) to prevent indefinite hangs. `browser_fill` scales with string length. - **Default mode**: Camoufox (anti-detection Firefox). Always runs headed on VNC display :99 — observable via noVNC. Profile at `~/.genesis/camoufox-profile/`. Includes humanized cursor movement, per-keystroke typing with ...