EtherAssist
  • Administration
  • Agent mode
  • Integrations
  • Getting Started
  • Models and AI
  • Partner portal
  • Security & Compliance
  • Settings
  • Support
  • Supported topics
  • Tools
  • Using EtherAssist
  • Windows 11 readiness
  • PowerShell
  • Release Notes

Version 2.3.5 (Major Release)

Summary

Version 2.3.5 is a major release focused on the refreshed EtherAssist experience, clearer administration workflows, AI and regional processing wording, reliability fixes, and a major documentation refresh.

What changed

Interface refresh

  • Refreshed the main EtherAssist interface with updated branding, spacing, navigation, and surface styling.
  • Improved light-theme consistency across the application.
  • Improved chat layout, composer controls, response cards, menus, popovers, and shared modal styling.
  • Improved sidebar readability with clearer conversation grouping and date context.
  • Refined onboarding, subscription, notes, settings, and integration screens to better match the current product experience.

Administration and user management

  • Refreshed user management with a clearer Users experience, improved role and status presentation, and more consistent action menus.
  • Improved administrator-only access handling for Security & Compliance detail pages.
  • Improved user quota and notification badge state handling.
  • Improved notification drawer behaviour so read and dismissed notifications stay in sync with the sidebar badge.
  • Improved partner and customer administration screens with clearer forms, tables, billing surfaces, and organisation detail views.

AI, models, and regional processing

  • Improved AI mode and topic-source wording so users see clearer choices for general, automatic, and topic-grounded responses.
  • Improved reflective response grounding behaviour.
  • Improved model handling and documentation around agent and chat experiences.
  • Clarified regional AI processing language so customers can better understand where model and knowledge processing occurs.
  • Improved assistant memory and context handling for longer-running conversations.

Documents, templates, diagrams, and integrations

  • Improved Document Manager and document preview layouts so longer content is easier to read.
  • Refined template creation, editing, import, and document-selection workflows.
  • Improved Draw.io and PlantUML diagram rendering, sizing, and continuation behaviour.
  • Improved API and PowerShell entry points so integration options are easier to find.
  • Improved GitHub and Azure Blob source views.

Documentation refresh

  • Reworked the documentation site structure to follow a clearer task-based flow.
  • Added and refreshed screenshots across Getting Started and Administration content.
  • Added annotated screenshots for key workflows where callouts make the task easier to follow.
  • Updated the Getting Started section with Microsoft Learn-style prerequisites, step-by-step instructions, expected results, troubleshooting, and next steps.
  • Fixed hidden legacy documentation routes so duplicate sidebar entries no longer appear.

Reliability and quality

  • Added broader UI workflow, accessibility, and visual regression coverage.
  • Improved template modal scrolling and general modal behaviour.
  • Improved cache and response handling for AI workflows.
  • Improved sign-in, onboarding, and shared tenant-context reliability.
  • Improved defensive UI behaviour around menus, focus rings, and theme-specific readability.

Customer impact

  • Users get a cleaner and more consistent EtherAssist experience across chat, administration, settings, documents, templates, and integrations.
  • Administrators get clearer user management, notification, quota, and security-page behaviour.
  • Documentation now better reflects the current interface and includes more task-oriented guidance.
  • Existing customer workflows should continue to work without configuration changes.

Next steps

  • Review the refreshed user management, settings, documentation, and integration pages that apply to your organisation.
  • Tell users about visible interface and navigation changes before rollout.
  • Validate any tenant-wide administration or security settings after the update.
  • Contact support if a documented behaviour does not match your environment.