Vercel CLI with Tokens

Deploy and manage projects on Vercel using the CLI with token-based authentication, without relying on

vercel login

Step 1: Locate the Vercel Token

Before running any Vercel CLI commands, identify where the token is coming from. Work through these scenarios in order:

A)

VERCEL_TOKEN

is already set in the environment

printenv VERCEL_TOKEN

If this returns a value, you're ready. Skip to Step 2.

B) Token is in a

.env

file under

VERCEL_TOKEN

grep '^VERCEL_TOKEN=' .env 2>/dev/null

If found, export it:

export VERCEL_TOKEN=$(grep '^VERCEL_TOKEN=' .env | cut -d= -f2-)

C) Token is in a

.env

file under a different name

Look for any variable that looks like a Vercel token (Vercel tokens typically start with

vca_

grep -i 'vercel' .env 2>/dev/null

Inspect the output to identify which variable holds the token, then export it as

VERCEL_TOKEN

export VERCEL_TOKEN=$(grep '^<VARIABLE_NAME>=' .env | cut -d= -f2-)

D) No token found — ask the user

If none of the above yield a token, ask the user to provide one. They can create a Vercel access token at vercel.com/account/tokens.

Important: Once

VERCEL_TOKEN

--token

# Bad — token visible in shell history and process listings
vercel deploy --token "vca_abc123"

# Good — CLI reads VERCEL_TOKEN from the environment
export VERCEL_TOKEN="vca_abc123"
vercel deploy

Step 2: Locate the Project and Team

Similarly, check for the project ID and team scope. These let the CLI target the right project without needing

vercel link

# Check environment
printenv VERCEL_PROJECT_ID
printenv VERCEL_ORG_ID

# Or check .env
grep -i 'vercel' .env 2>/dev/null

If you have a project URL (e.g.

https://vercel.com/my-team/my-project

# e.g. "my-team" from "https://vercel.com/my-team/my-project"
echo "$PROJECT_URL" | sed 's|https://vercel.com/||' | cut -d/ -f1

If you have both

VERCEL_ORG_ID

VERCEL_PROJECT_ID

.vercel/

export VERCEL_ORG_ID="<org-id>"
export VERCEL_PROJECT_ID="<project-id>"

Note:

VERCEL_ORG_ID

VERCEL_PROJECT_ID

CLI Setup

Ensure the Vercel CLI is installed:

npm install -g vercel
vercel --version

Deploying a Project

Always deploy as preview unless the user explicitly requests production. Choose a method based on what you have available.

Quick Deploy (have project ID — no linking needed)

When

VERCEL_TOKEN

VERCEL_PROJECT_ID

vercel deploy -y --no-wait

With a team scope (either via

VERCEL_ORG_ID

--scope

vercel deploy --scope <team-slug> -y --no-wait

Production (only when explicitly requested):

vercel deploy --prod --scope <team-slug> -y --no-wait

Check status:

vercel inspect <deployment-url>

Full Deploy Flow (no project ID — need to link)

Use this when you have a token and team but no pre-existing project ID.

Check project state first

# Does the project have a git remote?
git remote get-url origin 2>/dev/null

# Is it already linked to a Vercel project?
cat .vercel/project.json 2>/dev/null || cat .vercel/repo.json 2>/dev/null

Link the project

With git remote (preferred):

vercel link --repo --scope <team-slug> -y

Reads the git remote and connects to the matching Vercel project. Creates

.vercel/repo.json

vercel link

Without git remote:

vercel link --scope <team-slug> -y

Creates

.vercel/project.json

Link to a specific project by name:

vercel link --project <project-name> --scope <team-slug> -y

If the project is already linked, check

orgId

.vercel/project.json

.vercel/repo.json

Deploy after linking

A) Git Push Deploy — has git remote (preferred)

Git pushes trigger automatic Vercel deployments.

1. Ask the user before pushing. Never push without explicit approval.
2. Commit and push:

   git add .
   git commit -m "deploy: <description of changes>"
   git push
   

3. Vercel builds automatically. Non-production branches get preview deployments.
4. Retrieve the deployment URL:

   sleep 5
   vercel ls --format json --scope <team-slug>
   

   Find the latest entry in the

   deployments

   array.

B) CLI Deploy — no git remote

vercel deploy --scope <team-slug> -y --no-wait

Check status:

vercel inspect <deployment-url>

Deploying from a Remote Repository (code not cloned locally)

1. Clone the repository:

   git clone <repo-url>
   cd <repo-name>
   

2. Link to Vercel:

   vercel link --repo --scope <team-slug> -y
   

3. Deploy via git push (if you have push access) or CLI deploy.

About

.vercel/

Directory

A linked project has either:

• .vercel/project.json

  — from

  vercel link

  . Contains

  projectId

  and

  orgId

  .

• .vercel/repo.json

  — from

  vercel link --repo

  . Contains

  orgId

  ,

  remoteName

  , and a

  projects

  map.

Not needed when

VERCEL_ORG_ID

VERCEL_PROJECT_ID

Do NOT run

vercel ls

vercel project inspect

vercel link

vercel whoami

Managing Environment Variables

# Set for all environments
echo "value" | vercel env add VAR_NAME --scope <team-slug>

# Set for a specific environment (production, preview, development)
echo "value" | vercel env add VAR_NAME production --scope <team-slug>

# List environment variables
vercel env ls --scope <team-slug>

# Pull env vars to local .env file
vercel env pull --scope <team-slug>

# Remove a variable
vercel env rm VAR_NAME --scope <team-slug> -y

Inspecting Deployments

# List recent deployments
vercel ls --format json --scope <team-slug>

# Inspect a specific deployment
vercel inspect <deployment-url>

# View build logs
vercel logs <deployment-url>

Managing Domains

# List domains
vercel domains ls --scope <team-slug>

# Add a domain to the project
vercel domains add <domain> --scope <team-slug>

Working Agreement

• Never pass

  VERCEL_TOKEN

  as a

  --token

  flag. Export it as an environment variable and let the CLI read it natively.
• Check the environment for tokens before asking the user. Look in the current env and

  .env

  files first.
• Default to preview deployments. Only deploy to production when explicitly asked.
• Ask before pushing to git. Never push commits without the user's approval.
• Do not read or modify

  .vercel/

  files directly. The CLI manages this directory.
• Do not curl/fetch deployed URLs to verify. Just return the link to the user.
• Use

  --format json

  when structured output will help with follow-up steps.
• Use

  -y

  on commands that prompt for confirmation to avoid interactive blocking.

Troubleshooting

Token not found

Check the environment and any

.env

printenv | grep -i vercel
grep -i vercel .env 2>/dev/null

Authentication error

If the CLI fails with

Authentication required

• The token may be expired or invalid.
• Verify:

  vercel whoami

  (uses

  VERCEL_TOKEN

  from environment).
• Ask the user for a fresh token.

Wrong team

Verify the scope is correct:

vercel whoami --scope <team-slug>

Build failure

Check the build logs:

vercel logs <deployment-url>

Common causes:

• Missing dependencies — ensure

  package.json

  is complete and committed.
• Missing environment variables — add with

  vercel env add

  .
• Framework misconfiguration — check

  vercel.json

  . Vercel auto-detects frameworks (Next.js, Remix, Vite, etc.) from

  package.json

  ; override with

  vercel.json

  if detection is wrong.

CLI not installed

npm install -g vercel