windows-chat-verification

Windows Chat Verification

Use the plugin's declared DesktopManager MCP server in an interactive Windows session. Perform this workflow through its MCP tools. If the server or a required tool is unavailable, report the gap; do not substitute shell scripts, source builds, another automation service, or an app-owned pipe.

The server starts read-only. Interaction and screenshot capture require the host to enable --allow-mutations; use a narrow --allow-process pattern for the intended app. When process filtering is active, include the matching explicit processName on mutating calls instead of *. Focused fallback input additionally requires --allow-foreground-input. Task authorization still determines what may be sent; a server flag alone does not authorize a message.

Inspect and attach

Use list_windows, get_active_window and window_exists to identify the requested app. Inspect only that app. If the host permits mutating tools, capture its window with screenshot_window; in read-only mode continue with structural inspection and report that visual evidence is unavailable. If launching the installed app is authorized and the server's policy permits it, use launch_and_wait_for_window and wait_for_window.

Read list_window_controls before choosing the composer or send button. WebView2 and Chromium shells may expose incomplete or unstable controls; use diagnose_window_controls before falling back to screenshot-assisted targeting. Reacquire targets after navigation, resizing or a process change.

Enter the authorized message

Prefer click_control, set_control_text and send_control_keys for an addressable composer. Use focused fallback only when the host enabled mutation and foreground-input access, and pass allowForegroundInput: true on each set_control_text or send_control_keys call that needs that fallback. Retain the explicit process scope. If the controls remain inaccessible and screenshot capture is permitted, inspect the current screenshot and get_window_geometry, then use save_window_target and click_window_point for the narrowest visible target. Without a current screenshot, report the targeting gap instead of guessing coordinates.