desktopmanager-operator

name

desktopmanager-operator

description

Operate and validate Windows desktop state through DesktopManager using MCP first and CLI second. Use when Codex needs to inspect windows and monitors, capture screenshots, launch desktop applications, wait for windows to appear, inspect child controls, click controls, send text or keys to windows and controls, focus or move windows, apply named layouts, save or restore snapshots, clean up distractions, or prepare the desktop for coding or screen sharing.

DesktopManager Operator

Use this skill to operate the Windows desktop through DesktopManager.

Golden Path

1. Prefer MCP first: desktopmanager mcp serve
   • Add --allow-mutations only when the session really needs desktop or saved-state changes.
   • Add --allow-process <pattern> or --deny-process <pattern> when the session should stay scoped to specific desktop apps.
   • Add --allow-foreground-input only for sacrificial or tightly controlled sessions that may need focused fallback on zero-handle UIA text or key actions.
   • Add --dry-run when you want to preview mutating MCP calls without changing the desktop.
2. Start with inspection, not mutation.
   • Read resources first: desktop://windows/active desktop://windows/visible desktop://monitors
   • Use get_active_window when focus matters.
   • Use window_exists or active_window_matches when you need an explicit assertion first.
   • Use screenshot_desktop or screenshot_window when visual confirmation is needed.
   • Use get_window_geometry when you need exact outer-window and client-area bounds before a coordinate-based action.