Live data from Hacker News

Cloudflare OS: an open platform for agents, apps, and work

blog.cloudflare.com

301–310 of 365 posts

Re: Cloudflare OS: an open platform for agents, apps, and work

#301
post #271
post #85

Earlier quoted context omitted.

Does your LLM have hardware drivers in it? this is silly.

I'm obviously not saying that LLMs replace the glue between hardware and software. That would be absurd. An operating system is just the interface a user has to the programs they run on their computer. Surely you can imagine a world where you boot into a ChatGPT-like interface instead of the desktop OS you are familiar with? Different computing paradigms already exist: mobile OS sure, but also ChromeOS... heck, insta…

You seem to have a wrong definition of operating system in your head. The definition of Operating System is "The main software that manages a computer's hardware and software."

An operating system is definitely not "just the interface a user has to the programs they run on their computer."

> If you purchase a cloud VM...

Then the operating system there is the link between the interface you are accessing and the underlying hardware on the physical server.

An operating system is not just something that opens apps, it is the thing that lets you type, use a mouse, and see things on a screen. LLMs cannot do any of that, they are an app which runs on an OS.

Re: Cloudflare OS: an open platform for agents, apps, and work

#302
post #77

Earlier quoted context omitted.

Do you have a store/list of public blueprints like sandstorm?

Not yet, but that's an obvious direction to take things. :) I'm really excited by the idea that this platform makes it safe to use blueprints that someone else vibe coded, without worrying about whether they checked it for security bugs, etc. Basically if the app works, it works. So yeah, there absolutely should be a marketplace so everyone can try everyone else's stuff. BTW there are three blueprints installed autom…

Another request for Home lab geeks: A Proxmox installer script.

I tried going through the wizard to install, it would be nice if there was a proxmox container or vm to spin up quickly and test rather than npm or cloudflare account (which requires a $5/month workers plan).

Re: Cloudflare OS: an open platform for agents, apps, and work

#303

I 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…

Why not deploy cloudflare-os on proxmox?

Re: Cloudflare OS: an open platform for agents, apps, and work

#304
post #4

I liked Kenton's take on this: https://x.com/KentonVarda/status/2084990137180590572?s=20 Text from tweet: Today we are releasing Cloudflare OS, a chatbot with connectors, just like every other tech company is doing. Except actually, it's different. This is a remake of Sandstorm[.]io, my startup from 10 years ago, except this time built on Cloudflare Workers (the platform I've spent the last 9 years building) and deep…

Reminds me of EMacs, which I really like.

Re: Cloudflare OS: an open platform for agents, apps, and work

#305
post #4

I liked Kenton's take on this: https://x.com/KentonVarda/status/2084990137180590572?s=20 Text from tweet: Today we are releasing Cloudflare OS, a chatbot with connectors, just like every other tech company is doing. Except actually, it's different. This is a remake of Sandstorm[.]io, my startup from 10 years ago, except this time built on Cloudflare Workers (the platform I've spent the last 9 years building) and deep…

> the AI cannot introduce a significant security bug.

Famous last words.

Re: Cloudflare OS: an open platform for agents, apps, and work

#306

Earlier quoted context omitted.

> It doesn’t schedule tasks, It absolutely does. > doesn’t deal with physical memory, Well it sort of does. It allocates sandboxes and schedules apps in them. It handles loading code from storage and turning it into running programs with state. > it doesn’t initialize hardware or interface with it on a low level. Instead of devices it manages interfacing with external services (Gatekeepers are like drivers). I didn't…

Interesting points! Sent from my Gmail OS

xD

Sent from FirefoxOS using the KeyboardOS provided by iOS on my iPhone. . . OS

Re: Cloudflare OS: an open platform for agents, apps, and work

#307

As a paying Cloudflare customer, I am sad that they're spending their engineering talent on this, without first fixing their Terraform driver. Basics first!

(cf engineer) none of the people that worked on this, myself briefly included, are people that work on our terraform driver. Making our terraform support better quickly turns into "how do we fix the quirks present in all our various APIs in a backwards-compatible way" so we have a separate group of engineers working on this problem specifically.

Re: Cloudflare OS: an open platform for agents, apps, and work

#309
post #4

I liked Kenton's take on this: https://x.com/KentonVarda/status/2084990137180590572?s=20 Text from tweet: Today we are releasing Cloudflare OS, a chatbot with connectors, just like every other tech company is doing. Except actually, it's different. This is a remake of Sandstorm[.]io, my startup from 10 years ago, except this time built on Cloudflare Workers (the platform I've spent the last 9 years building) and deep…

> the AI cannot introduce a significant security bug. Famous last words.

[deleted]

Re: Cloudflare OS: an open platform for agents, apps, and work

#310

Earlier 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.

Let me quote the workers GitHub:

> WARNING: workerd is not a hardened sandbox

> workerd tries to isolate each Worker so that it can only access the resources it is configured to access. However, workerd on its own does not contain suitable defense-in-depth against the possibility of implementation bugs. When using workerd to run possibly-malicious code, you must run it inside an appropriate secure sandbox, such as a virtual machine. The Cloudflare Workers hosting service in particular uses many additional layers of defense-in-depth.

Sandstorm was great because it did proper sandboxing. This is pretty weak by comparison.

Post reply on HN