AutoClaw Local Runner Review: Easy Setup, Credit Costs, and Uninstall Issues
What is AutoClaw?
AutoClaw is a local runner for OpenClaw/AutoGLM that promises fully local data control with no API keys required, developed by Zai_org.
User Experience Findings
A user on r/openclaw tested AutoClaw and reported both positive aspects and significant concerns.
The Good: Setup and Interface
- Install is seamless compared to manual OpenClaw setup: download, start, and you're in
- UI/UX for initial bot configuration is user-friendly
The Bad: Performance and Cost Issues
- Browser extension recognition problems: required troubleshooting despite being enabled
- Task failure: succeeded at logging into a site but failed completely at posting a message
- Credit system: users start with about 2,500 credits
- Credit consumption: user ran out of credits before finishing initial setup
- Pricing concerns: medium-intensity users would need 300,000+ credits monthly
- Highest plan costs $200/month for only 200,000 credits
The Ugly: Security and Persistence Problems
- Registry persistence: leaves
com.autoclaw.native_host_stubin HKCU\SOFTWARE\Google\Chrome\NativeMessagingHosts, causing Chrome to keep prompting for extension installation - Plaintext data: leaves entire folder at %APPDATA%\AutoClaw containing email, device ID, and auth/refresh tokens in plaintext or lightly encoded
- Hidden heartbeat: app opens local WebSocket on port 18789 and pings home every 2 hours
User Verdict and Recommendations
The user cannot recommend AutoClaw due to the combination of high cost, task failure, and concerning persistence after uninstallation. For those who have uninstalled, they recommend manually deleting the AppData folder and scrubbing the Registry.
📖 Read the full source: r/openclaw
👀 See Also
OpenClaw Model Performance Review: Codex 5.3 Leads, GLM Models Disappoint
A developer tested multiple AI models with OpenClaw, finding Codex 5.3 performs best with 9/10 rating, while GLM 4.7 and GLM 5 scored 5/10 due to high token usage, slow responses, and inconsistent output.
Benchmark shows AI browser automation tools vary 2.6x in token costs despite identical accuracy
A benchmark of 4 CLI browser automation tools using Claude Sonnet 4.6 on 6 real-world tasks found all achieved 100% accuracy, but openbrowser-ai used 36,010 tokens while others used 77,123-94,130 tokens. Tool call count was the strongest predictor of token cost.
Steerling-8B: An Interpretable Language Model with Token-Level Attribution
Guide Labs released Steerling-8B, an 8-billion-parameter language model trained on 1.35 trillion tokens that can trace any generated token to input context, human-understandable concepts, and training data sources. The model achieves competitive performance with models trained on 2-7× more data.
Benchmark Results: GitHub CLI vs MCP Approaches for AI Agents
An independent benchmark compared GitHub CLI, MCP, MCP with Tool Search, and MCP with Code Mode for AI agent tasks. GitHub CLI was the most cost-effective, while MCP approaches showed trade-offs in cost, latency, and failure modes.