mirror of https://github.com/vercel/chat.git synced 2026-09-14 18:32:29 +08:00

Files

T

github-actions[bot] 7a1798bdfd chore(release): version packages (#841 )

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/shared@4.39.0

### Minor Changes

- 153bd96: guard Messenger attachment downloads against SSRF and
oversized responses

`downloadAttachment` in `@chat-adapter/shared` accepts an optional
`hosts` allowlist that restricts downloads, including redirect targets,
to the given hosts and their subdomains. The Messenger adapter uses it
to download attachment media only from Meta's `fbsbx.com` and
`fbcdn.net` hosts, with the shared SSRF guard, 25 MB size cap, and 30
second timeout. External fallback and link-share URLs are rejected
before any network request.

- bb92688: secure anonymous attachment downloads against SSRF and
oversized responses

`@chat-adapter/shared` gains `downloadAttachment`, a guarded downloader
that refuses private and internal addresses (as URL literals, through
DNS resolution, and after redirects), decodes compressed responses, caps
the body size at 25 MB, and bounds the whole download with a 30 second
timeout. All of these are configurable, including the transport for
proxied deployments.

The Teams adapter uses it for anonymous attachment downloads. HTTPS
attachments on any public host keep working, plain-HTTP URLs are
refused, and the Bot Framework Emulator's loopback connector now uses
bot authentication so local development keeps working.

- e71bfea: Add `normalizeCodeFences` to `@chat-adapter/shared`: a
code-fence normalizer for platforms whose triple-backtick fences treat
the text after the opening fence as code rather than a CommonMark info
string. Only paired fences become code blocks (unpaired fences, fences
inside inline code, and fences on quoted lines stay literal text), text
following a closing fence cannot be promoted to a block construct, and
per-segment callbacks keep text-level rewrites out of code content.

The WhatsApp adapter now uses it when parsing incoming messages: the
first line of a code block is preserved in message text and formatted
content, and bold/strikethrough rewriting no longer corrupts fenced
code.

- b6fa24c: guard attachment downloads across the remaining adapters

Slack, Discord, and WhatsApp attachment downloads now go through the
shared guarded downloader: private and internal addresses are refused
(as URL literals, through DNS resolution, and after redirects),
responses are capped at 25 MB, and downloads time out after 30 seconds.
Slack sends the bot token only on hops to trusted Slack origins, and
WhatsApp keeps its access token on Meta's media hosts and the configured
Graph origin. Telegram enforces the same size cap and timeout with the
Web Fetch API so downloads keep working in runtimes like Cloudflare
Workers.

`downloadAttachment` in `@chat-adapter/shared` now resolves `headers`
per hop (pass a function to control what each redirect target receives),
forwards the resolved headers to custom transports, and accepts an
`onResponse` hook to reject unexpected final responses before the body
is read.

### Patch Changes

- Updated dependencies [2ce2be0]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [5b538f6]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
  - chat@4.39.0
## @chat-adapter/slack@4.39.0

### Minor Changes

- 2ce2be0: Add Slack Agent Sessions lifecycle support, native stop
cancellation through `thread.signal`, automatic session titles, and
session stop/title-change events while preserving the legacy
`assistant_view` compatibility path.

### Patch Changes

- 864d922: Keep alert attachment content on normalized Slack messages.
Attachments that aren't link unfurls now contribute their pretext, title
(linked to `title_link` when present, with the URL also surfaced in
`message.links`), text, and fields instead of being dropped; `fallback`
fills in when nothing else on the attachment carries content. Matching
how Slack renders these fields, they are treated as plain text unless
listed in the attachment's `mrkdwn_in` array, so literal `*`, `_`, and
backticks in alert text survive normalization. Tables inside attachment
blocks now stay adjacent to their attachment's text.

Because attachment content is part of `message.text`, mention detection
and `onMessage` pattern handlers see it too: an attachment that quotes
the bot's mention routes to `onNewMention`, and patterns match alert
text. Handlers that should ignore other integrations' alerts can check
`message.author.isBot`.

- 7c26965: prevent attachment downloads from sending credentials to
untrusted hosts
- e71bfea: Preserve the first line of incoming Slack code blocks when
extracting message text and formatted content.

Only paired triple-backtick fences become code blocks: an unpaired
fence, a fence inside inline code or a `<…>` token, and a fence on a
quoted line all stay literal text, matching how Slack renders them. Bold
and strikethrough rewriting no longer touches fenced code content, and
text following a closing fence can no longer turn into a blockquote,
heading, or list.

- b6fa24c: guard attachment downloads across the remaining adapters

Slack, Discord, and WhatsApp attachment downloads now go through the
shared guarded downloader: private and internal addresses are refused
(as URL literals, through DNS resolution, and after redirects),
responses are capped at 25 MB, and downloads time out after 30 seconds.
Slack sends the bot token only on hops to trusted Slack origins, and
WhatsApp keeps its access token on Meta's media hosts and the configured
Graph origin. Telegram enforces the same size cap and timeout with the
Web Fetch API so downloads keep working in runtimes like Cloudflare
Workers.

`downloadAttachment` in `@chat-adapter/shared` now resolves `headers`
per hop (pass a function to control what each redirect target receives),
forwards the resolved headers to custom transports, and accepts an
`onResponse` hook to reject unexpected final responses before the body
is read.

- Updated dependencies [2ce2be0]
- Updated dependencies [153bd96]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [bb92688]
- Updated dependencies [5b538f6]
- Updated dependencies [e71bfea]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
- Updated dependencies [b6fa24c]
  - chat@4.39.0
  - @chat-adapter/shared@4.39.0
## @chat-adapter/telegram@4.39.0

### Minor Changes

- c4a359e: require webhook verification by default with an explicit
unverified opt-in
- 26a06ca: Add `mentionOnReply`: when enabled, a reply to one of the
bot's own messages reports `isMention`, so a bot in a group keeps the
conversation going without the handle being repeated. Off by default, so
existing mention-only bots are unaffected, and readable from
`TELEGRAM_MENTION_ON_REPLY`. Implicit forum-topic replies and the bot's
own echoed messages never count, and polling mode now retries the
startup `getMe` lazily so a transient outage cannot leave mention
detection disabled.
- d5ebec1: Implement `reply` in the Telegram adapter so `Thread.reply()`
threads the answer to its target instead of throwing
`NotImplementedError`. The reference travels as Bot API
`reply_parameters` and covers text, rich messages, documents,
attachments and media groups; `allow_sending_without_reply` keeps
delivery working when the target has been deleted. Malformed reply
target ids are rejected before anything is sent, and a rich-message
gateway that rejects `reply_parameters` falls back to a regular threaded
send.
- a18e792: Describe the message kinds Telegram sends with no text and no
file. A shared location, venue, contact, poll, dice, game, invoice or
story used to arrive as an empty message: the payload carried the
content, but a handler reading `text` saw nothing. Each now gets a short
literal description (`📍 55.75, 37.61`, `👤 Ada Lovelace +1555…`, `📊 Lunch
or dinner?`), and the structured payload stays on the raw message for
anyone who needs the numbers.
- a0ba986: Parse stickers and animations. A sticker used to arrive as an
empty message, since it carries no text, and an animation (Telegram GIF)
was dropped entirely. A sticker now reports the emoji it stands for as
its text (falling back to the sticker set name, then to "sticker") plus
an attachment matching its real format: an image for a still WebP
sticker, a video for a WebM one, a file for a Lottie (TGS) one. An
animation arrives as a single video attachment; the redundant `document`
field Telegram sets alongside it for backward compatibility is no longer
reported as a second attachment.

### Patch Changes

- eddcd7e: Return Telegram file downloads as portable ArrayBuffer data
while preserving Buffer support in the shared attachment contract.
- b6fa24c: guard attachment downloads across the remaining adapters

Slack, Discord, and WhatsApp attachment downloads now go through the
shared guarded downloader: private and internal addresses are refused
(as URL literals, through DNS resolution, and after redirects),
responses are capped at 25 MB, and downloads time out after 30 seconds.
Slack sends the bot token only on hops to trusted Slack origins, and
WhatsApp keeps its access token on Meta's media hosts and the configured
Graph origin. Telegram enforces the same size cap and timeout with the
Web Fetch API so downloads keep working in runtimes like Cloudflare
Workers.

`downloadAttachment` in `@chat-adapter/shared` now resolves `headers`
per hop (pass a function to control what each redirect target receives),
forwards the resolved headers to custom transports, and accepts an
`onResponse` hook to reject unexpected final responses before the body
is read.

- Updated dependencies [2ce2be0]
- Updated dependencies [153bd96]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [bb92688]
- Updated dependencies [5b538f6]
- Updated dependencies [e71bfea]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
- Updated dependencies [b6fa24c]
  - chat@4.39.0
  - @chat-adapter/shared@4.39.0
## @chat-adapter/twilio@4.39.0

### Minor Changes

- 75cadbf: feat(twilio): add RCS support with rich cards, button
actions, and location sharing

Extends the Twilio adapter with full RCS support: inbound button tap
routing via `processAction`, location share parsing, Content API
integration for rich outbound cards with SMS fallback, and channel
metadata detection. Cards sent to RCS-capable senders (Messaging Service
or `rcs:` address) are automatically rendered as Twilio Content
templates with embedded SMS fallback variants.

Existing deployments keep their thread ids: plain SMS threads stay keyed
by phone number even when the number belongs to a Messaging Service, and
`openDM` still prefers `phoneNumber` over `messagingServiceSid`. Only
taps of buttons rendered by Chat SDK become actions; foreign button taps
that carry a body keep arriving as messages.

### Patch Changes

- 28bc776: isolate Twilio message processing locks by conversation
- Updated dependencies [2ce2be0]
- Updated dependencies [153bd96]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [bb92688]
- Updated dependencies [5b538f6]
- Updated dependencies [e71bfea]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
- Updated dependencies [b6fa24c]
  - chat@4.39.0
  - @chat-adapter/shared@4.39.0
## chat@4.39.0

### Minor Changes

- 2ce2be0: Add Slack Agent Sessions lifecycle support, native stop
cancellation through `thread.signal`, automatic session titles, and
session stop/title-change events while preserving the legacy
`assistant_view` compatibility path.
- 169788b: Introduce the unified History API (`bot.history`) with user,
thread, and channel scopes.

`bot.history.user` replaces `bot.transcripts` for cross-platform
per-user message persistence. The API surface is identical — migrate by
changing the `transcripts` config key to `history.user` and updating
call sites from `bot.transcripts.*` to `bot.history.user.*`.
`bot.transcripts` remains available as a deprecated alias.

`bot.history.thread` and `bot.history.channel` expose promise-based
helpers for per-thread and per-channel message access, aligned with the
existing `thread.messages` and `channel.threads()` iterators. Reads
delegate to the adapter; adapters that persist history in the SDK-side
store (`persistThreadHistory: true`) are served from that cache. An
unregistered adapter prefix or an unsupported capability throws instead
of returning an empty result.

The new `toPromptEntries` helper converts `history.user.list()` entries
into `{ role, content }` messages ready for LLM prompts.

The `TranscriptEntry` type is deprecated in favour of `HistoryEntry`.
Both are exported from `chat`.

- 5b538f6: Keep thread locks alive while message handlers run so queue,
burst, and debounce strategies remain serialized beyond the lock TTL.
Renewal is capped by the new `concurrency.maxLockLifetimeMs` option
(default 10 minutes) so a hung handler cannot block a thread forever.
When the heartbeat detects that lock ownership was lost, the queue drain
and debounce loops stop instead of competing with the new lock holder,
and the debounce loop now keeps draining messages that arrive while a
handler is running instead of stranding them until the next webhook.

### Patch Changes

- 16ea171: preserve adapter-returned thread ids when editing channel
messages
- eddcd7e: Return Telegram file downloads as portable ArrayBuffer data
while preserving Buffer support in the shared attachment contract.
- 929878b: Allow JSX link buttons to include an explicit action ID.
- 500b7e6: enforce the conversation scope on write tools and stop
trusting client-supplied message history in the web adapter

`createChatTools` now runs the same scope guard on write tools that read
tools already used, so a thread or channel id the model supplies that
resolves outside the scoped conversation is rejected before the write
executes. `sendDirectMessage` targets a user id rather than a
conversation and stays gated by approval alone.

The web adapter no longer treats the request body's `messages` array as
a source of conversation state. Only the latest user message is
consumed, and tool parts are stripped from it so a browser cannot inject
forged tool-call or approval state. Text, file, and custom data parts
pass through unchanged; a message left with no parts after stripping is
rejected with HTTP 400. Prior turns come from the state adapter when
`persistMessageHistory` is enabled.
## @chat-adapter/discord@4.39.0

### Patch Changes

- c4f709f: fix edits, deletes, and reactions on Discord thread starter
messages

Operations on a thread's starter message now try the thread first and
fall back to the parent channel when Discord reports the message as
unknown. Threads on a text channel keep their starter message in the
parent channel, so those operations used to fail; forum and media posts
keep theirs in the thread and are unaffected.

Note that deleting a text-channel thread's starter message now deletes
the message, which Discord cascades into deleting the thread.

- b6fa24c: guard attachment downloads across the remaining adapters

Slack, Discord, and WhatsApp attachment downloads now go through the
shared guarded downloader: private and internal addresses are refused
(as URL literals, through DNS resolution, and after redirects),
responses are capped at 25 MB, and downloads time out after 30 seconds.
Slack sends the bot token only on hops to trusted Slack origins, and
WhatsApp keeps its access token on Meta's media hosts and the configured
Graph origin. Telegram enforces the same size cap and timeout with the
Web Fetch API so downloads keep working in runtimes like Cloudflare
Workers.

`downloadAttachment` in `@chat-adapter/shared` now resolves `headers`
per hop (pass a function to control what each redirect target receives),
forwards the resolved headers to custom transports, and accepts an
`onResponse` hook to reject unexpected final responses before the body
is read.

- Updated dependencies [2ce2be0]
- Updated dependencies [153bd96]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [bb92688]
- Updated dependencies [5b538f6]
- Updated dependencies [e71bfea]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
- Updated dependencies [b6fa24c]
  - chat@4.39.0
  - @chat-adapter/shared@4.39.0
## @chat-adapter/gchat@4.39.0

### Patch Changes

- Updated dependencies [2ce2be0]
- Updated dependencies [153bd96]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [bb92688]
- Updated dependencies [5b538f6]
- Updated dependencies [e71bfea]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
- Updated dependencies [b6fa24c]
  - chat@4.39.0
  - @chat-adapter/shared@4.39.0
## @chat-adapter/github@4.39.0

### Patch Changes

- Updated dependencies [2ce2be0]
- Updated dependencies [153bd96]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [bb92688]
- Updated dependencies [5b538f6]
- Updated dependencies [e71bfea]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
- Updated dependencies [b6fa24c]
  - chat@4.39.0
  - @chat-adapter/shared@4.39.0
## @chat-adapter/instagram@4.39.0

### Patch Changes

- Updated dependencies [2ce2be0]
- Updated dependencies [153bd96]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [bb92688]
- Updated dependencies [5b538f6]
- Updated dependencies [e71bfea]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
- Updated dependencies [b6fa24c]
  - chat@4.39.0
  - @chat-adapter/shared@4.39.0
## @chat-adapter/linear@4.39.0

### Patch Changes

- Updated dependencies [2ce2be0]
- Updated dependencies [153bd96]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [bb92688]
- Updated dependencies [5b538f6]
- Updated dependencies [e71bfea]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
- Updated dependencies [b6fa24c]
  - chat@4.39.0
  - @chat-adapter/shared@4.39.0
## @chat-adapter/messenger@4.39.0

### Patch Changes

- 153bd96: guard Messenger attachment downloads against SSRF and
oversized responses

`downloadAttachment` in `@chat-adapter/shared` accepts an optional
`hosts` allowlist that restricts downloads, including redirect targets,
to the given hosts and their subdomains. The Messenger adapter uses it
to download attachment media only from Meta's `fbsbx.com` and
`fbcdn.net` hosts, with the shared SSRF guard, 25 MB size cap, and 30
second timeout. External fallback and link-share URLs are rejected
before any network request.

- Updated dependencies [2ce2be0]
- Updated dependencies [153bd96]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [bb92688]
- Updated dependencies [5b538f6]
- Updated dependencies [e71bfea]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
- Updated dependencies [b6fa24c]
  - chat@4.39.0
  - @chat-adapter/shared@4.39.0
## @chat-adapter/notion@4.39.0

### Patch Changes

- Updated dependencies [2ce2be0]
- Updated dependencies [153bd96]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [bb92688]
- Updated dependencies [5b538f6]
- Updated dependencies [e71bfea]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
- Updated dependencies [b6fa24c]
  - chat@4.39.0
  - @chat-adapter/shared@4.39.0
## @chat-adapter/teams@4.39.0

### Patch Changes

- 63997ac: hydrate live Teams sender email without requiring Microsoft
Graph permissions
- bb92688: secure anonymous attachment downloads against SSRF and
oversized responses

`@chat-adapter/shared` gains `downloadAttachment`, a guarded downloader
that refuses private and internal addresses (as URL literals, through
DNS resolution, and after redirects), decodes compressed responses, caps
the body size at 25 MB, and bounds the whole download with a 30 second
timeout. All of these are configurable, including the transport for
proxied deployments.

The Teams adapter uses it for anonymous attachment downloads. HTTPS
attachments on any public host keep working, plain-HTTP URLs are
refused, and the Bot Framework Emulator's loopback connector now uses
bot authentication so local development keeps working.

- Updated dependencies [2ce2be0]
- Updated dependencies [153bd96]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [bb92688]
- Updated dependencies [5b538f6]
- Updated dependencies [e71bfea]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
- Updated dependencies [b6fa24c]
  - chat@4.39.0
  - @chat-adapter/shared@4.39.0
## @chat-adapter/web@4.39.0

### Patch Changes

- 500b7e6: enforce the conversation scope on write tools and stop
trusting client-supplied message history in the web adapter

`createChatTools` now runs the same scope guard on write tools that read
tools already used, so a thread or channel id the model supplies that
resolves outside the scoped conversation is rejected before the write
executes. `sendDirectMessage` targets a user id rather than a
conversation and stays gated by approval alone.

The web adapter no longer treats the request body's `messages` array as
a source of conversation state. Only the latest user message is
consumed, and tool parts are stripped from it so a browser cannot inject
forged tool-call or approval state. Text, file, and custom data parts
pass through unchanged; a message left with no parts after stripping is
rejected with HTTP 400. Prior turns come from the state adapter when
`persistMessageHistory` is enabled.

- Updated dependencies [2ce2be0]
- Updated dependencies [153bd96]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [bb92688]
- Updated dependencies [5b538f6]
- Updated dependencies [e71bfea]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
- Updated dependencies [b6fa24c]
  - chat@4.39.0
  - @chat-adapter/shared@4.39.0
## @chat-adapter/whatsapp@4.39.0

### Patch Changes

- 3e6e866: support business-scoped user IDs for inbound and outbound
WhatsApp messages
- e71bfea: Add `normalizeCodeFences` to `@chat-adapter/shared`: a
code-fence normalizer for platforms whose triple-backtick fences treat
the text after the opening fence as code rather than a CommonMark info
string. Only paired fences become code blocks (unpaired fences, fences
inside inline code, and fences on quoted lines stay literal text), text
following a closing fence cannot be promoted to a block construct, and
per-segment callbacks keep text-level rewrites out of code content.

The WhatsApp adapter now uses it when parsing incoming messages: the
first line of a code block is preserved in message text and formatted
content, and bold/strikethrough rewriting no longer corrupts fenced
code.

- 7c26965: prevent attachment downloads from sending credentials to
untrusted hosts
- b6fa24c: guard attachment downloads across the remaining adapters

Slack, Discord, and WhatsApp attachment downloads now go through the
shared guarded downloader: private and internal addresses are refused
(as URL literals, through DNS resolution, and after redirects),
responses are capped at 25 MB, and downloads time out after 30 seconds.
Slack sends the bot token only on hops to trusted Slack origins, and
WhatsApp keeps its access token on Meta's media hosts and the configured
Graph origin. Telegram enforces the same size cap and timeout with the
Web Fetch API so downloads keep working in runtimes like Cloudflare
Workers.

`downloadAttachment` in `@chat-adapter/shared` now resolves `headers`
per hop (pass a function to control what each redirect target receives),
forwards the resolved headers to custom transports, and accepts an
`onResponse` hook to reject unexpected final responses before the body
is read.

- Updated dependencies [2ce2be0]
- Updated dependencies [153bd96]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [bb92688]
- Updated dependencies [5b538f6]
- Updated dependencies [e71bfea]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
- Updated dependencies [b6fa24c]
  - chat@4.39.0
  - @chat-adapter/shared@4.39.0
## @chat-adapter/x@4.39.0

### Patch Changes

- Updated dependencies [2ce2be0]
- Updated dependencies [153bd96]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [bb92688]
- Updated dependencies [5b538f6]
- Updated dependencies [e71bfea]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
- Updated dependencies [b6fa24c]
  - chat@4.39.0
  - @chat-adapter/shared@4.39.0
## @chat-adapter/state-ioredis@4.39.0

### Patch Changes

- Updated dependencies [2ce2be0]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [5b538f6]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
  - chat@4.39.0
## @chat-adapter/state-memory@4.39.0

### Patch Changes

- Updated dependencies [2ce2be0]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [5b538f6]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
  - chat@4.39.0
## @chat-adapter/state-pg@4.39.0

### Patch Changes

- Updated dependencies [2ce2be0]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [5b538f6]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
  - chat@4.39.0
## @chat-adapter/state-redis@4.39.0

### Patch Changes

- Updated dependencies [2ce2be0]
- Updated dependencies [16ea171]
- Updated dependencies [169788b]
- Updated dependencies [eddcd7e]
- Updated dependencies [5b538f6]
- Updated dependencies [929878b]
- Updated dependencies [500b7e6]
  - chat@4.39.0
## @chat-adapter/tests@4.39.0

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

2026-08-28 20:37:34 +10:00

src

fix(slack): preserve first line of incoming code blocks (#843 )

2026-08-28 15:09:03 +10:00

CHANGELOG.md

chore(release): version packages (#841 )

2026-08-28 20:37:34 +10:00

package.json

chore(release): version packages (#841 )

2026-08-28 20:37:34 +10:00

README.md

docs: refresh agent docs, README badges, and Chat SDK skill (#646 )

2026-06-27 14:06:13 +10:00

tsconfig.json

Upgrade Biome configuration to use Ultracite preset (#81 )

2026-02-20 22:01:10 -08:00

tsup.config.ts

fix: disable source maps in published packages (#337 )

2026-04-07 09:02:36 +10:00

vitest.config.ts

Upgrade vitest

2026-02-27 09:58:28 -08:00

README.md

@chat-adapter/shared

npm package: @chat-adapter/shared

Shared utilities for Chat SDK adapters. Provides common helpers used across adapter implementations.

Documentation: chat-sdk.dev/docs/contributing/building · Guides: vercel.com/kb/chat-sdk

Installation

pnpm add @chat-adapter/shared

Utilities

Adapter helpers

extractCard(message) - extract a CardElement from an AdapterPostableMessage
extractFiles(message) - extract FileUpload[] from an AdapterPostableMessage
extractPostableAttachments(message) - extract Attachment[] from an AdapterPostableMessage

Buffer conversion

toBuffer(input) - convert various inputs (Buffer, Blob, string, URL) to Buffer
toBufferSync(input) - synchronous version of toBuffer
bufferToDataUri(buffer, mimeType) - convert a Buffer to a data URI string

Card conversion

cardToFallbackText(card) - render a CardElement as plain text for platforms that don't support cards
createEmojiConverter(platform) - create a function that converts emoji placeholders to platform format
mapButtonStyle(style) - map generic button styles to platform-specific variants
renderGfmTable(headers, rows) - render a GitHub Flavored Markdown table
escapeTableCell(text) - escape pipe characters in table cells

Token encryption

AES-256-GCM helpers for encrypting OAuth tokens at rest before writing them to a state adapter. Used by @chat-adapter/slack and @chat-adapter/linear; available to any adapter that persists credentials.

encryptToken(plaintext, key) - encrypt a string and return an EncryptedTokenData envelope (random 12-byte IV per call)
decryptToken(data, key) - decrypt an envelope back to the original string
decodeKey(encoded) - decode a hex-64 or base64-44 encoded 32-byte key; throws on wrong length
isEncryptedTokenData(value) - type guard for distinguishing envelopes from legacy plaintext records
EncryptedTokenData - the envelope type ({ data, iv, tag }, all base64)

Error classes

Standardized errors for adapter implementations:

AdapterError - base error class
AdapterRateLimitError - platform rate limit (includes retryAfter)
AuthenticationError - expired or invalid tokens
NetworkError - connection failures
PermissionError - missing scopes or permissions
ResourceNotFoundError - missing channel/thread/message
ValidationError - invalid config or input

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