# Manage Vercel Flags segments with Vercel CLI

Source: [Vercel](https://vercel.com/changelog/manage-vercel-flags-segments-with-vercel-cli)  
Feed7 permalink: https://feed7.dev/p/manage-vercel-flags-segments-with-vercel-cli-0uv8tq6  
Published: Unknown  
Trust: Official Source (official_source)

## 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.

## Source 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-Ready 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.

**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**.

**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.

## Context Map

- Layer: infra
- Domains: coding
- Topics: dev-ux

## 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.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.