Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-08-25 · high
Sensitive variables auto-converted August 24, and production secrets must now differ from other environments under a renamed policy.
Why now: Vercel's changelog dates the rollout to August 24, 2026.
Vercel retired the single Sensitive toggle on environment variables. It replaced the toggle with two types, per Vercel's changelog. Config stays readable after saving for members with access. Secret can be used and updated by deployments, but once it's saved, nobody can view it again.
That unviewable rule closes a real gap. Teams that shared credentials by pulling the current value from the dashboard and pasting it somewhere else lose that path the moment a variable is typed Secret. The only way to recover a Secret's value is to generate a new one and update it.
Anyone with existing sensitive variables doesn't have to touch anything. Vercel converted them automatically, no migration step required.
The policy side changed too. "Enforce Sensitive Environment Variables" is deprecated. Its replacement, "Separate Production Secret Values," requires that production Secrets differ from what's set in preview, development, and custom environments. That's a stricter default than the old policy asked for. Teams that reused the same API key across production and preview to save a step now have a named policy telling them not to.
Command-line users get the same split. vercel env add and vercel env update both take a --visibility flag to set Config or Secret from a terminal instead of the dashboard.
What the changelog doesn't say is what happens when a Secret is the suspect in a failing deployment. If the value is truly unviewable after save, debugging means rotating it first and comparing behavior after, not reading the old one back to check it.
Each link below shares sources, entities, or timing with this story.
Vercel supports Agent Skills / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Vercel supports Agent Skills); both cover August, Vercel; reported by the same outlet (vercel.com).
Vercel partners with Cursor / Shared entities / Earlier coverage
Linked by a graph relationship (Vercel partners with Cursor); both cover August, CLI, Vercel; earlier August coverage from 2026-08-03.
Vercel partners with Claude Code / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Vercel partners with Claude Code); both cover August, Vercel; overlapping topics (august, config).
Vercel released AI Gateway / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (Vercel released AI Gateway); both cover August, Vercel; reported by the same outlet (vercel.com).
Vercel partners with Claude Code / Shared entities / Earlier coverage / Tension
Linked by a graph relationship (Vercel partners with Claude Code); both cover August, Vercel; earlier August coverage from 2026-08-21.
Linked by a graph relationship (Vercel partners with Claude Code); both cover August, Vercel; earlier August coverage from 2026-08-13.
Vercel released AI Gateway / Shared entity: Vercel / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Vercel released AI Gateway); both cover Vercel; reported by the same outlet (vercel.com).
Vercel supports Datadog / Shared entity: August / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Vercel supports Datadog); both cover August; reported by the same outlet (vercel.com).