Vercel Connect replaces env tokens with runtime OIDC

WHY IT MATTERS: Long-lived provider tokens stored in environment variables are a standing liability that grows with every integration. They never expire, they are shared across every user and task, and a single leak exposes everything that token can reach. Rotating them after a breach means hunting down copies scattered across projects, environments, and local setups, then redeploying every service that depended on the old value. For teams running AI agents that touch production systems, source control, and messaging platforms, that risk scales linearly with agent capability. A vault makes the token harder to steal, but it does not reduce the damage once it is out.

WHAT CHANGED: Vercel Connect is now in Public Beta and replaces stored tokens with runtime credential exchange. You register a connector once for a provider like Slack or GitHub, attach it to the specific projects and environments that need it, and your app or agent requests a short-lived token at runtime through the Vercel Connect SDK. The app proves its identity using the OIDC identity that every Vercel deployment already receives, which means no provider secret ever lives in your code, environment variables, or local machine. Each token request defines its own scope, such as specific repositories, permissions, or a named user subject, so least privilege becomes the default shape of every operation. Environment-specific connectors prevent a credential compromised in development from being replayed against production, and revocation is instant because there is no long-lived secret to rotate by hand. Coding agents can also manage the setup through the vercel-connect skill.

WHAT TO WATCH: Connector coverage will expand beyond the initial providers, and teams will need to evaluate where per-user scoping with consent flows is worth the overhead compared to app-level access. If you run agents or serverless functions on Vercel, moving integrations from environment variables to Connect is now a concrete architectural step to reduce blast radius and eliminate manual secret rotation.