sincecutoff.com
/v1/json /v1/md llms.txt
← all changes

wrangler.json configures Flagship feature flag bindings

Introduced 2026-04-13 · score 0.94

HOW TO USE IT

When a Worker needs Flagship evaluations, add a `flagship` binding with its app ID to `wrangler.json`; set `remote` to `true` for live-service evaluation during local development. [Flagship configuration](https://developers.cloudflare.com/flagship/configuration/)

{"flagship":[{"binding":"FLAGS","app_id":"<APP_ID>"}]}
{"flagship":[{"binding":"FLAGS","app_id":"<APP_ID>","remote":true}]}

WHY THIS HELPS

Configure a Worker to evaluate Cloudflare Flagship feature flags during local development or against the live service.

REQUIREMENTS AND LIMITATIONS

  • Version: 4.82.0
  • binding (required): Name of the Worker environment variable used to access Flagship, such as `env.FLAGS`.
  • app_id (required): ID of the Flagship app to bind.
  • remote: Set to `true` for live-service evaluation during local development, per the Wrangler 4.82.0 release note.
  • Prerequisite: Use the app ID from a Flagship app.
  • Local development returns default values for all flag evaluations unless the binding uses `"remote": true`.
  • Docs conflict: Newer Flagship configuration docs (updated June 24, 2026) say local Workers use the live Flagship app configured by `app_id` and that there is no local flag store; they do not describe `remote` for Flagship. The Wrangler 4.82.0 release note says local evaluations return defaults unless `remote: true`. Do not infer current `remote` behavior from the newer docs.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card