Version 26.11 of the Ethora platform was tagged on 1 November. It collects the October development cycle, our largest by commit count, and the thread that runs through it is calls: a 1:1 call can now go peer to peer between the two devices, a group room can hold a call, and a call can be scheduled with a calendar invite and a join link. Around that, every client caught up with the web chat SDK, including a first Flutter SDK, and AI agents learned to write their own flows and collect what people submit through them.
Here is what shipped and why it matters.
What is new in Ethora 26.11?
- Peer-to-peer 1:1 calls, group calls in members-only rooms, and scheduled calls with calendar links, reminders and a join link
- Android, Swift and Flutter chat SDKs with the web feature set: calls, encrypted rooms, albums, receipts, reactions, search and push
- The Ethora app as an installable web app, with web push and an unread badge on the icon
- Pushes that are encrypted per device, or say nothing at all, with reaction pushes, sender avatars and texts in the device’s language
- Albums with captions, delivery and read receipts, a redesigned viewer, and Block user in 1:1 and group chats
- AI agents that generate a flow from a description, simulate it, and record completed runs as submissions with a webhook and CSV
- Agent Memory, a Try it chat, scheduled website re-crawls, and an AI usage ledger per app
- Website widget appearance saved on the app, a visitors tab, and a WordPress plugin that re-indexes pages the moment they are published
- Apps isolated from each other on the chat server, rooms hidden from directory discovery, a TURN server in the installer, and Ethora Core on Azure Marketplace
How do calls work in Ethora 26.11?
Three kinds of call now share one set of buttons in the chat header.
A 1:1 call goes peer to peer when the server allows it. The two devices open a direct WebRTC connection and exchange the offer, the answer and the network candidates as chat messages, so the media never passes through a media server. TURN and STUN servers come from your own platform, and a self-hosted installation can run a TURN server next to the stack with one setting in the deployment file. In an encrypted room the call media key travels over the room’s end-to-end encrypted channel, so the server never holds it.
A group call in a members-only room runs over LiveKit. The call screen is a grid of everyone in the room with the speaker outlined and a mute badge on anyone muted. The call goes on while anyone is in the room, and one member declining does not end it for the others.
A scheduled call starts from a Schedule call button next to the call buttons. You give it a title, a time, a duration and a video or audio type, and every member of the room sees an invite card with Google Calendar, Outlook and .ics links. The card opens for joining from 15 minutes before the start, a reminder push goes out before the call, and the join link opens a pre-join screen where nothing uses the camera or microphone until you tap Join call. Join links open in the web chat SDK, in the installed web app and in the mobile app through universal links.
Incoming calls also ring properly everywhere: on the web as a sticky notification with Answer and Decline even when the tab is hidden, on iOS through CallKit from a VoIP push, and on Android from the host app’s call notification.
Read more on the voice and video call API page: https://ethora.com/voice-video-call-api/
Which SDKs are now on par with the web chat SDK?
All of them. The React Native SDK took the web foundation earlier in the cycle and then added opt-in encrypted rooms, receipts, albums, message search, swipe actions and a new voice player across fifteen releases, from 26.8.7 to 26.10.12.
The Android SDK and the Swift SDK received the current web feature set in one merge each: 1:1 and group calls, OMEMO 2 end-to-end encryption for rooms marked as encrypted with sealed attachment uploads, multi-file messages with an album grid, delivery and read receipts, reactions and reply threads, message search and jump to message, room management and the public chats directory, push registration with credential recovery, message translation, and a dark palette. The Swift SDK adds a side-by-side room list and chat on iPad; the Android SDK adds a foreground service and an incoming-call notification.
A Flutter SDK is now in the repository with the same set, including calls, push and a production example app. It is a first version, and we would like to hear from Flutter teams who try it.
See the SDK pages: https://ethora.com/chat-sdk/chat-sdk-for-react-native/ , https://ethora.com/chat-sdk/chat-sdk-reactjs-web/ and https://ethora.com/chat-sdk/
Can I install the Ethora app without an app store?
Yes. The Ethora app now ships as an installable web app at pwa.chat.ethora.com, with the same flow as the mobile app: enter a workspace (any tenant address, including your own self-hosted cluster), sign in with email or Google, and chat with calls, inline translation and the built-in profile and settings. It installs from the browser on Android and desktop, shows an Add to Home Screen guide on iOS, receives web push and shows the unread total on the app icon. A tenant app opens with its own name, logo and primary colour, so a white-label deployment needs no store listing to reach a phone.
More on white-label options: https://ethora.com/chat-sdk/white-label-chat/
What changed in push notifications?
Push notifications were rebuilt end to end. There is one notification per chat that updates in place, the unread total is the badge, photo and video pushes carry a thumbnail, and messages a dead session had swallowed now reach offline delivery.
Two privacy levels sit on top. With encrypted pushes, each install registers a device key, the push service seals every chat push for that key, and Apple and Google relay only ciphertext; the app opens the box on the device. With generic push content, an app owner switches every chat push to “New message” or “You have received N new messages”, with no text, names or pictures, and child apps inherit the setting from their parent, so one switch covers a whole tenant.
Pushes also learned to carry a reaction to your message (silent, rate limited), the sender’s avatar next to the text, and fixed texts in the device’s language, with English, French and Spanish today.
The healthcare page explains where these settings fit a compliance setup: https://ethora.com/healthcare-chat-sdk/
What is new in the conversation itself?
Up to ten files go in one message, laid out as an album with the text as its caption. Your own messages show delivery and read ticks, with a tooltip that names who has read them, and receipts are coalesced in big rooms so a busy group does not flood the server. A redesigned full-screen viewer pages through pictures, videos and a continuously scrolling PDF. Reactions and bubbles were redrawn with tails. The room list previews media.
Block user works in 1:1 chats and in group chats, where a blocked member’s messages are replaced by a placeholder. Owners and moderators edit a group chat’s name, description and picture from its profile. An app’s chat component look can now be edited in the admin console with a live preview and applied to open chats without a reconnect.
What can AI agents do now?
An agent’s long-term notes are called Memory, its prompt is called Instructions, and both can be tested in a Try it chat before anything is deployed, with the knowledge excerpts it used shown under each answer. Knowledge search combines meaning with exact keywords, so product codes and names are found. The websites in an agent’s knowledge are re-crawled on a schedule, and the WordPress plugin re-indexes a page the moment it is published.
Flows written by AI. Describe what an agent should do, and the console generates a flow, shows it on a map and lets you try it in a simulator before it goes live. Every completed run is recorded as a submission: a Submissions tab lists them, sends them to a webhook, exports CSV and keeps them for a retention period you set. A lead form, an intake questionnaire or a booking flow can now be built, tested and connected to your systems without writing the script by hand.
New agents come with a setup checklist, you can invite colleagues to manage an app with a role, and a shareable link opens a person’s own private chat with an agent, which is how a class or a client list gets one link each. An AI usage ledger shows what every app’s tokens went on, by purpose, agent and model.
The AI SDK page covers agents, flows and knowledge: https://ethora.com/ai-sdk/
What changed for the website AI widget?
The widget’s appearance is saved on the app, with a live preview, theme presets and a colour picker, and every embed picks it up without re-pasting the snippet. Website visitors get their own tab under Users with the page the chat started on and the transcript. The widget gained a language picker, a resizable panel and quick-reply buttons, creates a visitor session only when someone reaches for the chat, and keeps the opening greeting at the start of a restored conversation. The WordPress plugin is at 1.8.1 with a Refresh website knowledge now button.
Embed the widget: https://ethora.com/ai-sdk/embeddable-ai-agent-script/
What changed for self-hosted servers?
Apps on one chat server are now isolated from each other: no message, presence or query crosses between apps, and server-to-server federation is off, since nothing in the deployment uses it. Rooms are hidden from directory discovery by default, with a migration for existing rooms on the next update. A TURN server for peer-to-peer calls runs from the installer. Only one install or update runs at a time, and the deployment environment file is written atomically. Monitoring raises an alert when a core container goes missing or restarts. Ethora Core is live on Azure Marketplace, every cloud image runs the same Compose bundle, and the Enterprise modules are Compose profiles.
Operators also got a second round of Server settings in the console: tabs for chats, users, AI, email and reports, system and API, module cards with each Enterprise module’s state and install command, and switches that turn AI agents or app-level encryption off for a whole install.
Self-hosting details: https://ethora.com/chat-sdk/self-hosted-chat-server-aws/ and https://ethora.com/get/
What changed for AI assistants and MCP?
The MCP server gained agent and widget tools (try an agent, check and rebuild its knowledge, stop a crawl, read and set the widget appearance), tools to list and refresh the websites in an agent’s knowledge, and account memory so a client that opens a session per call keeps its selected app. Every tool carries explicit annotation hints with a reason. A Claude Code skill adds Ethora chat to a React or React Native app from one prompt. Version 26.11.0 of the MCP server is tagged alongside the platform.
Connect an assistant: https://ethora.com/ai-sdk/mcp-server/
How do I try Ethora 26.11?
- Free tier: create an app at https://app.chat.ethora.com , open a group chat and press Schedule call. The invite card, the calendar links and the pre-join screen all work on the free tier.
- Developers:
npm install @ethora/chat-component@26.10.10or@ethora/chat-component-rn@26.10.12; the Android, Swift and Flutter SDKs are on GitHub under github.com/dappros. - Self-hosting: https://ethora.com/get/ lists every install channel, from AWS and Azure Marketplace to a one-line installer.
- Full changelog: https://github.com/dappros/ethora/blob/main/RELEASE-NOTES.md
Talk to us about an enterprise deployment: https://ethora.com/pricing/