Windows desktop automation for AI agents: Anode, BgDesk, Windows-MCP, Desktop Touch MCP, windows-computer-use-mcp and Terminator compared
Checked on 24 October 2026: two of these six Windows desktop-automation MCP servers, Anode and BgDesk, run the agent in a separate Windows session (a child session) with its own pointer and keyboard focus, while Windows-MCP, Desktop Touch MCP, windows-computer-use-mcp and Terminator act in your own session, and each of those four has click paths that move your real pointer. We read the five besides Anode from their docs and source code and did not run them. A third route, used by Ghost, lowlevel-computer-use-mcp and computer-use-plus, drives apps with window messages (Ghost and computer-use-plus also use UI Automation), starting them on a hidden desktop in your session: by default it leaves your pointer alone, but some apps ignore message input. In Anode's live validation of version 0.11.1 (2 October 2026), with your real pointer over Anode's hidden viewer, Windows' Remote Desktop control tried 7 times to copy the agent's pointer moves to your pointer, and Anode blocked all 7; the 0.11.3 release passed its 112 quick checks for this page. Method, sources and data are below.
We make Anode. Read this as a vendor's page: our own numbers come from real runs that you can repeat, and everything about the other tools links to where we read it. If we got something wrong, open an issue and we will correct it.
The short answer
- You want to keep using your mouse and keyboard while the agent works on the same PC: Anode or BgDesk. Both give the agent a child session, a second Windows session for your account with its own screen, pointer and keyboard focus, where its clicks and typing land. Anode has more tools (41, including UI Automation reads, command jobs, display changes and Android emulators) and one seat per Windows session that your agents share in turn. BgDesk has 13 tools and splits its session into up to 12 areas, so several agents work at once, and a local web page shows each one and lets you take it over.
- You want the agent to work on your own desktop while you watch: Windows-MCP, the most starred of these (10,216 GitHub stars) and listed in Claude's connector directory. Its 0.8.8 control gate pauses the agent when you use the mouse or keyboard (details below); to run it where your input doesn't reach it, see Windows-MCP in the background.
- You want the agent in your session but without moving your pointer where it can: Ghost works
through window messages and UI Automation, with real input off unless you turn it on in its settings;
lowlevel-computer-use-mcp and computer-use-plus work in the background on a hidden desktop. Desktop Touch MCP's
click_elementand Terminator'sinvoke_elementact through UI Automation without moving the pointer, though Terminator brings the target window to the front by default; their mouse tools, Terminator'sclick_element(which puts the pointer back), Desktop Touch'sbrowser_click, and Desktop Touch'sdesktop_actDevTools and mouse routes move it. Some apps ignore message input. - You are on Windows Home, or can't run an administrator step: not Anode, and probably not BgDesk. Both use child sessions, which Anode's install guide says Windows Home can't host (BgDesk's README names no editions and says editions other than the one it was developed on are untested), and both need an administrator step once. Windows-MCP and the tools that act in your session name no edition limit.
- You need a security boundary for untrusted work: none of these. Use a virtual machine or Windows Sandbox.
Side by side
Anode's column is measured or taken from its own release record. The other columns are from each project's README, docs and source at the commit named under Sources, read on 24 October 2026, not run by us.
| Anode | BgDesk | Windows-MCP | Desktop Touch MCP | windows-computer-use-mcp | Terminator | |
|---|---|---|---|---|---|---|
| Where the agent acts | A second Windows session for your account (a child session), with its own screen; one seat, shared by your agents in turn | A second Windows session for your account (a child session), its screen divided into up to 12 areas of 1440x900, one per agent | Your session | Your session | Your session | Your session |
| Your real pointer | Not used by the agent; the seat has its own. Live check (0.11.1, your pointer over the hidden viewer): 7 of 7 copied pointer updates blocked | Not used: real input goes to the child session's own pointer, or window messages for some app types; its README reports your pointer and foreground window unchanged in its tests | Moved: Click calls SetCursorPos, then a mouse event |
Moved by mouse_click, mouse_drag, scroll (at a given point) and browser_click, and by desktop_act's DevTools and mouse routes; not by click_element (UI Automation Invoke only) |
Moved by its mouse tool and coordinate clicks in either mode (SetCursorPos and mouse_event); element clicks go through pywinauto, and the opt-in "background" mode tries Invoke first, then a real click |
Moved: click_element moves the real pointer with SendInput to click, then puts it back by default (restore_cursor); mouse_drag moves it, and its typing tools click the target, without putting the pointer back, when focusing fails; invoke_element doesn't move it |
| Your keyboard focus | Not used; the seat has its own focus | Not used; focus changes happen inside the child session | Type clicks its target first; the App tool's switch brings a window to the front |
Its keyboard tool brings the window to the front by default, except background typing into terminal-class windows; optional forceFocus; browser_click brings the browser to the front |
Element text entry focuses the control (always by snapshot index, by selector when setting text fails); its keyboard tool types into whichever window has focus; its safety doc asks you to step back | Action tools, invoke_element included, bring the target window to the front by default; most then restore your keyboard focus, but click_element and invoke_element leave it on the target unless restore_focus is set |
| How you take over or stop it | anode show opens its viewer, where Take control lets you drive the seat; Ctrl+Alt+Shift+K or anode kill signs the seat out |
Take over any agent's area from a local web page (bgdesk workplace); the tray icon stops it; bgdesk down signs the session out |
A big mouse move or Ctrl+Alt+Shift+Backspace takes over (any input once the agent has been idle 15 s); new calls are refused until you've been idle 10 s | Park the mouse in the top-left corner for 0.5 s | Moving the pointer to the top-left corner aborts pointer actions; its mouse and keyboard tools refuse to act until approve_automation opens a window (5 minutes by default), a tool the agent can call itself; element clicks and text entry aren't gated |
A stop_execution tool cancels running tools; no hotkey or corner stop found |
| Signing in to the agent's session | Automatic when Windows allows it; otherwise your Windows password in Windows' own dialog (a PIN may not work), not saved by Anode | Windows' credential prompt at first start (an account with a password; a PIN doesn't count); the password is then kept in Credential Manager | Not needed: your own session | Not needed: your own session | Not needed: your own session | Not needed: your own session |
| MCP tools | 41 (counted from tools/list) |
13 (source) | 21 (source) | 32 (README) | 20, or 22 with two opt-in tools (source) | 35 (README and source) |
| Browsers | Headed Chrome or Edge inside the seat, on its own profile | Opens a URL in your default browser; Chromium browsers get their own data folder per area, without your logins; no DevTools protocol | DOM mode through UI Automation: Chrome and Edge, and Firefox through an IAccessible2 fallback | Chrome, Edge and Brave over the DevTools protocol (started with a debugging port) | None built in; it suggests a separate Playwright server | Through its Chrome extension, in your browser session |
| Android emulators | Yes, booted inside the seat | Not mentioned | Not mentioned | Not mentioned | Not mentioned | Not mentioned |
| Windows editions | 10/11 Pro, Enterprise, Education, or Windows Server with the Remote Desktop host; not Home; x64 | Windows 10 or 11, x64 (editions not named; other editions untested) | Windows 10 and 11 (needs Python 3.14+; the 0.8.8 README still lists Windows 7 to 11) | Windows 10/11 64-bit (editions not stated); a 4-tool macOS preview | Windows 10 and 11 (editions not stated) | Windows only (editions not stated) |
| Install | install.ps1, then anode setup (one administrator prompt: Remote Desktop and child sessions) |
install.ps1 from its README (downloads the release), then bgdesk enable (administrator, once; its README: child sessions only) |
uvx windows-mcp serve (Python 3.14+, uv) |
npx -y @harusame64/desktop-touch-mcp (Node 20+) |
install.ps1 from its release (an MCPB bundle), or uv |
npx -y terminator-mcp-agent |
| Telemetry | None | None found in its source | On by default (PostHog); ANONYMIZED_TELEMETRY=false turns it off |
None documented | A local action log (SQLite); no remote analytics found | On by default: PostHog usage analytics (always built in) and Sentry error reports (a default build feature); environment variables turn them off |
| Licence · stars · latest release | MIT · 3 · 0.11.3, 18 Oct 2026 | MIT · 5 · 2.0.0, 17 Oct 2026 | MIT · 10,216 · 0.8.8, 10 Oct 2026 | MIT · 22 · 2.3.2, 24 Oct 2026 | MIT · 48 · 0.8.0, 10 Oct 2026 | MIT · 1,659 · 0.24.32, 5 Apr 2026 (npm: 0.24.28) |
What we measured on Anode
Two sources: a fresh run for this page, and Anode's own release record, where each live check names the script that repeats it.
Run for this page (24 October 2026)
- Quick checks: the 0.11.3 release as users install it (
anode-windows-x64.zip, its SHA-256 matching the release'sSHA256SUMS) passed all 112 quick checks in each of three runs, on Windows 11 Pro (build 26200); the two timed runs took 26 s each. One of the checks confirms that hidden managed and native calls can't move the real pointer (full output). The quick checks use private test pipes and create no seat, so they test the code paths, not a live desktop. - Tool list: the same
anode.exelisted 41 tools in answer totools/list, run asanode --channel compare-probe-1024 mcpso it couldn't reach an installed Anode, and no seat was started (tool names and description sizes).
To repeat it, in PowerShell:
gh release download v0.11.3 -R skulitom/Anode -p anode-windows-x64.zip -p SHA256SUMS Get-FileHash anode-windows-x64.zip # compare with SHA256SUMS (it prints upper case) Expand-Archive anode-windows-x64.zip anode-0.11.3 .\anode-0.11.3\anode.exe selftest --quick | Out-Host
The first version of this page (16 October) measured main at 47feb59, before
the 0.11.3 tag: 110 quick checks passed and 41 tools listed (output,
tool list).
Live checks from Anode's release record
These ran in a real seat on Windows 11 Pro build 26200 (release record), with the viewer hidden except where noted:
- The 0.11.3 release check (18 October 2026, on the tagged commit, with the viewer visible):
scripts\release-check.ps1passed all five parts: 15 native-control checks, a Chrome form with no warnings, real mouse, key and text input confirmed in headed Chrome, a File Explorer window listing 148 controls, and four display sizes, then back to the startup display. - Pointer isolation (0.11.1, 2 October 2026):
scripts\test-pointer-isolation.ps1 -PlacePointerput the real pointer over the hidden viewer, where Windows' Remote Desktop control would otherwise copy the seat's pointer moves to it, and a probe in the seat moved its pointer the way an SDL game does. The control tried 7 pointer updates; Anode blocked all 7, forwarded none, and the watcher saw no matching jump of the real pointer. Later releases rely on the regression check above; the live script was last run on 0.11.1. - Real input in a headed browser (0.11.1 and 0.11.2, and 0.11.3 above):
test-development.ps1 -VerifyInputconfirmed that Anode's mouse, key and text input arrived in a Chrome page inside the seat. - Native controls (0.11.2, 10 October 2026):
test-desktop.ps1passed UI Automation discovery, text replacement with read-back, invocation, waits, check boxes, lists and sliders, and a File Explorer window exposed 99 controls. In Chrome,test-chrome-form.ps1replaced a text field and read it back in 584 ms. - Display changes (0.11.2): four resolutions and scalings, up to 2560x1440 at 125%, applied in 153–171 ms each, and the startup display came back afterwards.
- Android (0.11.1): a read-only API 36 emulator booted inside the seat in 15.8 s.
Each tool, and when to choose it over Anode
Windows-MCP
CursorTouch/Windows-MCP is a Python MCP server with 21 tools,
including Snapshot (the UI Automation tree), Screenshot, Click, Type,
PowerShell, Registry and FileSystem. It is listed in Claude's connector
directory. It works in your session: its Click moves the real cursor before pressing, and
Type clicks its target first. Its 0.8.8 release (10 October 2026) added a control gate: during each call
and for 15 seconds after it, it holds back your keyboard and mouse; a substantial mouse move or Ctrl+Alt+Shift+Backspace
takes control back, and once the agent has been idle for 15 seconds any input does (so does any input while it hides
its indicator to take a screenshot). It then refuses new calls until you have left the mouse and keyboard alone for 10
seconds. A screen edge and a cursor glow show when the agent has
control, and its README calls the takeover best-effort. Its main branch has an opt-out and gate policies
(#458,
#466) that no release carries yet. Its security
notes say it is not sandboxed and suggest a VM or Windows Sandbox. Anonymous telemetry is on until you set
ANONYMIZED_TELEMETRY=false.
Choose it when you are happy to watch the agent work on your own desktop, are on Windows Home (where Anode can't run; Windows-MCP needs Python 3.14, which runs on Windows 10 and 11, and names no editions), want the most starred project here, or want shell, registry and file tools in the same server. To keep its tools while your own input stays in your session, where its gate shouldn't see it (so far tested with nobody at the PC), run it inside Anode's seat: Windows-MCP in the background. Choose Anode when you want to keep working while the agent clicks.
Desktop Touch MCP
Harusame64/desktop-touch-mcp is a TypeScript server
with a native Rust core and 32 tools. It mixes routes. desktop_act tries UI Automation (Invoke and
Value), then the DevTools protocol, which finds a browser element and clicks it with the real mouse, then terminal
input (for Windows Terminal, a paste it asks you to approve each time), and finally a real mouse click at the element.
click_element uses UI Automation Invoke only, which its guide says works without moving the cursor; since
2.3.2 its docs say not to use it on list, tree or grid items. mouse_click, mouse_drag,
scroll at a given point and browser_click move the real mouse, animated by default;
browser_click first brings the browser window to the front, and since 2.3.2 it refuses to click when
another window covers the point. Its keyboard tool brings the target window to the front
by default, except background typing into terminal-class windows, and a forceFocus option forces a
window forward when Windows refuses. Parking the mouse in the top-left corner stops it.
Choose it for UI Automation-first work in your own session, Chrome pages over the DevTools protocol, terminal input, its Excel tool, or a macOS preview. Choose Anode when apps need real mouse and keyboard input and you don't want that input on your desktop.
windows-computer-use-mcp
sandraschi/windows-computer-use-mcp is a Python
server built on pywinauto, with 20 tools (22 with two opt-in ones), plus a local web UI and a desktop app. Its mouse
tool and coordinate clicks move the real pointer in either dispatch mode; element clicks go through pywinauto, and an
opt-in "background" mode tries UI Automation Invoke first but falls back to a real click. Its mouse and keyboard
tools are refused until approve_automation is called, which opens a 5-minute window by default (an
environment variable bypasses it, and also turns off the corner abort below). The project calls this human-in-the-loop, but the agent can call that tool itself,
so a person checks it only if your MCP client asks you to approve the call; element clicks and text entry aren't
gated. Moving the pointer to the top-left corner aborts pointer actions. Its safety doc calls desktop automation
"host-powerful", says the server doesn't start Windows Sandbox, and suggests a separate virtualisation server for
isolation.
Choose it when you want an approval call before its mouse and keyboard tools, a local operator UI, or pywinauto's control coverage. Choose Anode when nobody should have to step away from the PC.
Terminator
mediar-ai/terminator is a Rust automation library with an MCP
server (terminator-mcp-agent, 35 tools), from Mediar. Its README lists "Doesn't take over your cursor or keyboard" among its features. Its source at 73a381c shows that the click_element tool moves the real pointer
with SendInput to click and then puts it back by default (restore_cursor), and that its
action tools bring the target window to the front by default; most restore your keyboard focus afterwards, but
click_element and invoke_element don't unless asked. mouse_drag moves the pointer too, and its typing tools click the target, without putting the pointer back, when focusing fails. invoke_element (UI Automation Invoke) is the route that doesn't move the pointer. A
stop_execution tool cancels running tools, and a full-screen action overlay is on by default. PostHog
usage analytics (always built in) and Sentry error reports (a default build feature) are on by default; environment variables turn both off. Its optional OmniParser and Gemini vision modes call Mediar's hosted service by default.
Choose it when you want its Rust automation library as well as the MCP server, its Chrome extension in your own signed-in browser, or Mediar's workflow builder and managed hosting for teams. Choose Anode when the agent's clicks and windows must stay off your desktop.
BgDesk
enwong93-sketch/background-computer-use
(BgDesk, "Background Computer Use for Windows") is a C# MCP server, at release 2.0.0 since 17 October 2026, that uses
the same Windows feature as Anode: a child session, a loopback Remote Desktop session under your own logon, turned on
with WTSEnableChildSessions and hosted, off-screen, in Microsoft's Remote Desktop control. Its tagline says
"hidden desktop"; its "How it works" section explains that this is a child session, a second desktop with its own input
queue where SendInput works as it does for a person. That makes it a separate Windows session, not a
hidden Win32 desktop like those of the tools under Hidden desktops and other routes. An agent process inside that session sends
real mouse and keyboard input there, or window messages for app types it has tested (Chromium, Electron, Explorer,
consoles and classic dialogs). The session's one large screen is divided into up to 12 areas of 1440x900, one per
agent, so several agents can work at once. A local web page (bgdesk workplace, on 127.0.0.1 behind a
token) shows each area live with a timeline of actions and lets you take an area over, and an ask_user
tool hands logins, captchas and payments to you. It needs an account with a password and an administrator step once,
and keeps the password in Windows Credential Manager after the first sign-in. Its README says bgdesk
enable only turns on child sessions, leaving inbound Remote Desktop as you had it; Anode's setup also turns on
the Remote Desktop listener, without opening the firewall. Its README lists its tests, run on Windows 11 Enterprise,
says other editions are untested, and documents limits: no elevated windows, no whole-screen shortcuts, and message
input that some controls ignore, which it checks for afterwards and can repeat as real input.
Choose it when several agents should work side by side, you want to watch and take over each one from a browser page, or you want later starts to sign in silently (it stores the password). Choose Anode when you need its wider tool set (UI Automation reads and waits, command jobs, display changes, audio, gamepads and Android emulators), a published record of live checks for each release since 0.9, with their scripts in its repository, or would rather type your Windows password when Windows asks than have it stored.
Anode's limits
- Windows 10/11 Pro, Enterprise or Education, or Windows Server with the Remote Desktop host, on x64. Windows Home can't host a child session.
anode setupneeds one administrator prompt; it turns on Remote Desktop and child sessions and can restart Remote Desktop Services (what it changes).- One seat per Windows session, shared by your agents in turn.
- Windows may refuse to sign the seat in automatically; then you sign it in from the tray icon with your Windows password (it happened in the 0.11.3 release check). A PIN or Windows Hello sign-in may not work there.
- The seat runs as you, with your files, accounts and network: desktop isolation, not a security sandbox.
- The seat runs unelevated, so elevated windows may ignore its input, and UAC prompts inside the seat are awkward.
- Apps that allow one copy may already be open in your own session; browsers need a separate profile.
- Builds are unsigned, so SmartScreen may warn. Anode is young and has few users so far (3 GitHub stars).
Hidden desktops and other routes
In our discovery test of 22 October, AI agents asked to find a Windows MCP server that works in the background picked lowlevel-computer-use-mcp and computer-use-plus, and named Ghost and WindowsPC-MCP as alternatives (they also named BgDesk, in the table above). umbriel came up in a directory listing during our searches. All read from their README and source (umbriel from its README only) at the commits under Sources, not run by us.
- Ghost (Northtek; MIT, 28 stars, 0.23.4 of 6 September 2026,
54 tools on Windows) drives the windows on your desktop with window messages and UI Automation, and starts the apps it
launches on a hidden desktop in your session. Real mouse and keyboard input is off by default, and only you can turn
it on, in the server's settings:
GHOST_FOCUS_POLICYsets it, andGHOST_FOCUS_LOCK=offlets the agent switch it with a tool call. So by default it doesn't move your pointer. Chromium can still take the foreground for a moment, and Ghost hands it back: across six runs of about 490 keystrokes with a person typing, its README counts one keystroke that reached the wrong window. Ctrl+Alt+G stops every acting call. Its README says real input doesn't work on its hidden desktop, so apps that need real input need its foreground policy, on your own desktop. - lowlevel-computer-use-mcp (4 stars;
MIT in its README, no licence file; automated GitHub releases, the latest of 14 October 2026 at the commit read; 59
tools) starts apps on hidden Win32 desktops and clicks and types there with
posted window messages, without moving your pointer; its tools that do move it run only when the agent passes
confirm_focus_disruption=true. Its README says some apps ignore message input and that its install and release process "remain unverified", and its GUI installer turns on auto-approval of all its tools in Claude Code by default. - computer-use-plus (MIT, 2 stars, no release, last commit 15 August 2026; README in Chinese) works only on its own hidden desktop by default ("backgroundOnly"), through UI Automation and window messages, and never switches your screen to it, so there is no view of it for you. An opt-in foreground mode moves the real pointer.
- WindowsPC-MCP (MIT, 1 star, no release, last commit 27 May 2026) shows the agent's apps on a virtual monitor (Parsec's virtual display driver) and a hidden desktop. Its README says "Your monitors are untouched", but for each batch of real input its source switches the session's input desktop to the agent's desktop and back, and a comment there says switching on every input flickered for the user.
- umbriel (MIT, 2 stars, no GitHub release; npm 1.14.0 of 27 June 2026; last commit 15 August 2026) drives windows in your session through UI Automation and posted messages. Its README says invoke, scroll, set-value and toggle move no cursor, even on hidden windows and minimised classic Win32 windows, that typing and real clicks need an unlocked desktop, and that its SendInput fallback briefly takes the foreground.
- Cua Driver, Desktop Commander and Windows 365 for Agents are compared in Anode's When to use Anode, and when to use something else.
Method
- The searches this page answers, first run on 16 October 2026 and again on 24 October: "Windows desktop automation for AI agents MCP server", "best MCP server for Windows desktop GUI automation" and "MCP server automate Windows apps without taking over mouse and keyboard background", plus, on 24 October, two searches that AI agents ran in our discovery test ("MCP server Windows desktop automation UI Automation hidden background desktop screenshots click type" and "Windows MCP server separate virtual desktop isolated session AI agent computer use UIA"). Directories and marketplaces ranked (Glama, Playbooks, Enterprise DNA, mcpservers.org, G2, LobeHub and others), with Claude's connector listing for Windows-MCP; none of the results was a head-to-head comparison, and Anode appeared in none (the 24 October results).
- Anode was checked as described above, from its 0.11.3 release download. We did not start a seat for this page; the live results come from the release record.
- The other tools were not installed or run. They act on the live desktop, and we compare such tools from their docs and source only. We read each README and the files named below. Star counts and releases come from GitHub on 24 October 2026.
- What changed on 24 October: BgDesk joined the table and the "other routes" section is new; Desktop
Touch MCP's pointer row now includes
browser_clickanddesktop_act's DevTools route, which the first version missed; Windows-MCP's columns now follow the 0.8.8 release rather than its main branch, with its control gate described; windows-computer-use-mcp's approval gate is corrected (its mouse and keyboard tools refuse calls untilapprove_automation, which the agent can call itself; they don't wait); Terminator's rows no longer name ahover_elementtool (the name appears in two focus-exemption lists in itsserver.rs, but it isn't one of the 35 tools), and now includemouse_dragand its typing tools' click fallback; Anode's numbers come from the 0.11.3 release.
Sources
Read on 24 October 2026 at the commit shown. windows-computer-use-mcp, Terminator and umbriel were first read on 16 October 2026 and re-checked at the same commits on 24 October.
- Windows-MCP 0.8.8 (tag at
b74c507): README (ControlStatus, Supported Operating Systems, Telemetry), pyproject.toml (Python 3.14), uia/core.py (Click), desktop/service.py (click, window switching,type), desktop/control.py and control_hooks.py (the control gate), tools/, SECURITY.md; its main branch at9170e1b: README (control options and policies, not yet released); Claude connector listing. - Desktop Touch MCP 2.3.2 (tag at
c49a5d5): README, docs/guide.md (mouse speed, force-focus, failsafe, security), desktop-executor.ts (route order, the DevTools click), browser.ts (browser_click), mouse.ts (scroll), ui-elements.ts (click_element), CHANGELOG.md (2.3.2). - BgDesk 2.0.0 at
c25e1bc: README (requirements, how it works, workplace, tests, limits, what it changes), bgdesk/Program.cs (WTSEnableChildSessions), bgdeskw/HostForm.cs (ConnectToChildSession), Input.cs and Virtual.cs (input routes), bgdesk/Mcp.cs (tools), Cred.cs (credentials), Layers.cs (launch: your default browser, per-area browser data folders). - windows-computer-use-mcp at
1ace9e5: README, docs/SAFETY.md, dispatch.py (default mode), tools/__init__.py, app.py (approve_automation), tools/portmanteau_mouse.py and portmanteau_keyboard.py (the approval gate, typing), portmanteau_elements.py (element clicks and text entry), pyproject.toml (Windows 10 and 11). - Terminator at
73a381c: README, element.rs (click,invoke, typing's focus-then-click fallback, window activation), input.rs (send_mouse_click), MCP agent README, server.rs (click_element,mouse_drag,stop_execution, window-management defaults), utils.rs (restore_cursor,try_click_before, window-management options), Cargo.toml (default features), posthog.rs, sentry.rs. - Ghost 0.23.4 at
f966463: README, desktop.rs, focus.rs, postmessage.rs. - lowlevel-computer-use-mcp at
dbe1588: README, pyproject.toml, winio.py, server.py, installer_gui.py. - computer-use-plus at
6667b50: README, engine.js, execution-desktop.ps1, desktop-agent.cs, desktop.ps1. - WindowsPC-MCP at
28ba4e0: README, input/service.py, desktop/manager.py. - umbriel at
752d5f2: README. - Anode: the 0.11.3 release (tag at
0836c78); RELEASE-READINESS.md onmainat1ad6eae(the 0.11.3 live check is recorded there, after the tag), ARCHITECTURE.md (how the seat works), USAGE.md (the viewer's Take control), SECURITY.md (what setup changes; the seat runs unelevated), INSTALL.md (Windows Home), and this page's data: quick checks, tool list and the searches.