Vercel CLI adds DNS, domain and project commands with JSON output for scripts

Vercel has expanded its command-line tool with a dedicated set of commands for managing DNS records, domains and projects, moving work that previously required the web dashboard or the REST API into the terminal. According to the Vercel blog, the new commands can be used interactively, embedded in scripts, or driven by automated agents, and they ship in version 59.6.2 of the CLI.

DNS records from the terminal

The CLI can now retrieve the complete configuration of a DNS record and modify it in place using its record ID. Running vercel dns inspect on a record prints its full details, while vercel dns update accepts changes to the record name, type, value, TTL, MX priority and comment. SRV records are handled too, with their priority, weight, port and target fields available for update. The example in Vercel's announcement shows a record being repointed to the IP 76.76.21.21 with a TTL of 300 seconds in a single command.

Domain renewals on demand

Domains bought through Vercel can now be renewed directly from the CLI, and automatic renewal can be toggled per domain. Vercel notes that the renewal command displays the current renewal price and asks for confirmation before completing the purchase, making the cost visible before anything is charged.

Project state, observability and members

A group of project commands rounds out the release. Projects can be paused and resumed, and observability features can be enabled or disabled from the command line. Web Analytics and Speed Insights could already be switched on via the CLI; according to Vercel, they can now be turned off as well, closing a gap that previously sent users back to the dashboard.

Project membership is scriptable too. A new members command adds a user to a project with a specific role, such as developer, and a counterpart command removes an existing member.

Designed for scripts and agents

Two design choices stand out in the announcement. First, all of the new commands support structured JSON output, so the CLI can act as a data source for automation rather than only as an interactive tool. Second, any billable or destructive action requires explicit confirmation before it runs, which keeps automated workflows from quietly spending money or deleting configuration.

Vercel positions the agent use case explicitly, suggesting the terminal as an interface that automated tooling can operate on a user's behalf. Users need version 59.6.2 or later of the Vercel CLI to get the new commands, and Vercel points to its CLI documentation for the full reference.

Why it matters

Most platform CLIs cover deployment well but leave routine account administration — DNS edits, domain renewals, project membership — stuck behind a web interface. That forces operators and CI pipelines into brittle workarounds: manual browser steps or custom code against the REST API. By bringing these operations into the CLI with machine-readable output, Vercel makes them composable in shell scripts and pipeline definitions without anyone writing an API client.

The structured-output focus also reflects where developer tooling is heading. As agents increasingly operate infrastructure on behalf of users, CLIs with predictable JSON responses become the natural interface layer, and confirmation gates on billable or destructive actions are a sensible safeguard for exactly that scenario. For teams already standardised on Vercel, the practical effect is simpler: fewer context switches to the dashboard, and more of the platform under version-controlled, scriptable management.