nexus-windows-codex
Related Servers
Alternatives to nexus-windows-codex
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI agents to control Windows desktop applications by wrapping Codex's Computer Use capability.1311MIT
- AlicenseNot gradedqualityCmaintenanceEnables Codex sessions to observe and control the Windows desktop through screenshot reasoning, archived-frame inspection, pixel sampling, keyboard/mouse input, and workspace-local multimodal memory.MIT
- AlicenseAqualityFmaintenanceLets Claude Desktop and Claude Code inspect and drive Windows desktop applications in the background, including clicking, typing, launching, and verifying results, while the user keeps their mouse, keyboard, and foreground window.7420 PyPI4MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to see, locate UI elements, and operate any Windows desktop app through natural language, using accessibility-tree matching with optional vision-model fallback, plus an autonomous visual loop with introspection and meta-learning.14MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to automate Windows desktop applications through semantic UI Automation instead of brittle coordinate clicks, with tools for discovering windows, finding controls by stable identifiers, and verifying actions.41 PyPI5MIT
- 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
TDQS
Scored across 5 tools
The core purposes (enumerate, observe, act, launch, close) are conceptually distinct, but `windows` (list all desktop windows) and `window` (close a window) differ by a single letter and are easy to misselect when an agent scans tool names. The `look`/`act` pairing is intentionally coupled (act requires the last look's observation id), which is documented but adds another boundary the agent must track.
Naming mixes bare verbs (`look`, `act`, `launch`) with bare nouns (`windows`, `window`) and no verb_noun pattern, so there is no predictable rule to infer a tool's action from its name. The near-homograph `window`/`windows` compounds the inconsistency.
Five tools map cleanly onto the workflow: enumerate windows, observe one, act on it, launch apps, close a window. Each tool earns its place and there is no redundancy or filler.
Observation, interaction, launching, and closing are covered, but window lifecycle mutations beyond close are absent: no move, resize, minimize/maximize/restore, or explicit activate/focus operation. These are notable gaps for a server whose domain is desktop window management, forcing agents to fall back on UI-level workarounds.