ai-setup 4 min read

cloudflare-os: A Workers agent workspace

cloudflare-os is an agent workspace built on Cloudflare Workers for creating documents, building apps, and running agents with company context, with 10,581 GitHub stars.

By
Share: X in
GitHub social preview card for cloudflare/cloudflare-os

TL;DR: cloudflare-os is an Apache-2.0 agent workspace from Cloudflare, described as building on Workers so you can create documents, build apps, and run agents that have access to your company context and systems. It reached 10,581 stars in about five months, and the deployed product at os.cloudflare.app responds.

What it says it is

The project description is short and concrete: an agent workspace built on Cloudflare Workers for creating documents, building apps, and running agents with your company context and systems. Three verbs, one platform. Nothing in that sentence needs unpacking, which is a good sign.

The interesting part is the framing. Most agent tooling in this category is a memory layer, a skill pack, or a wrapper around someone else’s model. This one is a workspace, which implies a surface you open and work in, with Workers as the substrate underneath.

The repository confirms the Workers claim

The description asks you to take the Workers dependency on faith. The repository layout settles it. The root of the tree contains a wrangler configuration file, which is the deployment manifest for Cloudflare Workers, alongside a Cloudflare config file and a pnpm workspace file with a packages directory. That is a Workers monorepo, not a library that happens to integrate.

The language breakdown is equally concentrated:

curl -sL -H "Accept: application/vnd.github+json" \
  https://api.github.com/repos/cloudflare/cloudflare-os/languages
{
  "TypeScript": 13866081,
  "CSS": 55025,
  "HTML": 3255
}

TypeScript accounts for more than 99 percent of the measured bytes. There is no service in another language hiding in here.

Metadata at a glance

FieldValue
Full namecloudflare/cloudflare-os
Homepagehttps://os.cloudflare.app
LanguageTypeScript
LicenseApache-2.0
Stars10,581
Forks1,283
Open issues128
Sizeabout 21 MB
Owner typeOrganization
Created2026-04-15
Last push2026-10-04

Two entries deserve a second look. The repository is roughly 21 MB, which is small for a product of this scope, and that points to a codebase that generates most of its weight at build and deploy time rather than committing it. And 128 open issues on 10,581 stars is a low ratio, in the same range as other heavily adopted agent projects.

The root of the tree also contains an .agents directory alongside an AGENTS.md file. A workspace for running agents ships instructions for agents. If you adopt it, that is the first file to read, and it is also the clearest statement of intent in the repository.

Checking the deployment yourself

The homepage in the metadata is a real deployed URL, not a placeholder. It answers:

curl -sI https://os.cloudflare.app | head -1

The response came back HTTP/2 200 with an HTML content type when this was written. That is not proof of anything about features, but it does confirm the product is live rather than announced.

When it fits

Worth evaluating if you already run on Cloudflare and your agents need to touch internal systems. The description makes company context and systems part of the pitch, and Workers gives you a deployment target with a global edge and no server to manage, which is a reasonable default for glue code that runs occasionally.

It is also a useful reference even if you never deploy it. A public, vendor-maintained, Apache-2.0 workspace built on Workers is a working example of how this category is being structured, and the source is readable for that.

When it does not

Skip it if you are not on Cloudflare. The whole design rests on Workers being the runtime, so porting means rewriting the substrate, not swapping a configuration value.

Weigh the vendor question too. The Apache-2.0 license is permissive and the code is auditable, but a workspace that holds company context is infrastructure you now depend on someone else’s roadmap for. That can be exactly what you want. It should be a decision rather than a default.

Source and Accuracy Notes

  • Project page: https://github.com/cloudflare/cloudflare-os
  • Source repository: cloudflare/cloudflare-os (verified via GitHub API html_url)
  • License: Apache-2.0 (verified via GitHub API license.spdx_id)
  • Stars at time of writing: 10,581
  • Additional verification: languages and contents API endpoints, and an HTTP status probe of the homepage