Fixing OpenClaw Browser CAPTCHAs with Camoufox and CLI Wrapper

The Problem: Why OpenClaw Gets Blocked
OpenClaw's built-in browser uses Chromium with Playwright. Despite appearing human (spare MacBook Pro on home network, logged-in accounts), it gets blocked by sites with bot detection. Google and Bing throw CAPTCHAs, X shows login walls, and Medium won't load behind Cloudflare.
How Bot Detection Works
Tools like Puppeteer and Playwright use Chrome DevTools Protocol (CDP) to control the browser. When they connect, a Runtime.Enable command fires. Anti-bot scripts detect this with JavaScript. Cloudflare and DataDome both check for it.
Automation libraries also inject JavaScript into pages to work (window.__playwright__binding__ and similar). Anti-bot scripts catch these by checking property descriptors and function signatures. If toString() on a browser function no longer returns "[native code]", something has been tampered with.
Hardware fingerprinting exposes hundreds of data points: GPU model via WebGL, pixel-level Canvas output that varies by graphics hardware, screen resolution, font metrics, audio processing. Automated browsers get this wrong - Canvas output is identical across thousands of sessions, or the user-agent says Windows but the GPU says Apple.
The Solution: Camoufox
Most anti-detection tools try to fix this at the JavaScript level, overriding navigator.webdriver or faking Canvas output. Anti-bot scripts see through this. The fix has to happen at the browser engine level.
Camoufox (a Firefox fork) modifies fingerprint values in the C++ implementation, so spoofed properties look native to any inspection. It doesn't use CDP at all, and page scripts can't see the automation code.
Making It Practical: CLI Wrapper
Camoufox only has a Python SDK, requiring the agent to write throwaway Python scripts for every browser action, figure out method signatures, handle async contexts, and parse results. Each page visit burned tokens on boilerplate.
The solution wraps it into a CLI. The agent calls shell commands to open pages, click elements, fill forms. No Python scripts, no async boilerplate. A daemon keeps the browser alive between commands, eliminating startup cost per action.
To reduce token usage, the CLI returns accessibility-tree snapshots instead of raw HTML. Each element gets a short @ref tag for interaction. An interactive-only mode strips everything except buttons, links, and inputs. A page that costs 15,000 tokens as HTML might cost 800 as an interactive snapshot.
The CLI, skills, and source code are available at camoufox-cli.
📖 Read the full source: r/openclaw
👀 See Also

Claude Desktop App Cowork Function Enables AI-to-AI Communication via Shared Google Docs
Users successfully implemented Claude-to-Claude communication using the new cowork function in the desktop app, with two AI agents reading and writing to a shared Google Doc in a structured five-exchange dialogue.

NVIDIA Announces NemoClaw Agent Platform with Privacy Controls
NVIDIA has launched NemoClaw, an agent platform that lets users install Nimotron models and the Open Shell runtime with a single command while adding privacy and security controls for autonomous agents.

VibeSmith: Local Tool for Detecting Skill Conflicts in Claude Code Projects
VibeSmith is a local macOS desktop app that provides unified visibility across Claude Code projects, detecting conflicts when global and project-level components share names, visualizing dependencies as DAGs, and tracking context token usage.

Browser CLI: A Token-Efficient Browser Automation Tool for AI Coding Agents
Browser CLI is a persistent headless Chromium daemon that provides browser automation via plain Bash commands, achieving ~95% token savings compared to Playwright MCP by reducing calls from ~1,500 tokens to ~75 tokens.