# Chat SDK now supports Vercel Connect

DevFeed: [Chat SDK now supports Vercel Connect](<https://devfeed.tech/articles/chat-sdk-now-supports-vercel-connect-861.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/chat-sdk-vercel-connect>)

Author: Ben Sabic

Published: 2026-07-08T00:00:00Z

Content type: release

Language: en

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

Topics: [SDKs](<https://devfeed.tech/topics/sdks.md>)

Tags: [bots](<https://devfeed.tech/tags/bots.md>), [events](<https://devfeed.tech/tags/events.md>), [github](<https://devfeed.tech/tags/github.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [slack](<https://devfeed.tech/tags/slack.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

## AI overview

Vercel Connect now supports Chat SDK bots through adapter helpers for Slack, GitHub, and Linear. It manages short-lived outbound tokens and validates OIDC tokens for inbound events, removing the need to store or rotate signing secrets.

## Source excerpt

You can now use Vercel Connect to manage credentials for your Chat SDK bots, with no tokens or signing secrets to store or rotate yourself. The new @vercel/connect/chat subpath provides adapter helpers for Slack, GitHub, and Linear. Each helper takes a connector UID and returns a config you spread into the matching adapter factory. Outbound bot calls use a function-form token field backed by getToken, so each API request gets a fresh, short-lived token that Vercel Connect rotates for you. Inbound triggers use a webhookVerifier that validates the OIDC token Connect attaches to forwarded events, eliminating the need for a signingSecret. Read the documentation to set up your first connector with Chat SDK or follow the knowledge base guide to build your own Slackbot with Vercel Connect. Read more