// Vercel CLI expert guidance. Use when deploying, managing environment variables, linking projects, viewing logs, querying metrics, managing domains, or interacting with the Vercel platform from the command line.
Vercel Firewall expert guidance — automatic DDoS mitigation, the Vercel WAF (custom rules, IP blocking, managed rulesets, rate limiting), Attack Mode, system bypass, bot management, and the `vercel firewall` CLI. Use when configuring platform-level security, responding to attacks, or staging firewall rules.
Deploy, manage, and develop projects on Vercel from the command line
Vercel Workflow DevKit (WDK) expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause/resume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.
Vercel AI Gateway expert guidance. Use when configuring model routing, provider failover, cost tracking, or managing multiple AI providers through a unified API.
Corrects outdated LLM knowledge about the Vercel platform and introduces new products. Injected at session start.
next-forge expert guidance — production-grade Turborepo monorepo SaaS starter by Vercel. Use when working in a next-forge project, scaffolding with `npx next-forge init`, or editing @repo/* workspace packages.
| name | vercel-cli |
| description | Vercel CLI expert guidance. Use when deploying, managing environment variables, linking projects, viewing logs, querying metrics, managing domains, or interacting with the Vercel platform from the command line. |
| metadata | {"priority":4,"docs":["https://vercel.com/docs/cli"],"sitemap":"https://vercel.com/sitemap/docs.xml","pathPatterns":["vercel.json","vercel.ts",".vercel/**",".vercelignore","now.json"],"bashPatterns":["^\\s*vercel(?:\\s|$)","^\\s*vc(?:\\s|$)","\\bnpx\\s+vercel\\b","\\bpnpm\\s+dlx\\s+vercel\\b","\\bbunx\\s+vercel\\b","\\byarn\\s+dlx\\s+vercel\\b","\\bnpx\\s+@vercel/config\\b"],"promptSignals":{"phrases":["check deployment","check deploy","deployment status","deploy status","vercel logs","vercel metrics","deployment logs","deploy logs","vercel inspect","is it deployed","deploy failing","deploy failed","deployment error","check vercel","vercel status"],"allOf":[["check","deployment"],["check","deploy"],["vercel","status"],["vercel","logs"],["vercel","metrics"],["deploy","error"],["deploy","failed"],["deploy","stuck"]],"anyOf":["deployment","deploy","vercel","production"],"noneOf":["terraform","aws deploy","heroku"],"minScore":6}} |
| retrieval | {"aliases":["vercel command line","vc cli","deploy command","vercel terminal"],"intents":["deploy from cli","link project","manage domains","view logs from terminal"],"entities":["vercel CLI","vercel deploy","vercel env","vercel link","vercel logs","vercel metrics"]} |
| chainTo | [{"pattern":"\"functions\"\\s*:\\s*\\{|\"maxDuration\"\\s*:|\"memory\"\\s*:","targetSkill":"vercel-functions","message":"Functions configuration detected in vercel.json — loading Vercel Functions guidance for runtime options, streaming, and Fluid Compute.","skipIfFileContains":"\"crons\"\\s*:"},{"pattern":"\"redirects\"\\s*:\\s*\\[|\"rewrites\"\\s*:\\s*\\[|\"headers\"\\s*:\\s*\\[","targetSkill":"routing-middleware","message":"Routing rules in vercel.json — loading Routing Middleware guidance for platform-level request interception patterns."}] |
The Vercel CLI (vercel or vc) deploys, manages, and develops projects on the Vercel platform from the command line. Use vercel <command> -h for full flag details on any command.
Commands must be run from the directory containing the .vercel folder (or a subdirectory of it). How .vercel gets set up depends on your project structure:
.vercel/project.json: Created by vercel link. Links a single project. Fine for single-project repos, and can work in monorepos if there's only one project..vercel/repo.json: Created by vercel link --repo. Links a repo that may contain multiple projects. Always a good idea when any project has a non-root directory (e.g., apps/web).Running from a project subdirectory (e.g., apps/web/) skips the "which project?" prompt since it's unambiguous.
When something goes wrong, check how things are linked first — look at what's in .vercel/ and whether it's project.json or repo.json. Also verify you're on the right team with vercel whoami — linking while on the wrong team is a common mistake.
npm i -g vercel
vercel login
vercel link # single project
# OR
vercel link --repo # monorepo
vercel pull
vercel dev # local development
vercel deploy # preview deployment
vercel --prod # production deployment
Use this to route to the correct reference file:
references/deployment.mdreferences/local-development.mdreferences/environment-variables.mdreferences/ci-automation.mdreferences/domains-and-dns.mdreferences/projects-and-teams.mdreferences/monitoring-and-debugging.mdreferences/storage.mdreferences/integrations.mdvercel curl (see references/monitoring-and-debugging.md)vercel api as a fallback (see references/advanced.md)references/node-backends.mdreferences/monorepos.mdreferences/bun.mdreferences/flags.mdreferences/advanced.mdreferences/global-options.mdreferences/getting-started.mdvercel link creates project.json, which only tracks one project. Use vercel link --repo instead. When things break, check .vercel/ first.vercel link if .vercel/ doesn't exist. This creates project.json, which may be wrong. Run vercel link (or --repo) explicitly first.vercel whoami to check, vercel teams switch to change.--yes in CI: Required to skip interactive prompts.vercel deploy after vercel build without --prebuilt: The build output is ignored.VERCEL_TOKEN env var instead of --token.vercel curl instead to access preview deploys.