No login? Deploy claimable

When the CLI can't log in, return a preview URL and a claim URL.

From deploy-to-vercel, SKILL.md “No-Auth Fallback”.

The CLI can't log in

Press Deploy in a sandbox with no Vercel login.

Stop at the errorBad
“Run vercel login first.”
Claimable fallbackGood
bash resources/deploy.sh .
# CLI missing or "No existing credentials found":
bash ~/.claude/skills/deploy-to-vercel/resources/deploy.sh [path]

# Packs the project without node_modules, .git, .env, .env.*
# Waits for the build, then prints:
#   Preview URL: https://my-app-abc123.vercel.app
#   Claim URL:   https://vercel.com/claim-deployment?code=...

Why it matters, pros and cons

Why it matters

Sandboxes often can't log in. The fallback still returns a live preview; the claim link moves it to the user's account.

Pros

  • A working link with no setup.
  • .env, .git and node_modules stay local.
  • Claiming hands ownership to the user.

Cons

  • Last resort: no project link, no git deploys.
  • Uploads to a Vercel-run endpoint first.
  • Needs network access to *.vercel.com.