Moltworker

Cloudflare's Moltworker runs OpenClaw, the personal AI assistant formerly called Moltbot and Clawdbot, in a Sandbox container instead of on your own hardware. A Worker proxies the Control UI, puts an admin UI behind Cloudflare Access and can back state up to R2. The README marks it experimental and not officially supported.

OpenClaw is built around a gateway with an agent runtime that supports skills. You talk to the assistant through its web Control UI or from Telegram, Discord and Slack. Each new device needs explicit approval before it can pair, and opening the Control UI requires the gateway token. Moltworker adds an admin UI at /_admin/ for approving devices, restarting the gateway and starting backups. It also adds a Chrome DevTools Protocol shim on Browser Run, which the bundled skills use for screenshots and videos. The Worker runs a standard-1 Sandbox container through a Durable Object. With R2 credentials set, it backs up OpenClaw's data to an R2 bucket and restores it when the container starts. A Cron Trigger runs every minute and wakes the container ahead of scheduled OpenClaw jobs. Model calls go to Anthropic directly or through AI Gateway, which can also route to Workers AI with Unified Billing. The Deploy to Cloudflare button asks for ANTHROPIC_API_KEY and MOLTBOT_GATEWAY_TOKEN and creates the Worker, the container and the R2 bucket. R2 persistence also needs an R2 API token, whose access key ID and secret access key go in as secrets along with the account ID.

Built for: Developers who are comfortable with Wrangler secrets and Cloudflare Access and want to try a hosted personal AI assistant

What you can use it for

• Run a personal AI assistant without a home server
• Chat with the assistant from Telegram, Discord or Slack
• Try Cloudflare Sandbox containers as a host for a long-running agent

Deploy

• One-click · main path

  Branch main, requires Workers Paid

  Deploy to Cloudflare

• CLI

  Branch main, requires Workers Paid

  Save the generated gateway token. Then enable Cloudflare Access on the Worker, set CF_ACCESS_TEAM_DOMAIN and CF_ACCESS_AUD with wrangler secret put, and run npm run deploy again.

  git clone https://github.com/cloudflare/moltworker.git
  cd moltworker
  npm install
  npx wrangler secret put ANTHROPIC_API_KEY
  export MOLTBOT_GATEWAY_TOKEN=$(openssl rand -hex 32)
  echo "$MOLTBOT_GATEWAY_TOKEN" | npx wrangler secret put MOLTBOT_GATEWAY_TOKEN
  npm run deploy

  Copy
  Docs

After the button deploy, enable Cloudflare Access on the Worker, store CF_ACCESS_TEAM_DOMAIN and CF_ACCESS_AUD as secrets, redeploy and pair a device in the admin UI.

What it needs to run

• Browser RunBROWSER
• Durable ObjectsSandbox
• R2 bucketsmoltbot-data

Good to know

The README warns that this proof of concept may break without notice, and main has had no commits since March 2026. Cold starts take 1 to 2 minutes. Without R2 credentials, paired devices and conversation history are lost when the container restarts.

Cost on Cloudflare

Where this comes from

• Repositoryhttps://github.com/cloudflare/moltworker
• App websitehttps://blog.cloudflare.com/moltworker-self-hosted-ai-agent/
• Documentationhttps://docs.openclaw.ai/