Vercel Connect now manages credentials for Chat SDK bots — no tokens to store, no signing secrets to rotate.
The new @vercel/connect/chat subpath ships adapter helpers for three platforms:
- Slack — pass a connector UID, get a config you spread into the Slack adapter factory
- GitHub — same pattern, same spread-into-factory approach
- Linear — identical helper shape across all three
Outbound calls use a function-form token field backed by getToken. Each API request gets a fresh, short-lived token that Vercel Connect rotates automatically. Inbound triggers switch to a webhookVerifier that validates the OIDC token Connect attaches to forwarded events — replacing the manual signingSecret you’d otherwise manage yourself.
The practical win: you stop handling secrets. No .env entries for bot tokens, no rotation schedules, no incidents because a Slack token expired mid-sprint. Vercel Connect becomes the single credential layer for both directions of bot traffic.
NOTE
Each helper takes a connector UID and returns a config object you spread into the matching adapter factory. The shape is identical across Slack, GitHub, and Linear — switching platforms means changing one UID, not rewriting adapter setup.
Available now in the @vercel/connect/chat subpath. Setup guide at chat-sdk.dev/docs/vercel-connect. Changelog: Vercel Connect + Chat SDK.