[dead]
ive been tinkering with this all day. its far more than a chat app. going to change how our team collaborates on work tasks
Cloudflare OS: an open platform for agents, apps, and work
281–290 of 365 posts
Re: Cloudflare OS: an open platform for agents, apps, and work
#282Earlier quoted context omitted.
Sandstorm's use of containers was just a means to an end. The real innovation was the fine-grained instances -- each document in its own container. No other container platform did that. But honestly, it didn't work well, because of cold start times and memory usage. It's bad enough when a server takes seconds to start, but if every document you open has a long startup time and uses hundreds of MB of RAM, it's really…
This is far too Cloudflare flavored to be interesting to me. It's using Workers (capital W) and the core Cloudflare primitives. I don't feel safe building on this or touching this. I'd be happier if a startup or neutral party built this in a more agnostic way.
We're going to prove it's hostable outside Cloudflare, if you're interested in the tech but want an (experimental) "neutral" hosting option - email us hello@zqm.sh if you have questions/feedback.
Re: Cloudflare OS: an open platform for agents, apps, and work
#283Earlier quoted context omitted.
dumb question: is this javascript/typescript only? can you use webassembly based languages instead?
In theory Wasm could be supported, but generally JS/TS is much more efficient when running inside isolates (our lightweight sandboxes) since you don't have to bundle a language runtime into the app. CFOS at present only exposes JS (with TS coming soon).
Mmm so application-level sandboxing. Lovely.
And I’m assuming your worker runtime is a process in a container on a shared node? What happens if the agent exploits your runtime?
Does it get access to the whole container? VM? Node?
Why should I ever choose this over MicroVMs? I have to design my architecture around your JS runtime. This isn’t an OS.
Re: Cloudflare OS: an open platform for agents, apps, and work
#284It looks like another tool, something along the lines of Codex or Hermes.
Re: Cloudflare OS: an open platform for agents, apps, and work
#285Earlier quoted context omitted.
> The blog post is for a different audience. No one? Like literally, I don't understand a thing of what the blog post is saying. It's vague to the point of meaning nothing. Every piece of text I've seen that explains CloudflareOS is clear except the blog post.
This matches my perception of a ton of recent Cloudflare blog posts. I literally have no idea who they are targeting. It almost feels like they're targeting themselves.
I believe this happens when someone decides on a particular cadence of posts rather than waiting until you actually have something to say
Re: Cloudflare OS: an open platform for agents, apps, and work
#286Earlier quoted context omitted.
In theory Wasm could be supported, but generally JS/TS is much more efficient when running inside isolates (our lightweight sandboxes) since you don't have to bundle a language runtime into the app. CFOS at present only exposes JS (with TS coming soon).
Mmm so application-level sandboxing. Lovely. And I’m assuming your worker runtime is a process in a container on a shared node? What happens if the agent exploits your runtime? Does it get access to the whole container? VM? Node? Why should I ever choose this over MicroVMs? I have to design my architecture around your JS runtime. This isn’t an OS.
Workers are in the same process but have separate heap, global vars, gc etc, the isolation is managed and achieved by V8. It is much lightweight compared to micro VM or containers. But the downside is you have to use JS because of V8.
Re: Cloudflare OS: an open platform for agents, apps, and work
#287So, this is not an actual OS? I clicked thinking that I was about to read about some excellent systems innovation, but I was met with automation of boring office work
Re: Cloudflare OS: an open platform for agents, apps, and work
#288Earlier quoted context omitted.
Workers is a product and you're paid to develop and sell it as an employee. I 100% understand the hustle. I do the same thing. I just don't trust a giant like Cloudflare that has done several things to weaken the open web and establish a position that is all too powerful. I don't want to give them an iota of support. Even using open source buys into their mindshare, distribution, ecosystem, and eventual supremacy and…
I tried it as a startup once, so I know what that's like. It's a lot of time spent running around begging for money (from investors and from customers) rather than building technology. Workers is my startup-within-Cloudflare. It won't make me a billionaire, but it has still made me more money than I actually know what to do with, while being able to delegate all the stuff I don't like doing to other parts of the comp…
Love the wisdom and transparency, such an amazing thread
Re: Cloudflare OS: an open platform for agents, apps, and work
#289I just deployed it on my cloudflare workers, it went live in a minute, worked through my CF Access SSO. Wasn't able to configure providers easily. But reading the blog this is wild! I have been driving a hermes agent off a VM in a proxmox from my slack and wondering how to handle security. If this takes off, this is really how enterprise agents should end up looking like. The dynamic workers hosting applications is t…
No luck either with custom providers from the AI Gateway working within CFOS (deployed to my CF account)...
Re: Cloudflare OS: an open platform for agents, apps, and work
#290Earlier quoted context omitted.
I'm talking about setting up one provider for the entire OS not about BYOK per user. Right now only cloudflare AI gateway is supported and in it you hardcoded it to US providers. Plus your AI workers and from your model you only supporting two.
The code currently supports Anthropic, OpenAI, Gemini, Workers AI, and ollama as AI providers. It additionally optionally supports sending all requests through Cloudflare AI Gateway as a proxy. The same set of providers is supported either way, but when you configure AI Gateway, we assume you intend to install side-wide API keys into the gateway. The idea here is that you're setting up the gateway for your entire com…
I can't get an AI Gateway custom provider to work within CFOS (deployed to my CF account). No matter what custom model path I use in the cfos admin add provider mechanism, I get a model not found error when attempting to use the model in a conversation...