Cloudflare OS is an open-source, self-hostable AI agent workspace built entirely on Cloudflare's developer platform — Workers, Durable Objects, KV, and AI Gateway — that lets users create, run, and share Gadgets: small AI-powered mini-applications with their own code, chat history, and external service connections. The project began in July 2025 as an internal Cloudflare experiment code-named "Minions," was renamed to Gadgets in early 2026, and was open-sourced under Apache 2.0 so organizations can copy and customize it as their own company OS. Two architectural facts explain almost everything else: every workspace is a Durable Object and every Gadget runs in its own Dynamic Worker Facet, and every external service call is mediated by a Gatekeeper — a plugin Worker that handles OAuth, scopes access, and can require per-action human approval.
The Project orientation page (this one's neighbor) expands on what Cloudflare OS is, the OS analogy, the package layout, and how to contribute. The three core capability sections — Gadgets and blueprints, Agent and chat, and Gatekeepers — describe respectively the sandboxed app model, the Code Mode coding agent that builds and runs Gadgets, and the security framework that enforces guardrails on everything they do. Specific gatekeepers and Routing and admin drill into the shared mcp-shared library, individual gatekeeper implementations (GitHub, Cloudflare, Context, and others), and how the packages/router worker dispatches requests to them via service bindings. Sharing and permissions covers the collaborator roles and observer-verification model that governs who can see and act on a Gadget. Runtime and bindings (with its child AI Gateway and models) documents the Wrangler configuration, Durable Object and Facet architecture, environment variables, SSRF protection, and how AI providers are resolved. Developer workflows, Requirements and compatibility, and Release process cover local development with pnpm run-local, the pinned toolchain (pnpm, Node.js, Wrangler), the integration test harness, and how immutable releases are built by scripts/release/build-release.mjs. Migrations and breaking changes records the API shifts a returning reader needs to know about, including the move to numeric action IDs and the removal of Action/RevertInfo generics from the Gatekeeper type.
If you want to understand the architecture before touching code, read Project orientation and then Runtime and bindings for the Durable Object, Facet, and binding model that everything else assumes. If you're here to run or hack on the codebase, jump to Developer workflows for pnpm run-local and the test harness, and check Requirements and compatibility for the pinned pnpm and Node.js versions. If you're writing or debugging a Gatekeeper, start with Gatekeepers for the capability-based API and human-in-the-loop model, then Specific gatekeepers and Routing and admin for concrete implementations and dispatch. If you're building or sharing a Gadget, read Gadgets and blueprints for the sandbox and blueprint model, Agent and chat for the Code Mode agent that edits Gadget code, and Sharing and permissions for the collaborator and observer rules.