I have a feeling we're all working towards the same thing, but with different frameworks and infra. The Cloudflare OS experience looks, to me, very much like what I created for myself with https://rcarmo.github.io/projects/piclaw (except that I rely on focusing different instances on different sets of skills and tooling, so only two have "Office" skills, for instance).

I am confused... it's not an OS, is it?

In case anyone else is curious, local Gemma4 12B Q6 XL really struggles to make use of this for simple goals like a daily briefing after an MCP tool call. I don't think there's a simple artifact concept? Still early but confused.

> Cloudflare OS is available today and is open source. Check out the cloudflare-os GitHub repository. You can deploy it into your own Cloudflare account and use your own Access policies, AI Gateway configuration, data, and integrations.

In case anybody missed it.

this is a cool idea, but i suspect will be limited in use cases. the vast majority of people don't want or can't modify their software competently and will rely on others to do that. once you're relying on someone else, they do not want to maintain different copies for every user, that sounds like a maintenance nightmare for admins or else such a new paradigm that it takes a new generation of admins 20 years to get comfortable.

AOS would make more sense for the naming convention here.

This "OS" label reminds me of ms with ".NET", a choice they definitely seemed to regret

I can't help but wonder if these things that are now emerging have a sort of "borrowed time" component tied to them.

I see the examples, and they clearly tackle both organizational inefficiencies and human connection/communication as the core problems.

Sounds like things are converging to "my AI will talk to your AI" and the role of humans will just be a human "router" in the loop switching up nodes in a graph, like the return of Switchboard Operators from the 1950s.

Really not a fan of calling things an OS that are not an OS. This seems interesting, but it is also tied to CloudFlare workers, so beware.

I really don't know how folks accept such vendor lock-in. Imagine using Cloudflare Workers as your main tech stack. This is crazy.