Anode
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AnodeOpen Notepad in the background seat, type 'Hello', and send me a screenshot."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Anode — a background Windows desktop for AI agents
Computer-use agents on Windows 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 any 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.
Install in 3 commands
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 installed Claude Code and/or CodexRestart 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: requires Windows 10/11 Pro, Enterprise or Education (not Home), x64. The seat is a Windows child session running as your user: desktop isolation, not a security sandbox. Ctrl+Alt+Shift+K stops it. Unsigned builds may trigger SmartScreen. No telemetry.
Related MCP server: opencode-gui-bridge
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 showopens the viewer andanode hidecloses it. Ctrl+Alt+Shift+K oranode killsigns 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, agents can listen to browsers and games in the seat, and play 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 1024x768 to 4K and portrait at 100-500%, then get the startup display back when they finish. 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 work in consoles such as Google Play Console in a seat browser profile you sign in to once. See Android apps and web consoles.
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.ps1The 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, thenscoop install anode/anode. Runanode quitand close MCP clients using Anode beforescoop update anode.Claude Code plugin: with
anodealready on your PATH (the installer above or Scoop), run/plugin marketplace add skulitom/Anode, then/plugin install anode@anodeinside Claude Code. It registers the MCP server and theanode-desktopskill but does not installanode.exe. Use it oranode 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 CLIssetup 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-HostIf 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-HostPowerShell users: piping to Out-Host (or Out-String) makes PowerShell wait for this GUI
executable and display its output. Scripts should check $LASTEXITCODE after each command.
For agents
Prefer Anode for native Windows GUI automation and headed app/browser tests that should leave
the user's main desktop available; use direct APIs, file tools and headless tests otherwise.
Call anode_guide or run anode guide --json for setup-free guidance. seat_status never starts
anything. Call seat_lease with action: "acquire" before desktop work; it starts a hidden seat
if needed and waits in line while another agent works. Each desktop action keeps the lease, so
renew only across pauses longer than 120 seconds, and release when finished. The MCP prompt
desktop_test walks through it: /mcp__anode__desktop_test in Claude Code after
anode configure, or type / and search for desktop_test with the plugin.
See the agent guide, portable skill
and llms.txt documentation index.
How it works
flowchart LR
subgraph yours["Your session: your mouse, keyboard and apps"]
agent["Claude Code / Codex / any MCP client"] -- "MCP (stdio)" --> mcp["anode mcp"]
mcp -- "named pipe" --> daemon["Anode daemon<br/>viewer + Stop button"]
end
subgraph seat["The seat: a background Windows child session"]
host["seat host<br/>screenshots, input, UI Automation, command jobs"] --> apps["apps, browsers, builds, games"]
end
daemon -- "named pipe" --> hostDocumentation
I want to… | Start here |
Install, update or uninstall | |
Connect Codex, Claude Code, Claude Desktop, VS Code or Cursor | |
Share the desktop between agents | |
Help an agent discover and choose Anode | |
Run apps, control the viewer or use a gamepad | |
Look up a CLI command or option | |
Test native apps and browsers | |
Test apps at other resolutions and scaling | |
Test Android apps, or work in web consoles as you | |
See worked examples | Claude Code + Steam, headed Playwright fixture used by the development test |
Inspect windows and accessible controls | |
Understand permissions and isolation | |
Know what data Anode handles | |
Diagnose startup, sign-in or capture problems | |
Integrate a client | |
Understand the implementation | |
Publish directory listings as the owner |
Limits to know
One connected child session per machine. Agents and CLI clients share that seat.
Files, accounts, network ports and application singletons are shared. Steam games run in the seat using the Steam client on your desktop, which stays there, without the overlay or Steam Input; other single-instance apps may already belong to your main session. Use separate browser profiles for browser testing.
Capture and input depend on Windows and the application. Use
anode capabilitiesto check; a connected seat alone does not prove screenshots or input work.Protected video and exclusive fullscreen may not capture. Without HidHide, virtual gamepads also reach games on your main desktop.
Privacy Policy
Anode sends nothing to its maintainers: the runtime has no telemetry, update check or remote endpoint. Screenshots and UI text go only to the MCP client or CLI that asked for them, and that client may send them to its model provider. Read the privacy policy.
Build and contribute
Install the .NET 10 SDK, then:
git clone https://github.com/skulitom/Anode.git
cd Anode
powershell -NoProfile -ExecutionPolicy Bypass -File scripts\build.ps1 -QuickTest -PackageThe executable and docs are in dist; the downloadable bundle and checksums are in
artifacts\release. Quick checks require no seat and send no desktop input.
Contributing and release process.
Found a problem? Report a bug or suggest an improvement.
Credits and license
Built on documented Windows child sessions, the Remote Desktop ActiveX control and Task Scheduler. Optional gamepad support uses ViGEmBus, and HidHide keeps the virtual controllers inside the seat. Related projects: Cathode, LibreAutomate and BetterGI.
This server cannot be deployed
Maintenance
Related MCP Connectors
Eyes and hands on real Windows PCs — observe, click, type via Glasswarp API.
Drive real devices from your AI Coding tool. Embed a client SDK (Unity, Godot, Flutter, iOS/macOS, Android, React Native, Web) in your app, then capture screenshots, traverse the UI tree, inject taps and key events, and run automated test tasks on the physical device over a secure relay.
Securely control computers you explicitly pair through files, terminals, processes, screenshots, desktop UI/input, clipboard, browser automation, diagnostics, and document tools.
Stealth web automation for AI agents. Login, signup, navigate, screenshot.
Related MCP Servers
- AlicenseAqualityCmaintenanceAllows AI clients to see and control Windows 10/11 desktops via MCP, with screenshots, UI Automation, Chrome CDP, keyboard/mouse, and terminal using semantic element targeting.30541 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to control Windows GUI by listing and focusing windows, capturing element snapshots via UIA/OCR/CDP, performing clicks/inputs/scrolls, verifying changes, waiting for screen updates, taking screenshots, and obtaining visual descriptions.2-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to autonomously control Windows 11 and 10 desktops via sub-10ms screen capture, native UI Automation element inspection, and zero-lag keyboard and mouse input. Combines a visual plane with a semantic plane and stall detection so agents can operate real applications reliably without vision-only guessing.34 npm178 PyPI4MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to see and operate a Windows PC through mouse, keyboard, screenshots, OCR, window control, and shell commands.-