Cursor's account says Cursor can now control your computer, with agents driving desktop apps such as the iOS Simulator to test the features they build
Cursor can now control your computer. Agents can drive desktop apps like the iOS Simulator to test the features they build.
Context
If it works as shown, coding agents could check their own work inside real apps instead of only in code, but the post is a short demo and no Cursor changelog or blog entry for it had been published at scan time.
Cursor is an AI coding editor and agent platform. Its public documentation describes a computer use feature, called new, that lets agents on a self hosted worker click, type, take screenshots and drive applications with a UI on macOS and Linux. The docs do not mention the October 23 post, so this entry does not assume the post announces that same feature. The post was published at 11:59 AM Eastern on October 23.
Deep dive
The Cursor account posted at 11:59 AM Eastern on October 23: Cursor can now control your computer, and agents can drive desktop apps like the iOS Simulator to test the features they build. The post carries a 21 second video and no link.
The video opens on title cards reading Cursor can now control your laptop and Use it to drive apps like the iOS simulator. It then shows a Cursor prompt box, set to This Mac, with the instruction Computer Use add the ability to favorite trails and demo it. Next it shows a Cursor window beside an iPhone simulator running a trails app, with a pointer moving over the app and a Favorites screen at the end. The video does not show how permissions are granted or which plans have access.
Cursor's documentation page on computer use and desktop sharing says computer use lets an agent on a self hosted worker click, type, take screenshots and drive applications with a UI. On macOS it runs through a helper app called Cursor Computer Use that needs Accessibility and Screen Recording permissions, and the docs say both features are opt in and call them new. The documentation does not say this is what the post announces.
In a forum reply dated October 18, a Cursor staff member said a native local computer use mode for the editor agent had no timeline and that a computer use MCP server was the way to give an agent full desktop access. Cursor's changelog page, as fetched for this scan, listed no entry after October 16, and its blog listed none for this feature.
What to expect next
The sources reviewed do not say which plans, operating systems or agent types get the feature, how permissions work for the editor agent, or whether it is the self hosted worker feature in the docs. Watch for a changelog or blog entry, updated documentation, and any statement of platform support, since the docs list macOS and Linux workers. Independent testing of how reliably agents finish app flows has not been published.