Sign InOpen Brain
VercelEngineering PostOfficial Source

Vercel CLI expands commands for DNS, domains, and projects

Vercel CLI 59.6.2 adds agent-friendly control over DNS, domains, projects, observability, and membership, with JSON output and confirmation gates for risky actions.

Vercel · Aug 28, 2026
Open Source Open MarkdownOpen JSON
Source Summary

**Vercel CLI 59.6.2 or later** adds commands for DNS record updates, domain renewal, project pause and resume, observability settings, and project membership. Every new command supports **structured JSON output**.

Practical Implication

Coding agents can now handle more Vercel administration without dashboard automation. Use the JSON surfaces for parsing, while retaining the built-in confirmation boundary around **billable or destructive actions**.

Agent-Ready Context
**Vercel CLI 59.6.2 or later** adds commands for DNS record updates, domain renewal, project pause and resume, observability settings, and project membership. Every new command supports **structured JSON output**.

Coding agents can now handle more Vercel administration without dashboard automation. Use the JSON surfaces for parsing, while retaining the built-in confirmation boundary around **billable or destructive actions**.

Terminal access increases the impact of an over-broad agent instruction. Scope credentials and permissions carefully, and do not treat confirmation prompts as a substitute for reviewing the intended target and change.
Connected Context · Feed7 Judgment

This materially widens the infrastructure state that coding agents can inspect and change through parseable CLI interfaces. It reduces dashboard dependence, but the added DNS, billing-adjacent, membership, and project-state controls raise the importance of scoped credentials, target validation, dry runs where available, observability, and explicit human approval.

Vercel CLI expands support for DNS, domains, and project commandsThis directly reinforces that the expanded structured command surface is intended for supervised automation because billable and destructive operations retain confirmation gates.Dry-run deployments with Vercel CLIDeployment dry runs provide a complementary preflight pattern: agents can inspect structured intended effects before mutation, a safeguard not supplied for every newly added administrative command.Agent Runs now available in the Vercel MCP and CLIAgent Runs traces complement the new mutation surface by exposing tool calls and usage for post-run inspection, improving accountability for agent-operated infrastructure.How Factory scaled its cloud backend to tens of millions of daily requests on VercelFactory’s agent-operated deployment case reinforces the implementation consequence of broader CLI control: programmable production changes need scoped authority, validation, observability, and review.
Context Map
infracoding#tool-use#dev-ux#observability
Uncertainty
Terminal access increases the impact of an over-broad agent instruction. Scope credentials and permissions carefully, and do not treat confirmation prompts as a substitute for reviewing the intended target and change.