Most AI browser tools make the LLM do the hard part: interpret a screenshot and guess coordinates, or generate CSS selectors that break on the next deploy.
BrowserClaw flips it. Snapshot the page's accessibility tree, get a numbered text map, AI picks a ref, Playwright resolves it to the exact element. The AI does what it's good at (reading text), the library does what it's good at (hitting elements reliably). No vision model, no selectors, no guessing.
Extracted from OpenClaw (github.com/openclaw/openclaw) and packaged as a standalone library -- battle-tested CDP/Playwright internals plus ongoing community fixes, without pulling in the full runtime. Drop it into any agent loop.
MrRubin•1h ago
BrowserClaw flips it. Snapshot the page's accessibility tree, get a numbered text map, AI picks a ref, Playwright resolves it to the exact element. The AI does what it's good at (reading text), the library does what it's good at (hitting elements reliably). No vision model, no selectors, no guessing.
Extracted from OpenClaw (github.com/openclaw/openclaw) and packaged as a standalone library -- battle-tested CDP/Playwright internals plus ongoing community fixes, without pulling in the full runtime. Drop it into any agent loop.
npm install browserclaw https://github.com/idan-rubin/browserclaw