// AI Platform Drift
Flagship bindings now evaluate flags locally by default during development
Cloudflare developer changelog · published 2026-11-11 04:55 UTC
WHAT CHANGEDFlagship bindings in wrangler dev, Cloudflare Vite plugin, Vitest integration, and cf dev now evaluate feature flags against a local flag store instead of calling the remote app. The local store starts empty and returns code-default values until populated. Developers can add flags using --local with wrangler flagship commands, Local Explorer, or cf CLI. To restore remote evaluation, set remote: true on the binding. Requires Wrangler v4.135.0 or @cloudflare/vite-plugin v1.56.0 minimum; Local Explorer support requires Wrangler v4.148.0 or @cloudflare/vite-plugin v1.63.0.
WHY IT MATTERSDevelopment workflows that depend on remote flag evaluation will now receive code-default values instead of production flag states unless the binding is explicitly configured for remote evaluation. Tests and local development that assume remote flag values will behave differently.
WHAT TO DOCheck development and test code that uses Flagship bindings. If remote flag evaluation is required, add remote: true to the binding configuration. Otherwise, populate the local flag store using npx wrangler flagship flags pull <APP_ID> or manage flags through Local Explorer. Upgrade to the minimum required Wrangler or Vite plugin version.
Model-reported confidence 85% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Flagship - Evaluate Flagship flags locally +https://developers.cloudflare.com/changelog/post/2026-11-02-local-flag-store/ +Mon, 02 Nov 2026 00:00:00 GMT + +Flagship bindings now evaluate flags against a local flag store during local development, instead of calling your remote app. You can develop offline and test flag changes without affecting production. This applies to wrangler dev, the Cloudflare Vite plugin, the Vitest integration, and cf dev. +The local store starts empty, so evaluations return the default value you pass in code. Add and manage local flags in any of these ways: + +Wrangler — Add --local to wrangler flagship flags commands, such as create, update, and evaluate. To copy all flags from your remote app, run npx wrangler flagship flags pull <APP_ID>. +Local Explorer — Create, edit, toggle, and evaluate flags in Local Explorer while your dev server runs. +cf CLI — Add --local to cf flagship commands. + +To keep evaluating against your remote app instead, set remote: true on the binding. +The local flag store requires Wrangler v4.135.0 or @cloudflare/vite-plugin v1.56.0 or later. Flagship in Local Explorer requires Wrangler v4.148.0 or @cloudflare/vite-plugin v1.63.0 or later. +Refer to Flagship local development for details.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.92, needed 0.5 |
|---|---|
| triage reasoning | New feature with version requirements and changed default behavior for local development workflows. |
| signals | new feature announcement · version floor introduced (Wrangler v4.135.0, v4.148.0) · breaking workflow change (local vs remote evaluation default) · new CLI flags (--local) · new tooling integration (Local Explorer, Vitest, cf dev) |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |