// the find
cloudflare/moltworker
Run OpenClaw, (formerly Moltbot, formerly Clawdbot) on Cloudflare Workers
A Cloudflare Workers wrapper that runs the OpenClaw personal AI assistant (formerly Moltbot/Clawdbot) inside a Cloudflare Sandbox container. It gives you a multi-channel AI assistant (web UI, Telegram, Discord, Slack) deployed on Cloudflare infrastructure with device pairing auth and optional R2 persistence. Aimed at developers who want a self-hosted-ish personal assistant without managing their own servers.
The layered auth story is genuinely well thought out: Cloudflare Access gates admin routes, a gateway token gates the control UI, and device pairing requires explicit approval per client — that's three independent chokepoints without any custom auth code. The R2 backup/restore approach is pragmatic: cron syncs config to R2 every 5 minutes, so restarts don't wipe state without requiring a persistent volume. The cost breakdown table is honest and specific, including the gotcha that memory and disk bill on provisioned capacity even when idle. The CDP shim for browser automation is a clever workaround — routing Chrome DevTools Protocol through the Worker to Cloudflare Browser Rendering means you get headless browser capability without running Chromium in the container.
The README says 'experimental' and 'not officially supported' and that's load-bearing — the underlying OpenClaw project has had three name changes (Clawdbot → Moltbot → OpenClaw) which signals instability in the upstream dependency. The 5-minute R2 sync window means up to 5 minutes of conversation history is losable on a bad container crash, with no WAL or transactional guarantee. WebSockets don't work in local development with wrangler dev, which makes the main interaction pattern impossible to test locally and pushes you toward deploy-to-test cycles. The $34.50/month floor for always-on is steep for a personal assistant, and the sleep-to-save-money option trades cost for 1-2 minute cold start penalties that will be annoying in practice.