chore(deps): update dependency chat to v4.40.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
chat (source)	4.20.0 → 4.40.0

---

Release Notes

vercel/chat (chat)

v4.40.0

Compare Source

Minor Changes

• 4a0b5c0: Add tooltip to Button and LinkButton, and a width hint to Card. The Teams adapter and the @chat-adapter/teams/cards subpath render them as the Adaptive Card action tooltip and the msteams full-width card property; other adapters ignore them. Emitted Adaptive Cards now declare schema version 1.5, which is the version that introduced action tooltips. Buttons with a callbackUrl keep their tooltip and other fields when the URL is swapped for a callback token.

Patch Changes

• f485255: Harden webhook tenant isolation, require explicit Google Chat bot identity for reliable mention handling, use native Google Chat pagination, isolate Slack caches, and bound recording storage.
• b7c9316: Tighten AI tool and queued-message scoping, isolate direct-message conversations, preserve ephemeral follow-ups, consume callback tokens once, and mark external link metadata as untrusted.

v4.39.0

Compare Source

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.

v4.38.1

Compare Source

Patch Changes

• 6cb933e: isolate queued and debounced messages by thread when using channel-scoped locks
• 764e475: toPlainText keeps empty table cells so tab-separated columns stay aligned, and drops table rows with no content (such as placeholder header rows)

v4.38.0

Compare Source

Minor Changes

• 0f24cc3: Preserve normalized replied-to message context and populate it from Telegram replies.

• bdeb2bf: Add a workflow-safe chat/serialization entrypoint and isolate automatic Chat class serializers from Node-only runtime dependencies.

• a0cba02: Add Vercel Connect credential resolvers and custom webhook verification to the Discord adapter, with create-chat-sdk --connect scaffolding for Discord bots.

• 83ede7e: add native message replies with WhatsApp contextual reply support

• 18d4a23: Add a shared thread API for marking messages as read across WhatsApp, Messenger, and XChat.

  Note for anyone calling XchatAdapter.markAsRead() directly: it now rejects when a receipt fails instead of logging a warning and resolving. Automatic read receipts are unaffected, since the adapter still catches and logs those internally. If you call the method yourself without awaiting it, add a .catch() so a failed receipt does not surface as an unhandled rejection.

v4.37.0

Compare Source

Minor Changes

• 2a2b2c5: Add a native Instagram Direct Messages adapter with signed webhooks, media, quick replies, story context, reactions, and typed Meta API errors.

• 4ac0455: Add message update and delete lifecycle callbacks, with Slack message_changed and message_deleted dispatch support.

• 0ec6a73: Add @chat-adapter/notion for Notion page and block comment discussions: webhook HMAC verification, Post+Edit streaming, conversation history, message.subject page metadata, plain-text @userName/@botUserId mention detection, and File Uploads (up to 3 native attachments). Registers the adapter in the chat/adapters catalog and create-chat-sdk CLI scaffold, and adds Notion emoji platform support.

• 85e3d22: Close residual gaps in agent read-tool scoping. createChatTools's read guard now wraps modal, assistant-thread, assistant-context, app-home, app-context, and member-joined dispatch so tools built in those handlers inherit the active conversation, and it logs a warning (instead of failing open silently) when a read runs with no resolvable scope. Scoping stays channel-level by default, so a thread scope still permits sibling threads in its channel. Pass the new strictScope: true to confine a thread scope to that thread alone, rejecting both sibling threads and the parent channel, which matters on platforms where a channel is the widest read available (a GitHub channel is an entire repo).

  Note that reads inside those newly wrapped handlers were previously unscoped. An agent built in an onModalSubmit, onAppHomeOpened, or onMemberJoinedChannel handler that reads another channel will now be rejected. Pass an explicit scope, or scope: false for intentionally workspace-wide reads.

v4.36.0

Compare Source

Minor Changes

• c5d86b1: confine built-in agent read tools to the conversation being handled, with an optional scope override

• 0153a39: Add DateInput and NumberInput modal children. The Slack adapter renders them as a datepicker and a number_input, the Teams adapter as Input.Date and Input.Number, and both submitted values arrive in event.values as strings.

  Teams submit values that arrive as JSON numbers are now stringified into event.values instead of being dropped. This fixes Input.Number, but applies to any numeric value a Teams dialog submits — a key that was previously absent from event.values will now be present as a string.

