Release Notes - 25.2.2026
This update brings a major upgrade to the Chat Widget experience, better styling control, stronger API flexibility, smarter conversation handling, and important reliability improvements across the platform.
We’ve fully rebuilt the Chat Widget in ReactJS to improve performance, flexibility, and compatibility with modern websites and frontend setups.
What this means for you:
The Appearance section has been redesigned to make widget customisation much easier — whether you prefer visual controls or full design control.
You now have more control across areas like:
See your widget updates instantly before saving.
Why it matters:
You can now create a much more brand-aligned widget experience — from simple tweaks to fully custom styling.
The Human / Agent toggle from the Conversations UI is now available through a public API endpoint.
Previously, this could only be changed manually in the dashboard. Now it can be triggered programmatically.
human → hand the conversation over to a humanagent → return control to the AI Chat Agentconversation_idmodeIt returns the updated conversation state and mirrors the exact behavior of the UI toggle.
Why it matters:
This makes it easier to build automated handoff workflows, escalation logic, and integrations with external tools.
Conversation titles are now generated within the same OpenAI request as the assistant response.
Previously, title generation required a separate request. This update removes that extra step.
A new LLM-Driven Conversation Titles toggle is now available in Chat Agent Settings:
Why it matters:
Better efficiency, lower cost, and more control over how titles are handled.
We’ve improved the Lead Collection Form to make lead capture more structured and more useful during live conversations.
Why it matters:
Better lead capture quality, more context for agents, and smoother sales/support workflows.
We fixed an issue that could cause incomplete records to appear in webhook history when pagination was involved.
Why it matters:
Improved visibility, easier recovery, and more reliable webhook management.
JSON payloads in the Custom Function history table are now formatted more clearly.
Why it matters:
Cleaner output and easier debugging when reviewing function responses.
We’ve upgraded from deprecated grok-2-1212 to grok-3.
Why it matters:
Improved compatibility, ongoing support, and better performance going forward.
This update is focused on improving the parts that matter most in day-to-day usage:
More upgrades are on the way.