Cloudflare Quick Tunnels add JSON output, courting the coding-agent crowd

Cloudflare’s Quick Tunnels expose a local development server to the public internet with a single command—cloudflared tunnel --url http://localhost:8000—and no account, DNS setup, or inbound ports. The tunnel daemon dials out to the nearest of Cloudflare’s 335+ edge locations, then routes traffic back to the machine over an encrypted, outbound-only connection that inherits automatic HTTPS and edge DDoS filtering. A URL is issued in roughly three seconds and disappears when the process exits, making the tunnels genuinely ephemeral with nothing to revoke or clean up.

The newsworthy addition is structured JSON output on stdout, emitting the assigned hostname, edge location, and health status so automated tools no longer have to scrape log lines with regex. Cloudflare is explicitly positioning this at AI coding agents that build, test, and review in loops and need a real, reachable address for webhooks, screenshot services, or eval harnesses—alongside the more familiar use of pointing Stripe or GitHub callbacks at a live endpoint instead of local fixtures.

The practical draw is the same as it has always been for this class of tool: skip firewall and port-forwarding friction to share work-in-progress instantly. The shift here is framing an existing developer convenience as agent infrastructure, betting that autonomous coding workflows will become a meaningful consumer of on-demand public URLs.