Overview
The Messaging SDK deploys an AI Agent into websites and mobile applications. It is the next generation of Ada’s embedded chat. The Messaging SDK works with generative AI Agents.
The SDK provides a complete chat interface that supports both AI-powered and human-agent conversations. It also provides a programmatic surface, so your own code can configure, observe, and drive the conversation.
Supported platforms
Continuously delivered web runtime
The web runtime ships from Ada’s CDN. Every page load resolves the current rollout version, so fixes and improvements reach your site without a redeploy on your side.
The npm packages follow the same model. They carry TypeScript types, test mocks, and a thin loader. They never pin the runtime version. See Choosing an integration for details.
To validate a specific runtime build before it rolls out, use the ?ada-messaging-version query parameter.
What’s new in Messaging
- Control over the conversation UI. Replace the built-in UI with an app you host, through the
appUrlsetting and@ada-cx/messaging-bridge. Build that app from Lovelace, Ada’s React component library. On mobile, headless mode connects to the AI Agent without rendering any Ada UI, so you drive the conversation from your own native components. - Message delivery that survives a bad network. The SDK recovers dropped messages and restores order after a reconnect. A live-agent handoff survives a page reload. Conversation-scoped event acceptance stops a stale event from reaching a new conversation.
- Accessibility improvements. Keyboard operability, visible focus indicators, ARIA roles and labels, screen-reader announcements for incoming messages, and per-bubble sender attribution. Right-to-left layouts render in the correct direction. Automated axe checks run in CI.
- A typed developer surface.
@ada-cx/messaging-sdkcarries TypeScript types for the full SDK surface and an in-memory mock for your unit tests. Subscribe to conversation events, read the conversation, and control the client lifecycle from your own code. - Attachments in the conversation. Files pass through a live-agent handoff. In the hosted chat window, an end user can also attach up to 3 images to one AI Agent message. Enable it with Enable image uploads to your AI Agent under Config > CHANNELS > Messaging > Appearance > General.
- Identity tokens. Start sessions as a known end user with a short-lived, single-use token minted by your backend. Available on web, iOS, Android, and React Native.
Legacy Chat SDK
The Chat SDK is deprecated. The Messaging SDK replaces it.
Looking for Chat SDK documentation? See the Chat SDK docs.
Ada switches each AI Agent to Messaging by December 15, 2026. What you need to do depends on how your website or app loads the Chat SDK:
- Web script tag: No code change is required. The script loads Messaging after the switch. See Migrate from the Chat SDK web script.
- npm package: Replace
@ada-support/embed2with the Messaging SDK package before December 15, 2026. See Migrate from the embed2 npm package. - iOS, Android, and React Native SDKs: No app release is required. The SDK loads Messaging after the switch.
For details, see Introducing Messaging.
Next steps
- Pick the right integration pattern in Choosing an integration.
- Embed the AI Agent on the web with the Web SDK getting started guide.
- Embed the AI Agent in a mobile app with the iOS, Android, or React Native guides.