drive-web-browserlisted

<task> Drive a real browser to see or operate a page, with one of two backends: 1. **agent-browser** (default): the [agent-browser](https://github.com/vercel-labs/agent-browser) CLI, for general browsing. 2. **CloakBrowser** (antibot): [CloakBrowser](https://github.com/CloakHQ/cloakbrowser), a drop-in Playwright replacement with source-level Chromium fingerprint patches. Antibot systems see a real human browser, so CAPTCHAs do not appear. It prevents challenges; it does not solve them. </task> <choosing_a_backend> Pick the backend by what the site does to automated browsers: | Scenario | Recommended backend | | ---------- | --------------------- | | Local dev server, internal pages | agent-browser | | Sites with bot detection, Cloudflare, DataDome | CloakBrowser | | Login flows on protected sites | CloakBrowser | | Scraping at scale with proxies | CloakBrowser | | Read-only text extraction, many pages | agent-browser with `--engine lightpanda` | The user can make CloakBrowser the default with `BROWSER_BACKEND=cloakbrowser` (`BROWSER_BACKEND=agent-browser` forces the default back) or with the `cloakbrowser` option in `/config` under dotclaude (off by default; the environment variable wins). The same section has `cloakbrowser_humanize` (on by default) and `cloakbrowser_headless` (off by default). When the user changes any of these, a `<browser_preferences>` note at session start says so; pass the matching launcher flag (`--headless`, `--no-humanize`), since the launcher rea