--- schema_version: 1 route: /t/vercel.md tool: "vercel" --- # sincecutoff.com /t/vercel — Vercel CLI - name: Vercel CLI - kind: cli - children: none - homepage: Changes to the tools coding agents drive, since a model's training cutoff, each linked to its first-party source. Check installed versions and limitations before acting; a cutoff date does not establish what a model knows. Original editorial content: [Apache 2.0](https://sincecutoff.com/v1/data-license.txt), by [0xPatrick](https://0xpatrick.dev). Preserve applicable license and [NOTICE](https://sincecutoff.com/notice.txt) attribution when redistributing. Third-party source text and examples retain their own rights. [License scope and attribution](https://sincecutoff.com/v1/license.json). To stay current, read the changes feed: [`/v1/changes.md?tool=vercel`](https://sincecutoff.com/v1/changes.md?tool=vercel) (or `.json`), adding `since=YYYY-MM-DD` for your training cutoff. Entries for registered children are included; the registry itself is `/v1/tools.json`. How to page and save your place: [llms.txt](https://sincecutoff.com/llms.txt). ### vercel connect discover and categories list connector services and categories (2026-10-14) - slug: vercel-connect-discover-and-categories-list-connector-services-and-categories-2d64e1ac59fc - score: 0.98 How to use it: When you need to choose a connector service, run `vercel connect discover [query]` with optional filters; run `vercel connect categories` to list valid category slugs. Examples: ``` vercel connect discover [query] ``` ``` vercel connect discover --category --connection-method --target --supports-triggers --limit --next ``` ``` vercel connect categories ``` - why_it_matters: Find available connector services and their category slugs before creating a connector. - sources: , - gotchas: "Version: 64.1.0"; "query: Searches service names, aliases, keywords, and descriptions."; "--category : Filters by category; repeatable. Use `vercel connect categories` for valid slugs."; "--connection-method : Filters by connection method, such as `oauth`, `api-key`, or `mcp`; repeatable."; "--target : Filters by exposed product, such as `api` or `mcp`; repeatable."; "--supports-triggers: Shows only services that can forward webhook triggers."; "--limit : Sets the number of services to return; default 50, maximum 500."; "--next : Sets the cursor for the next results page." ### vercel domains buy and renew support nonterminal approval flows (2026-10-08) - slug: vercel-domains-buy-and-renew-support-nonterminal-approval-flows-e667f781490e - score: 0.97 How to use it: When buying or renewing a domain without an interactive terminal, explicitly select the paying team and first request the price without `--amount`. After a person approves the price and terms, run the returned command with the approved amount; for purchases, also provide required registrant details and choose auto-renewal. Examples: ``` vercel domains buy --scope --json ``` ``` vercel domains buy --scope --amount --first-name --last-name --email --phone <+countrycode-and-number> --address --city --state --zip --country --auto-renew --json ``` ``` vercel domains renew --scope --json ``` - why_it_matters: When buying or renewing a domain from a script without a terminal, retrieve the price and renewal terms or submit the approved charge with the required team scope. - sources: , - gotchas: "Version: 63.1.0"; " (required): Domain to buy or renew."; "--scope (required): Select the paying team for a non-interactive charge; saved team selection or `vercel.json` scope alone is insufficient."; "VERCEL_ORG_ID: Alternative to `--scope`: set to the ID of the paying team for a non-interactive charge."; "--amount (required): Required to charge; must equal the current price approved by a person. Omit to request price and approval instructions without charging."; "--first-name (required): Registrant's first name."; "--last-name (required): Registrant's last name."; "--email : Registrant email; required unless supplied by approved billing details."; "--phone (required): Registrant phone, starting with `+` and containing 10–15 digits including country code."; "--address : Street address; required unless supplied by approved billing details. Quote values containing spaces."; "--city : Registrant city; required unless supplied by approved billing details."; "--state : State or province; required unless supplied by approved billing details. Required for every country when specified as a contact field."; "--zip : Postal or ZIP code; required unless supplied by approved billing details. Required for every country when specified as a contact field."; "--country : Two-letter country code; required unless supplied by approved billing details."; "--company : Registrant company name."; "--use-billing-details: Use available team billing email and address fields for registrant details; does not supply first name, last name, or phone. Contact flags override billing details."; "--auto-renew (required): Allow recurring renewal charges at the end of each term. Provide exactly one of this flag and `--no-auto-renew`; neither takes a value."; "--no-auto-renew (required): Turn automatic renewal off. Provide exactly one of this flag and `--auto-renew`; neither takes a value."; "--json: Return structured output without prompts; equivalent documented option: `--format json`."; "Prerequisite: Use Vercel CLI 63.1.0 or later for prompt-free buy/renew commands."; "Prerequisite: Before a non-interactive charge, specify the paying team with `--scope ` or `VERCEL_ORG_ID` set to that team's ID."; "Prerequisite: For a purchase, supply required registrant fields and exactly one auto-renew choice; approved billing details can supply available email and address fields."; "Without a terminal, the team must be named with `--scope` or `VERCEL_ORG_ID`."; "Without `--amount`, no charge is made; the command returns the price, paying team, renewal terms, and exact command to run after a person approves the price."; "A failed or unconfirmed charge returns a JSON error, and the charge request is never retried."; "Without a terminal, `domains buy` requires `--auto-renew` or `--no-auto-renew`; auto-renew has no default there because it starts a recurring charge." ### vc curl accepts full URLs and bare hosts (2026-10-06) - slug: vc-curl-accepts-full-urls-and-bare-hosts-c81bad88aa14 - announced: 2026-05-11 - status: ga - score: 0.91 How to use it: When targeting a deployment by full URL or bare host, use `vc curl` with that target; the CLI resolves project authentication from the target URL. [Release note](https://github.com/vercel/vercel/releases/tag/vercel@53.4.0) Examples: ``` vc curl https:/// ``` ``` vc curl / ``` - why_it_matters: Use `vc curl` to send a request to a project when specifying its target as a full URL or bare host. - sources: , , - gotchas: "Version: 53.4.0"; "url|path (required): Request target: a full URL, bare hostname, or API path. Full URLs and bare hostnames let the CLI resolve the deployment’s owning project; paths target the linked project’s latest production deployment."; "Prerequisite: Vercel CLI v48.8.0 or later; `curl` must be installed on the system."; "Availability: generally available since 2026-10-06" ### vercel CLI adds webhook management commands (2026-10-06) - slug: vercel-cli-adds-webhook-management-commands-4a0562fba043 - announced: 2026-02-03 - status: ga - score: 0.98 How to use it: When maintaining a Vercel account’s webhooks, use `vercel webhooks ls` to list, `get` to inspect, `create` to add, and `rm` to remove; use `--format json` on list/get and `--yes` to skip the removal prompt. Examples: ``` vercel webhooks ls --format json ``` ``` vercel webhooks create https://example.com/webhook --event deployment.created --event deployment.ready ``` ``` vercel webhooks rm --yes ``` - why_it_matters: Manage webhooks while maintaining a Vercel project from the CLI. - sources: , , , , - gotchas: "Version: 50.10.0"; " (required): Webhook identifier for `get` or `rm`."; " (required): Webhook endpoint URL for `create`."; "--event (required): Event to subscribe to when creating; repeat to add events."; "--format json: Output list or get results as JSON; `json` is the only supported value."; "--yes: Skip the removal confirmation prompt."; "Prerequisite: Account webhooks are available on Pro and Enterprise plans."; "Prerequisite: Authenticate the Vercel CLI; docs support a `--token` argument or `VERCEL_TOKEN` environment variable."; "Prerequisite: The CLI webhooks command is marked beta in the current docs."; "Webhook event types are fetched dynamically from the OpenAPI spec."; "Availability: generally available since 2026-10-06" ### vercel flags evaluations supports grouping across flags (2026-10-06) - slug: vercel-flags-evaluations-supports-grouping-across-flags-2316efc2fdcc - score: 0.96 How to use it: To find SDK keys and services still evaluating flags after rotation, query project-wide evaluations grouped by SDK key or client. The release note also supports grouping by variant, flag, environment, or reason. Examples: ``` vercel flags evaluations --group-by sdk-key ``` ``` vercel flags evaluations --group-by client ``` - why_it_matters: Review flag evaluations across a project to identify SDK keys and services still evaluating flags after a key rotation. - before: The documented command took a flag argument: `vercel flags evaluations [flag]`. - sources: , - gotchas: "Version: 62.5.0"; "[flag]: Omit to query evaluations across every flag in the project."; "--group-by : Groups evaluations by variant, flag, sdk-key, client, environment, or reason."; "The `--group-by` values are `variant`, `flag`, `sdk-key`, `client`, `environment`, and `reason`."; "The flag argument is optional to query across every flag in the project." ### vercel pricing lists public plan features (2026-10-06) - slug: vercel-pricing-lists-public-plan-features-5430cde1def3 - score: 0.93 How to use it: When reviewing a repository’s Vercel deployment plan, compare Hobby, Pro, and Enterprise feature availability with `vercel pricing`. The command reads the public pricing table and groups features by the lowest plan that includes them. Examples: ``` vercel pricing ``` ``` vercel pricing ``` - why_it_matters: Compare Hobby, Pro, and Enterprise features while reviewing a repository's Vercel deployment plan. - sources: , - gotchas: "Version: 62.5.0"; "query (optional positional argument): Filters the pricing table; multiple words form one query."; "Lists Hobby, Pro, and Enterprise features from the public pricing table." ### vercel build and dev support requestMethod for flat path schedules (2026-10-05) - slug: vercel-build-and-dev-support-requestmethod-for-flat-path-schedules-d85900a0005e - score: 0.93 How to use it: For a flat path schedule that needs a specific HTTP method, set `requestMethod` to `GET` or `POST`; it defaults to `POST`. `vercel build` writes the method to Build Output, and `vercel dev` invokes the schedule with it. Examples: ``` {"schedules":[{"path":"","schedule":"","requestMethod":"GET"}]} ``` - why_it_matters: When configuring flat path schedules that need GET requests during local development or build output generation, set the schedule request method. - sources: , - gotchas: "Version: 62.4.0"; "requestMethod: HTTP method for a flat path schedule: `GET` or `POST`; defaults to `POST`."; "path (required): Path target for a flat schedule. The flat schedule format aligns with `crons` and uses `schedule` plus one target."; "Prerequisite: Use Vercel CLI 62.4.0 or later for this feature."; "`requestMethod` accepts `GET` or `POST`."; "The default request method is `POST`."; "The behavior applies to flat path schedules." ### vercel traces get accepts trace IDs or request IDs (2026-10-02) - slug: vercel-traces-get-accepts-trace-ids-or-request-ids-b0fae1bd80ab - score: 0.90 How to use it: When you have a trace ID or request ID, run `vercel traces get ` to retrieve the trace details. Examples: ``` vercel traces get ``` - why_it_matters: Retrieve trace details when you have a trace ID or request ID. - sources: , - gotchas: "Version: 62.2.0"; " (required): Trace ID or request ID to retrieve."; "Prerequisite: Use Vercel CLI 62.2.0 or later; the change is included in version 62.2.0."; "Prerequisite: The trace retrieval feature is available on all plans." ### vercel ci logs displays and follows task logs for a run (2026-10-01) - slug: vercel-ci-logs-displays-and-follows-task-logs-for-a-run-3caf8a3b32db - score: 0.99 How to use it: When debugging a Vercel CI run, use `vercel ci logs ` to inspect task logs; add the documented filters or `--follow` to stream a running task. If the run fails before any tasks start, retrieve its setup logs. Examples: ``` vercel ci logs ``` ``` vercel ci logs --failed --task --level ``` ``` vercel ci logs --follow ``` - why_it_matters: Inspect or follow task logs while debugging a Vercel CI run. - sources: - gotchas: "Version: 62.1.0"; " (required): Vercel CI run to inspect."; "--failed: Filter task logs to failed tasks."; "--task : Filter logs by task."; "--level : Filter logs by level."; "--follow: Stream logs for a running task."; "Follow mode performs a final full-snapshot read without the stream timestamp cursor when a task completes, reconnects healthy stream timeouts, handles JSON snapshot responses, respects stdout backpressure, preserves JSONL errors, and bounds interrupted or invalid response retries."; "For completed retried tasks, empty logs produce a stderr warning when no level filter is applied; valid quiet, cached, or skipped tasks do not fail. JSON mode emits a structured stderr warning and reserves stdout for log records."; "Human output distinguishes runs without failures yet from completed runs; empty `--failed` JSON results include `run.finished`."; "Commands resolve the latest attempt from the attempts endpoint instead of relying on list-row ordering."; "Reconnects replay retained logs and deduplicate by timestamp, level, message, and occurrence count, preserving repeated identical lines and older late arrivals in append-only history."; "Replay stops explicitly at its 8 MiB estimated-state or 50,000 distinct-record limit instead of silently evicting records; the final snapshot recovers retained logs suppressed within the active stream."; "Without server record IDs, an ingestion cursor, and a completion watermark, logs ingested after the final snapshot are not guaranteed; the final read drains logs available at that point, not future ingestion." ### vercel dev serves Vercel Queues and Runtime Cache on local endpoints (2026-09-17) - slug: vercel-dev-serves-vercel-queues-and-runtime-cache-on-local-endpoints-ed4fa0326b67 - score: 0.92 How to use it: When developing a project that uses Vercel Queues or Runtime Cache, run `vercel dev` from the project root to use their local endpoints, including when no queue services are configured. Examples: ``` vercel dev ``` ``` vercel dev --queue-port --runtime-cache-port ``` - why_it_matters: Run a project with Vercel Queues or Runtime Cache locally, including when no queue services are configured. - sources: , , - gotchas: "Version: 59.22.0"; "--queue-port : Pins the local Queues port."; "--runtime-cache-port : Pins the local Runtime Cache port."; "Prerequisite: Install project dependencies with `npm install` before running `vercel dev`."; "A manually set `RUNTIME_CACHE_ENDPOINT` takes precedence."; "Occupied default ports are incremented automatically unless pinned." ### vercel schedules get and list inspect linked-project schedules (2026-09-16) - slug: vercel-schedules-get-and-list-inspect-linked-project-schedules-db17cd1ef3ae - score: 0.94 How to use it: If inspecting schedules in a Vercel project, run `vercel schedules list` to list them or `vercel schedules get ` to inspect one. The project must be linked. Examples: ``` vercel schedules list ``` ``` vercel schedules get ``` - why_it_matters: Inspect schedules configured for a linked Vercel project. - sources: , - gotchas: "Version: 59.20.0"; "Prerequisite: The CLI must have a linked Vercel project; `vercel link` links the current directory to a project."; "Prerequisite: The official release note adds these commands in Vercel CLI 59.20.0."; "The project must be linked." ### vercel storage commands manage Blob and Global Config stores (2026-09-14) - slug: vercel-storage-commands-manage-blob-and-global-config-stores-8b1f24bdfcf6 - score: 0.97 How to use it: To manage a Vercel project's Blob or Global Config stores, use `vercel storage list|create|get|delete`. For `create`, supply `--type` and that store type's product flags; use `--type` with `get` or `delete` when names collide, and handle `action_required` when deletion is non-interactive. Examples: ``` vercel storage list ``` ``` vercel storage create --type [--access ] [--region ] [--items ] ``` ``` vercel storage get --type vercel storage delete --type ``` - why_it_matters: Manage Blob and Global Config storage resources for a Vercel project. - sources: , - gotchas: "Version: 59.17.0"; "--type (required): Selects the store type for create; get and delete accept it to disambiguate stores with the same name."; "--access : Blob create product flag; valid values and default are not stated in the release note."; "--region : Blob create product flag; valid values and default are not stated in the release note."; "--items : Global Config create product flag; accepted format is not stated in the release note."; "Prerequisite: Authenticate with `vercel login`, or use a token with `--token` in CI/CD. CLI commands that access resources or perform administrative tasks require authentication."; "Prerequisite: Install the Vercel CLI, for example with `pnpm i -g vercel`."; "`delete` cannot be undone and drops every project connection."; "`delete` always requires interactive confirmation and returns an `action_required` payload in non-interactive contexts."; "`get` and `delete` accept `--type` to distinguish a Blob store and a Global Config with the same name."; "Docs conflict: The current Blob CLI documentation describes older product-specific forms (`vercel blob create-store`, `get-store`, `delete-store`); it does not document the `vercel storage` command. Do not substitute those forms for the 59.17.0 release-note command. https://vercel.com/docs/cli/blob" ### vercel flags inspect supports --json output (2026-09-11) - slug: vercel-flags-inspect-supports-json-output-68e88e7b9d8c - score: 0.97 How to use it: When a workflow needs structured output for a feature flag, run `vercel flags inspect --json` to print its definition to stdout. Examples: ``` vercel flags inspect --json ``` - why_it_matters: Inspect a feature flag definition in a script or other workflow that consumes structured output. - sources: , , - gotchas: "Version: 59.16.0"; " (required): Flag key to inspect. The CLI docs show `[flag]` as optional; supply the flag key to inspect a specific definition."; "--json: Output the flag definition as JSON to stdout; added in Vercel CLI 59.16.0."; "Prerequisite: Use an authenticated Vercel CLI. Install with `pnpm i -g vercel`."; "Prerequisite: CLI-only flag management does not require SDK packages, Toolbar, Flags Explorer, or `.env.local`." ### vercel flags entities create adds schema-validated entity creation (2026-09-09) - slug: vercel-flags-entities-create-adds-schema-validated-entity-creation-1a3d8b6cec23 - score: 0.95 How to use it: When creating a flag-targeting entity in a linked Vercel project, run `vercel flags entities create` with the entity kind and one or more typed attributes. The CLI validates the entity kind, attribute keys, and attribute types. Examples: ``` vercel flags entities create --label