Vercel expands commands in Vercel CLI 59.6.2 for inspecting and updating DNS records, renewing domains, pausing projects, controlling observability, and managing project members. Released August 28, 2026, the update moves dashboard and API operations into terminals, scripts, and AI-agent workflows while retaining confirmation gates for billable or destructive actions.
The release is more than a longer command list. Every new operation supports structured JSON output, giving developers and agents machine-readable results instead of forcing them to parse terminal prose. Vercel still requires explicit confirmation when an action can create a charge or remove resources, so automation does not silently erase the platform’s safety boundary.
Which Vercel CLI commands are new?
The official Vercel changelog groups the release into four areas: DNS, domains, project controls, and membership. The minimum supported release is Vercel CLI 59.6.2.
How do the new Vercel DNS commands work?
Vercel now lets an operator retrieve a DNS record by ID and update that same record without deleting and recreating it. vercel dns inspect rec_123 returns the complete record configuration, while vercel dns update rec_123 --value 76.76.21.21 --ttl 300 changes selected fields in place. The update command supports the record name, type, value, TTL, MX priority, and comment. For SRV records, it also accepts priority, weight, port, and target fields. This record-ID workflow is valuable in scripts because it gives the automation a stable object to inspect before applying a change. A careful production sequence is to inspect the record in JSON, validate the current type and value, apply only the required fields, and inspect it again. That reduces the chance of replacing an unrelated DNS entry or losing configuration that was not included in the update request.
bash
vercel dns inspect rec_123 –format json
vercel dns update rec_123
–value 76.76.21.21
–ttl 300
The Vercel DNS command reference also covers listing, adding, removing, and importing records. The new inspect and richer update path closes the gap between basic record management and configuration-aware automation.
How does domain renewal work from the terminal?
The new domain commands apply to domains bought through Vercel. vercel domains renew example.com starts an on-demand renewal, displays the current renewal price and term, and asks for confirmation before completing the purchase. Separate auto-renew commands let an operator turn future renewals on or off without opening the dashboard. This distinction matters for automation: JSON output can make the result machine-readable, but it does not remove the required acknowledgement for a billable operation. A script or agent should first inspect the targeted domain, confirm the account scope, record the displayed renewal terms, and proceed only under an approved policy. Teams should also avoid treating auto-renew off as an immediate cancellation; the command changes renewal behavior rather than deleting the domain. Vercel’s documentation does not announce a new price model in this release, so renewal cost remains domain-specific and should be read from the command output.
bash
vercel domains renew example.com
vercel domains auto-renew example.com on
vercel domains auto-renew example.com off
What project controls can developers automate?
Vercel CLI can now pause or resume a project and configure several observability features from the terminal. Web Analytics and Speed Insights could already be enabled through the CLI; version 59.6.2 adds the corresponding disable operations. The release also provides direct enable and disable commands for project observability.
bash
vercel project pause
vercel project resume
vercel project observability enable
vercel project observability disable
vercel project web-analytics disable
vercel project speed-insights disable
These controls are useful for repeatable operating procedures. A team can encode project-state changes and telemetry settings in reviewed scripts instead of relying on manual dashboard navigation. This is also where Vercel’s broader agent strategy becomes visible. BriefFlash previously covered its official Cursor harness adapter, while Vercel Connect for v0 gives generated apps access to external services. Machine-readable project administration adds another layer: agents can now observe a resource, act through a defined command, and evaluate the structured result.
How are project members added or removed?
The membership commands accept a project and a user identified by email address or username. An administrator can assign a specific role when adding the member, while removal targets an existing member. Vercel’s example uses the developer role.
bash
vercel project members add my-project user@example.com
–role developer
vercel project members remove my-project user@example.com
These commands reduce friction in onboarding and offboarding scripts, but they also change access. Teams should resolve the intended project scope and user identity before execution, capture the JSON response for an audit trail, and keep human approval around removal. That pattern mirrors the need for governed agent tool access described in BriefFlash’s coverage of agentic observability controls.
Why does JSON output matter for scripts and agents?
Human-formatted terminal output can change spacing, colors, or labels, making text scraping brittle. Structured JSON gives software explicit fields that can be validated, logged, compared, and passed to another tool. For example, an agent can inspect a DNS record, compare its current value with an approved target, request confirmation, update the record, and verify the final state.
The safety boundary remains important. Vercel says billable or destructive actions require explicit confirmation. JSON is therefore an interface for reliable automation, not permission to make irreversible choices. Production agents still need least-privilege credentials, an allowlist of projects and domains, dry-run or inspection steps where available, and clear escalation rules when the observed state differs from the plan.
How do you install or update Vercel CLI 59.6.2?
Vercel’s published update command is:
bash
npm i -g vercel@latest
The same npm-based installation covers Vercel downloads for Windows, macOS, and Linux when Node.js and npm are available. The Vercel CLI Overview(https://vercel.com/docs/cli)(https://vercel.com/docs/cli) says the installed vercel and vc launchers run the native binary matching the operating system and CPU architecture, including x64 and arm64. After installation, check the result with vercel --version and confirm that it is 59.6.2 or later.
A common search query, “Vercel install command,” can cause confusion. npm i -g vercel@latest installs or updates the CLI itself. The separate vercel install command installs Marketplace native integrations and provisions their resources; it is not the CLI installer.
If the terminal reports vercel: command not found, reopen the shell after installation and verify that npm’s global executable directory is included in the system PATH. Also confirm that the global installation completed successfully. The problem is usually command discovery, not an absent Windows or Mac edition.
What should teams check before using the new commands?
- Upgrade to Vercel CLI 59.6.2 or later and confirm the active account and team scope.
- Inspect DNS and domain state before changing it, preferably with structured JSON output.
- Treat renewals as billable operations and member removal as an access-control change.
- Log the requested action, confirmation, command result, and post-change verification.
- Keep credentials narrowly scoped when commands are exposed to scripts or agents.
Vercel expands commands at a useful administrative layer: the terminal can now cover more of the resource lifecycle, while JSON makes the results easier for software to consume. The release’s practical value will depend on teams pairing that new reach with identity checks, approval policies, and verification after every sensitive change.
Key Takeaways
- Vercel CLI 59.6.2 adds dedicated DNS inspection and update commands, including MX and SRV record fields.
- Vercel-bought domains can be renewed on demand or switched between automatic and manual renewal from the terminal.
- Projects can be paused or resumed, observability features can be controlled, and members can be added or removed with defined roles.
- All new commands support structured JSON output, while billable or destructive actions still require explicit confirmation.
FAQ
How do I install the latest Vercel CLI?
Run npm i -g vercel@latest, then use vercel --version to confirm version 59.6.2 or later. The CLI supports macOS, Linux, and Windows across x64 and arm64 architectures.
Why is the Vercel command not found after installation?
First confirm that the global npm installation completed, reopen the terminal, and check whether npm’s global executable directory is included in your system PATH. The vercel and vc launchers should become available once the installed binary can be discovered by the shell.
What is the difference between installing Vercel CLI and vercel install?
npm i -g vercel@latest installs or updates Vercel CLI. The vercel install subcommand has a different purpose: it installs Vercel Marketplace native integrations and provisions their resources.
