VibeRaven
Vercel Environment Variables Checklist for AI Apps
Vercel environment variables are a top reason AI-built apps break after deploy. Run npx -y viberaven --agent-mode and npx -y viberaven audit --vercel-supabase to scan repo evidence for required env vars, preview/production drift, and exposed secrets.
Vercel environment variables to verify
- List every env var the repo reads at build time versus runtime.
- Separate preview and production values for auth URLs, Supabase keys, Stripe keys, and webhooks.
- Confirm server-only secrets are not prefixed for client exposure.
- Match .env.example and docs to what Vercel projects actually define per environment.
- Re-check callback URLs, webhook endpoints, and canonical URLs after env promotion.
- Ask your coding agent to fix one env validation or documentation gap with a verification command.
vercel environment variables
Document every var the repo needs, set preview and production values in Vercel, and keep server secrets out of client bundles. Run npx -y viberaven --agent-mode and npx -y viberaven audit --vercel-supabase to map env gaps from repo evidence first.