<style> /* Reveal x-cloak content so sidebar branch lists and closed-state chips render — EXCEPT the mobile slide-in backdrop, which would otherwise cover the whole viewport in black/40 with no way to dismiss (the dismiss handler is x-on:click="mobileHeader = false" and can't fire without Alpine). */ [x-cloak]:not([x-show="mobileHeader"]) { display: revert !important; } /* (1) Force every version card OPEN so all release-notes content is visible. Overrides the default `.rn-ver-body { grid-template-rows: 0fr }` from release-notes.css, which is normally lifted to `1fr` via Alpine's `:class="{ 'rn-ver-body--open': open }"`. */ .rn-ver-body { grid-template-rows: 1fr !important; } /* (1b) Strip `hidden="until-found"` from collapsed card bodies. WEB-3164 added that attribute on cards 2..N (the first card omits it, see the `{% unless forloop.first %}` in release-notes-cards.eleventy.liquid) so Chrome/Edge browser find-in-page can reveal text inside collapsed bodies and fire a `beforematch` event Alpine catches to pop the card open. Alpine's `x-effect` directive normally removes the attribute when `open` flips true — but without JS that directive never runs, so cards 2..N stay hidden via either `content-visibility: hidden` (Chrome/Edge/Safari 17+ resolve `hidden="until-found"` to that) or `display: none` (older Safari / unknown browsers treat it as a plain boolean `hidden`). Rule (1) above lifts the SCSS-based grid-rows collapse but does NOT override `[hidden]` — the attribute applies a higher-priority `display: none` / `content- visibility: hidden` that wins over grid-template-rows. This rule covers both browser-engine paths: `display: revert` restores the element's normal display (the `grid` utility on the wrapper), `content-visibility: visible` overrides the modern-browser path. */ .rn-ver-body[hidden] { display: revert !important; content-visibility: visible !important; } /* (2) Hide controls that can't do anything without JS so the UI doesn't lie about being interactive: the expand/collapse chevron, the closed-state category chips (Security 3 / Features 5 / …), the section-level expand-all toggle if reintroduced, and the cursor-pointer hint on the header. */ .rn-ver-chevron, .rn-ver-chips, .rn-toggle-all { display: none !important; } .rn-ver-header { cursor: default !important; } /* (3) Hide status pills (Current / Beta / Extended maintenance) and the matching sidebar dots. Pills are rendered server-side from productInfo.json at build time and are accurate at publish — but a stale cached page in Sparkle could surface them on a version that is no longer "Current" by the time the user opens RDM, so hiding them entirely under no-JS removes the whole class of misleading-stale-pill failure modes. */ .rn-ver-tag-line, .rn-status-pill, .rn-status-dot { display: none !important; } /* (4) Sidebar branch chevrons stay frozen in the "closed" rotation without Alpine to flip them — drop them since the branch lists below are already revealed by the x-cloak rule above. */ .rn-toc-branch-head > span:first-child { display: none !important; } /* (5) Hide mobile-only chrome whose Alpine click handlers can't fire: the top mobile menu-open bar and the sidebar's mobile close bar. Both gate `mobileHeader`, which never toggles without JS. */ .rn-main-header, .rn-sidebar > div:first-child { display: none !important; } </style>

Release notes

Release notes

RDM 2026.2 brings practical AI automation to daily IT operations

Adam Listek · June 23, 2026

Table of contents

With Remote Desktop Manager 2026.2, the AI assistant takes a meaningful step forward toward being a practical operator feature you can lean on day to day.

At Ignite in late 2025, we showed what was possible by driving RDM through Visual Studio Code and RDM’s local MCP server, a powerful proof of concept that demonstrated an assistant that can understand intent and execute real work in live sessions.

In 2026.2, that capability becomes even easier to use because the workflow is simply in RDM: the assistant understands which sessions are open and can carry out the steps within them. Fewer tool hops, less “copy this command, paste it there,” and more completed tasks.

Here is what that looks like in practice:

  • One place to work: prompts, context, and actions stay in RDM, rather than bouncing between tools.
  • Multi-session execution: a single request can span Windows RDP, Linux SSH, and more.
  • Governed automation: approvals are built in, so you can move fast without giving up control.

Under the hood, RDM exposes structured capabilities through its built-in Model Context Protocol (MCP) server. The model decides what to do, and RDM executes it against your RDP/SSH/Agent sessions, with governance controls layered in.

Where it pays off day to day:

  • Setup and tooling: install what you need across machines without rebuilding the same command sequences.
  • Maintenance: apply updates, then leave a clean record you can paste into a ticket or handoff.
  • Triage: pull the top issues from logs quickly, so you spend time fixing instead of filtering.

Three real-world wins with the AI assistant

Install across Windows and Linux without switching tools.

One prompt installs Sysinternals Suite via WinGet in Windows, installs btop via APT in Ubuntu, and launches the right tools. The point is not the packages; it is the pattern: one intent, two sessions, and the usual fiddly details (like the Sysinternals EULA) handled during the run.

Patch, then produce a record.

Routine updates are rarely “run the command and move on.” This clip updates 7-Zip, checks for other pending tasks, and writes a clean summary to Notepad before jumping to Linux to update jq. That “do the work, then leave a readable trail” is what makes the assistant useful in real operations.

Quick triage, not log spelunking.

The last clip asks for the top issues on a Windows host (Event Viewer) and an Ubuntu host (system logs). The assistant iterates when the first query does not return a signal, then returns a ranked summary and concrete next steps. It is the kind of morning health check or first-response pass that usually eats up time across multiple consoles.

Governance that matches how teams operate

The approvals mode you see in the videos is intentional. Most teams will keep Default approvals on for change control. When you are in a lab, running a scoped maintenance task, or recording a demo, Bypass approvals can make sense when you want an uninterrupted run. The important part is that this choice is now built into the workflow rather than bolted on.

Faster IT operations with AI in RDM

RDM 2026.2 makes the AI assistant into an operator feature inside the tool that IT admins already use for sessions and access. Routine installs, updates, and first-pass triage can go from intent to executed work (with governance) without switching consoles.

Download the latest version of Remote Desktop Manager and try the AI assistant in one of your day-to-day tasks. Then share feedback, ideas, use cases, and any bugs you run into in the Devolutions forum.