Let it drive the desktop.
Some apps have no API and no command line. Switch on computer use, and a session can look at the screen, click and type, the way you would.
- Developers
- Computer use
How it goes
- Step 1
Open Settings, then General, and switch Computer use on. On a Mac, grant the two permissions listed under the switch.
Still 30Settings, General, the Computer use switch on, with the Mac permission rows reading Granted. Detail 800 × 600 at 2×. Light and dark.The Computer use switch and the Mac permission rows. - Step 2
Ask a session to do the job: "Open the settings app, find the display scale, and set it to 125%."
Still 10Computer use mid-task. Window 1280 × 800 at 2×. Light and dark.Computer use, partway through a task. - Step 3
A bar at the top of the screen names the session that's driving. Press Stop in it at any time.
Still 31The driving bar at the top of the screen, naming the session. Detail 800 × 600 at 2×. Light and dark.The driving bar. - Step 4
The session reports what it did in the conversation.
Still 32The session's report of what it did. Window 1280 × 800 at 2×. Light and dark.The session's report.
A session never clicks or types into Turret itself. On a Windows machine it can't drive an app running as administrator.
Computer use runs on macOS, Windows and Linux. On Linux it needs GNOME on Wayland, or an X11 session. Under GNOME on Wayland, GNOME's own screen-sharing indicator takes the place of the bar.
Try it
More use cases
Ship a feature with a team of agents
One session writes the plan. Child sessions take a phase each, every one in its own worktree, and one of them runs on Codex.
Let it work overnight
An automation triages the issues every night. In the morning, its runs are waiting to be read.
Steer from Telegram or Slack
Approve a permission request from Telegram, and start a session from a Slack message.