Cloudflare gives every agent change its own sandbox
Every Git branch on Workers now gets a production-like place to run, with its own URL, settings and state, so an agent's changes can be tested before they reach live traffic.
Cloudflare has launched Worker Previews, an environment that mirrors production for each branch of a project rather than for the project as a whole. It was announced on the company's blog on 22 September, during its Agents Week run of releases, and it is aimed squarely at teams whose code is increasingly written by software agents.
What a preview gets
A preview carries its own variables, secrets and bindings, separate from the live configuration, and it is started from the command line with npx wrangler preview. Each branch keeps a stable address that every push updates in place, so the same URL can be clicked through or hit with test requests as work continues. Cloudflare says hundreds of previews can run at once without touching each other or production.
The stateful parts of the platform are isolated too. Durable Objects and containers are scoped per branch, which keeps sessions, memory, migrations and concurrent tests inside the preview instead of leaking into a shared database. Logs, errors, metrics and traces are collected per preview, so a failure can be diagnosed on the branch that caused it.
Starting from a base, then diverging
Previews begin from what Cloudflare calls a base configuration: a copy of the variables, secrets, bindings and settings an operator defines, in the same way a code branch starts from main. Where a preview needs something different, such as its own database or a test key for a migration, that configuration can be overridden without changing production, the base or any other preview. Preview addresses can also be served on a custom domain, which matters because authentication providers, cookies, cross-origin rules and OAuth redirects rarely behave the same on a throwaway host.
Why the timing is the point
Cloudflare's stated reason for building this now is volume. Its blog notes that agents are producing more code than before, that bigger changes need more testing before release, and that the testing itself should not become the bottleneck for the agent doing the work. Worker Previews is that argument turned into a product: the testing step becomes another branch to open, inspect and close rather than a staging window everyone has to queue for.
Our opinion
This is the least glamorous release Cloudflare could have made this week and probably the most consequential. The interesting part is not the URL per branch, which other platforms offer, but the decision to isolate Durable Objects and containers as well, because shared state is what turns parallel agent work into an afternoon of archaeology. The catch is the same one that follows every convenience: hundreds of live previews are hundreds of live things, and someone still has to decide who pays for them and who notices when one is left pointing at a real database. Watch whether the accounting arrives with the feature, or a quarter later, as it usually does.