CLI add succeeds but pull returns empty values
Body:
I’m experiencing what appears to be a platform bug where environment variables are not persisting their values despite successful CLI operations.
Project: tyebenals-projects/enerzas
Affected Variables:
NEXT_PUBLIC_SUPABASE_URL
NEXT_PUBLIC_SUPABASE_ANON_KEY
SUPABASE_SERVICE_ROLE_KEY
Reproduction Steps:
Deleted all existing entries for these variables (confirmed clean via vercel env ls)
Re-added each variable via CLI with values piped on stdin
vercel env add returned 
Added Environment Variable for each
Ran vercel env pull .env.production.local --environment=production
All three values come back as empty strings
What I’ve Tried:
Adding via Dashboard — same result
Deleting and re-adding via CLI — same result
Verified no clipboard/UI issues by piping values directly
Expected Behavior: Variables should retain their values after successful add.
Actual Behavior: Variables exist but values are empty, breaking production builds.
This is blocking production deployments. Any help from the Vercel team would be appreciated.-- Questions that get answered the fastest are the ones with relevant info included in the original post. Be sure to include all detail needed to let others see and understand the problem! →
If the variables were added as sensitive environment variables, then they’re only available in production or preview environments and can’t be pulled into local development.
You could mark them non-sensitive to enable them for development use, though that presents a security risk. For development environments, you can use separate non-sensitive environment variables linked to a development database and pull those into your local environment.