# Chat SDK now supports reactions and ephemeral messages on Teams

Source: [Vercel](https://vercel.com/changelog/chat-sdk-reactions-and-ephemeral-messages-on-teams)  
Feed7 permalink: https://feed7.dev/p/chat-sdk-reactions-and-ephemeral-messages-on-teams-1e9k504  
Published: 2026-07-31T00:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

Chat SDK’s Teams adapter adds reactions, user-only ephemeral messages, custom token supply, and routing fixes useful for building safer agent approval and progress flows.

## Source Summary

The Teams adapter now supports **reactions** and **ephemeral messages** through the shared Chat SDK API. It also exposes author emails, accepts a custom token factory, shows native DM status, and fixes group routing and mention conversion.

## Practical Implication

Use targeted messages for permission prompts or user-specific agent output, and reactions or native status for lightweight progress feedback. The **custom token factory** removes the need for a static client secret on runtimes without Azure IMDS.

## Agent-Ready Context

The Teams adapter now supports **reactions** and **ephemeral messages** through the shared Chat SDK API. It also exposes author emails, accepts a custom token factory, shows native DM status, and fixes group routing and mention conversion.

Use targeted messages for permission prompts or user-specific agent output, and reactions or native status for lightweight progress feedback. The **custom token factory** removes the need for a static client secret on runtimes without Azure IMDS.

These capabilities apply specifically to the Microsoft Teams adapter. The material does not describe delivery guarantees, supported reaction sets, or how ephemeral content behaves under Teams retention policies.

## Connected Context

Feed7 judgment across 318 accumulated Signals:

This makes Teams a more capable surface for interactive agents, especially where approvals, private responses, progress cues, and non-static authentication matter. It strengthens the shared-adapter approach while also showing that channel parity remains uneven: these additions are Teams-specific, and retention and delivery semantics still require platform-level validation.

- [Chat SDK adds X adapter support](https://feed7.dev/p/chat-sdk-adds-x-adapter-support-1tpeb4z) — The X adapter demonstrates broad channel reach but lacks streaming and supports only likes as reactions; the Teams update shows why a shared API still requires capability-aware behavior per adapter.
- [Use any Chat SDK adapter with eve](https://feed7.dev/p/eve-chat-sdk-channel-03h905c) — eve supplies the cross-adapter agent layer and approval/proactive-send patterns, while these Teams capabilities make that abstraction more useful for targeted permission prompts and lightweight status feedback on one enterprise channel.
- [Introducing Claude Tag](https://feed7.dev/p/introducing-claude-tag-042b1r5) — Claude Tag confirms demand for persistent enterprise agents inside messaging channels, while the Teams update supplies lower-level interaction primitives for builders implementing comparable channel-native workflows.

## Context Map

- Layer: tools
- Domains: coding
- Topics: agent-sdks, tool-use, enterprise

## Uncertainty

- These capabilities apply specifically to the Microsoft Teams adapter. The material does not describe delivery guarantees, supported reaction sets, or how ephemeral content behaves under Teams retention policies.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.