Vercel Connect replaces stored tokens with runtime credential exchange
Vercel Connect, now in Public Beta, eliminates long-lived provider tokens stored in environment variables by replacing them with short-lived, task-scoped credentials issued at runtime via OIDC identity verification.
Score breakdown
Vercel Connect removes the standing risk of leaked long-lived provider tokens by ensuring no provider secret ever resides in the app, replacing broad standing grants with short-lived, task-scoped credentials that expire automatically and can be revoked without a full secret rotation.
- 01Vercel Connect is now in Public Beta.
- 02It replaces long-lived provider tokens in environment variables with short-lived, task-scoped credentials issued at runtime.
- 03Every Vercel deployment receives an OIDC identity, which the `@vercel/connect` SDK presents to prove authorization — no provider secret is stored in the app.
Vercel Connect, now in Public Beta, tackles a foundational security problem in agentic applications: long-lived provider tokens stored in environment variables are shared across all users, never expire, and grant broad access regardless of the task at hand. If such a token leaks, everything it can reach is exposed. Vercel Connect replaces this model with runtime credential exchange — a connector is registered once, and when an agent needs to act, the app proves its identity to Vercel Connect and receives a short-lived credential scoped to that specific task.
The identity proof relies on OIDC: every Vercel deployment automatically receives an OIDC identity, which the `@vercel/connect` SDK presents when requesting a token.
The identity proof relies on OIDC: every Vercel deployment automatically receives an OIDC identity, which the `@vercel/connect` SDK presents when requesting a token. Vercel Connect verifies the identity, checks that the project and environment are authorized to use the connector, and returns the provider credential. For local development, `vercel link` and `vercel env pull` make the same identity available; outside Vercel, the SDK accepts a Vercel access token. Connectors can be created from the dashboard, the CLI, or by a coding agent using `npx skills add vercel/vercel-plugin --skill vercel-connect`.
The system supports fine-grained, per-request scoping — a single agent step can request only the specific repositories and permissions it needs for that task, with GitHub cited as a sharp example of this capability. Connectors can also be scoped per environment (development, preview, production), so a compromised credential in one environment cannot be replayed against another. Revocation replaces the painful token rotation process: rather than hunting down and updating every copy of a secret, operators revoke the connector's tokens directly, with Vercel Connect propagating the revocation to the provider where supported.
Key facts
- 01Vercel Connect is now in Public Beta.
- 02It replaces long-lived provider tokens in environment variables with short-lived, task-scoped credentials issued at runtime.
- 03Every Vercel deployment receives an OIDC identity, which the `@vercel/connect` SDK presents to prove authorization — no provider secret is stored in the app.
- 04Connectors are registered once and can be attached to specific projects and environments via the dashboard or CLI.
- 05A coding agent can set up connectors using `npx skills add vercel/vercel-plugin --skill vercel-connect`.
- 06Per-request scoping allows an agent step to request only the exact repositories and permissions needed for that task.
- 07Revocation replaces manual secret rotation: operators revoke connector tokens directly, and Vercel Connect propagates revocation to the provider where supported.
Topics
Summary and scoring are generated automatically from the original article. We always link back to the publisher and never republish images or paywalled content. Last processed Jun 17, 2026 · 10:39 UTC. How this works →