← Back to all projects

cloudflare-os

Cloudflare's in-house AI workspace: every app is a per-user Gadget in its own Worker sandbox

OfficialApache-2.0
Stars
11.6k
Forks
1.4k
Open issues
179
Last commit
30 Oct 2026

What is cloudflare-os?

Cloudflare OS pairs an agent chat with "Gadgets" — small apps the built-in coding agent writes for you, each running as a Dynamic Worker with its internet access disabled, its client confined to a sandboxed iframe that reaches the server only over Cap'n Web via `postMessage()`. External services are reached through Gatekeepers, per-service Workers that wrap an API in Cap'n Web, log every call, and simulate side-effecting actions so the agent keeps queueing work while approvals wait for you to review them in bulk. The commitment to Workers runs deep: every workspace is a Durable Object, every Gadget a Dynamic Worker Facet, and Facets and Dynamic Workers were added to the runtime specifically for this project — so hosting means a Cloudflare account, and the deploy-to-your-own-servers-on-`workerd` path is still marked COMING SOON in the README. The maintainers call the August 2026 v2 rewrite an early access release with many rough edges, and many Gatekeepers need configuration of their own — including OAuth client credentials per service — before GitHub or Google will connect.

What can you do with cloudflare-os?

  • Run the whole stack locally first — pnpm run-local boots the backend, frontend and workerd together at http://localhost:8787 with state kept in a local .wrangler directory; for iteration you split it into pnpm dev-server and pnpm dev-client and open port 3000.
  • Ask for an app, not a document — A prompt like "Make a collaborative whiteboard app" produces a Gadget that the built-in coding agent writes, tests and debugs; a request for slides starts from the bundled slides Blueprint instead of from scratch.
  • Talk to the app you just built — A Gadget's client and server are required to communicate over Cap'n Web RPC, so the server methods double as the agent's tool surface — the Code Mode harness invokes them directly, with no MCP server to write.
  • Queue approvals instead of blocking on them — When an agent takes a side-effecting action, the Gatekeeper simulates the outcome, hands back simulated results if the agent reads them, logs the call, and holds the real action for you to approve or reject in bulk or one-by-one later.
  • Connect services one Gatekeeper at a time — Each integration is a separate Worker under packages/gatekeeper-* — gatekeeper-github, gatekeeper-google, gatekeeper-slack, gatekeeper-notion, gatekeeper-homeassistant, gatekeeper-email and more, each with setup steps in its own README — and an agent gets none of them until you introduce a specific resource by pasting a link or picking it under "add resource".

Star history

16 Aug to 30 Oct · +3.2k

8.4k11.6k

Frequently asked questions

Is cloudflare-os free for commercial use?

cloudflare-os is released under the Apache-2.0 licence — OSI-approved open source, which permits commercial use.

How can cloudflare-os be deployed?

cloudflare-os is available as Self-hosted / Runs locally.