Skip to content
NewA calmer, faster ZeroHour

Introducing Worker Previews: isolated preview environments for every change your agent makes

Cloudflare Blogby Yomna Shousha ()9 min read5 · 1 read
AI summary · grok-4.7Summaries by Vani AI

Cloudflare launches Worker Previews, isolated per-branch environments for testing agent code changes.

Cloudflare launched Worker Previews, giving each Git branch an isolated production-like environment with its own URL, configuration, secrets, bindings, observability, and state. Previews are started with npx wrangler preview and can run concurrently without sharing production traffic or Durable Object namespaces. The feature targets an agent development workflow in which changes are tested, observed, and revised before merge. Preview URLs can use a custom domain so authentication, cookies, CORS, and OAuth behave as they will in production.

Key facts
  • Each Git branch gets an isolated Worker Preview URL.
  • Previews keep separate secrets, bindings, logs, and state.
  • Created with npx wrangler preview under one Worker.
  • Custom domains preserve auth, cookies, CORS, and OAuth.
  • Aimed at testing agent changes before production merge.
Explain this AI news with Vani AIWhat was announced, what is new and why it matters, in a new chat

From the original article

9 min read at blog.cloudflare.com

Worker Previews gives every branch its own URL, configuration, state, and observability, so you and your agents can test changes in parallel without affecting production.

Cloudflare Blog

By Yomna Shousha · blog.cloudflare.com

Read the full article at Cloudflare Blog

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.