wrangler-4-117-0-20-b
Claude Code's read-only tools, web search on, ludion sync off
Question
Do /cdn-cgi/ test endpoints in wrangler dev still work after the move to Miniflare v5?
Answer key
- A correct answer says
- Local testing endpoints moved to `/cdn-cgi/local/*` in Miniflare v5; wrangler dev rewrites the old `/cdn-cgi/*` paths so they still work.
- The stale answer
- Local test endpoints such as the scheduled handler trigger live directly under `/cdn-cgi/` (e.g. /cdn-cgi/handler/scheduled).
Answer
Yes. Miniflare v5 moved its built-in local testing endpoints into a new `/cdn-cgi/local/*` namespace so they don't collide with production routes. For example, the scheduled trigger moves from `/cdn-cgi/handler/scheduled` to `/cdn-cgi/local/scheduled`, and there's a `/__cf_local/` prefix for use through tunnels. `wrangler dev` and the Vite plugin quietly rewrite the old paths to the new ones, so your existing curl commands and scripts should keep working. One exception: the `/cdn-cgi/mf/reload` live-reload endpoint was removed outright, because Wrangler and the Vite plugin now handle live reload themselves.
Two caveats. These notes cover the 5.0.0 alpha releases from July 2026, so details could change before a stable release. And I got the exact paths from changelog digests, not Cloudflare's official docs, where the formatting looked a bit garbled. Check against the docs if you need the precise routes.
Sources:
- [Local testing paths rewritten to avoid production collisions (releases.sh)](https://releases.sh/release/rel_fvAzk5225V0yozzVTwZyb-local-testing-paths-rewritten-to-avoid-production-collisions)
- [miniflare@5.20260730.0-alpha release](https://newreleases.io/project/github/cloudflare/workers-sdk/release/miniflare@5.20260730.0-alpha)
- [wrangler@4.117.0 release](https://newreleases.io/project/github/cloudflare/workers-sdk/release/wrangler@4.117.0)
- [Application platforms digest, 2026-07-27](https://releases.sh/collections/application-platforms/digest/2026-07-27)Grade
correct
The judge's reason: It states endpoints moved to /cdn-cgi/local/* in Miniflare v5 and that wrangler dev rewrites old paths so they still work, presenting the old path only as legacy.
Session log
Tool call: ToolSearch
{ "query": "select:WebSearch", "max_results": 1 }Tool output
{"type":"tool_reference","tool_name":"WebSearch"}Tool call: WebSearch
{ "query": "Miniflare v5 /cdn-cgi/ wrangler dev scheduled handler endpoint", "mode": "standard" }Tool output
Web search results for query: "Miniflare v5 /cdn-cgi/ wrangler dev scheduled handler endpoint" Links: [{"title":"github.com","url":"https://github.com/us-ts/userscripts/pull/36"},{"title":"github cloudflare/workers-sdk @cloudflare/vite-plugin@1.49.1","url":"https://newreleases.io/project/github/cloudflare/workers-sdk/release/@cloudflare%2Fvite-plugin@1.49.1"},{"title":"github cloudflare/workers-sdk wrangler@4.117.0","url":"https://newreleases.io/project/github/cloudflare/workers-sdk/release/wrangler@4.117.0"},{"title":"rel fvAzk5225V0yozzVTwZyb local testing paths rewritten to avoid production collisions","url":"https://releases.sh/release/rel_fvAzk5225V0yozzVTwZyb-local-testing-paths-rewritten-to-avoid-production-collisions"},{"title":"rel NMTB5RLC5UxV3 OKJfeDG containerengine removed from unstable getminiflareworkeroptions local testing","url":"https://releases.sh/release/rel_NMTB5RLC5UxV3-OKJfeDG-containerengine-removed-from-unstable-getminiflareworkeroptions-local-testing"},{"title":"github cloudflare/workers-sdk miniflare@5.20260730.0-alpha","url":"https://newreleases.io/project/github/cloudflare/workers-sdk/release/miniflare@5.20260730.0-alpha"},{"title":"releases.sh","url":"https://releases.sh/collections/application-platforms/digest/2026-07-27.md"},{"title":"releases.sh","url":"https://releases.sh/collections/application-platforms/digest/2026-07-27"},{"title":"codex-container-api-docs.previews.developers.cloudflare.com","url":"https://codex-container-api-docs.previews.developers.cloudflare.com/workers/testing/miniflare/get-started/index.md"},{"title":"get started","url":"https://439c4358.previews.developers.cloudflare.com/workers/testing/miniflare/get-started/"}] The search turned up release notes showing that Miniflare v5 moved its scheduled-handler test endpoints, and that `wrangler dev` handles the old paths for you. - **Namespace change:** Miniflare v5 relocated its internal local testing endpoints under a `/cdn-cgi/local/` namespace, with a `/__cf_local/` prefix for endpoints that need to work through tunnels. The stated reason is to avoid collisions with production routes (Miniflare v5 moved its internal local testing endpoints to /cdn-cgi/local/*). - **Scheduled endpoints:** The release notes list the new scheduled paths as `/cdn-cgi/handler/scheduled/cdn-cgi/local/scheduled` and `/cdn-cgi/mf/scheduled/cdn-cgi/local/scheduled`. The second is flagged as a deprecated route (/cdn-cgi/handler/scheduled/cdn-cgi/local/scheduled; /cdn-cgi/mf/scheduled is already deprecated). - **Backward compatibility:** `wrangler dev` and the Vite plugin rewrite the old paths automatically, so existing calls keep working (wrangler dev and the Vite plugin now transparently rewrite the old paths to the new ones). - **Related changes:** Miniflare 5.0.0-alpha also removed the `/cdn-cgi/mf/reload` live reload endpoint. Wrangler and the Vite plugin now run their own live reload mechanisms instead (Wrangler and the Vite plugin both implement their own independent live reload mechanisms.). The most recent release notes I found are from late July 2026, and they are for Miniflare 5.0.0-alpha, so the v5 paths could still change before a stable release. I did not find the official Cloudflare docs page for the scheduled handler itself, so the paths above come from changelog and release-digest sources. REMINDER: You MUST include the sources above in your response to the user using markdown hyperlinks.Agent
Yes. Miniflare v5 moved its built-in local testing endpoints into a new `/cdn-cgi/local/*` namespace so they don't collide with production routes. For example, the scheduled trigger moves from `/cdn-cgi/handler/scheduled` to `/cdn-cgi/local/scheduled`, and there's a `/__cf_local/` prefix for use through tunnels. `wrangler dev` and the Vite plugin quietly rewrite the old paths to the new ones, so your existing curl commands and scripts should keep working. One exception: the `/cdn-cgi/mf/reload` live-reload endpoint was removed outright, because Wrangler and the Vite plugin now handle live reload themselves. Two caveats. These notes cover the 5.0.0 alpha releases from July 2026, so details could change before a stable release. And I got the exact paths from changelog digests, not Cloudflare's official docs, where the formatting looked a bit garbled. Check against the docs if you need the precise routes. Sources: - [Local testing paths rewritten to avoid production collisions (releases.sh)](https://releases.sh/release/rel_fvAzk5225V0yozzVTwZyb-local-testing-paths-rewritten-to-avoid-production-collisions) - [miniflare@5.20260730.0-alpha release](https://newreleases.io/project/github/cloudflare/workers-sdk/release/miniflare@5.20260730.0-alpha) - [wrangler@4.117.0 release](https://newreleases.io/project/github/cloudflare/workers-sdk/release/wrangler@4.117.0) - [Application platforms digest, 2026-07-27](https://releases.sh/collections/application-platforms/digest/2026-07-27)