Vercel CLI Gains Commands for DNS, Domains, and Projects Right in the Terminal

Vercel announced in its changelog a significant expansion of its CLI: there are now dedicated commands for managing DNS records, domains, and projects. The idea, according to the text signed by David Lee and Melkey Moksyakov, is to bring to the terminal much of what was previously only available in the dashboard or via API, in a format that works for both interactive use and scripts, and explicitly, for AI agents.

For those who host on Vercel, the practical gain is being able to automate and debug infrastructure configuration without leaving the command line, instead of switching between the web dashboard and manual REST API calls.

What Was Added

The update covers four areas:

• DNS inspection and editing: you can retrieve the complete configuration of a record and update it in place using the record ID. vercel dns update accepts changes to name, type, value, TTL, MX priority, and comment. SRV records can also be edited via the priority, weight, port, and target fields.
• Renewal of domains purchased on Vercel: on-demand renewal or auto-renewal control. The command shows the current price and asks for confirmation before completing the purchase.
• Project state and observability control: pause or resume a project and configure observability features directly from the CLI. Web Analytics and Speed Insights could already be enabled from there; now they can also be disabled.
• Project member management: add a member with a specific role or remove an existing one.

The detail that ties all of this together is that all the new commands support structured JSON output, and billable or destructive actions require explicit confirmation. This combination (JSON + mandatory confirmation) is what differentiates a utility designed only for humans from one designed also for pipelines and agents.

Why JSON Output Changes the Game

The most interesting point isn't each individual command, but the response format. A CLI that only prints pretty tables in the terminal is great for human reading and terrible for automation: you end up writing fragile grep, awk, and sed to extract a value. With JSON output, the same command becomes input for a reliable script.

In practice, this means you can do something like:

vercel dns ls example.com --json | jq '.[] | select(.type == "A")'

and parse the result without hacks. In a CI pipeline, this allows validating whether a DNS record has the expected value before promoting a deploy, or reacting to configuration mismatches automatically.

The explicit mention of agents in the source isn't marketing decoration. An AI agent that needs to change an infrastructure configuration depends on two requirements: a predictable input and output interface (JSON solves the output) and protection against irreversible actions (mandatory confirmation on destructive and billable operations solves this). This is Vercel designing its CLI for a scenario where part of infrastructure changes are mediated by LLMs, without giving up a safeguard in case the agent makes a mistake.

A Concrete Workflow Example

Imagine a team that buys domains on Vercel and wants to make sure none of them expire due to forgetfulness, but also doesn't want auto-renewal turned on for everything due to cost. Before, this meant manual navigation in the dashboard. Now you can build a report and decide renewals in a script, knowing that the renewal command shows the price and asks for confirmation before charging, which prevents a poorly written automation from spending money on its own.

The same applies to the pause/resume project pair: in staging environments that only need to exist during business hours, pausing via CLI in a cron job becomes trivial. And being able to disable Web Analytics and Speed Insights from the command line (not just enable them, as before) closes an annoying gap for those managing dozens of projects who want to standardize configuration via script.

What This Replaces and Where It's Not Worth It

In practice, these commands replace part of the direct uses of the Vercel REST API and dashboard navigation. For one-off DNS operations or member management, writing against the API required dealing with authentication, endpoints, and manual parsing; the CLI encapsulates that and still delivers clean JSON.

But there are clear limits. This doesn't replace real infrastructure as code. If the team already uses Terraform or Vercel's official provider to version DNS and project configuration, imperative CLI commands coexist as a tool for inspection and quick adjustment, not as a source of truth. Running vercel dns update outside the declarative flow creates drift between the actual state and what's in the repository, exactly the problem IaC exists to avoid.

Another important distinction: domain renewal only applies to domains purchased on Vercel. Anyone who registers a domain with another registrar and only points it to Vercel continues to manage renewal and much of the DNS elsewhere.

For Brazilian Developers

The direct impact depends on how much of the stack already lives on Vercel. For those who use the platform as the main hosting for Next.js projects and similar, the update reduces operational friction and opens up room for automation that previously depended on clicks or extra code against the API. It's worth remembering that domain purchase and renewal through Vercel are billed in dollars, so the command that shows the price before confirming is a welcome safeguard against exchange-rate surprises in scripts.

To get started, just update the CLI:

npm i -g vercel@latest

Details for each command are in the official CLI documentation, referenced in the changelog itself. What remains open is how much further Vercel will push this layer toward agents: the insistence on structured JSON and confirmation for sensitive actions suggests the CLI is increasingly becoming an interface designed to be operated by machines as much as by people.