Vercel CLI adds spend budgets and build cache size reporting

Vercel has rolled out two cost-focused changes to its platform: spend budgets can now be managed directly from the Vercel CLI, and deployments expose how much build cache they saved and how close that cache is to its limit. Both announcements appeared on the Vercel blog on October 23, 2026.

Spend budgets come to the command line

Running vercel budgets now returns the team's current spend and its active budget, or a message explaining that no budget exists. According to the Vercel blog, this is the same On-Demand Budget found in team billing settings, now surfaced for terminals, scripts and coding agents.

Budgets are created with vercel budgets set --amount and removed again with vercel budgets remove. Vercel notes that setting a budget alone does not curb usage. Enforcement comes from the optional --pause flag, which stops production deployments for every project on the team once spend reaches 100% of the budget. In the example Vercel gives, a $200 budget on a team that had already spent $63.33 showed 32% used, with pausing enabled.

Alert history in the terminal

A new vercel budgets alerts command prints the full history of budget alerts, filterable with --since, --until, --limit and --json. A plain vercel budgets invocation includes the three most recent alerts alongside the budget table. Each entry records the date, the threshold crossed, spend at the time, the budget amount and the actions configured.

Access and availability

Managing budgets requires the Owner or Billing role on the team. The Vercel blog says Spend Management costs nothing extra for Pro teams, and is also included for Enterprise teams on the Flexible Commitment plan.

Deployments now report build cache size

The second change targets a quieter cost driver: build caches. Deployment summaries now display the size of the build cache each deployment saved and how close it sits to the limit of its build machine. The same data is available through vercel inspect on CLI version 65.1.0 or newer, and in the get-deployment REST API endpoint.

The details explain why this matters for billing. Uploading the build cache counts as billable build time, and a cache that exceeds its machine's limit is discarded outright, so the next build starts cold. The feature is on by default across all plans for deployments built on or after October 21, and Vercel's documentation lists the maximum cache size for each build machine type.

Why it matters

Cloud cost overruns often go unnoticed until the invoice arrives, and platforms with per-build billing are no exception. By moving budgets into the CLI, Vercel turns what was a dashboard-only control into something automation can act on: a script or AI coding agent can check spend, set a cap and enable a hard pause without anyone opening a browser. The pause flag is the notable part, converting a budget from a passive notification into an enforcement mechanism that halts production deployments at the limit.

The cache-size reporting addresses the other half of the problem: diagnosis. Teams that could not see their cache usage had no way to know why builds ran long, why build minutes climbed, or why a cache had silently been thrown away. With sizes and limits now visible in the CLI and API, both humans and agents can spot oversized caches before they are discarded and adjust build configurations accordingly. Together, the two features give Vercel users terminal-level visibility and control over the levers that dominate platform costs: spend and build time.