Cloudflare Workers

Cloudflare OS offers an agent and workspace built around a company’s systems and knowledge. The company’s explanation emphasizes isolated app instances—called Gadgets—whose access control is managed by the platform and whose users can modify their own copies with an agent.

The HN thread objected to the “OS” label, then supplied the useful distinction: a familiar agent interface may sit on top of a security model designed to let non-technical users change software without granting it broad access.

The surprise is in the invoice: requests that used to be free, like static assets and worker-to-worker calls over service bindings, now bill at the standard request rate because each one first checks the cache.

One developer's flat verdict on the new charges: 'that sounds like a bug that just happens to generate them more money.'

`wrangler deploy --temporary` provisions a working account with no registration, live for 60 minutes, claimable into a permanent one via a link. The failure message tells the agent the flag exists, so it self-discovers the path.

One developer called handing deploy control to a non-deterministic process 'madness'. The simpler objection: humans get pushed into endless Turnstile loops while bots get a frictionless lane.