Use Vercel Chat SDK's new X adapter to handle public mentions and direct messages from one bot codebase. Vercel added an X adapter to Chat SDK on July 14, 2026. It lets teams build bots that reply to public mentions and direct messages through X API v2 and the X Activity API while keeping the same Chat SDK pattern used for Slack, Discord, GitHub, Teams, Telegram, and WhatsApp. Best fit: teams already building multi-channel support, community, or workflow bots with Chat SDK. Check before use: The adapter handles CRC verification, webhook signature checks, and OAuth token refresh for long-running bots. X supports likes as the only reaction in this adapter. Responses post once after completion because X has no native streaming. X automation rules still apply to automated messages, so review policy and rate limits before production use.

LinkLoot access: Free
Provider costs: Unknown

Review open

@ZachasADMIN

Open loot

Use Vercel Connect to stop storing bot tokens in Chat SDK projects

No votes yet

#Vercel #Chat SDK+4

Vercel's Chat SDK now supports Vercel Connect, letting bot builders use connector-backed Slack, GitHub, and Linear credentials instead of storing long-lived tokens and signing secrets in their own app. Use Vercel Connect to stop storing bot tokens in Chat SDK projects Vercel Connect support in Chat SDK is worth bookmarking if you build bots that talk to Slack, GitHub, or Linear. The practical win is credential handling: @vercel/connect/chat returns adapter helpers that use connector UIDs, fresh short-lived tokens, and OIDC-verified inbound triggers instead of app-managed token storage. Best fit Use case Why it helps Caveat --- --- --- Slack bots on Vercel connectSlackAdapter() can feed credentials into the Slack adapter. Vercel Connect is still beta. GitHub or Linear workflow bots Connector-backed auth reduces manual token rotation work. Check connector availability for your account. Inbound bot events Vercel documents trigger forwarding with OIDC validation. Review event scope and permissions before production use. What to check first Confirm your project can use Vercel Connect and the needed connector. Review the @vercel/connect/chat adapter helper docs. Keep least-privilege scopes on Slack, GitHub, and Linear connectors. Test inbound trigger verification before trusting production events. Read the beta terms, because connector behavior can change before GA. Practical LinkLoot angle This is not broad platform news, but it is a useful security and maintenance shortcut for bot projects. If your Chat SDK bot currently stores tokens or webhook signing secrets, test Vercel Connect in a staging deployment and compare the operational surface: fewer secrets, shorter-lived outbound credentials, and a standard verification path for inbound events. Source check Vercel's July 8, 2026 changelog confirms Chat SDK support for Vercel Connect and the @vercel/connect/chat subpath. The Chat SDK documentation explains setup, connector UIDs, adapter helpers, outbound token handling, and inbound webhook verification.

LinkLoot access: Free
Provider costs: Unknown

Review open

@ZachasADMIN

Open loot

Blog

#bots

Mehr aus diesem Thema

Build X bots with Vercel Chat SDK

Use Vercel Connect to stop storing bot tokens in Chat SDK projects

Verwandte Artikel

Use Telegram Communities and Private Bot Replies Without Cluttering Group Chats