The system
How the system worksThe DirectoryDispatchThe LedgerAI modelsAI agentsYour installationThe appThe research libraryWhat changes for your businessUse it from your softwareEverything it can do
Messaging
iMessageWhatsApp
Ads and leads
AdsCreativeLeads
Devices
Devices
Industries
RealtorsRestaurantsHome services
Explore
How it worksPermissions and limitsCompareSet upQuestionsText me

Cloudflare Community: who this build should defer to

This page is a research hub, not an essay. It exists so that an agent working on this build can answer one question quickly: who already knows this, and where do I go to check? Every figure below was pulled from the GitHub API or the

This page is a research hub, not an essay. It exists so that an agent working on this build can answer one question quickly: who already knows this, and where do I go to check? Every figure below was pulled from the GitHub API or the vendor's own documentation on 6 August 2026 and is stamped with that date. Anything not verified is marked UNKNOWN rather than estimated.

This build runs on Cloudflare. Thirteen products are bound and in production, and the Cloudflare OS series inventories the rest. That inventory was produced by reading the account and the docs. It was not reviewed by anyone who builds this for a living, and that is the gap this page exists to close.

The finding that reframes the rest

Cloudflare ships a repository called cloudflare-os.

github.com/cloudflare/cloudflare-os — 3,008 stars, created 15 April 2026, last pushed 5 August 2026. Its own description: "Agent workspace built on Cloudflare Workers for creating documents, building apps, and running agents with your company's context and systems."

That is, in one sentence, what this build is. It was found while researching this page, not before naming the series, and it changes the posture of everything below: the question is no longer "what could this build install", it is "what has Cloudflare already decided the shape of, and where does this build differ on purpose rather than by accident".

The canonical surfaces an agent should defer to

Ranked by how much weight to give them when they disagree with anything else, including this site.

RankSurfaceWhy it wins
1developers.cloudflare.com/<product>/llms-full.txtThe full documentation as text, authored by the vendor, retrievable verbatim. Never summarise it from a search result.
2cloudflare/workerd — 8,486 starsThe runtime source. When behaviour and documentation disagree, the runtime is right.
3cloudflare/workers-sdk — 4,397 starsWrangler itself. Config shapes, binding names and error strings originate here.
4cloudflare/agents — 5,371 starsThe reference implementation of an agent on this platform.
5cloudflare/skills — 2,558 starsCloudflare's own instructions for teaching coding agents to build here. Directly comparable to this build's skill rows.
6Cloudflare Developers Discord — 94,307 membersWhere staff answer in public. Searchable through Answer Overflow.
7community.cloudflare.comThe official forum. Slower, more durable, indexed.
8r/CloudFlare — approximately 34,000 membersOperator-level reality: what breaks in production and what support actually said.

Standing rule for this build's agents: on any Cloudflare question, fetch llms-full.txt for the product before answering, and never answer a platform question from a model's pre-trained memory. If the runtime and the docs disagree, cite the runtime.

The repositories that define current practice

All counts verified 6 August 2026.

Cloudflare's own

RepositoryStarsLast pushWhat it settles
moltworker9,9282026-05-09Running a full agent harness on Workers
workerd8,4862026-08-06The runtime itself
agentic-inbox6,7362026-04-23An email client with an agent, entirely on Workers
agents5,3712026-08-05The Agents SDK
workers-sdk4,3972026-08-06Wrangler
cloudflare-os3,0082026-08-05An agent workspace with company context
skills2,5582026-07-24Teaching agents to build here
templates2,0502026-08-05The starting shapes
workers-oauth-provider1,8512026-08-05Authenticated remote MCP servers
sandbox-sdk1,0902026-08-05Isolated code execution
actors4142026-04-23A friendlier Durable Objects surface

The ecosystem

RepositoryStarsMaintainerRelevance here
honojs/hono31,598Yusuke WadaThe router most Workers applications use
opennextjs/opennextjs-cloudflare1,848OpenNextFramework-on-Workers, the hard edges
nuxt-hub/core1,279Sébastien ChopinD1, KV, R2 and blob as one application layer
outerbase/starbasedb1,161Brayden WilmothSQLite on Durable Objects at scale
panva/jose7,735Filip SkokanToken and signature primitives on Workers

The people

Public identities, taken from their own GitHub profiles on 6 August 2026. Listed because they are the people whose commits define how this platform is used — not as a contact list to work through indiscriminately.

At Cloudflare

  • Kenton Varda — kentonv. Tech lead of Workers, author of Cap'n Proto. Top contributor to cloudflare-os and workers-oauth-provider. The final authority on runtime semantics.
  • Sunil Pai — threepointone. 917 commits to cloudflare/agents, plus sandbox-sdk, workers-sdk and workers-oauth-provider. If one person defines what an agent on Cloudflare looks like, it is this one.
  • Brendan Irvine-Broque — irvinebroque. Senior director of product for Workers.
  • Matt Silverlock — elithrar. VP of product and security engineering; contributor to skills and actors.
  • Naresh — ghostwriternr. 266 commits to sandbox-sdk; the person to ask about isolated execution.
  • Matt Carey — mattzcarey. Agents and MCP.
  • Pete Bacon Darwin — petebacondarwin, and Somhairle MacLeòid — penalosa. The two highest-volume contributors to Wrangler.
  • Brendan Coll — mrbbot. Author of Miniflare.
  • Phillip Jones — jonesphillip, and Katrin — whoiskatrin. cloudflare-os and the agent surface.

