Back to the changelog

v0.85.10

August 27, 2026

**Reorganized settings, guides one click away, and summaries that admit their age.** The Management section becomes Settings with a readable order, every page gains a question mark that opens the right guide chapter in its own window, and the AI Summary stops presenting itself as current when something important has happened in the meantime.

  • Design

    Settings, reorganized

    The **Management** section is now **Settings**, grouped by topic: company profile and behaviour, connectors and credentials, data and security, automation plan. Some entries were renamed to say better what they hold — "Email sending" becomes **Email**, "Integrations" becomes **Automation**, "API" becomes **API Keys** — and two new ones appear: **Flow templates**, a shortcut to the templates page, and **Integration Packs**, for now a placeholder for a feature on its way. Page addresses are unchanged: your bookmarks keep working.

  • Feature

    The guide where you need it

    Next to every page title — and every Settings section — you now find a **(?)** that opens the matching guide chapter in its own window, without losing what you were doing. Those windows open in a lean mode, content only and no sidebar, with a link at the bottom to jump back to the full app whenever you need it.

  • Improvement

    An old summary no longer looks fresh

    An item's AI Summary reflects what was true when it was generated. If an SLA escalation fired right afterwards, it kept showing itself as valid and "green": anyone using it to set priorities underestimated a case that needed attention. The item now declares the summary out of date — and **names what made it so**: SLA escalation or breach, an unresolved timeout, stalled automation, queue wait. Reopening the item regenerates it: keep in mind this means a fresh call to your AI provider.

  • Improvement

    Changing a task type no longer blocks saving

    A task created as Automatic and later switched to Manual silently kept the previous type's fields. Saving was rejected because of a field no longer visible anywhere, and the only way out was to delete the task and start over. Now only what the chosen type expects is sent on save — and while you switch types to explore, whatever you had already written stays where it is.