agent-vercel

Vercel CLI for AI agents

Language
Go
Version
0.1.2
License
PolyForm Perimeter 1.0.0
Category
CLI Tool
View on GitHub

A Vercel CLI for AI agents that triages and carefully acts on Vercel through compact, structured output. It is read-default and cross-project: inspect deployments, build and runtime logs, what is live in production, env-var diffs across environments, domains, DNS, certs, aliases, and billing — without exposing the Vercel token to the agent.

Features

01

LLM-shaped output — lists default to NDJSON, single resources to JSON, and errors include fixable_by plus hints

02

Read-default triage — deployments, builds, logs, runtime logs, projects, env, domains, DNS, certs, aliases, and billing

03

Cross-project and history-aware — answers questions the deploy-loop vercel CLI cannot, straight from the Vercel REST API

04

Credential vs scope model — one Keychain-stored token reaches many teams; --auth picks the secret, --scope picks the team

05

Keychain-first credentials — the access token is stored securely and there is no command to read it back out

06

Env diffing — compare environment variables across production and preview without printing secret values

07

Mutation safety — promote, rollback, cancel, redeploy, env writes, and domain/alias changes require --yes

08

Raw API escape hatch — call any Vercel REST endpoint when a dedicated command does not exist yet

09

Mock Vercel fixture — HTTP logic is dependency-injected and tested without touching the real API

Install

Homebrew

>_ 
$ brew install shhac/tap/agent-vercel

AI Agent Skill

>_ 
$ npx skills add shhac/agent-skills --skill agent-vercel --global

GitHub Release (macOS)

>_ 
$ curl -L https://github.com/shhac/agent-vercel/releases/latest/download/agent-vercel-darwin-arm64.tar.gz | tar xz

Go Install

>_ 
$ go install github.com/shhac/agent-vercel/cmd/agent-vercel@latest

Build from Source

>_ 
$ git clone https://github.com/shhac/agent-vercel.git && cd agent-vercel && make build

Getting Started

agent-vercel needs a Vercel access token before it can triage deployments or account state. Tokens live in the OS keychain, and one credential can reach many teams via scopes.

01 · Add a Vercel token

>_ 
$ agent-vercel auth add personal

Create a token at vercel.com/account/tokens and store it in the Keychain. The token is never printed back and there is no command to read it out.

02 · Verify the credential

>_ 
$ agent-vercel auth test

Checks the stored token against GET /v2/user without printing the secret.

03 · Pick a team to act on

>_ 
$ agent-vercel scope set-default acme

Lists the teams the credential can reach and sets a default scope; override per call with --scope.

04 · See what is live in production

>_ 
$ agent-vercel deployment current --prod

Reads the current production deployment, including rolling releases, as JSON.

Usage

>_ List recent deployments across projects 
$ agent-vercel deployment list --limit 20
>_ See what is live in production 
$ agent-vercel deployment current --prod
>_ Fetch a failed build's logs 
$ agent-vercel deployment logs dpl_... --limit 100
>_ Diff env vars between environments 
$ agent-vercel env diff --project web production preview
>_ Inspect a domain's DNS records 
$ agent-vercel domain records example.com
>_ Repoint an alias to a deployment 
$ agent-vercel alias set staging.example.com dpl_... --yes
>_ Use the raw API escape hatch 
$ agent-vercel api call GET /v2/user