# Introducing Vercel Connect

DevFeed: [Introducing Vercel Connect](<https://devfeed.tech/articles/introducing-vercel-connect-765.md>)

Original publisher: [Read original article](<https://vercel.com/blog/introducing-vercel-connect>)

Author: Kevin Corbett

Published: 2026-06-17T04:00:00Z

Content type: article

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Vercel](<https://devfeed.tech/topics/vercel.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [SDKs](<https://devfeed.tech/topics/sdks.md>), [API](<https://devfeed.tech/topics/api.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [api](<https://devfeed.tech/tags/api.md>), [cli](<https://devfeed.tech/tags/cli.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [github](<https://devfeed.tech/tags/github.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [slack](<https://devfeed.tech/tags/slack.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

## AI overview

Vercel Connect, now in Public Beta, replaces long-lived provider tokens with short-lived, task-scoped credentials obtained through runtime credential exchange. Applications authenticate with Vercel using their deployment OIDC identity, while reusable connectors link Vercel teams to providers such as Slack and GitHub across projects and environments.

## Source excerpt

Giving your agents access to your tools, data, and services is what makes them useful. As agents perform deeper work across systems, authenticating and authorizing that access becomes central to your application architecture. Today, agent access is usually granted through long-lived provider tokens stored in your environment variables, provisioned for everything your agent might need. These tokens are shared across every user, never expire, and give your agent full reach across every task, no matter how small the job. A vault makes that token harder to steal. It doesn't make it less dangerous. The problem is what happens when the token leaks: everything it can touch is now exposed. We built Vercel Connect to solve this problem. Now in Public Beta, Vercel Connect replaces the stored token with runtime credential exchange. You register a connector once. When your agent has work to do, your app proves its identity to Vercel Connect and gets back a short-lived credential, scoped to the task. Everything you used the token for still works. The agent just requests access each time instead of holding it. Register a connector once, then reuse it across projects and environments A connector is a reusable connection between your Vercel team and a provider like Slack or GitHub. You create it once from the dashboard or the CLI, then attach it to the projects and environments that need it, with project-level access controls. The relationship with the provider becomes a single entity you can see and manage, not something scattered across a dozen environment variable panels where a rotation means hunting down every copy. Your coding agent can run this setup too. Install the vercel-connect skill with npx skills add vercel/vercel-plugin --skill vercel-connect, and it can create and attach connectors for you. Request scoped tokens at runtime With a connector in place, the agent asks for a credential only when it has work to do. The @vercel/connect SDK returns a token you use immediate