vercel-cli
Command-line interface for deploying, managing, and developing Vercel projects locally and in CI/CD pipelines.
- Requires explicit project linking via
vercel link(single project) orvercel link --repo(monorepos); commands must run from the directory containing.vercel/folder - Core workflows:
vercel devfor local development,vercel deployfor preview deployments,vercel --prodfor production - Supports environment variables, domains, DNS, blob storage, integrations, Node.js backends, monorepos, Bun runtime, and feature flags through dedicated command categories
- Includes
vercel apias a fallback for operations without direct CLI commands, andvercel curlfor accessing preview deployments without disabling protection
Vercel CLI Skill
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.
Critical: Project Linking
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 byvercel 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 byvercel 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.
Quick Start
npm i -g vercel