NexusWindows
Provides background Windows desktop computer-use capabilities to Google Antigravity, enabling UI Automation-based observation and verified background interaction with desktop applications.
Provides background Windows desktop computer-use capabilities to the OpenAI Codex desktop app, enabling UI Automation-based observation and verified background interaction with desktop applications.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
NexusWindows
Your Windows desktop, driven in the background.
Windows computer use for AI agents: your desktop apps observed through UI Automation and driven without taking your mouse, keyboard or foreground, with every action read back. For Claude, Codex and Antigravity.
๐ Website ยท ๐ฆ Get it with NexusSystem ยท โถ๏ธ Watch the video ยท ๐ Changelog
One engine, three profiles
โจ Why NexusWindows
Related MCP server: ORVEX
๐ Quick start
Windows 10 or 11, x64 or ARM64; nothing else to install (one self-contained native program, no Python, Node.js or .NET runtime needed).
Let your AI install it. NexusSystem detects your AI apps and sets up the right profile:
Install Nexus for me by following https://raw.githubusercontent.com/pironjulien/NexusSystem/main/INSTALL-AI.mdOr the NexusSystem app from the Microsoft Store
(winget install --id 9NSH2P3QLWT1 --source msstore).
By hand, from the release files (no administrator rights):
$r = 'https://github.com/pironjulien/NexusWindows/releases/latest/download'
Invoke-WebRequest "$r/get.ps1" -OutFile get.ps1
Invoke-WebRequest "$r/SHA256SUMS.txt" -OutFile SHA256SUMS.txt
(Get-FileHash get.ps1 -Algorithm SHA256).Hash # must equal the get.ps1 line of SHA256SUMS.txt
gh attestation verify get.ps1 --repo pironjulien/NexusWindows --signer-repo pironjulien/NexusSystem # optional: provenance
powershell -NoProfile -ExecutionPolicy Bypass -File .\get.ps1get.ps1 downloads NexusWindows-win-x64.zip or NexusWindows-win-arm64.zip from the latest release, checks its
SHA-256 against SHA256SUMS.txt, installs the engine under %USERPROFILE%\.nexus\nexus-windows and declares it to
Claude Code, Claude Desktop, Codex and Antigravity when they are present. Every client starts the same stable path,
%USERPROFILE%\.nexus\nexus-windows\NexusWindows.exe --mcp --agent <claude|codex|antigravity>; updates never change
it. Release files carry a build provenance attestation (gh attestation verify <file> --repo pironjulien/NexusWindows --signer-repo pironjulien/NexusSystem).
The Claude Desktop extension is nexus-windows-claude.mcpb in each release.
For unattended maintenance of an existing installation, NexusSystem calls get.ps1 -UpdateOnly: it updates only
the installed engine and stable launcher, without registering or enabling clients. -RefreshExistingProfiles
additionally refreshes the shipped files of an already installed, active Antigravity plugin. Disabled or custom
declarations and client configuration remain unchanged. Running sessions keep their engine; new connections use
the new version. The launcher itself never downloads updates.
Each MCP session writes an atomic runtime receipt under %USERPROFILE%\.nexus\status\runtime, with its actual PID,
process birth, loaded executable, assembly SHA-256, version and idle/busy/stopped lifecycle. MCP initialization and
discovery expose the same identity. A receipt must be checked against the live process and its AI host before it
can establish that a particular AI uses the installed version; an installation manifest alone cannot prove this.
โ๏ธ How it works
flowchart LR
A["Claude / Codex / Antigravity"] -- "stdio (MCP)" --> W["NexusWindows.exe --mcp --agent ..."]
W -- "UI Automation, Win32" --> D["Windows apps (in the background)"]One repository, one common engine, three profiles:
Profile | Folder | For |
Claude | Claude Code and Claude Desktop | |
Codex | the OpenAI Codex desktop app | |
Antigravity | Google Antigravity |
For current MCP requests, native file dialogs, UTF-8 stdio and blank Chromium pages, use the shared MCP cookbook. How the engine compares with Cua Driver on the same bench is in the 3 November 2026 benchmark.
Outward actions (send, pay, publish, delete) are held for your explicit yes, and text read on screen is treated as data, never as instructions.
commun/engine/: the common C# (.NET 10) engine,NexusWindows.exe, serving the three profiles as MCP stdio servers (--mcp --agent claude|codex|antigravity) and declaring itself to them (--register).commun/: the shared safety policy (garde-fous.json), the stable launcher (launcher/), the workstation installer of the immutable engine (native-runtime.ps1) and the release packaging (package.ps1).plugin/: the single plugin of the three AI apps (Claude Code, Codex, Antigravity), served by the native engine.claude/,agy/,codex/: each profile's documentation (and the Claude Desktop extension inclaude/).tests/: xUnit tests of the engine, the launcher and the installers.
๐ ๏ธ Development
./test.ps1 # dotnet test (xUnit) of the engine, launcher and installers; offline, same command as the CI
./test.ps1 -Full # the same, plus the live tests: real Explorer launch, shared foreground token, capture sessionBefore a stable promotion (see NexusSystem's
RELEASING.md), ./test.ps1 -Full must pass on a
real interactive Windows session with a GPU, at a moment nobody is using the PC (the live tests take the shared
foreground token and open real windows). The hosted CI skips those tests, so a green CI alone is not enough to
promote. Releases ship the engine compiled ahead of time (Native AOT, commun/package.ps1): run the suite against
that very binary, installed by get.ps1 from a local package in a throwaway profile:
./commun/package.ps1 -Version X.Y.Z -Out <dist> -Runtimes win-x64 -NoMcpb
$env:NEXUS_WINDOWS_PROFILE = '<empty folder>'; $env:NEXUS_WINDOWS_SOURCE = '<dist>\NexusWindows-win-x64.zip'
powershell -NoProfile -ExecutionPolicy Bypass -File ./get.ps1
./test.ps1 -Full -Engine '<empty folder>\.nexus\nexus-windows\native\<sha-256>\NexusWindows.exe'-Engine runs the process tests (MCP over stdio, helper children) against that executable. The installers accept
both engine layouts:
Native AOT single file (releases since 3.17.0):
NexusWindows.exealone holds the code;framework-dependent (the working-folder installation,
commun/native-runtime.ps1, and releases up to 3.16.28):NexusWindows.exewithNexusWindows.dll,.deps.jsonand.runtimeconfig.json, all three recorded together; a partial set is refused.
These cases live in LauncherTests, NativeRuntimeInstallerTests and PublicMaintenanceTests (get.ps1,
commun/native-runtime.ps1, the stable launcher); NexusSystem's WindowsRuntime/RuntimeObservation follow the same
rule since NexusSystem 1.7.0.
Build and test outputs go to %USERPROFILE%\.nexus\build\nexuswindows. The three profiles were separate repositories
until 30 October 2026; those repositories have since been removed (see CHANGELOG.md).
๐ Privacy & security
Everything runs on your PC. Nothing is sent anywhere by NexusWindows; screenshots, logs and routines stay under
%USERPROFILE%\.nexus. See SECURITY.md to report a vulnerability.
Part of the Nexus ecosystem
Your AIs (Claude, Codex, Antigravity) at work on your Windows apps, real Chrome and Android phone โ in the background.
Get them all with NexusSystem ยท Microsoft Store ยท julienpiron.fr ยท @julienpironfr
Built in France ๐ซ๐ท by Julien Piron
MIT ยฉ Julien Piron
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
This server cannot be deployed
Maintenance
Related MCP Connectors
Connect AI assistants to your approved computer for files, commands, browser and desktop tasks.
Connect ChatGPT, Claude, Cursor or VS Code to your Windows PC: files, terminal, browser, apps.
Eyes and hands on real Windows PCs โ observe, click, type via Glasswarp API.
Give your AI hands on every computer you own. Remote control of your Windows, Mac and Linux machines from one ChatGPT, Claude or Cursor chat โ even from your phone. Ask it to find out why the office server is crawling, update every PC in the house, sort out your mom's laptop from another city, or ship the site from your work machine while you're on a train. It runs commands, reads files and takes a screenshot when it needs to see the screen. You decide what each computer allows, and you can cut any of them off in a second.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables safe Windows desktop automation and computer use through natural language, including window observation, UI Automation, and execution of verified actions like clicking, typing, and scrolling.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to drive Windows desktop automation โ opening and interacting with applications, native UI controls, keyboard/mouse input, files, processes, clipboard, and Chrome/Edge browsing via UI Automation and CDP. All actions pass through a safety policy with human approval, emergency stop, and deterministic verification.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to inspect and drive Windows desktop applications text-first through the UI Automation tree, reading interactive elements and performing element-level actions (click, invoke, set value, type, drag, menu and window/app lifecycle) without relying on screenshots or coordinates. Actions are dry-run by default and pass an internal confirmation gate with snapshot binding and an audit log, while deterministic waits/verifications and an explicit screenshot or OCR fallback cover self-drawn surfaces.1MIT
- AlicenseAqualityFmaintenanceEnables OpenAI Codex to inspect and operate Windows desktop applications in the background while the user keeps control of the mouse, keyboard, and foreground window, with each action verified against the application's real state.54,780 npm3MIT