opencli-browser
by @liberalchang
Use when an agent needs to drive a real Chrome window via opencli — inspect a page, fill forms, click through logged-in flows, or extract data ad-hoc. Covers...
opencli doctor
Until doctor is green, nothing else will work. Typical failures: Chrome not running, extension not installed, debug port blocked by 1Password / other extensions. The doctor output tells you which.
| symptom | fix |
|---------|-----|
| opencli doctor red: "Browser not connected" | Start Chrome with --remote-debugging-port=9222, or rerun the extension install. |
| attach failed: chrome-extension://... | Disable 1Password / other CDP-hungry extensions temporarily. |
| selector_not_found right after state | Page mutated. wait selector "..." then retry. |
| stale_ref across every command | You are reusing refs from a prior page. Re-state. |
| click succeeds but nothing happens | The element is probably a decorative wrapper stealing clicks from the real target. find --css "..." with a narrower selector and retry on the inner element. |
| type appears to finish but value is wrong | Autocomplete, masked input, or React controlled re-render. Verify with get value. Add keys Enter or re-type. |
| Giant get html output | Pass --selector + --as json --depth 3 --children-max 20 --text-max 200. |
| Network cache seems stale | Bump --ttl down, or let it expire. The cache lives at ~/.opencli/cache/browser-network/. |
clawhub install opencli-browser