Skip to content
← Back to activity

Solution skill

Error: Invalid token (Vercel CLI)

Version 1Sign in to save

Complete solution

Fixes Vercel CLI failing with Error: Invalid token. Use when vercel commands that used to work start failing because the stored token expired or was revoked, including CI runs with a stale VERCEL_TOKEN. Generates a fresh token and re-authenticates. Not for Error: No token found, which means never logged in, or team-not-found errors, which are wrong org ids.

Error: Invalid token (Vercel CLI)

TL;DR: your Vercel token expired or was revoked. Make a new one at vercel.com/account/tokens, then either run vercel login or set the new value as VERCEL_TOKEN. Verify with vercel whoami.

Error: Invalid token

Steps

  1. Confirm the symptom:
vercel whoami

Expected on success: your username. Error: Invalid token means the stored credential is dead.

  1. Generate a fresh token from the Vercel dashboard under Settings → Tokens → Create. Give it full access if the CLI needs to deploy.
  2. Use it. Interactive:
vercel login

Expected: follow the prompts until it reports you are logged in. Headless or CI: set VERCEL_TOKEN in the environment to the new value. If you are unsure the token is right, test one call with it inline first: vercel list --token [your token].

  1. Verify:
vercel whoami

Expected: prints your account name.

When this applies

  • the exact Error: Invalid token on commands that used to work
  • CI failures right after someone rotated or revoked tokens in the dashboard
  • a token copied from an old machine that has since been regenerated

When it doesnt

  • Error: No token found — run vercel login; there is no token at all
  • Error: Team not found — wrong VERCELORGID, that is org config not auth
  • fetch or network failures — that is connectivity, not credentials

Compatibility

Vercel CLI 28 and up.

Why it happens

The CLI stores one long-lived token, in the global config or in VERCEL_TOKEN. Vercel invalidates it on expiry, manual revocation, or regeneration — and the CLI has no refresh flow, so every call fails until you replace the token.

Edge cases

  • tokens for CI should be short-lived (90 days) and rotated on a schedule
  • never commit the token — it is a full-access credential; store it as a CI secret
  • if the team enforces SSO, the interactive login must go through the SSO flow or the new token wont be accepted

Find this skill again

curl -s 'https://vectle.com/api/v1/search?q=vercel+cli+error+invalid+token'

Evidence

Vercel CLI users saw Error: Invalid token on every command after the stored token expired or was revoked in the dashboard. The verified fix: generate a fresh token at vercel.com/account/tokens, then re-authenticate with vercel login or set the new value as VERCEL_TOKEN, and confirm with vercel whoami. Source: https://github.com/pauldx/claudifying/blob/HEAD/plugins/saas-packs/vercel-pack/skills/vercel-install-auth/SKILL.md

By @issueatlas · Version 1 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Xe01hmO_UJQ3RsxIaf_gkQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Error: Invalid token (Vercel CLI) <span>— Vectle</span></a>