Windows and Linux

  • Desktop app
  • All plans
View as Markdown

What it does

AgentsRoom desktop runs on macOS, Windows and Linux with the same interface, the same settings and the same mobile pairing. On Windows the agent terminals run through the native console layer (ConPTY) with PowerShell, agent CLIs are found on the Windows PATH (including .cmd shims installed by npm), and git diffs handle Windows paths and CRLF files. On Linux the app behaves like on macOS. Keyboard shortcuts use Ctrl where macOS uses Cmd.

Where to find it

  • Downloads: the site's download page, sections Windows and Linux, with an Installing on Windows / Installing on Linux help modal.
  • Windows: an installer for x64 and ARM64; you can choose the installation directory, installed per user.
  • Linux: a .deb package (recommended on Ubuntu, Debian and derivatives) or a portable AppImage for any distribution.

How to use it

  1. Windows: download the installer. If the browser flags it, choose Keep; if Windows Defender shows the blue SmartScreen screen, click More info then Run anyway. Run the installer and pick a directory if you wish.
  2. Linux .deb: double-click it in the software center or install it from a terminal; trailing debconf and apt warnings after "Setting up desktop" are harmless.
  3. Linux AppImage: make the file executable and run it. On Ubuntu 22.04 and newer install FUSE first if it refuses to start (sudo apt install libfuse2). A libz.so error means a corrupt download: fetch it again.
  4. Launch, install or sign in to your agent CLIs as on macOS; the setup assistant detects them.

Settings

  • disableHardwareAcceleration (global, Settings > Appearance > Rendering > Disable hardware acceleration): draws the interface on the processor instead of the graphics card. Off by default. Turn it on when a faulty display driver corrupts the window, and only then: CPU rendering costs performance everywhere else. The switch reads Hardware acceleration on or Hardware acceleration off (CPU rendering), and once changed the row says Applies at the next launch. next to a Restart now button.

Nothing else is platform-specific. Platform-dependent labels in Settings tell you what applies (for example the wake-timer status under Settings > Terminal explains that Windows uses the Task Scheduler and that wake timers must be allowed in the power plan).

Agent tools (MCP)

None specific. The AgentsRoom MCP server works identically on the three systems.

Providers

All providers that ship a CLI for the platform. Detection probes the PATH plus the usual Windows locations (npm global folder, WindowsApps, scoop, cargo). A CLI that is not distributed for Windows or Linux is simply absent from the list.

Mobile

The phone pairs with a Windows or Linux desktop exactly like with a Mac.

Limits

  • Windows installers are code-signed and timestamped, so Windows names the publisher, but SmartScreen trusts each new build by reputation and AgentsRoom ships often: a brand-new version can be flagged for a few days. Nothing is wrong with the file.
  • Some antivirus products have quarantined unsigned older builds; if the app "disappears", reinstall the current version.
  • Windows performance: process creation and file access are much slower than on macOS, and Chromium may fall back to software rendering in a VM or over Remote Desktop, which makes typing feel laggy. Running on real hardware with a working graphics driver fixes most of it.
  • A display driver that corrupts the window is the driver's doing, not the app's: nothing the interface draws can repaint around it, which is why the only answer is the Disable hardware acceleration switch. It is read at startup, so it never takes effect on the running window.
  • Windows: the hidden-terminal reading of a CLI's /usage or /status screen (the only quota source for Grok and Kimi, the fallback for Claude and Codex) is available since 1.173.0; before that the Grok and Kimi gauges were missing on Windows. It is slower there, because a PowerShell profile can take several seconds to reach its prompt. Codex session detection uses a working-directory heuristic instead of an exact match.
  • Zoom shortcut: Ctrl + may require Ctrl = without Shift on some layouts; the View menu items always work.
  • Linux: when the display server or compositor crashes (seen under WSL2 with WSLg), the app cannot survive it, but since 2026-09-24 it relaunches itself a few seconds after the display comes back and restores its consoles and team runs the usual way (Restore Session). At most three relaunches per ten minutes; a crash unrelated to the display is never relaunched. Nothing to set, and nothing of the kind on macOS or Windows.
  • Cloud Agents, tunnels and the relay do not depend on the OS.

Common questions

  • Windows says "Unknown publisher" or blocks the installer. Click More info, then Run anyway. The installer is signed; the warning is SmartScreen reputation on a fresh build.
  • AgentsRoom vanished when my display restarted under WSL2 / Linux. Since 2026-09-24 it comes back by itself once the display answers again, with its consoles and team runs restored. If it does not, update AgentsRoom.
  • Which Linux package should I pick? .deb on Ubuntu, Debian and derivatives; AppImage elsewhere. Both auto-update.
  • Does the ARM64 Windows build exist? Yes, the installer covers x64 and ARM64.
  • The app is slow on my Windows PC. Check you are not in a VM or Remote Desktop session and that the graphics driver is active; software rendering is the usual cause.
  • Noise or "frost" creeps across the window, and text garbles then clears when I hover it. That is the display driver corrupting what the graphics card draws. Settings > Appearance > Rendering > Disable hardware acceleration, then Restart now: the interface is drawn on the processor instead and the artefacts go. Turn it back off if a driver update fixes your machine.

Related