---
name: Vercel CLI
slug: vercel-cli
type: github
source_url: https://github.com/vercel/vercel
organization: Vercel
organization_slug: vercel
total_releases: 684
latest_version: @vercel/passport@0.1.3
latest_date: 2026-07-18
last_updated: 2026-07-20
tracking_since: 2026-03-05
canonical: https://releases.sh/vercel/vercel-cli
organization_url: https://releases.sh/vercel
---
Vercel CLI shipped a major redesign of blob store management, graduating metrics to general availability, and expanded experimental services support. The `vercel blob` command now requires explicit `--access` flags, replaced deprecated subcommands with `create-store`, `delete-store`, and `list-stores`, and added `empty-store` with confirmation flows that surface connected projects. The `vercel metrics` CLI shed its beta label while simplifying metric selection and cleaning up schema output. Behind the scenes, experimental services gained support for dynamically specifying crons from Python, configurable environment prefixes per service, multiple topics for workers, and auto-detection from Railway configs. New CLI commands arrived for managing deploy hooks, edge configs, project checks, speed insights, web analytics, tokens, team SSO, OAuth apps, and project-level routing rules with AI-powered generation. The CLI also strengthened observability with deployment checks support in `deploy --prod`, showed check run logs inline with deep-links, and cached authenticated user IDs to reduce API requests.
March shipped agent-focused enhancements and expanded routing capabilities. The CLI auto-installs agent tooling (Claude, Cursor) and accepts structured JSON prompts for plugin approval via `vercel login`, `vercel link`, and `vercel deploy`. New `vercel routes` command lets developers manage project-level routing rules—rewrites, redirects, response headers—with optional AI generation. Build-utils exposed hash and lambda utilities for shared consumption, while Python gained Django static file handling and Celery worker declarations with `broker_url="vercel://"`. Services configuration matured with multiple topics per worker, env prefix support, and subdomain routing.
### Patch Changes
- 86d88dd: Add a `verifyIdentity` helper for verifying forwarded Passport identity tokens.
### Patch Changes
- dad41da: Test Connect against a recent stable Eve and AI SDK 7 release.
### Patch Changes
- 145eb34: Improve `vercel ai-gateway coding-agents setup` prompts: use the searchable team picker, keep the multiselect key legend visible after the first selection, and narrow the prompt lines by moving context off the question line.
The apply step now offers a coding-agent handoff: when the key is stored in the macOS Keychain it asks whether to write the files or "Copy a prompt for my agent" (which creates the key, stores it in the Keychain, and copies agent-ready setup instructions — with no plaintext key — to the clipboard); without the Keychain it stays a plain yes/no confirm. A new `--apply ` flag drives this non-interactively — `--apply prompt` writes the prompt to stdout so it can be piped into an agent (`… --apply prompt --yes | claude -p`), and in machine mode it rides along as a `prompt` JSON field.
### Patch Changes
- b08b736: Support linked-project deploys with project-scoped tokens that cannot fetch owner user/team resources.
### Patch Changes
- a55e7df: Replace user-facing `experimentalServices` references with `services` in error/warning messages and rename error codes (`NO_EXPERIMENTAL_SERVICES_CONFIGURED` → `NO_SERVICES_CONFIGURED`, `MISSING_EXPERIMENTAL_SERVICES` → `MISSING_SERVICES`). The deprecated v1 config key should no longer appear in guidance shown to users.
- Updated dependencies [238543c]
- @vercel/build-utils@13.34.0
### Minor Changes
- c636d67: Add optional `claims` field to `ConnectTokenResponse` for allow-listed upstream OAuth token claims
### Minor Changes
- e4866e9: Skip the Rust `target/` directory by default for Rust projects.
Rust projects produce a `target/` directory of build artifacts that can be
hundreds of MB. It's rebuilt on Vercel during the deployment (and cached
server-side), so uploading it only slows deployments down. When a root
`Cargo.toml` is detected, `target/` is now ignored by default during
`vercel deploy` and `vercel dev`. Users can opt back in with `!/target` in
their `.vercelignore`.
Also hardened the local file scanner used by `vercel dev` so that a directory
removed mid-scan (a common race with `cargo build` churning `target/`) is
skipped instead of crashing the process.
### Patch Changes
- Updated dependencies [238543c]
- @vercel/build-utils@13.34.0
### Minor Changes
- 238543c: Support Python services that declare their web app and development workflow sidecars through a `pyproject.toml` entrypoint in `vercel dev`.
### Patch Changes
- d5751d6: Allow Env, Target, Flags rules, Routes, Redirects, Firewall, and Git commands to select a project explicitly with `--project`, including from an unlinked directory.
- 1d8e0ee: Extract project-link validation shared by routes, redirects, and firewall commands.
- b0aa678: Consolidate suggested-command and subcommand-argument helpers while preserving explicit project context and required-argument validation.
- c06b596: Fix `vercel domains add` sending the alias mutation under a stale ambient team scope. When run inside a directory linked to a project in another team, the command now resolves the local project link (like `vercel domains ls`) and scopes the domain/alias request to the linked team, so a same-name project in the ambient team can no longer be targeted by mistake.
- a39869e: Fix `vercel dev` returning 404 for `api/` functions using the rust, python, ruby, or go runtimes when the project has a framework dev command (e.g. Next.js). These runtimes are registered by backend framework presets, which caused the dev server to misclassify `api/` functions as the frontend build and skip building them.
- a55e7df: Replace user-facing `experimentalServices` references with `services` in error/warning messages and rename error codes (`NO_EXPERIMENTAL_SERVICES_CONFIGURED` → `NO_SERVICES_CONFIGURED`, `MISSING_EXPERIMENTAL_SERVICES` → `MISSING_SERVICES`). The deprecated v1 config key should no longer appear in guidance shown to users.
- e4866e9: Skip the Rust `target/` directory by default for Rust projects.
Rust projects produce a `target/` directory of build artifacts that can be
hundreds of MB. It's rebuilt on Vercel during the deployment (and cached
server-side), so uploading it only slows deployments down. When a root
`Cargo.toml` is detected, `target/` is now ignored by default during
`vercel deploy` and `vercel dev`. Users can opt back in with `!/target` in
their `.vercelignore`.
Also hardened the local file scanner used by `vercel dev` so that a directory
removed mid-scan (a common race with `cargo build` churning `target/`) is
skipped instead of crashing the process.
- 7ea6c7a: Preserve buildCommand and combine preDeployCommand when writing inferred services config to vercel.json in V2 format.
- 4cce813: Write `[SENSITIVE]` placeholder instead of an empty string when `vercel env pull` encounters sensitive environment variables whose values cannot be read, so an unset value is distinguishable from a redacted one
- Updated dependencies [b0ed8e5]
- Updated dependencies [c555d3a]
- Updated dependencies [238543c]
- Updated dependencies [f97e2e0]
- @vercel/python@6.51.0
- @vercel/build-utils@13.34.0
- @vercel/static-build@2.11.8
- @vercel/backends@0.8.25
- @vercel/container@0.0.5
- @vercel/elysia@0.1.102
- @vercel/express@0.1.116
- @vercel/fastify@0.1.105
- @vercel/go@3.10.2
- @vercel/h3@0.1.111
- @vercel/hono@0.2.105
- @vercel/hydrogen@1.4.0
- @vercel/koa@0.1.85
- @vercel/nestjs@0.2.106
- @vercel/next@4.20.4
- @vercel/node@5.8.26
- @vercel/redwood@2.5.0
- @vercel/remix-builder@5.9.1
- @vercel/ruby@2.5.1
- @vercel/rust@1.4.0
### Patch Changes
- fa14ee9: Mark the Services framework preset as stable.
### Patch Changes
- ce094f1: Show a specific error message when purchasing v0 credits without a paid v0 plan, instead of the generic unexpected-error fallback.
- 3e0e6a8: Refactor linked project resolution to use named options.
- 877c1ba: Allow `vercel env ls` to target a project explicitly without linking the current directory.
- 81360cf: Use `/v5/certs` instead of legacy `/v5/now/certs` when listing custom certs for a domain.
- a6af051: Add `vercel flags versions ` and `vercel flags versions diff --revision ` to inspect feature flag version history and changes.
Examples:
```bash
vercel flags versions my-flag
vercel flags versions my-flag --environment production
vercel flags versions diff my-flag --revision 4
```
- 51c7c32: `vercel logs --follow` now resolves a deployment automatically instead of erroring. When no deployment is specified it follows, in order: the latest deployment on the current git branch (using the provider-agnostic `branch` filter, which also matches deployments from unrecognized git remotes), your latest deployment, then the latest production deployment. `--environment production` streams the latest production deployment directly, and `--environment preview` restricts resolution to preview deployments.
- 51c7c32: `vercel logs` now defaults to `--expand` output when stderr is not a TTY (agents, pipes, CI), printing every log message in full instead of truncating messages to a fixed-width table column.
- def07fc: Migrate `@vercel/client` and `@vercel/build-utils` from `node-fetch` to native `fetch`. This removes the last `url.parse()` usage from the CLI bundle, which triggered a `DEP0169` DeprecationWarning on Node 24 (visible in the standalone binary during `vercel deploy`).
BREAKING CHANGE (`@vercel/client`): the `agent?: http.Agent` option was replaced with `dispatcher?: FetchDispatcher` (an undici dispatcher, e.g. `undici.ProxyAgent`), since native `fetch` does not support Node.js HTTP agents. The CLI now threads its proxy-aware dispatcher through automatically, so `HTTP_PROXY`/`HTTPS_PROXY` behavior is unchanged for CLI users.
- 75342cb: Resolve an explicit scope before looking up a project for local builds.
- b16a9a2: Standardize explicit project resolution across existing project-aware commands.
- 075dc0c: Respect explicit project and scope selection when resolving project context.
- Updated dependencies [def07fc]
- @vercel/build-utils@13.33.1
- @vercel/backends@0.8.24
- @vercel/container@0.0.5
- @vercel/elysia@0.1.101
- @vercel/express@0.1.115
- @vercel/fastify@0.1.104
- @vercel/go@3.10.2
- @vercel/h3@0.1.110
- @vercel/hono@0.2.104
- @vercel/hydrogen@1.4.0
- @vercel/koa@0.1.84
- @vercel/nestjs@0.2.105
- @vercel/next@4.20.4
- @vercel/node@5.8.25
- @vercel/python@6.50.0
- @vercel/redwood@2.5.0
- @vercel/remix-builder@5.9.1
- @vercel/ruby@2.5.1
- @vercel/rust@1.4.0
- @vercel/static-build@2.11.7
### Patch Changes
- 0cc0e8d: Expose and document the per-issuance `tokenId` on `ConnectTokenResponse` (returned by `getToken`/`getTokenResponse`). It's a stable identifier for the issued token — new on each issuance/refresh — for correlating a token with its usage in Vercel observability/billing data.
### Minor Changes
- 997d319: `vercel env add` now accepts a comma-separated list of environments to create a single Environment Variable entry spanning multiple targets, e.g. `vercel env add API_URL production,preview,development`. Invalid environment names fail locally with a clear error (`invalid_environment` in non-interactive mode), custom Environment slugs are resolved to ids, and a Git branch is rejected unless Preview is the only target. Non-interactive `missing_environment`, `missing_requirements`, and sensitivity-conflict payloads now suggest the multi-target command form.
### Patch Changes
- e6b11f0: Add finer-grained `vc.doBuild` spans (`vc.readConfigInputs`, `vc.prepareFlagsDefinitions`, `vc.getFiles`, `vc.populateFilesMap`, and `vc.setMonorepoDefaultSettings`) so build-container traces can attribute previously unaccounted CLI orchestration time.
- 383c0a0: Fix native-trampoline test hardcoding 55.0.0 that broke after version bump to 56.1.0.
The test now reads the version from packages/cli/package.json and strips
NODE_PATH/VITEST env vars so require.resolve inside the temp install does
not leak the repo's pnpm store. Also fixes VERCEL_VC_NATIVE leak on
ENOENT/EACCES fallback (JS fallback was mislabeled as "(native)") and
updates the stale Part-1 comment in src/vc.js.
- 351a9b6: Exclude `vercel.ts` config file variants from static file serving
### Minor Changes
- fac79dc: Make the CLI bin native-aware: resolve and spawn a `@vercel/vc-native-*`
binary when present, otherwise no-op into the existing JS CLI. Part 1 of 2;
no optionalDependencies are wired yet, so this release is a no-op that
confirms the JS path is unaffected. Part 2 wires the release flow to
publish natives before vercel.
### Patch Changes
- e01c1d2: Harden filesystem trust boundaries: `vercel init` no longer materializes symlink or hardlink entries from downloaded example archives (blocking tar link-following path traversal, CVE-2024-12905 / CVE-2025-48387, and upgrading `tar-fs` to 1.16.5), the deploy root-directory check now normalizes paths before the containment test so a sibling directory sharing the project's path prefix can no longer be selected, and `ai-gateway coding-agents setup` now flags in its plan when a target config path is a symlink so the approval prompt reflects the file the write actually lands on.
### Minor Changes
- 7bbfd48: Support `"entrypoint": "pyproject.toml"` for services. A service may now set `entrypoint: "pyproject.toml"` to build exactly what that file declares: the web app from `tool.vercel.entrypoint` (when present) and queue subscribers from `[[tool.vercel.subscribers]]`. Filename-based entrypoint auto-detection never runs in this mode, and subscribers-only services (no web function) are supported.
- f11c4c4: Bytecode-first packing for runtime-dependency-install builds (>225 MB) when `VERCEL_PYTHON_COMPILEALL` is enabled.
The zip bundles only the mandatory packages plus a `sys.pycache_prefix` bytecode tree covering the app and all dependencies including those installed into `/tmp` at cold start, and defers every other public package to the cold-start `uv sync`. Falls back to knapsack packing (now with a slack-capacity bytecode fill) when the externalized set would not fit Lambda ephemeral storage.
### Patch Changes
- 9637ae6: Add support for declaring the workflow entrypoint via `tool.vercel.workflows` in `pyproject.toml`.
### Major Changes
- 4998ec8: `vercel routes export` now uses `--output` (`-o`) instead of `--format` to select the output file format (`json` or `ts`, dotted forms like `.ts` also accepted). This frees `--format` to align with the standard output-format convention used by other commands. Update any scripts from `routes export --format ts` to `routes export --output ts`.
### Minor Changes
- 5ae15fa: Add `vercel ai-gateway coding-agents setup` to connect Claude Code to the AI Gateway from an existing API key (`--key`): it sets the gateway base URL and authentication in `~/.claude/settings.json` (honoring `CLAUDE_CONFIG_DIR`), never pins a default model, is idempotent, masks the key in output, skips unparseable configs instead of clobbering them, edits existing config files in place so your own keys and formatting are untouched, and emits a structured JSON result in non-interactive mode.
- 24c2b3c: Automatically install a marketplace product's declared agent skills after `vercel integration add` provisions it, replacing the interactive confirmation prompt. The transcript ends with an install summary linking to the product's marketplace page, and failed installs fall back to printing the manual `npx skills add` command.
- 607f0ef: Add service information to deploy-manifest.
- 8642a47: Remove the `vercel oauth-apps` sub-command, reverting the OAuth / connected apps parity scope.
- 57e2091: `vercel env pull` now keeps variables that only exist in the local env file instead of deleting them. Kept variables are listed in the command output. CLI-managed variables (`VERCEL_OIDC_TOKEN` and analytics IDs) are still removed when they no longer exist upstream.
### Patch Changes
- 2a403e2: Add Codex support to `vercel ai-gateway coding-agents setup`. It writes a `vercel` model provider to `~/.codex/config.toml` (OpenAI-compatible base URL, `responses` wire API) without pinning a default model, and exports the gateway API key via your shell rc (honoring `CODEX_HOME` and fish/`ZDOTDIR`). Merging into an existing `config.toml` edits assignments in place, preserving your comments and formatting.
- 683f013: `ai-gateway coding-agents setup` can now **provision a key** for you: run it without `--key` and it creates an AI Gateway API key (prompting for the owning team and a name, or using `--name`/`--scope` and the current scope with `--yes`), then writes that key into the agent configs.
Re-running when everything is already set up is no longer a dead end: it prompts to **rotate the key or switch team**, and `--reconfigure` does the same non-interactively (useful for a rotated or expired key, or a different org). A plain re-run stays a no-op.
- e64b222: `ai-gateway coding-agents setup` now detects the Codex desktop app and asks for consent before configuring Codex, since the desktop app cannot use custom model providers and stops working when one is set (the Codex CLI keeps working). Non-interactive and `--yes` runs configure Codex only when it is explicitly requested with `--agent`/`--all`; JSON output gains a `warnings` array and a `requires_consent` skip reason, and a run refused for lack of consent exits 1 with a self-contained `requires_consent` error payload (structured warnings, skip entries, and a runnable `next[]` command). A declined agent's configuration is left untouched.
- 7190684: `ai-gateway coding-agents setup` now configures only the agents detected on the machine when run non-interactively without `--agent`/`--all`, exits with code 1 (without creating an API key) when no agent configuration can be written, and on Windows reports the environment variable to set instead of writing a shell file that is never loaded (unless `--shell-rc` is passed explicitly). Non-interactive re-runs with `--key` on an already-configured macOS Keychain setup now refresh the stored key instead of silently keeping the old one.
- 097395b: `ai-gateway coding-agents setup` can now put **limits** on a key it creates: a spend cap (`--budget` with `--refresh-period` / `--include-byok`) and an expiry (`--expiration` `7d|30d|60d|90d|1y|none`). Interactively it asks whether to set each. The limits are sent only when creating a key; reusing one with `--key` is unaffected.
- fcdf5cd: Store the `coding-agents setup` API key in the macOS login Keychain instead of writing it into plaintext config files. When available it's used automatically: env-based agents resolve the key from the shell at runtime (a managed shell-rc block runs `security find-generic-password`), so the secret never lands in a config file. Pass `--no-keychain`, or run off macOS, to embed the key directly; it also falls back to embedding if the Keychain write fails.
- c66bae3: Add OpenCode support to `vercel ai-gateway coding-agents setup`. It supplies the gateway API key to OpenCode's native `vercel` provider in `~/.config/opencode/opencode.json` (honoring `XDG_CONFIG_HOME`) without pinning a default model. With the macOS Keychain in use, the key is kept out of the config and resolved from `AI_GATEWAY_API_KEY` (exported from the shell rc) at runtime instead.
- 2ffbf59: Add Pi support to `vercel ai-gateway coding-agents setup`. It writes the gateway credential to Pi's native `vercel-ai-gateway` auth entry in `~/.pi/agent/auth.json` (created `0600`, honoring `PI_CODING_AGENT_DIR`) without pinning a default model.
- bb16ec9: `ai-gateway coding-agents setup` now previews before it writes. `--dry-run` and the pre-apply summary show the planned per-file changes as a masked diff, the resolved key/quota/expiry, and the `.bak` backups it would create (suppressed with `--no-backup`), then ask for confirmation before applying. For non-standard setups, `--agent-config =` overrides an agent's config-file location and `--shell-rc ` the shell rc; interactively it offers a custom path when an agent isn't found at its default location.
- 35fba40: Attribute marketplace agent-skill auto-installs in the skills CLI's install telemetry by passing `--metadata` (origin, flow, integration and product slugs) to the `npx skills add` invocation. Older skills versions (< 1.5.16) ignore the flag and install unchanged.
- fd8e544: Preserve an environment's serving mode when feature flag rules are added,
updated, moved, or removed. When the environment is serving a fixed variant,
the CLI identifies that variant and warns that rule changes will not affect flag
evaluation until the environment uses targeting again.
- Updated dependencies [607f0ef]
- Updated dependencies [7bbfd48]
- Updated dependencies [9637ae6]
- Updated dependencies [f11c4c4]
- @vercel/build-utils@13.33.0
- @vercel/python@6.50.0
- @vercel/backends@0.8.23
- @vercel/container@0.0.5
- @vercel/elysia@0.1.100
- @vercel/express@0.1.114
- @vercel/fastify@0.1.103
- @vercel/go@3.10.2
- @vercel/h3@0.1.109
- @vercel/hono@0.2.103
- @vercel/hydrogen@1.4.0
- @vercel/koa@0.1.83
- @vercel/nestjs@0.2.104
- @vercel/next@4.20.4
- @vercel/node@5.8.24
- @vercel/redwood@2.5.0
- @vercel/remix-builder@5.9.1
- @vercel/ruby@2.5.1
- @vercel/rust@1.4.0
- @vercel/static-build@2.11.6
### Patch Changes
- 6b2cfc6: Reject routePrefix path traversal when mounting static build output
- @vercel/gatsby-plugin-vercel-builder@2.2.25
### Patch Changes
- 0f67a94: Include instrumentation for Node.js Middleware
### Patch Changes
- 7bc4db0: [frameworks] Add Lovable platform framework and platform attribute
### Patch Changes
- 8d25cea: Apply `functions` configuration (`memory`, `maxDuration`, `architecture`, `regions`, `functionFailoverRegions`, `experimentalTriggers`, `supportsCancellation`) to container runtime outputs. The `@vercel/container` builder now resolves matching `vercel.json` / per-service `functions` entries at build time, and the CLI writes those settings into the container `.vc-config.json`.
### Patch Changes
- 067a068: Finish CLI deployments from alias-assigned build stream events while retaining deployment polling as a fallback.
- Updated dependencies [7b30856]
- @vercel/build-utils@13.32.3