This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @chat-adapter/github@4.33.0 ### Minor Changes -6750d59: Add Vercel Connect support to the GitHub adapter. A new `installationToken` config option (string or resolver) supplies installation access tokens directly, skipping the GitHub App private-key JWT exchange, and an optional `webhookVerifier` verifies inbound webhooks (e.g. Connect trigger-forwarded requests via a Vercel OIDC token) in place of the GitHub webhook secret. Pair with `connectGitHubAdapter()` from `@vercel/connect/chat`. `botUserId` now also auto-detects from the `GITHUB_BOT_USER_ID` env var, and the adapter learns its bot user id from the first comment it posts. In Connect mode (where the bot user id can't be auto-detected from an installation token) set `botUserId` / `GITHUB_BOT_USER_ID` to enable self-message detection and avoid the adapter replying to its own comments. Note: the `connectGitHubAdapter()` helper ships in `@vercel/connect` — release this adapter together with (or after) the `@vercel/connect` version that adds the `@vercel/connect/chat` subpath so the documented helper resolves. ### Patch Changes - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [d4c52ca] - Updated dependencies [076fe5d] - chat@4.33.0 - @chat-adapter/shared@4.33.0 ## @chat-adapter/linear@4.33.0 ### Minor Changes -4115c94: Add Vercel Connect support to the Linear adapter. The `accessToken` config option now accepts a resolver (`() => string | Promise<string>`) in addition to a string, so tokens can be sourced from Vercel Connect at runtime, and a new optional `webhookVerifier` verifies inbound webhooks (e.g. Connect trigger-forwarded requests via a Vercel OIDC token) in place of the Linear webhook secret. Pair with `connectLinearAdapter()` from `@vercel/connect/chat`. Connect-mode outbound calls outside webhook handling are supported via `withInstallation(organizationId, fn)`. Note: the `connectLinearAdapter()` helper ships in `@vercel/connect` — release this adapter together with (or after) the `@vercel/connect` version that adds the `@vercel/connect/chat` subpath so the documented helper resolves. ### Patch Changes - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [d4c52ca] - Updated dependencies [076fe5d] - chat@4.33.0 - @chat-adapter/shared@4.33.0 ## @chat-adapter/shared@4.33.0 ### Minor Changes -d4c52ca: add `replaceBareMentions`, a context-aware bare-`@mention` resolver that skips code spans, URLs, schemeless hosts, and existing angle-bracket tokens before handing each real `@name` to a platform-specific replacer ### Patch Changes - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [076fe5d] - chat@4.33.0 ## @chat-adapter/x@4.33.0 ### Minor Changes -ef2542c: add X (Twitter) adapter: reply to public mentions, send and receive direct messages, post and edit from the bot account, and like posts, using the X API v2 with OAuth 2.0 and managed token refresh ### Patch Changes - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [d4c52ca] - Updated dependencies [076fe5d] - chat@4.33.0 - @chat-adapter/shared@4.33.0 ## chat@4.33.0 ### Minor Changes -ef2542c: add X (Twitter) adapter: reply to public mentions, send and receive direct messages, post and edit from the bot account, and like posts, using the X API v2 with OAuth 2.0 and managed token refresh ### Patch Changes -3abdc69: docs(adapters): add Cloudflare Agents as a vendor-official state adapter (`agents/chat-sdk`) to the catalog and docs listing. It is hidden from the create-chat-sdk CLI (Worker/Durable Objects runtime), and the interactive state picker now filters out CLI-incompatible state adapters. -0b63791: Raise the default message dedupe TTL from 5 to 10 minutes so it outlives the longest platform redelivery window. Slack's Events API retries up to ~5 minutes after the original delivery — exactly at the old TTL boundary, where a retried event could miss the expired dedupe entry from its first processing and be handled twice. Configurable behavior is unchanged (`dedupeTtlMs` still overrides). -0c761f1: docs(adapters): add Dial as a vendor-official adapter (`@getdial/chat-sdk-adapter`) to the catalog, docs listing, and CLI scaffold spec -24a04d5: docs(adapters): add Photon as a vendor-official adapter (`@photon-ai/chat-adapter-imessage`) to the catalog, docs listing, and CLI scaffold spec -076fe5d: preserve skipped mention routing for debounce and message patterns ## create-chat-sdk@0.2.0 ### Minor Changes -ba375ce: Add Vercel Connect support to the scaffolder. Pass `--connect` (or choose **Vercel Connect** at the new interactive auth-mode prompt) to authenticate the Slack, GitHub, and Linear adapters with a Vercel Connect connector instead of stored provider secrets. The generated `src/lib/bot.ts` spreads the matching helper from `@vercel/connect/chat` into the adapter factory, `@vercel/connect` is added to dependencies, and `.env.example` lists each connector UID (for example `SLACK_CONNECTOR`) plus the recommended `GITHUB_BOT_USER_ID` for GitHub, in place of native secrets. -ef2542c: add X (Twitter) adapter: reply to public mentions, send and receive direct messages, post and edit from the bot account, and like posts, using the X API v2 with OAuth 2.0 and managed token refresh ### Patch Changes -3abdc69: docs(adapters): add Cloudflare Agents as a vendor-official state adapter (`agents/chat-sdk`) to the catalog and docs listing. It is hidden from the create-chat-sdk CLI (Worker/Durable Objects runtime), and the interactive state picker now filters out CLI-incompatible state adapters. -0c761f1: docs(adapters): add Dial as a vendor-official adapter (`@getdial/chat-sdk-adapter`) to the catalog, docs listing, and CLI scaffold spec -24a04d5: docs(adapters): add Photon as a vendor-official adapter (`@photon-ai/chat-adapter-imessage`) to the catalog, docs listing, and CLI scaffold spec ## @chat-adapter/tests@4.33.0 ### Minor Changes -e7a396a: Add two shared behavioral test contracts for adapter authors: - `threadIdContract` — verifies an adapter's thread-id codec round-trips (`decode(encode(x))`), prefixes ids with the adapter name, matches any pinned encoded strings, and (optionally) distinguishes DM from non-DM threads. - `selfMessageContract` — verifies an adapter dispatches inbound messages from other users (to `processMessage` by default) but ignores messages the bot authored itself, so it never replies to itself. Requires the matchers to be registered via `setupFiles: ["@chat-adapter/tests/setup"]`. -a7fb1bc: Add `connectWebhookContract`, a shared Vitest suite for verifying an adapter's Vercel Connect webhook verification. Given a small per-adapter descriptor (how to build the adapter in Connect mode and craft an inbound webhook), it asserts the behavior every Connect-capable adapter shares: a `webhookVerifier` replaces the native signature/secret check and gates inbound requests — accept (`200`) on a truthy result, reject (`401`) on a thrown error or falsy result — and is invoked with the request and raw body. Connect-capable adapters can opt in with ~10 lines. ## @chat-adapter/discord@4.33.0 ### Patch Changes -d4c52ca: use the shared `replaceBareMentions` scanner for `@mention` conversion so email addresses, `@handles` inside URLs, and mentions inside code spans are no longer mangled into Discord mentions, and already-formatted `<@id>` tokens are not double-wrapped -6de4572: Implement `rehydrateAttachment` on the Discord adapter. Serialization strips an attachment's `fetchData` closure (queue/debounce strategies), and consumers rebuild it via `adapter.rehydrateAttachment`. The Discord adapter did not implement the method, so downstream consumers could not download inbound Discord attachments after deserialization. The Discord CDN `url` survives serialization, so `fetchData` is now rebuilt to fetch that url (preserving its signed query params), matching how the other adapters implement the method. - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [d4c52ca] - Updated dependencies [076fe5d] - chat@4.33.0 - @chat-adapter/shared@4.33.0 ## @chat-adapter/gchat@4.33.0 ### Patch Changes - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [d4c52ca] - Updated dependencies [076fe5d] - chat@4.33.0 - @chat-adapter/shared@4.33.0 ## @chat-adapter/messenger@4.33.0 ### Patch Changes - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [d4c52ca] - Updated dependencies [076fe5d] - chat@4.33.0 - @chat-adapter/shared@4.33.0 ## @chat-adapter/slack@4.33.0 ### Patch Changes -0b63791: Process Slack Socket Mode retry envelopes instead of discarding them. Slack redelivers an event (immediately, +1 min, +5 min) when a prior delivery wasn't acknowledged — including events sent while the app had no open socket, e.g. during a restart or a routine connection refresh. The adapter previously acked and dropped every envelope with `retry_num > 0`, so such events were permanently lost even though Slack redelivered them. Retries are now routed like first deliveries (logged at info with `retry_num`/`retry_reason`); `Chat.processMessage`'s message-id dedupe drops true duplicates. - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [d4c52ca] - Updated dependencies [076fe5d] - chat@4.33.0 - @chat-adapter/shared@4.33.0 ## @chat-adapter/teams@4.33.0 ### Patch Changes -d4c52ca: use the shared `replaceBareMentions` scanner for `@mention` conversion so email addresses, `@handles` inside URLs, and mentions inside code spans are no longer mangled into `<at>` mention tags - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [d4c52ca] - Updated dependencies [076fe5d] - chat@4.33.0 - @chat-adapter/shared@4.33.0 ## @chat-adapter/telegram@4.33.0 ### Patch Changes - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [d4c52ca] - Updated dependencies [076fe5d] - chat@4.33.0 - @chat-adapter/shared@4.33.0 ## @chat-adapter/twilio@4.33.0 ### Patch Changes - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [d4c52ca] - Updated dependencies [076fe5d] - chat@4.33.0 - @chat-adapter/shared@4.33.0 ## @chat-adapter/web@4.33.0 ### Patch Changes - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [d4c52ca] - Updated dependencies [076fe5d] - chat@4.33.0 - @chat-adapter/shared@4.33.0 ## @chat-adapter/whatsapp@4.33.0 ### Patch Changes - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [d4c52ca] - Updated dependencies [076fe5d] - chat@4.33.0 - @chat-adapter/shared@4.33.0 ## @chat-adapter/state-ioredis@4.33.0 ### Patch Changes - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [076fe5d] - chat@4.33.0 ## @chat-adapter/state-memory@4.33.0 ### Patch Changes - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [076fe5d] - chat@4.33.0 ## @chat-adapter/state-pg@4.33.0 ### Patch Changes - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [076fe5d] - chat@4.33.0 ## @chat-adapter/state-redis@4.33.0 ### Patch Changes - Updated dependencies [3abdc69] - Updated dependencies [0b63791] - Updated dependencies [0c761f1] - Updated dependencies [ef2542c] - Updated dependencies [24a04d5] - Updated dependencies [076fe5d] - chat@4.33.0 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@chat-adapter/state-pg
npm package:
@chat-adapter/state-pg
Production PostgreSQL state adapter for Chat SDK built with pg (node-postgres). Use this when PostgreSQL is your primary datastore and you want state persistence without a separate Redis dependency.
Documentation: chat-sdk.dev/adapters/official/postgres · Guides: vercel.com/kb/chat-sdk
Installation
pnpm add @chat-adapter/state-pg
Scaffold with the CLI
To scaffold a new Slack bot that uses PostgreSQL for state:
npx create-chat-sdk@latest my-bot --adapter slack postgres
Visit the adapters directory to see other available official and vendor-official adapters.
Usage
createPostgresState() auto-detects POSTGRES_URL (or DATABASE_URL) so you can call it with no arguments:
import { Chat } from "chat";
import { createPostgresState } from "@chat-adapter/state-pg";
const bot = new Chat({
userName: "mybot",
adapters: { /* ... */ },
state: createPostgresState(),
});
To provide a URL explicitly:
const state = createPostgresState({
url: "postgres://postgres:postgres@localhost:5432/chat",
});
Using an existing client
import pg from "pg";
const client = new pg.Pool({ connectionString: process.env.POSTGRES_URL! });
const state = createPostgresState({ client });
Configuration
| Option | Required | Description |
|---|---|---|
url |
No* | Postgres connection URL |
client |
No | Existing pg.Pool instance |
keyPrefix |
No | Prefix for all state rows (default: "chat-sdk") |
logger |
No | Logger instance (defaults to ConsoleLogger("info").child("postgres")) |
*Either url, POSTGRES_URL/DATABASE_URL, or client is required.
Environment variables
POSTGRES_URL=postgres://postgres:postgres@localhost:5432/chat
Data model
The adapter creates these tables automatically on connect():
chat_state_subscriptions
chat_state_locks
chat_state_cache
chat_state_lists
chat_state_queues
All rows are namespaced by key_prefix.
Features
| Feature | Supported |
|---|---|
| Persistence | Yes |
| Multi-instance | Yes |
| Subscriptions | Yes |
| Distributed locking | Yes |
| Key-value caching | Yes (with TTL) |
| Automatic table creation | Yes |
| Key prefix namespacing | Yes |
Locking considerations
The Redis state adapters use atomic SET NX PX for lock acquisition, which is a single atomic operation. The PostgreSQL adapter uses INSERT ... ON CONFLICT DO UPDATE WHERE expires_at <= now(), which relies on Postgres row-level locking. This is safe for most workloads but under extreme contention (many processes competing for the same lock simultaneously) may behave slightly differently than Redis. For high-contention distributed locking, prefer the Redis adapter.
Expired row cleanup
Unlike Redis (which handles TTL expiry natively), PostgreSQL does not automatically delete expired rows. The adapter performs opportunistic cleanup — expired locks are overwritten on the next acquireLock() call, expired cache entries are deleted on the next get() call for that key, and expired queue entries for a given thread are purged on the next enqueue() or dequeue() call. Expired list entries are filtered out on read but never deleted by the adapter.
For high-throughput deployments, you may want to run a periodic cleanup job:
DELETE FROM chat_state_locks WHERE expires_at <= now();
DELETE FROM chat_state_cache WHERE expires_at <= now();
DELETE FROM chat_state_lists WHERE expires_at <= now();
DELETE FROM chat_state_queues WHERE expires_at <= now();
AI Coding Agents
If you use an AI coding agent such as OpenAI Codex, Claude Code, or Cursor, install the Chat SDK skill so it knows the SDK APIs, adapter patterns, and project conventions before writing code.
npx skills add vercel/chat
The skill references bundled documentation in node_modules/chat/docs, plus adapter guides and starter templates in the published package.
You can also install the Vercel Plugin for a broader agent toolkit — it includes the Chat SDK skill alongside specialist agents, agent slash commands, and more:
npx plugins add vercel/vercel-plugin
The plugin is optional; the skill alone is enough to build with Chat SDK.
For agent-readable documentation, see chat-sdk.dev/llms.txt (page index) or chat-sdk.dev/llms-full.txt (full text).
License
MIT