Skip to navigation

Release notes

September 30, 2026

Introducing Messaging

Messaging is Ada’s new chat experience for websites and mobile apps. It replaces Chat and the legacy Chat SDKs: the embed2.js script tag, the @ada-support/embed2 npm package, and the iOS, Android, and React Native SDKs. Chat retires on December 15, 2026.

What end users notice

Messaging changes the conversation in four ways that end users can see.

  • Replies stream as the AI Agent writes them. An end user reads the first sentence while the Agent writes the rest.
  • When Enable image uploads to your AI Agent is enabled, an end user can attach an image for the Agent to read. See Images.
  • When the network drops, the conversation restores and recovers missed messages after the connection returns.
  • The chat window supports keyboard operation, screen readers, and right-to-left languages.

Your appearance, launch, handoff, and reporting settings carry over. Two report counts can look different after the move. See Reporting and surveys.

What this means for you

How your Agent moves to Messaging depends on how your website or app loads it.

  • Script tag. If your website uses the embed2.js script tag, you do not need to change your code. Ada moves each Agent to Messaging in stages, starting October 1, 2026. After the move, your dashboard shows Messaging in place of Chat. See the web script migration guide.
  • npm package. If your website uses the @ada-support/embed2 npm package, your developers replace it with the Messaging SDK package before December 15, 2026. Ada cannot make this change for you. See the npm migration guide.
  • Mobile SDKs. If your app uses a legacy iOS, Android, or React Native SDK, upgrade to the Messaging SDK for that platform before December 15, 2026. See the upgrade guide for iOS, Android, or React Native.

For developers

Messaging also adds controls for custom apps and rollouts. On desktop, a custom app can size, position, and style its frame with setFrameStyles, including a transparent background, and read appearance.hostViewport to fit the available space. Launch Controls now serves the alternative Agent in the Messaging web SDK.

To choose a setup, use the integration chooser. For the SDK reference, start with the Messaging SDK overview. To see working examples, open the integration examples.

September 30, 2026

Availability rules for Knowledge API sources

You can now set availability rules on a knowledge source that you create through the Knowledge API. Every article that the source adds gets those rules automatically. Set them when you create the source with availability_rules on POST /v2/knowledge/sources, so the first import is covered, or later with PATCH /v2/knowledge/sources/{id} or from the Sources tab with the Settings button beside the source.

Rules on the source apply to articles added after you save them. Existing articles keep their own rules. A new article whose request omits availability_rules gets the rules of its source. An article that sends its own availability_rules keeps them.

For more information, see Connect through the Knowledge API and Sources in the API reference.