Exploring Windows applications

You drive the person's real desktop app through the robomotion-windows-mcp server, step by step, the way the robot will. Every action you take is recorded as the Robomotion.WindowsAutomation node that repeats it, with a selector the server has verified: generated from the element you acted on, then resolved with the Windows Automation package's own engine back to that same element. When you are done you get a sequence; creating-flow turns it into main.ts.

This is the desktop twin of exploring-browser. Same habits: snapshot first, act with refs, close when done, ask before building.

Step 0 — load the tools

The mcp__windows__* tools are deferred in Claude Code. Calling one cold sends malformed JSON and loses the server for the session. Before the first call:

ToolSearch query="select:mcp__windows__windows_list_windows,mcp__windows__windows_launch,mcp__windows__windows_snapshot,mcp__windows__windows_find,mcp__windows__windows_click,mcp__windows__windows_type,mcp__windows__windows_send_keys,mcp__windows__windows_select,mcp__windows__windows_menu,mcp__windows__windows_end"

Add the others as you need them (windows_screenshot, windows_wait, windows_get_table, windows_set_checkbox, windows_expand, windows_inspect, windows_get_selector, windows_pick_element, …). If the server shows as failed in /mcp, the binary is missing or not on PATH: say so, do not guess selectors.

The loop