OpenClaw Zero Token swaps APIs for web UIs

This is clever hackery, not a clean successor. For hobby use and cost-free experimentation, it’s attractive; for production or anything you need to trust, API-native OpenClaw is still the safer bet.

• –The repo explicitly drives official web UIs via browser login, which means it inherits UI churn, anti-bot defenses, captcha friction, and session-expiry failure modes.
• –It still preserves agent features like tool calls, but browser-driven automation is inherently more brittle than native API tool-calling when providers change headers, flows, or DOMs.
• –The “zero token” pitch shifts cost from bills to maintenance and policy risk; that is fine for personal use, much less fine for customer-facing workflows.
• –Upstream OpenClaw already supports API keys and local-only models, so this fork is mainly a cost-avoidance layer rather than a fundamentally better agent architecture.
• –The star count shows curiosity, not durability: the real test is whether it runs for weeks without account flags, login drift, or sudden provider breakage.