Cloudflare gives agent browsers private hostnames for development previews

Cloudflare added private hostnames for development previews inside an agent's browser.

Cloudflare’s Agents SDK added internal browser hostnames on October 28. A configured hostname such as preview.internal can direct a persistent browser to a server in an agent’s sandbox or to a service-backed Worker. The browser reaches the application through the configured internal route. That gives an agent building a website a way to inspect it in a browser before the team has exposed the development server publicly. [Cloudflare AI changelog](https://developers.cloudflare.com/changelog/post/2026-10-28-browser-internal-hostnames/)

How a preview gets routed

Cloudflare’s example defines an internal host with a target schema. The agent can choose a permitted target, such as the port on which its development server is listening, and the browser opens the internal hostname. A Durable Object handler can supply the response, while a service binding can route an internal host directly to another Worker. The documentation lists adapters for Pi Durable, AI SDK and TanStack AI. It also describes a way to connect a different harness through a browser-session tool. [Cloudflare AI changelog](https://developers.cloudflare.com/changelog/post/2026-10-28-browser-internal-hostnames/)

The feature changes how a browser reaches a server. It does not change what application permissions a person or tool should have after arriving. A server might still need authentication for realistic acceptance tests. An operator should also define what the internal hostname can target. If only a known development port is required, a broad target selection adds reach without helping the preview task.

What the browser can verify

An agent can use the preview to inspect an actual page, follow navigation and check responsive or keyboard behavior. A good test should cover the page that needs review, a route requiring sign-in when one exists, and an attempted request outside the intended target. It can also confirm that the service has no public development URL when the intended setup is internal only. A successful screenshot proves the browser reached a page. It gives less evidence than successfully exercising the feature the page was built to provide.

A private preview is useful early in a change, when a team wants feedback about behavior before choosing whether to release it. The October SDK update supplies that browsing path inside the agent’s environment. A later deployment still has its own authentication, route and availability checks. [Cloudflare AI changelog](https://developers.cloudflare.com/changelog/post/2026-10-28-browser-internal-hostnames/)