Anode background Windows desktop

Anode — a background Windows desktop for AI agents

Computer-use agents that drive your Windows desktop take over your mouse and keyboard; Anode gives them their own desktop instead. Anode is a Windows MCP server and CLI for computer use, GUI automation and UI testing. Claude Code, Codex or another local (stdio) MCP client gets a hidden Windows session with its own screen, pointer and keyboard focus, called the *seat*. The agent drives native apps and headed browsers and takes screenshots while you keep working in yours.

Recorded inside the seat with Anode 0.11.0, from real MCP tool calls. Idle time between calls is cut, and the nine clicks, which took 0.4 s, are shown four times slower.

• Who it's for: developers on Windows who let an AI agent test their desktop apps, browser pages or Android apps, or do other work in real Windows programs, while they keep using the same PC; and anyone running several agents that take turns on one shared background desktop.
• Use it when an agent has to click, type, read controls and take screenshots in native apps or a headed browser, and it must not take over your mouse, keyboard or screen.
• Don't use it when you are on Windows Home or macOS, when you need a security sandbox (the seat runs as your user, with your files and network), or when the task needs no desktop at all: an API, a shell or a headless browser test is simpler. When to use which compares the alternatives.
• Compared with BgDesk, Windows-MCP, Desktop Touch MCP, windows-computer-use-mcp and Terminator, on whether the agent moves your real pointer, with Anode's measured results: Windows desktop automation for AI agents, compared (checked 24 October 2026).
• Using Windows-MCP? Since 0.8.8, its control gate pauses the agent while you use your own mouse or keyboard. Run it inside the seat, so your input stays in your own session: Windows-MCP in the background (tested 22 October 2026 with nobody at the PC: 13 tool calls, no pause, the PC's pointer never moved; not yet measured while someone works).

Install in 3 commands

Before you start: Anode needs Windows 10/11 Pro, Enterprise or Education (not Home) on x64, and administrator rights once, for anode setup. On a managed work PC, a policy that blocks unsigned programs or keeps Remote Desktop off will stop it; see exactly what setup changes.

In PowerShell, run the first line, then open a new terminal for the next two:

iwr -UseBasicParsing https://github.com/skulitom/Anode/releases/latest/download/install.ps1 -OutFile install.ps1; powershell -NoProfile -ExecutionPolicy Bypass -File .\install.ps1

anode setup | Out-Host # in a NEW terminal: one administrator prompt, once per machine anode configure | Out-Host # registers Anode with the Claude Code and/or Codex CLIs on your PATH

anode setup can restart Remote Desktop Services, which disconnects any Remote Desktop session to this PC, so run it at the machine itself. If you sign in to Windows only with a PIN or Windows Hello, the seat needs your Windows password to sign in, and Windows may ask for it again when you create another seat: see sign-in.

Restart your agent session and ask it:

Use Anode to open Notepad in the background seat, type "Hello from Anode", and show me a screenshot.

Keep the viewer hidden and leave my main desktop available.

See Install for custom locations and offline installs, or other ways to install for Scoop and the Claude Code plugin.

Good to know: the seat is a Windows child session running as your user: desktop isolation, not a security sandbox. Ctrl+Alt+Shift+K stops it (if another program holds that shortcut, use Stop seat in the viewer or anode kill). Unsigned builds may trigger SmartScreen. No telemetry.

What can you do with it?

• Develop and test apps: run builds and local servers, collect command output, inspect native controls, test browser forms and capture screenshots in the background desktop.
• Give an agent a desktop: 41 MCP tools for guidance, screenshots, audio, mouse/keyboard input, accessibility, UI waits, display changes, Android emulators, application launches and cancellable command jobs.
• Watch or stop it: anode show opens the viewer and anode hide closes it. Ctrl+Alt+Shift+K or anode kill signs the seat out and closes every application in it, including unsaved work.
• Automate games: optional virtual Xbox 360 controller support through ViGEmBus, kept inside the seat with HidHide so you can play your own games meanwhile.
• Coordinate several agents: exclusive desktop leases and command jobs scoped to each agent. Agents share one seat and take turns; see multiple agents.
• Listen and play sound: with --audio, set when Anode starts, agents can record what plays in the seat, such as a browser or a game, and play short 16-bit PCM WAV clips. This also sends seat sound to your speakers. See audio.
• Test other displays: agents change the seat's resolution and Windows scaling while its apps keep running, from 640x480 to 8192x8192, portrait included, at Windows' scaling steps from 100% to 500%; Anode restores the startup display when they finish and reports what Windows actually applied. See test other displays.
• Test Android apps and use web consoles: agents boot your AVDs read-only on an emulator in the seat, drive them through adb, open Android Studio there on its own profile, and open web consoles such as Google Play Console in a seat browser profile you sign in to (sites may ask you to sign in again). See Android apps and web consoles.

In use: haltere, the author's research project in which a fruit-fly connectome flies an FPV drone in a racing simulator, runs the game, its capture and its virtual gamepad in Anode's seat. With HidHide installed, Anode keeps the gamepad inside the seat (haltere checks anode gamepad state), so flights continue while the user plays on the main desktop. See haltere's game setup.

The seat is a Windows *child session*: a second session for your own account, created by Windows' built-in loopback Remote Desktop feature. It has its own pointer and focus; adding a virtual monitor to your current session does not. The seat runs as your Windows user and shares your files, account and network. This is desktop isolation, not a security sandbox. Virtual gamepads stay in the seat only with HidHide installed. See security and isolation.

Install

Requires: Windows 10/11 Pro, Enterprise or Education, or Windows Server with a Remote Desktop host. The release targets x64; ARM64 is not validated. Windows Home is unsupported. Release builds include .NET; you do not need an SDK or runtime. ViGEmBus is optional.

Run in an ordinary PowerShell terminal:

Invoke-WebRequest -UseBasicParsing https://github.com/skulitom/Anode/releases/latest/download/install.ps1 -OutFile install.ps1

You can inspect install.ps1 before running it.

powershell -NoProfile -ExecutionPolicy Bypass -File .\install.ps1

The installer verifies the release archive's SHA-256 checksum, installs to %LOCALAPPDATA%\Programs\Anode, adds that folder to your user PATH and adds Anode to the Start menu, where opening it shows the viewer, and to Installed apps, where you can uninstall it. Open a new terminal afterward. Machine setup and agent registration are separate steps below.

Prefer portable? Download the ZIP, extract the entire folder, and use .\anode.exe in place of anode. Builds are currently unsigned; Windows may show a SmartScreen warning. Custom locations, offline installation, updates and removal →

Other ways to install

Both still need the one-time anode setup below; plugin users skip anode configure for Claude Code.

• Scoop: scoop bucket add anode https://github.com/skulitom/Anode, then scoop install anode/anode. Run anode quit and close MCP clients using Anode before scoop update anode.
• Claude Code plugin: with anode already on your PATH (the installer above or Scoop), run /plugin marketplace add skulitom/Anode, then /plugin install anode@anode inside Claude Code. It registers the MCP server and the anode-desktop skill but does not install anode.exe. Use it or anode configure claude, not both; see Claude Code.

Set up and connect

anode doctor | Out-Host           # reports prerequisites; no changes

anode setup | Out-Host # one administrator prompt, once per machine anode configure | Out-Host # detects installed Codex / Claude Code CLIs

setup enables Remote Desktop and child sessions. It adds no firewall rules, but can restart Remote Desktop Services and disconnect existing RDP sessions. See exactly what changes.

configure backs up client settings, registers Anode by absolute path, sets a 420-second tool timeout, and installs the discoverable anode-desktop skill. Use anode configure codex or anode configure claude to choose one client, or add --no-skill for MCP registration alone. Installed the Claude Code plugin? It already registers Anode and the skill there, so skip anode configure, or run anode configure codex to add Codex only. Restart your agent session to load the tools. Claude Desktop: add Anode to its config. VS Code, Cursor and other clients: Connecting agents.

Try it

Start and check the background seat:

anode start --hidden | Out-Host

anode capabilities | Out-Host

If Windows Hello/PIN sign-in prevents automatic login, choose Sign in… from the Anode tray icon (or the viewer's header) to request the Windows credential dialog. When starting Anode, you can also use anode start --sign-in. See sign-in troubleshooting.

Then ask your agent:

Use Anode to open Notepad in the background seat, type "Hello from Anode", and show me a

screenshot. Keep the viewer hidden and leave my main desktop available.

Or work through the CLI:

$env:ANODE_AGENT_ID = 'my-cli-task'

$lease = anode lease acquire | Out-String | ConvertFrom-Json if ($LASTEXITCODE -ne 0) { throw 'Desktop acquisition failed.' } $env:ANODE_LEASE_TOKEN = $lease.leaseToken anode exec --cwd C:\project --wait 1000 -- dotnet build | Out-Host anode windows | Out-Host anode shot seat.png | Out-Host anode lease release | Out-Host

PowerShell users: piping to Out-Host (or Out-String) makes PowerShell wait for this GUI executable and