{
  "schema_version": "1.0",
  "id": "archive:https://vercel.com/changelog/manage-vercel-flags-segments-with-vercel-cli",
  "slug": "manage-vercel-flags-segments-with-vercel-cli-0uv8tq6",
  "url": "https://feed7.dev/p/manage-vercel-flags-segments-with-vercel-cli-0uv8tq6",
  "title": "Manage Vercel Flags segments with Vercel CLI",
  "why_included": "New vercel flags segments command lets you create and edit flag-targeting segments from the terminal; --json output makes targeting scriptable from CI and agent-driven pipelines.",
  "summary": "**The gist** The Vercel CLI adds a **vercel flags segments** command for managing flag targeting from the terminal. A segment decides who sees a flag; membership composes from three repeatable tokens — **include:, exclude:, and rule:** — passed via **--add and --remove** for incremental edits, while **--data** replaces a whole segment definition with raw JSON.",
  "practical_implication": "**Why it matters** Flag targeting was dashboard work; now it is terminal-scriptable. Every segment command supports **--json** output, so a CI job or coding agent can inspect and update who sees a feature — say, add an enterprise-plan rule to a beta segment — without leaving the pipeline. Vercel explicitly pitches this for **agent-driven pipelines**.",
  "agent_context": "**The gist** The Vercel CLI adds a **vercel flags segments** command for managing flag targeting from the terminal. A segment decides who sees a flag; membership composes from three repeatable tokens — **include:, exclude:, and rule:** — passed via **--add and --remove** for incremental edits, while **--data** replaces a whole segment definition with raw JSON.\n\n**Why it matters** Flag targeting was dashboard work; now it is terminal-scriptable. Every segment command supports **--json** output, so a CI job or coding agent can inspect and update who sees a feature — say, add an enterprise-plan rule to a beta segment — without leaving the pipeline. Vercel explicitly pitches this for **agent-driven pipelines**.\n\n**Watch out** You need the **latest Vercel CLI** to get the command, and the changelog mentions no extra guardrails: a scripted or agent-run segment edit changes production targeting as directly as a dashboard change, so gate these commands in automation.",
  "source": {
    "name": "Vercel",
    "url": "https://vercel.com/changelog/manage-vercel-flags-segments-with-vercel-cli",
    "published_at": null
  },
  "source_class": "blog_post",
  "content_type": "Engineering Post",
  "layer": "infra",
  "domains": [
    "coding"
  ],
  "topics": [
    "dev-ux"
  ],
  "verification": {
    "status": "official_source",
    "label": "Official Source",
    "method": "source_feed",
    "verified_at": null
  },
  "uncertainty": [
    "You need the **latest Vercel CLI** to get the command, and the changelog mentions no extra guardrails: a scripted or agent-run segment edit changes production targeting as directly as a dashboard change, so gate these commands in automation."
  ],
  "lifecycle": "Current",
  "published_at": null,
  "modified_at": null,
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/manage-vercel-flags-segments-with-vercel-cli-0uv8tq6",
    "json": "https://feed7.dev/p/manage-vercel-flags-segments-with-vercel-cli-0uv8tq6.json",
    "markdown": "https://feed7.dev/p/manage-vercel-flags-segments-with-vercel-cli-0uv8tq6.md"
  }
}