winapp-ui-automation

If you can't run winapp yourself (no shell, or the command is denied), give the user the exact winapp command(s) for their project instead of only describing the steps.

When to use

• Inspecting a running Windows app's UI from the command line
• AI agents interacting with Windows applications (clicking buttons, reading text, taking screenshots)
• Verifying UI state during development or testing
• Automating UI workflows without Playwright or Selenium
• Debugging WinUI 3, WPF, WinForms, Win32, or Electron app UIs by what the user sees and can operate
• Not for a WinUI 3 app's XAML internals (why a value or binding resolved the way it did, which XAML line made an element, live property edits, UI review comments): use winui-devtools

Prerequisites

For WinUI 3 XAML source/tree, bindings or dependency-property diagnosis and edits, use the winui-devtools skill and winapp devtools. It requires an attached target or explicit authorization to inject with --attach; a PID alone is not consent. An AutomationId works as a selector in both tools; generated slugs do not transfer to DevTools. Continue using winapp ui for cross-framework actions, screenshots, waits and accessibility.