Summary
This is your reference when juggling Vercel environment variables, `.env` file hierarchy, and the `vercel env` CLI. It walks you through the load order (`.env`, `.env.local`, `.env.production.local`), when to use `vercel env pull` versus dashboard settings, and how OIDC tokens expire after 12 hours locally. The chainTo pattern catches raw API keys like `OPENAI_API_KEY` and nudges you toward Vercel's keyless OIDC flow instead. Honest take: `vercel env pull` overwrites your entire `.env.local`, so any custom debug flags you added manually vanish. Back them up first or you'll be recreating them every time you pull fresh secrets.
Install to Claude Code
npx -y skills add vercel-labs/vercel-plugin --skill env-vars --agent claude-codeInstalls into .claude/skills of the current project.
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
Files
SKILL.md
Select a file.
Featured
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
