infochanged

Flagship - Manage Flagship from the command line with Wrangler

Announced: 2026-07-16
Tags: Flagship
Severity: info, set by reef/rss-rule-v1
Source: https://developers.cloudflare.com/changelog/post/2026-07-16-wrangler-commands/

<a href="https://developers.cloudflare.com/workers/wrangler/">Wrangler</a> now includes <code>wrangler flagship</code>, a command suite for managing <a href="https://developers.cloudflare.com/flagship/">Flagship</a> apps and feature flags from your terminal. Create an app and, if you use it from a Worker, add it to your <code>wrangler.json</code> or <code>wrangler.jsonc</code> file as a binding: <figure class="nb-code-figure" data-nb-lang="bash"><pre class="astro-code astro-code-themes github-light github-dark nb-shiki-c6xiwz" tabindex="0" data-language="bash" data-nb-lang="bash"><code>wrangler flagship apps create "My Worker App" \ --binding FLAGS \ --update-config</code></pre></figure> Then create flags for the behavior you want to control. Flags can be booleans, strings, numbers, or JSON values: <figure class="nb-code-figure" data-nb-lang="bash"><pre class="astro-code astro-code-themes github-light github-dark nb-shiki-c6xiwz" tabindex="0" data-language="bash" data-nb-lang="bash"><code>wrangler flagship flags create <APP_ID> new-checkout wrangler flagship flags create <APP_ID> checkout-flow \ --variation control=old-checkout \ --variation treatment=new-checkout \ --default control \ --type string</code></pre></figure> After a flag exists, change its default variation or use enable and disable commands as kill switches. Existing targeting rules continue to apply unless you change or clear them explicitly: <figure class="nb-code-figure" data-nb-lang="bash"><pre class="astro-code astro-code-themes github-light github-dark nb-shiki-c6xiwz" tabindex="0" data-language="bash" data-nb-lang="bash"><code>wrangler flagship flags update <APP_ID> checkout-flow --default treatment wrangler flagship flags disable <APP_ID> checkout-flow wrangler flagship flags enable <APP_ID> checkout-flow</code></pre></figure> For release workflows, use <code>rollout</code>, <code>split</code>, and <code>rules</code> to change exposure without redeploying your Worker: <figure class="nb-code-figure" data-nb-lang="bash"><pre class="astro-code astro-code-themes github-light github-dark nb-shiki-c6xiwz" tabindex="0" data-language="bash" data-nb-lang="bash"><code>wrangler flagship flags rollout <APP_ID> new-checkout \ --to on \ --percentage 25 \ --by user_id wrangler flagship flags split <APP_ID> checkout-flow \ --weight control=80 \ --weight treatment=20 \ --by user_id wrangler flagship flags rules update <APP_ID> checkout-flow \ --priority 1 \ --when "country equals US"</code></pre></figure> These commands can also be used from CI/CD pipelines, scripts, and AI agents to inspect Flagship state, update flag behavior, or roll back changes through Wrangler. Refer to the <a href="https://developers.cloudflare.com/flagship/reference/wrangler-commands/"><code>wrangler flagship</code> command reference</a> for the full command guide.

The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.