SaaS Release — 2026-04-27 to 2026-05-10
Window: 2026-04-27 → 2026-05-10
Highlights
Section titled “Highlights”No headline features this cycle — see Integrations, Improvements, and Fixes below.
Integrations
Section titled “Integrations”Microsoft Outlook: list available email addresses
Section titled “Microsoft Outlook: list available email addresses”The Microsoft Outlook Email integration can now enumerate the email addresses a connected account has access to, making downstream address selection in agents more reliable.
ServiceNow: knowledge-base custom field updates
Section titled “ServiceNow: knowledge-base custom field updates”ServiceNow knowledge-base article updates now support custom fields, including markdown-typed fields. This unblocks workflows that need to write to instance-specific KB schemas.
Freshservice: Service Catalog APIs
Section titled “Freshservice: Service Catalog APIs”The Freshservice integration now exposes Service Catalog tools (requested items, service catalog items) alongside the existing ticketing surface.
Guardicore: refresh-token authentication
Section titled “Guardicore: refresh-token authentication”Guardicore connections now support refresh-token authentication in addition to Basic auth, simplifying long-lived deployments where rotating credentials would otherwise be needed.
Improvements
Section titled “Improvements”Command Center: credit and token usage for unlimited-credit orgs
Section titled “Command Center: credit and token usage for unlimited-credit orgs”Command Center now shows credit and token usage stats for organizations on unlimited-credit billing. These panels previously appeared blank for those orgs, hiding visibility into actual usage.
Tab and sidebar navigation polish
Section titled “Tab and sidebar navigation polish”Hover and selected states across the tab and sidebar navigation are clearer and more consistent.
Org Security: clearer Default Settings copy
Section titled “Org Security: clearer Default Settings copy”The copy in the Org Security panels (Integrations / Tools and Providers / Models) now more clearly explains what “default” means and how it interacts with per-user overrides.
Removed the legacy send_email tool
Section titled “Removed the legacy send_email tool”The legacy send_email tool has been removed from the default tool set. Email-sending workflows should use the supported Gmail or Microsoft 365 integrations, which provide richer authentication and audit controls.
Larger workflow outputs handled cleanly
Section titled “Larger workflow outputs handled cleanly”Workflow outputs that exceed the platform’s per-message size limit now fail fast with a clear error, instead of producing a problematic message that could affect workflow throughput. Workflows that produce smaller outputs are unaffected.
More reliable long-running background work
Section titled “More reliable long-running background work”Long-running background tasks now remain healthy across extended idle periods. A class of intermittent connection-drop errors that some longer-running workflows occasionally hit has been resolved.
Stop request on inactive conversations
Section titled “Stop request on inactive conversations”Requests to stop a chat that is not in a stoppable state now return a precise client-side error indicating the conversation cannot currently be stopped, instead of a generic failure.
Markdown content: no more indefinite loading on render failure
Section titled “Markdown content: no more indefinite loading on render failure”If the Markdown renderer fails to load, the chat now shows a clear error state and recovers on retry, instead of displaying indefinite skeleton placeholders.
Intercom widget and chat for users with no cookie consent
Section titled “Intercom widget and chat for users with no cookie consent”A change in cookie-consent handling had broken the Intercom widget and Kindo chat for users who had denied or not yet answered the consent prompt. Both flows now work regardless of consent state.
Model IDs in API responses: consistent provider prefixes
Section titled “Model IDs in API responses: consistent provider prefixes”API responses that include model identifiers now consistently include the provider prefix (for example anthropic/claude-3-sonnet), bringing them into parity with the rest of Kindo’s model handling.