Cloudflare lets Flagship flags evaluate locally during dev

Cloudflare’s Flagship feature-flag service can now evaluate flags locally during development. As of 2 November, Flagship bindings check a local flag store under wrangler dev, the Cloudflare Vite plugin, the Vitest integration and cf dev, instead of making a network call to your remote app.

The local store starts empty, so flags return whatever default you pass in code until you populate it:

npx wrangler flagship flags pull <APP_ID>

That copies every flag from production into the local store. You can also manage flags live in Local Explorer while your dev server runs, or add --local to individual wrangler flagship flags or cf flagship commands. Setting remote: true on a binding keeps it talking to the real app instead. The feature needs Wrangler v4.135.0 or @cloudflare/vite-plugin v1.56.0 or later, with v4.148.0 or v1.63.0 for Local Explorer support.

Why it matters: a flag binding that always calls out to your production app means every local dev run makes a network request, and testing a flag change risks affecting real users. A local store removes both problems: you can work offline, and flip flags without anyone outside your machine seeing it.