Vercel CLI expands support for DNS, domains, and project commands

The Vercel CLI now provides dedicated commands for managing DNS records, domains, and projects. This brings more of the functionality available through the Vercel dashboard and API to the terminal, where it can be used interactively, in scripts, or by agents.
Copy link to headingInspect and update DNS records
Retrieve the complete configuration for a DNS record or update it in place using its record ID.
vercel dns update
supports changes to the record name, type, value, TTL, MX priority, and comment. SRV records can also be updated using their priority, weight, port, and target fields.
Copy link to headingRenew domains bought on Vercel
Renew a domain on demand or control whether it renews automatically.
The renewal command displays the current renewal price and asks for confirmation before completing the purchase.
Copy link to headingControl project state and observability
Pause or resume a project and configure its observability features directly from the CLI. Web Analytics and Speed Insights could already be enabled from the CLI; they can now be disabled as well.
Copy link to headingAdd and remove project members
Add a project member with a specific role or remove an existing member.
All of the new commands support structured JSON output for scripts and agents. Billable or destructive actions require explicit confirmation.
Update to the latest version of the Vercel CLI to get started:
npm i -g vercel@latest
Learn more in the Vercel CLI documentation.

Facts Only

* The Vercel CLI offers dedicated commands for managing DNS records, domains, and projects.
* Commands exist to retrieve and update DNS records using record IDs.
* The `vercel dns update` command supports changes to record name, type, value, TTL, MX priority, and comment.
* SRV records can be updated via their priority, weight, port, and target fields.
* A command exists for renewing domains on demand or setting automatic renewal.
* The renewal command displays the current price and requires confirmation before purchase.
* The CLI allows pausing or resuming projects.
* Observability features like Web Analytics and Speed Insights can be enabled or disabled via the CLI.
* Commands support structured JSON output for scripting and agents.

Executive Summary

The Vercel CLI has introduced dedicated commands for managing DNS records, domains, and projects. These features extend the functionality previously available in the Vercel dashboard and API to the terminal for interactive use, scripting, or agent operations. Specific commands allow users to inspect and update DNS records by retrieving configurations or updating them in place using record IDs, supporting changes to various record fields like name, type, value, TTL, and MX priority. There are also commands to manage domain renewals on demand, which display pricing and require confirmation for purchase. Furthermore, the CLI provides controls for project state, allowing users to pause or resume projects, and configuring observability features such as Web Analytics and Speed Insights. Project members can be added or removed, and all new commands output structured JSON suitable for automation.

Full Take

The introduction of comprehensive CLI functionality shifts domain management from a GUI-centric interaction to an automated, scriptable paradigm. This move emphasizes efficiency for power users and automation workflows by bringing granular control over core infrastructure functions directly into the terminal. The ability to manage DNS records, handle domain lifecycle events like renewal, and control project observability via command-line interfaces suggests a design philosophy prioritizing programmatic control and speed over ad-hoc dashboard navigation. The structured JSON output reinforces this direction, positioning the CLI as an agentic interface capable of integrating deeply into CI/CD pipelines or autonomous agents managing infrastructure. This capability creates a potential friction point: while granting immense power for efficiency, it necessitates a higher degree of technical proficiency to avoid unintended consequences, raising questions about the systemic risk when operational control is fully delegated to command-line operations without the contextual safeguards inherent in a visual dashboard environment. The pattern observed is an acceleration toward API-first management, which centralizes potential control and responsibility, thereby demanding stronger protocols for explicit user confirmation on destructive or high-impact actions.