Vercel Connect GA, Introducing Short-Lived Credentials for AI Agents

AI agents need to access various external systems such as Slack, GitHub, and Snowflake, but previously relied on long-lived tokens, posing significant security risks in case of leaks. Vercel has officially launched (GA) Vercel Connect to address these issues.

Key Change: From Long-Lived to Short-Lived Tokens

The existing Vault-based approach made credential theft difficult, but it was impossible to limit or expire the permissions of leaked tokens. Vercel Connect operates by having applications not store credentials and instead request only the necessary permissions at runtime.

• Short-Lived Validity: Tokens are automatically refreshed and expire immediately after the task is completed.
• Permission Scoping: Grants the minimum permissions required for specific tasks (e.g., read-only access to a single repository) at the time of the request.
• Automatic Refresh and Revocation: Eliminates the need for manual token rotation, allowing specific users or entire tokens to be revoked with a single command.

Technical Implementation

Vercel Connect supports over 100 connectors and uses the OIDC ID built into the Vercel deployment environment to authenticate the token request principal. This eliminates the need for apps to hardcode provider secrets in code or manage them via environment variables. For GitHub, fine-grained permission control per service is possible, such as granting only read-only access at the single repository level instead of organization-wide permissions.