# Use any Chat SDK adapter with eve

Source: [Vercel](https://vercel.com/changelog/eve-chat-sdk-channel)  
Feed7 permalink: https://feed7.dev/p/eve-chat-sdk-channel-03h905c  
Published: Unknown  
Trust: Official Source (official_source)

## Why Included

eve’s Chat SDK channel lets one agent span messaging adapters while retaining threads, approval cards, proactive sends, webhook handling, and overridable defaults.

## Source Summary

eve’s new **Chat SDK channel** connects an agent to adapter-backed surfaces such as Messenger, WhatsApp, Resend, and Liveblocks. It mounts adapter webhooks, posts replies, persists threads, renders approval requests as cards, and reports failures in the conversation.

## Practical Implication

Builders can keep normal Chat SDK handlers and hand messages to the agent by calling **send** inside a handler. This is useful when one agent must retain conversation state across replies and scheduled proactive messages while sharing channel behavior.

## Agent-Ready Context

eve’s new **Chat SDK channel** connects an agent to adapter-backed surfaces such as Messenger, WhatsApp, Resend, and Liveblocks. It mounts adapter webhooks, posts replies, persists threads, renders approval requests as cards, and reports failures in the conversation.

Builders can keep normal Chat SDK handlers and hand messages to the agent by calling **send** inside a handler. This is useful when one agent must retain conversation state across replies and scheduled proactive messages while sharing channel behavior.

The built-in behavior is overridable, but the material does not describe production storage, authentication, delivery guarantees, or adapter-specific constraints. The example uses in-memory state, so persistence architecture still needs an explicit production choice.

## Context Map

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

## Uncertainty

- The built-in behavior is overridable, but the material does not describe production storage, authentication, delivery guarantees, or adapter-specific constraints. The example uses in-memory state, so persistence architecture still needs an explicit production choice.

## 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.