Manage Cloudflare Feature Flags from Wrangler
Cloudflare added wrangler flagship, a command suite for creating Flagship apps, managing feature flags, running rollouts, splitting traffic, evaluating flags, and using CLI kill switches from local terminals or CI.
- LinkLoot access
- Free
- Provider costs
- Unknown
What you get from it
Practical testing not documented.
LinkLoot assessment · not a user rating.
Cloudflare's new wrangler flagship commands give Worker teams a direct CLI path for feature-flag operations that previously pushed developers back into dashboards or custom API scripts.
Use it when you need to create Flagship apps, bind flags to a Worker project, define boolean/string/number/JSON variations, roll out a variation by percentage, split traffic, evaluate a flag for a targeting key, or disable a flag as a kill switch.
Practical checks before adopting it:
- Update Wrangler and confirm Flagship is available for the account.
- Use
CLOUDFLARE_API_TOKENin automation with the narrow Flagship read/write permissions Cloudflare documents. - Keep flag keys stable because application code evaluates by key.
- Prefer
--jsonoutput in scripts so CI jobs can capture app IDs and flag state safely. - Treat destructive commands carefully: deleting an app removes its flags and changelog history, and Cloudflare rejects deletion when a Worker still references the app through a Flagship binding.
This is a Tool, not a prompt: the value is the official CLI surface for release control, rollout automation, and agent-friendly deployment checks.
Discussion
Share practical experience, questions, or warnings with the community.
Sign in to join the discussion and vote on comments.
Sign in