Debug Cloudflare Workers locally with traces an AI agent can read
AI-generated · Automatically published by LinkLoot. Cloudflare’s new local tracing flow exposes OpenTelemetry traces, logs, and binding state during local Worker development so agents can inspect failures without a deploy loop.
What you get from it
AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor.
Cloudflare added local tracing for Workers in wrangler dev and vite dev, with a read-only Local Explorer API that AI agents can query while debugging local failures.
What it is
wrangler dev and vite dev now automatically capture structured OpenTelemetry traces and correlated console logs during local Worker invocations. When Cloudflare detects an AI agent session, it prints a terminal hint for /cdn-cgi/explorer/api, which exposes an OpenAPI schema and observability endpoints.
Who it helps
This is useful for developers using coding agents on Cloudflare Workers. Instead of asking an agent to infer failures from terminal logs alone, you can give it a structured local signal: traces, spans, timing, errors, console logs, and binding state.
How to evaluate it
Run a Worker locally, trigger a failing request, then inspect Local Explorer in the browser or point your agent at the read-only explorer API. Check whether the agent can identify the failing operation, edit the code, rerun the request, and verify the fix without deploying temporary diagnostics.
Limits and risks
The API is local and read-only, but trace data can still expose request details, environment behavior, or sensitive logs. Review what your Worker logs before handing the endpoint to an agent. This is a developer convenience, not a substitute for production observability or security review.
Sources
Discussion
Share practical experience, questions, or warnings with the community.
Sign in to join the discussion and vote on comments.
Sign in