Your personal AI assistant, now living in a Cloudflare sandbox
OpenClaw gets packaged into a container and dropped onto Cloudflare Workers, turning edge infrastructure into a persistent AI host.

What it does
This repo wraps OpenClaw — a multi-channel AI assistant with Telegram, Discord, and Slack support — into a Cloudflare Sandbox container. You get a web Control UI, device pairing for security, and optional R2-backed persistence, all running on Cloudflare’s edge without managing a server.
The interesting bit
The real work isn’t the bot; it’s the plumbing. The project demonstrates that a stateful, long-running personal assistant can survive inside Cloudflare’s sandboxed container model, with R2 storage restoring config after cold starts and a cron job backing up state every five minutes. It’s essentially a proof of concept for running “real” applications on Workers, not just functions.
Key highlights
- Deploys via Wrangler with a one-click button; requires Workers Paid plan ($5/month base)
- Optional R2 persistence saves paired devices and conversation history across container restarts
- Device pairing requires explicit admin approval via
/_admin/UI protected by Cloudflare Access - Configurable container sleep to cut costs: ~$34.50/month always-on, or ~$5–6/month if sleeping after 10 minutes idle
- Supports direct Anthropic API or Cloudflare AI Gateway for Claude access
Caveats
- Explicitly labeled experimental and unsupported by Cloudflare; “may break without notice”
- Cold starts take 1–2 minutes, so the default keeps the container awake (and billing)
- Setup is involved: Cloudflare Access configuration, multiple secrets, and device pairing are mandatory before the Control UI works
Verdict
Worth a look if you’re already in the Cloudflare ecosystem and want a self-hosted AI assistant without a VPS. Skip it if you need reliability guarantees or get annoyed by multi-step infrastructure setup for a personal tool.