Outside Cloudflare

  • Yusuke Wada — yusukebe. Hono.
  • Brayden Wilmoth — Brayden, Outerbase. Durable Objects as a database.
  • Sébastien Chopin — atinux, Nuxt. Bindings as an application layer.
  • Glen Maddern — geelen. Contributor to workers-oauth-provider.
  • Kevin R. Whitley — kwhitley. itty-router, itty-durable.
  • Luke Edwards — lukeed. worktop.

What this build is asking them

The solicitation sent alongside this page asks three questions, and they are the questions this page exists to get answered.

1. Where should an agent defer? When this build's agent has a Cloudflare question, which surface should it treat as canonical, and which should it distrust? The ranking above is this build's current answer and it is a guess made from the outside.

2. What are the emergent practices? Not the documented ones. The patterns that have become normal among people shipping agents on Workers in 2026 and are not written down anywhere official — how state is partitioned across Durable Objects, when a Container is worth its cold start, what people actually do about deploy safety, whether anyone runs Code Mode in production.

3. What is obviously wrong here? The full inventory of what this build runs and what it has not installed is public, in ten parts, with verdicts. An outside reader who builds on this platform for a living will see mistakes in it that no amount of reading the documentation would surface.

What this build actually runs on Cloudflare

Stated in full, because a solicitation that asks for review without disclosing the object is asking for a favour rather than a critique.

In production: Workers and Pages; four D1 databases; one KV namespace; two R2 buckets; three Durable Object classes with SQLite; three Queues; ten Workflows across two Workers; Workers AI; AI Gateway on every model call; Browser Rendering; outbound email through a send_email binding; Secrets Store bound by reference; service bindings; cron triggers; observability on every Worker.

What it does with them: it is a public site of 1,183 articles where every article is the same object — atomized claims, each with an evidence tier and a source carrying that source's own verbatim words, rendered as addressable regions an outsider can challenge. Every action appends a hash-chained audit row. Writes pass a chain of gates enforced in the Worker: a headline law, an image law, a source-quote law, a claim law, a shrink guard and an optimistic-concurrency check. Agents lease work as rows rather than choosing it, and submit evidence rather than declaring completion.

Verified empty on the account, 6 August 2026: Vectorize, Hyperdrive, Pipelines, Containers.

Not installed anywhere: AI Search, Analytics Engine, Pipelines, R2 Data Catalog and R2 SQL, R2 event notifications, the Sandbox SDK, Code Mode, the Agents SDK, hosted MCP with OAuth, Images, Stream, Realtime, Snippets, the rate-limit binding, Turnstile, Cache Reserve, Logpush, Log Explorer, Tail Workers, gradual deployments, version metadata, Workers Builds, Tunnel, Workers VPC, mTLS bindings, Access, WAF custom rules, inbound Email Routing, API Shield, Workers for Platforms, Terraform.

The full reasoning for each, with a verdict of install, later or no, is in the series.

How to reply

Anything sent back becomes a public object here, attributed, or anonymous on request. Corrections are applied to the article they correct and the revision is kept. An objection can be filed directly against any claim on any page without an account.

The two items this build most wants challenged: that a Tail Worker is the right way to make a failure become a task row, and that Code Mode is the correct fix for an agent spending most of its calls discovering tool contracts rather than doing work.

References (9)
  1. cloudflare/cloudflare-os on GitHub“Agent workspace built on Cloudflare Workers for creating documents, building apps, and running agents with your company's context and systems.”
  2. cloudflare/agents on GitHub“Build and deploy AI Agents on Cloudflare”
  3. cloudflare/workerd on GitHub“The JavaScript / Wasm runtime that powers Cloudflare Workers”
  4. cloudflare/skills on GitHub“Skills for teaching agents how to build on Cloudflare.”
  5. cloudflare/sandbox-sdk on GitHub“Run sandboxed code environments on Cloudflare's edge network”
  6. cloudflare/workers-oauth-provider on GitHub“OAuth provider library for Cloudflare Workers”
  7. honojs/hono on GitHub“It works on any JavaScript runtime: Cloudflare Workers, Fastly Compute, Deno, Bun, Vercel, AWS Lambda, Lambda@Edge, and Node.js.”
  8. Kenton Varda on GitHub“Tech lead of Cloudflare Workers, Cap'n Proto, Sandstorm.io.”
  9. outerbase/starbasedb on GitHub“HTTP SQLite scale-to-zero database on the edge built on Cloudflare Durable Objects”