Topic

#feature-flags

Loot, blog posts and adjacent themes connected to this topic. Follow the tag to keep it in your orbit.

#feature-flags
#developer-tools#CLI#cloudflare#release management#Vercel#workers#wrangler
Loot

More from this topic

Explore all loot
Manage Cloudflare Feature Flags from Wrangler 1

Manage Cloudflare Feature Flags from Wrangler

0
#cloudflare#wrangler+3
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. 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 CLOUDFLAREAPITOKEN in automation with the narrow Flagship read/write permissions Cloudflare documents. Keep flag keys stable because application code evaluates by key. Prefer --json output 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.
Free
Review open
0
Open loot
Blog

Related reads

Browse blog
Tools & Apps

Script Vercel Flags Segments Before Agents Change Targeting by Hand

Vercel Flags segments can now be managed from the Vercel CLI, giving teams a scriptable way to create, inspect, and update reusable targetin…