Patch Changes

• 257a32d: Route Teams personal and group conversations using their explicit conversation type so group chats use buffered fallback even when their IDs resemble direct messages.

• b547f45: Stop treating email addresses as bot mentions. A message containing jane@acme.com no longer triggers a bot named acme, because the @ in detectMention must not follow a word character. Real mentions are unaffected, including at the start of a message, after punctuation, and suffixed names such as GitHub's mybot[bot].

• caa6325: Add XChat support to @chat-adapter/x, shipped from the new @chat-adapter/x/chat subpath so it sits alongside the existing X adapter. The XChat crypto stack (@xdevplatform/chat-xdk, @xdevplatform/xdk, juicebox-sdk) is an optional peer dependency, so existing @chat-adapter/x users are unaffected. All cryptography is handled inside the adapter via @xdevplatform/chat-xdk (wasm) and all REST goes through the typed @xdevplatform/xdk client. Only a bot token and a Juicebox PIN are required: the bot's identity (user id and @​handle) is resolved from GET /2/users/me at startup.

  • Encrypted send/receive in DMs and groups (webhook push + polling), signature verification on by default; undecryptable or unverified events are dropped
  • Webhook POSTs must carry a valid x-twitter-webhooks-signature, which X sends on every delivery. Set consumerSecret (or X_CONSUMER_SECRET) to receive webhooks, or disableWebhookVerification when an upstream layer already verifies them. Polling deployments are unaffected
  • Mention detection from structured mention entities, swipe-replies to the bot, and a plain-text @handle fallback; group replies sent as quoted replies
  • openDM(userId) starts (or reuses) an encrypted 1:1, running a full key exchange when needed so the bot can message first
  • Media both ways: inbound attachments with lazy download+decrypt, outbound encrypted uploads
  • Edit and delete of the bot's own messages; the first edit of a fresh message is age-gated by editSafetyDelayMs (default 5000ms) so receiving clients have stored the original
  • Reactions in and out, read receipts (sendReadReceipts, default on), typing keep-alive, configurable group welcome message
  • Cards degrade to text with tappable URL/mention entities plus a URL preview attachment
  • Requests carry a chat-sdk-xchat/<version> User-Agent product token so Chat SDK traffic is identifiable in X API request logs (a User-Agent set via apiHeaders takes precedence)
  • Registered in the chat/adapters catalog and the create-chat-sdk CLI scaffold, with a new optional importPath catalog field for adapters that ship on a subpath

v4.35.0

Compare Source

Minor Changes

• 4cb7e5d: Add a chat/workflow subpath with requestApproval(): durable human-in-the-loop approvals built on Workflow SDK. It posts an approval card with Approve/Deny buttons, suspends the workflow until a user decides (or an optional timeout elapses), validates approvers, finalizes the card with the outcome, and returns { approved, timedOut, user }. Also exports the buildApprovalCard and buildResolvedCard builders. Requires the new optional workflow peer dependency.
• 46681f5: Expose Microsoft Graph email addresses on normalized incoming Teams message authors. Resolved user profiles are cached in the state adapter (1 hour, failed lookups 5 minutes) so the lookup doesn't add a Graph call per message.

Patch Changes

• 80def3a: Add optional isSystem field to the normalized message Author type to distinguish platform-generated messages from humans and bots. The Slack adapter now sets isSystem: true for messages authored by Slack's reserved USLACK user (e.g. "@​user archived the channel" notifications in DMs), so consumers no longer need to hard-code Slack-specific user IDs.

• 93a58af: Show explicitly configured progress as a native Teams DM status while preserving native streaming.

