sincecutoff.com
← all changes

wrangler flagship manages Flagship apps and flags

Introduced 2026-07-02 · score 0.94

HOW TO USE IT

If your Wrangler workflow needs to manage Flagship apps or feature flags, use `wrangler flagship apps` for apps and `wrangler flagship flags <APP-ID>` for flags; add the documented subcommand and arguments for the action, such as creating, inspecting, evaluating, rolling out, or deleting.

wrangler flagship apps create <NAME>
wrangler flagship flags create <APP_ID> <KEY> --variation <NAME>=<VALUE> --default <NAME> --type <boolean|string|number|json>
wrangler flagship flags evaluate <APP_ID> <KEY> --context <NAME>=<VALUE> --targeting-key <KEY>

WHY THIS HELPS

Manage Flagship apps and feature flags from a coding workflow that uses Wrangler.

REQUIREMENTS AND LIMITATIONS

  • Version: 4.107.0
  • <NAME> (required): App name.
  • <APP_ID> (required): App ID; first argument to flag commands.
  • <KEY> (required): Flag key.
  • --variation <name>=<value> (-V): Add a variation; repeatable. All variations on a flag must resolve to one value type.
  • --default <NAME>: Choose the default variation.
  • --type <TYPE>: Flag value type: boolean, string, number, or json; inferred if omitted.
  • --context <NAME>=<VALUE>: Evaluation context attribute; repeatable. Values are sent as strings.
  • --targeting-key <KEY>: Stable bucketing key for percentage rollouts.
  • Prerequisite: Wrangler v4.107.0 or later.
  • Prerequisite: Authenticate with `wrangler login` or `CLOUDFLARE_API_TOKEN` with Flagship permissions. Reads require `flagship:read`; writes require `flagship:write`. Most writes that update existing flags also need read permission.

FIRST-PARTY EVIDENCE

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

Report a problem with this card