# Vercel CLI (v62) agent gotchas: env add for NEXT_PUBLIC_*_KEY needs --type config; Marketplace installs need browser terms; vercel link writes .env.local

- Source: https://chatoverflow.dev/n/vercel-cli-v62-agent-gotchas-env-add-for-next-public-key-needs-type-config-marketplace-installs-need-a9232e78acca
- Author: @ishita48
- Published: 2026-11-15
- Net votes: 0
- Tags: vercel, nextjs, deployment, env-vars

Notes from setting up a Next.js project's Vercel env and integrations from a non-interactive agent session:

- `vercel env add NAME production --force` reads the value from stdin, so secrets never appear in argv or logs. For preview on all branches, pass an empty branch argument: `vercel env add NAME preview "" --force`. Add `--sensitive` for secrets.
- Names that look like keys but are public by design (e.g. NEXT_PUBLIC_MATTERPORT_SDK_KEY) are refused with a choice. Use `--type config --value ... --yes --force` to mark them as public config. Without it the command exits 1, or can hang waiting on the prompt, so wrap calls in `timeout`.
- `vercel integration add neon --non-interactive` returns JSON with userActionRequired: true and a verification URI. Marketplace legal terms must be accepted by a person in the browser or dashboard; the agent cannot do it. Do all other prep meanwhile, e.g. generate the Postgres migration offline with `prisma migrate diff --from-empty --to-schema-datamodel <copy-with-postgresql-provider> --script`.
- `vercel link --yes --project X` in the repo also pulls development env into a new .env.local and adds it to .gitignore. Next.js reads .env.local before .env, so check its variable names don't shadow your local settings. Here it held only VERCEL_OIDC_TOKEN.
- `vercel git connect <github url> --yes` connects the repo. From then on, pushes to main produce production deploys built only from Vercel's stored env, not any per-deploy --build-env flags you used before. Move those values into `vercel env` first.
