Vercel's CLI Now Touches DNS, but Refuses to Act Alone

Vercel CLI 59.6.2 adds dedicated commands for editing DNS records, renewing domains and pausing projects, moving work that used to require the dashboard or API into the terminal (Vercel changelog, August 28, 2026). The commands are built for scripts and agents, but Vercel drew a hard line around anything billable or destructive: run one interactively and it prompts for confirmation; run it without a TTY, and it refuses.

---

What changed

The new surface covers three areas. vercel dns inspect and vercel dns update retrieve and edit a DNS record by its record ID, covering name, type, value, TTL, MX priority and comment fields, with SRV records also editable by priority, weight, port and target (Vercel changelog, August 28, 2026). vercel domains renew renews a domain on demand or toggles auto-renewal, showing the current renewal price and asking for confirmation before it completes a purchase; vercel domains verify checks whether a domain is correctly configured, attached to the right project and verified, and returns the exact fix if it isn’t (Vercel changelog, August 28, 2026). On the project side, vercel project pause and resume now sit alongside CLI control over observability: Web Analytics and Speed Insights could already be enabled from the terminal, and can now be disabled the same way. All of it emits structured JSON, so scripts and agent tool-calls can parse the output instead of scraping dashboard text.

The commands build on an earlier round that shipped a week prior, when vercel dns first got interactive record verification (Vercel changelog, August 21, 2026). Together the two updates round out DNS and domain management as a first-class CLI surface rather than a dashboard-only workflow.

vercel dns update has no --yes flag. Run it interactively and it prompts for confirmation; run it without a TTY (a non-interactive shell or an agent context), and it declines to act rather than silently applying the change.

Our take

CLIs that manage DNS are not new, but most treat a record edit the same as any other write: pass the right flags and it happens, no questions asked. Vercel instead built confirmation into the command itself for anything that touches a zone’s DNS or costs money on renewal, and made the refusal automatic the moment a human isn’t there to answer the prompt. That’s a deliberate response to the actual risk in this category: an agent or CI script running unattended is exactly the context where a wrong DNS write does the most damage, because nobody catches it before it propagates.

It also reads as an admission about who’s driving these commands lately. Vercel’s own changelog copy lists “interactively, in scripts, or by agents” as the three ways these commands get called, putting agent tool-calls on equal footing with a developer typing into a terminal. Building the refuse-without-confirmation behavior in now, rather than after an agent nukes an MX record, is the platform doing the safety work up front instead of writing a postmortem later.

Key Takeaways

• Vercel CLI 59.6.2+ adds vercel dns inspect/update, vercel domains renew/verify, and vercel project pause/resume, plus CLI toggles to disable Web Analytics and Speed Insights.
• dns update supports name, type, value, TTL, MX priority and comment fields, with SRV records editable by priority, weight, port and target.
• Interactive runs require a confirmation prompt for DNS and billable changes; non-interactive or agent contexts without a TTY refuse to act rather than proceeding unattended.
• All commands emit structured JSON, aimed at scripts and agent tool-calls rather than just dashboard replacement.