• 25f3099: toAiMessages no longer drops messages that have no text. A message with an empty text body is now kept when it has links or attachments the converter can include: images and text files (text/*, JSON, XML, YAML, etc.) with a working fetchData(). Messages whose only attachments are unsupported (video, audio, other file types, or attachments without fetchData()) are still skipped, and onUnsupportedAttachment now fires for video/audio attachments on these previously filtered messages.

  Note: multipart content no longer always starts with a text part. When a kept message had no text, its content array contains only attachment parts.

v4.34.0

Compare Source

Minor Changes

• 1721fa0: Add support for Slack's Agent messaging experience (agent_view).

  • New core event onAppContextChanged with a normalized AppContextEntity[] describing the user's active view (channel / canvas / list / message / unknown).
  • AppHomeOpenedEvent now carries the folded active-view context as entities and the opened tab (Slack: "home" / "messages"), so handlers can tell a Home-tab open from the DM-open signal under agent_view.
  • Slack adapter: new agentView config flag (under agent_view, app_home_opened is the DM-open signal regardless of tab and folded context is surfaced), routing for the app_context_changed event, and a getAppContext(message) helper to read the folded context on DM messages.
  • setSuggestedPrompts now accepts an optional thread reference (agent_view lets prompts sit at the top of the agent conversation).
  • Under agentView, DM (Messages-tab) messages are threaded per new Slack's model — each user message is a thread root (thread_ts ?? ts). Conversation-scoped threads returned by openDM() keep working: when that thread is subscribed, incoming top-level DM messages route to it.
  • createSlackAdapter env auth fallback (SLACK_BOT_TOKEN / SLACK_CLIENT_ID / SLACK_CLIENT_SECRET) is now disabled only when an auth or verification field (botToken, clientId, clientSecret, installationProvider, signingSecret, webhookVerifier) is passed explicitly, instead of by any config object — so createSlackAdapter({ agentView: true }) still picks up env credentials, while explicit-secret configs stay immune to ambient env vars.
  • Bumped @slack/web-api to ^7.18.0 (adds the optional thread_ts typing for setSuggestedPrompts).

• 4717a38: Add chart support and richer table rendering, with native Slack data table and data visualization blocks.

  • New core ChartElement and Chart() builder (JSX supported) with pie, bar, area, and line charts, mirroring Slack's data visualization model: pie charts take segments, series charts take named series plotted against shared categories with optional xLabel/yLabel.
  • TableElement / Table() gain optional caption (accessible table description) and pageSize (rows per page) fields.
  • Charts degrade gracefully on platforms without native chart support: the underlying data renders as a text table via the shared card fallback (new chartElementToFallbackText helper).
  • Slack adapter: card tables now render as data table blocks by default — paginated and sortable — instead of plain table blocks. Header-only tables keep the plain table block; tables exceeding Slack limits (100 data rows, 20 columns, 10,000 characters) fall back to ASCII as before.
  • Slack adapter: card charts render as data visualization blocks. Charts violating Slack constraints (50-character title, 12 segments/series, 20 categories, 20-character labels, one data point per category, max 2 charts per message) fall back to a text rendering instead of being rejected by the API.
  • The @chat-adapter/slack/blocks subpath gets the same treatment: SlackChartElement types, chart card children, data table rendering, and matching limits.
  • postMessage now surfaces Slack's per-block validation details when the API rejects blocks (invalid_blocks), instead of the bare "An API error occurred" message.

• 6714efc: Support AI SDK v7 as a peer dependency.

  • chat now accepts ai@^6.0.182 || ^7.0.0 (chat/ai tools work with both majors).
  • @chat-adapter/web now accepts ai@^6 || ^7, @ai-sdk/react@^3 || ^4, @ai-sdk/svelte@^4 || ^5, and @ai-sdk/vue@^3 || ^4.
  • The chat/ai tool factories now declare explicit Tool<Input, Output> return types instead of relying on inference, so the published declarations no longer depend on ai internals that changed in v7. The public type surface is unchanged.

Patch Changes

• 5c926f1: Preserve markdown structural whitespace when extracting normalized message text.
• 2531a42: Fix detectMention (and the Telegram adapter's isBotMentioned) falsely matching @bot when @bot-dev is mentioned. \b (word boundary) matches between a word character and a hyphen, so /@bot\b/ incorrectly matches @bot-dev. Replaced with (?![\w-]) to exclude hyphens.

v4.33.0

Compare Source

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

v4.32.0

Compare Source

Minor Changes

• 2e47351: Add autoCompletePrevious option to Plan.addTask(). Defaults to true so sequential workflows keep auto-completing existing in-progress tasks; pass false to keep multiple tasks in progress for parallel execution.

Patch Changes

• eccc6b9: detect bot mentions in skipped queue and burst messages
• 438f551: Fix lightweight thread handles so streaming posts without an incoming message context no longer crash.
• d034b8b: docs(adapters): add Linq as a vendor-official adapter (@linqapp/chat-sdk-adapter) to the catalog, docs listing, and CLI scaffold spec
• 06af3e1: docs(adapters): add Novu as a vendor-official adapter (@novu/chat-sdk-adapter) to the catalog, docs listing, and CLI scaffold spec
• efa9610: Sync bundled KB resources from Edge Config: add four new guides (Vercel Connect, the Slack Vercel Connect bot, AI Gateway + AI SDK, and the daily digest bot), refresh existing guide bodies, and regenerate resources/templates.json. The sync-resources script now fetches and validates all guides before writing (so a failed fetch leaves the tree untouched), validates the source config shape, rejects duplicate slugs, retries transient fetches, and mirrors SKILL.md to all four committed copies.

v4.31.0

Compare Source

Minor Changes

• 778ae69: Add a zero-dependency chat/adapters catalog subpath for official and vendor-official adapter metadata, environment specs, and setup helpers.
• 171657a: Adding support for stable IDs to link button action handlers

v4.30.0

Compare Source

Minor Changes

• 5461ea9: Add native Telegram private chat draft streaming with fallback streaming elsewhere.

v4.29.0

Minor Changes

• ac8a207: Add chat/ai subpath as the home for AI utilities, including createChatTools for the Vercel AI SDK and toAiMessages for converting chat history into AI SDK prompts.

  createChatTools exposes Chat SDK operations as ready-to-use AI SDK tools so an agent can read messages, post replies, send DMs, react, edit, delete, and manage thread subscriptions across every adapter the supplied Chat instance has registered. Write operations require user approval by default and can be toggled globally or per-tool via requireApproval. Three presets (reader, messenger, moderator) scope the toolset, and tools can also be cherry-picked from the same subpath.

  toAiMessages (and the AiMessage / AiMessagePart / ToAiMessagesOptions types) now ship from chat/ai alongside the tools — keeping the optional ai and zod peer dependencies out of bundles that don't use them. The previous chat re-exports continue to work, but are marked @deprecated so editors surface a hint pointing at chat/ai; existing code keeps compiling, and migrating is a single import-path change.

• b75eedb: add burst concurrency strategy

Patch Changes

• e60bc8c: chore: set supported Node versions in engines

v4.28.1

Patch Changes

• 0cc3d06: fix StreamEvent type from step-finish to finish-step

v4.27.0

Minor Changes

• 1e7c551: restore attachment fetchData after queue/debounce serialization

• b0ab804: Bundle guide markdown and a templates manifest with the package so AI agents can discover Chat SDK resources without fetching at runtime. Guides are written to resources/guides/*.md and templates to resources/templates.json by the root-level pnpm sync-resources script.

• b9a1961: Switch Telegram adapter's outbound parse_mode from legacy Markdown to MarkdownV2, and replace the standard-markdown passthrough renderer with a proper AST → MarkdownV2 renderer. Standard markdown (**bold**) and legacy Markdown (*bold*) use different syntaxes and have no shared escape rules, so any message containing ., !, (, ), -, _ in regular text — which is virtually every LLM-generated message — was being rejected with can't parse entities. The new renderer walks the mdast tree and emits MarkdownV2 with context-aware escaping (normal text vs. code blocks vs. link URLs), uniformly applies MarkdownV2 parse_mode to every format-converter output (including AST messages, which previously shipped without parse_mode and rendered asterisks literally), and escapes card fallback text.

  Also fix silent message truncation that the MarkdownV2 migration widened from a rare bug into a reliable 400. The previous truncator sliced messages at 4096/1024 chars and appended literal ..., but in MarkdownV2 . is a reserved character that must be escaped, the slice can leave an orphan trailing \, and it can cut through a paired entity (*bold*, `code`) leaving it unclosed — all of which cause can't parse entities. The two truncate methods are unified into truncateForTelegram(text, limit, parseMode), which appends an escaped \.\.\. for MarkdownV2 and walks back past unbalanced entity delimiters or orphan backslashes before appending. Plain-text messages keep literal ....

  Internal typing hardening: renderMarkdownV2 is now typed exhaustively on mdast's Nodes union with a never assertion, so new mdast node types fail the build rather than silently falling through. Introduce TelegramParseMode = "MarkdownV2" | "plain" replacing the previous string | undefined at call sites, with toBotApiParseMode mapping to the Bot API wire format at the boundary. The chat package gains a re-export of mdast's Nodes union so adapters can build exhaustively typed renderers without importing mdast directly.

• a520797: Add chat.getUser() method and UserInfo type for cross-platform user lookups. Implement getUser on Slack, Discord, Google Chat, GitHub, Linear, and Telegram adapters.

• 70281dc: add initialOption and option_groups support for ExternalSelect

• 9093292: add streaming options to thread.post() with platform-specific namespacing

• 7e90d9c: Add Socket Mode support for environments behind firewalls that can't expose public HTTP endpoints, and add { action: "clear" } modal response to close the entire modal view stack

• bca4792: Allow task_update streaming chunks to include optional details text for Slack task cards

• 37dbb4a: Add thread.getParticipants() to get unique human participants in a thread

• 608d5f0: Add chat.thread(threadId) method to create Thread handles outside of webhook contexts

• a179b29: Implement external_select block kit for Slack

• a8f2aab: Allow plan.updateTask() to target a specific task by ID via { id: taskId } instead of always updating the last in_progress task

Patch Changes

• 8a0c7b3: Fix Slack structured streaming when thread.post(stream) is called from a handler created by an interactive (block_actions) payload.
  The team ID is now resolved from team.id in addition to team_id / team.
• d630e6c: fix(chat): honor concurrency.maxConcurrent in the concurrent strategy. The cap was documented but never applied, so handlers dispatched unbounded. Also warns when maxConcurrent is paired with a non-concurrent strategy (previously ignored silently) and throws on maxConcurrent < 1 to prevent a deadlock.

v4.26.0

Compare Source

Minor Changes

• 2235c16: export standalone reviver for workflow-safe deserialization without adapter dependencies

Patch Changes

• ddb084b: guard fallback streaming against empty post and edit calls

v4.25.0

Compare Source

Minor Changes

• 2700ce8: Allow Slack native streaming to send markdown tables without wrapping them in code fences, while preserving the previous append-only table fallback for other consumers.

v4.24.0

Compare Source

Minor Changes

• 4f5d200: Add Teams dialog (task module) support with actionType: "modal" on buttons and onOpenModal webhook hook

Patch Changes

• 8d89274: fix: disable source maps in published packages
• 27b34e1: Use adapter to parse channel id for thread.channelId

v4.23.0

Compare Source

Minor Changes

• 4166e09: Add channelVisibility enum to distinguish private, workspace, external, and unknown channel scopes. Implements getChannelVisibility() on the Adapter interface and Slack adapter, replacing the previous isExternalChannel boolean.

v4.22.0

Compare Source

Minor Changes

• f2d8957: Implement new concurrency strategies for overlapping messages

v4.21.0

Compare Source

Minor Changes

• e45a67f: Add optional disconnect() hook to the Adapter interface, called during chat.shutdown() for resource cleanup

Patch Changes

• 13ba1c7: Fix fromFullStream() step separator detection for AI SDK v5+: rename step-finish event check to finish-step
• 95fd8ce: Add missing toJSON() method declarations to Thread and Channel interfaces to match their implementations.

v4.20.2

Compare Source

v4.20.1

Compare Source

Patch Changes

• e206371: new toAiMessages API for history-to-AI-SDK transformation. And introduces LinkPreview object on Message
• 8d88b8c: Fix GitHub adapter streaming: accumulate text and post once instead of using the fallbackStream post+edit loop, which caused 422 errors from empty body edits during TTFT. Also log fallbackStream edit failures via the Logger instead of silently swallowing them.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	chat@​4.38.1

View full report