# io.Connect Desktop 10.1 Release Highlights

**URL:** <https://community.interop.io/t/io-connect-desktop-10-1-release-highlights/547>\
**Category:** io.Connect Desktop\
**Tags:** release, News\
**Created:** [April 7, 2026, 4:00pm UTC](https://community.interop.io/t/io-connect-desktop-10-1-release-highlights/547 "2026-04-07T16:00:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![toni.petrov](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.interop.io/toni.petrov/32/17_2.png) [@toni.petrov](https://community.interop.io/u/toni.petrov)\
**Post date:** [April 7, 2026, 4:00pm UTC](https://community.interop.io/t/io-connect-desktop-10-1-release-highlights/547/1 "2026-04-07T16:00:48Z")

</div>

We’re excited to announce that **io.Connect Desktop 10.1** is here. It introduces major observability capabilities through **io.Insights** , **group visibility operations** in the default platform mode, a more flexible **User-Agent configuration** , and gives control over **username case sensitivity** in io.Connect Gateway. It also upgrades the platform to **Electron 40.8.3** , **Chromium 144.0.7559.236** , and **Node.js 24.14.0**.

### [io.Insights – Traces, Metrics, Logs](https://docs.interop.io/desktop/getting-started/changelog/10-1/index.html#new_features-ioinsights__traces_metrics_logs)

The biggest addition in 10.1 is the improved **io.Insights** implementation. io.Connect Desktop now publishes **traces** and **logs** , and also supports **custom metrics** , enabling observability for both the platform and interop-enabled apps. Few

- **Trace instrumentation** has been added across the platform and the `@interopio/desktop` library, making it easier to observe platform operations and API usage.
- **Insights API** is now available with the `@interopio/otel` package providing support for publishing OpenTelemetry **metrics, traces, and logs** from your apps.
- Custom metrics like `custom_counter`, `custom_gauge`, `custom_histogram`, `custom observable_counter` and a few more were added
- The platform configuration under the `otel` key has been extended substantially, and the available settings have been extracted into a dedicated `otel.json` schema.

There’s much more here:

- [io.Insights overview](https://docs.interop.io/insights/general-overview/index.html)
- [Insights API](https://docs.interop.io/insights/insights-api/javascript/index.html)
- [io.Insights configuration for io.Connect Desktop](https://docs.interop.io/insights/configuration/io-connect-desktop/index.html)

#### Breaking change to note

For **io.Insights** , the `defaultMetricsEnabled` property under `otel.metrics` has been renamed to `platformMetricsEnabled`.

### [Groups Visibility Operations in the Default Platform Mode](https://docs.interop.io/desktop/getting-started/changelog/10-1/index.html#new_features-groups_visibility_operations_in_the_default_platform_mode)

If you’re using the **default platform mode** , **group visibility operations** are now supported there as well. You can hide and show groups programmatically with `myGroup.hide()` and `myGroup.show(true)` without needing advanced mode.

Details here:

- Window Management \> JavaScript

### [User Agent Configuration](https://docs.interop.io/desktop/getting-started/changelog/10-1/index.html#new_features-user_agent_configuration)

The `userAgent` property is now more flexible. Besides accepting a plain string, it can also take an object that lets you choose between a clean **Chromium** user agent or a fully **custom** one, and optionally append a suffix. This can be configured **globally** in `system.json` or **per app** in the app definition.

This is useful when you need tighter control over how requests identify themselves to upstream services, while still avoiding the default Electron token when needed.

Details here:

- System configuration \> Window Settings \> User Agent
- Application configuration \> User Agent

### [io.Connect Gateway Username Case Sensitivity](https://docs.interop.io/desktop/getting-started/changelog/10-1/index.html#new_features-ioconnect_gateway_username_case_sensitivity)

By default, io.Connect Gateway treats usernames as **case-insensitive**.. In 10.1, you can now change that behavior by setting `usernameCaseSensitive` to `true` in the gateway authentication configuration.

Details here:

- System configuration \> io.Connect Gateway \> Username Case Sensitivity

* * *

Full changelog:

## [io.Connect Desktop 10.1](https://docs.interop.io/desktop/getting-started/changelog/10-1/index.html)