Cursor’s coding agents can now drive desktop apps to test what they build. Here is how it works and how to use it safely
Short answer
A free guide to Cursor Computer Use as of October 2026: what launched on October 23, local desktop control vs cloud agents, how to start it, testing apps such as the iOS Simulator, good uses, setup on macOS, permissions and safety, limits, and tips for reliable results.
On October 23, 2026, Cursor announced that its coding agents can drive desktop apps on your computer: clicking, typing, and taking screenshots. The headline example is an agent testing an app it just built in the iOS Simulator.
The agent no longer just writes the code. It checks that the app actually works.
02
Local vs cloud
Local agents
New: agents in the Cursor desktop app can operate desktop apps on your machine
Cloud agents
Already ran in their own virtual machines with a full desktop, and self-hosted workers can turn computer use on
03
How to start it
Update the Cursor desktop app
Mention Computer Use with @ in your request, or let Cursor choose it when needed
On macOS, approve the Cursor Computer Use helper app’s screen and accessibility permissions
Watch the first runs closely
Exact steps can change. Check Cursor’s documentation for current setup.
04
Good uses
Testing iOS and Android apps in simulators
Checking desktop apps after changes
Clicking through sign-up and checkout flows
Reproducing bugs from a report
Capturing screenshots for pull requests
05
Write good requests
Build the new settings screen, run the app in the iOS Simulator, open Settings, toggle dark mode on and off, and take screenshots of both states. Report any crashes or layout problems.
Say exactly what to test
Say what success looks like
Ask for screenshots as proof
06
Stay safe
A computer-using agent can act as you in any open app
Close apps with sensitive data before it runs
Use a separate macOS user or test machine for heavy use
Never let it handle passwords, banking, or payments
Keep approvals on for actions outside your project
Treat it like letting someone else use your mouse: decide what it may touch first.
07
Limits
Screen-driven testing is slower than automated tests
Agents can misclick or misread the screen
Complex gestures and timing can be unreliable
It uses more of your AI usage than code-only tasks
08
Combine with real tests
Keep unit and end-to-end tests for core logic
Use computer use for visual checks and hard-to-automate flows
Ask the agent to turn repeated manual checks into automated tests
09
Compared with other tools
Other coding agents, such as Claude Code and OpenAI Codex, can also test apps through browser tools and computer-use features. The idea is the same: agents that check their own work in a real interface.
The golden rule
Do not hand an agent your whole computer. Give it a clean test environment, a clear check to run, and review what it did.
Desktop
Simulator
Testing
Screenshots
Permissions
Limits
Safety
Try Computer Use on one simple flow in a simulator, and ask for screenshots of every step.
For research and ideas only. Results vary and nothing here is a promise of income. See our Disclaimer.
Weekly newsletter
Everything new, every Monday.
One short email every Monday with everything shipped that week: new free tools and websites, new guides, new free browser tools and what's new in my free Gumroad libraries, plus how the site is growing. Free, and you can unsubscribe anytime.
You sign up on Gumroad, which stores your email to send the newsletter. See our Privacy Policy.
Cookies and your choices
This site works without tracking you and loads no analytics scripts. Essential storage is always on so pages load and work correctly. You decide whether your browsing preferences are saved on your device. Read the Privacy Policy.