NexusWindows for Antigravity

Windows computer use for Antigravity, in the background. An MCP server (nexus-computer) that lets Google Antigravity (Gemini) see and operate Windows desktop applications while the user keeps their mouse, keyboard and foreground window. Built for a fast model: one look, then one batch of steps with label targets, and every reply says what to do next.

Version 2.8.2 · Windows 10/11 · Python 3.10+ · MIT licence

Part of the Nexus family: NexusWindows (Claude · Codex · Antigravity), NexusBrowser (repo), NexusAndroid (repo). Project page: julienpiron.fr/nexuswindows.

Why

Screenshot-and-click computer use moves the real cursor and brings windows to the front, so the person at the PC has to stop working while the agent acts. Most Windows applications can be driven without that: native controls accept window messages and modern frameworks expose UI Automation. This server acts in the background first, reads the effect back, and only falls back to the real mouse or keyboard when the step allows it (foreground=True).

Related MCP server: dsh-desktop-operator

Tools

Five listed MCP tools; the ten older names (computer_click, computer_type_text...) stay callable as unlisted aliases.

Tool descriptions and replies are in French; tool and parameter names are in English.

What it does

• Designed for Gemini: golden rule look, then act in one batch with label targets; every action reply carries a one-line next (✓ done · = already done, do not redo · ~ effect not seen, look at the attached image · ✗ failure, cause and what to try) and, when the effect was not read back, a compact WebP image (≤ 1280 px) of the window. A batch identical to one sent in the last 10 s on the same window without a computer_look in between is refused (repeat=true forces it).

• Background first, even with foreground=True: a box_2d or (x, y) target is mapped to the element under the point in the window's own UI Automation tree (covered windows included) and handled like a label target; a click on a text field retains it, so type without target, ctrl+a, ctrl+v and erase keys become background writes read back; plain keys are posted (WM_KEYDOWN/WM_KEYUP) in Win32, WinForms and WPF. Real mouse and keyboard only as a fallback with foreground=True; otherwise an explicit refusal (needs_foreground) and nothing is sent.

• Per UI family: Win32 → direct messages (BN_CLICKED, BM_SETCHECK, EM_REPLACESEL, CB_SETCURSEL / LB_SETCURSEL with their notifications, menu WM_COMMAND); WinForms → UI Automation then messages; WPF, UWP, Chromium → UI Automation only. Never UI Automation Invoke on a Win32 button (its proxy activates the window) nor Select on a Win32 list (silent).

• One cross-process read: the window-scoped UI Automation tree is read in one round trip (IUIAutomationCacheRequest + BuildCache, AutoSetFocus = False). A truncated or failed read is reported (uia.status, warning), never a silent empty list.

• Read-back after every action: verified true/false/None from a real read (field value, check state, selection, focused element, window title, image); success is never true on "command sent" alone. Steps accept a postcondition expect (already true: step skipped with already: true; false after: step failed).

• The user's physical input via Raw Input (injected input ignored): wait for a pause before any real mouse or keyboard action, and stop at the next checkpoint if the user touches keyboard or mouse (interrupted_by_user).

• Guards in the code, not only in the instructions: the window is always named (never the foreground one by default, ambiguous titles refused with the candidates); an ambiguous label is refused with the candidates; the target window is read back in the foreground right before every SendInput; password managers (KeePass, KeePassXC, Bitwarden, 1Password, Dashlane, NordPass, RoboForm, LastPass) are never looked at, captured or driven; the sign-in screen, lock screen and UAC prompt are refused. An action labelled pay, buy, order, transfer money, send, publish, delete permanently, uninstall, format, reset, cancel a subscription, erase data or make a repository public needs confirm: true on the step, and so does any key, submit or coordinate click that would trigger one. NEXUS_AGY_CONFIRM=off in the MCP server environment turns confirmation off entirely (default: on).

• Clipboard: saved in all its formats and restored; the text put there is excluded from Win+V history and cloud clipboard. Used only as a last resort for typing (multi-line or more than 300 characters).

• Shared with the other desktop agents of the PC: foreground token (%USERPROFILE%\.nexus\foreground.lock) and emergency stop (Ctrl+Alt+Shift+Esc, %USERPROFILE%\.nexus\stop), the same file protocols as NexusWindows for Claude.

Architecture

Install

Requirements: Windows 10 or 11, PowerShell 7, uv (installed by install.ps1 through winget if missing).

git clone https://github.com/pironjulien/NexusWindows-Antigravity.git
cd NexusWindows-Antigravity
pwsh -NoProfile -File install.ps1

The Python environment, logs and screenshots live in %USERPROFILE%\.nexusagy (outside the clone). Then declare the server in Antigravity's mcp_config.json:

{
  "mcpServers": {
    "nexus-computer": {
      "command": "pwsh",
      "args": ["-NoProfile", "-File", "C:/path/to/NexusWindows-Antigravity/scripts/start-computer-mcp.ps1"]
    }
  }
}

The agent guide is plugins/nexus-computer/skills/nexus-computer/SKILL.md.

Checks

pwsh -NoProfile -File test.ps1         # offline: ruff, Pyright, pytest
pwsh -NoProfile -File test.ps1 -Full   # plus the real desktop validation on its own Win32, WinForms and WPF windows

The real validation shows its test windows without activation and closes them at the end; real mouse and keyboard checks run only when the PC has been idle for 120 s, otherwise they are reported as skipped.

Privacy

NexusWindows for Antigravity runs entirely on your PC. It has no account, no telemetry, no analytics and makes no network requests of its own.

• What it reads: window titles, the accessibility tree and window images of the applications the agent works in, only when a tool is called. Password managers are neither read nor driven.

• Where it goes: tool results are returned to Antigravity, which may send them to Google under its own privacy policy; this server sends nothing anywhere else.

• What it stores, under ~/.nexusagy/: the Python environment, an action log computer.log (action, method, window, duration, outcome and short details such as a target label, coordinates, key names, a menu path or the number of characters typed, never the typed text; rotated at 5 MB, three backups) and screenshots (at most 50, each kept under 24 hours). Under ~/.nexus/: the shared foreground token and emergency-stop state.

• Removing it: remove the server from Antigravity's MCP settings, then delete ~/.nexusagy/.

Questions or concerns: open an issue on this repository.

Limits

• Windows only. Tool descriptions, replies and code comments are in French.

• Keyboard input is refused in UWP/WinUI and Chromium, and Ctrl/Alt shortcuts in WPF, where it cannot be done in the background; for web pages, NexusBrowser is more reliable.

• An effect with nothing readable stays ~ (not verified).

Licence

MIT, see LICENSE. Copyright (c) 2026 Julien Piron.