Review your app’s user flow with computer use

Claude Code was used on Windows to inspect an app for usability problems, but the Windows setup sounded patchy.

Done with Claude Code· Intermediate· May 2026

What they did
A user turned on Claude Code’s computer-use feature in Windows and had it navigate their app to look for friction in the interface. Because the screenshot MCP server would not run, the session fell back to a shell-script approach for collecting screenshots. In replies, people said the native computer-use MCP server appeared on macOS rather than in Claude Code on Windows PowerShell or WSL, though one person said WSL2 handled screenshots, debugging, and video analysis.
How it went
The result for this Windows app-review setup was unreliable native support, not a smooth inspection. The thread did not include any measured UX gains or a score for the output; it mainly suggested that Windows was not supported directly, while WSL2 might behave better.
Tips
On Windows, assume you may need WSL2 or extra tooling before this is workable. Let the agent observe first and hold off on any code changes until you review its findings.

Try it yourself with Claude Code

Start [app name] with [how to launch it]. Use computer-use to move through these key tasks: [task 1], [task 2], [task 3]. While you test, record anything that seems confusing, inconsistent, slow, or hard to recover from. Give me a ranked set of [5-10] UX improvements with the screen or step tied to each one. Do not edit code or make changes yet. If you reach any action that would submit information, delete data, make a purchase, or otherwise be difficult to reverse, stop and ask me first.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on reddit.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.