Computer use
Computer use lets Nod work in apps on your computer, for example to write a list in TextEdit, fill a table in Numbers or write a reply into a Mail draft. Nod reads each app's window through the system's accessibility service, the same information screen readers use, and presses its buttons, chooses its menu items and types into its fields. It works in the desktop app, using the open-source agent-desktop tool bundled in the app, and never moves your pointer. It works in the background where it can, and brings an app to the front only for steps that need it; see When Nod brings an app to the front. A source install and a self-hosted server don't offer it.
Computer use is experimental on macOS, Windows and Linux: it hasn't been tested on many computers yet. Windows and Linux use the same checks as macOS; see Windows and Linux for what differs.
Nod uses computer use last. When a connected app can do the work, Nod uses it, even when you name the service: "message Priya on Slack" goes through your Slack connection. It uses the app on your computer instead only when you ask for it, such as "in the Slack app on my Mac", or when no connection can do the work, for example when Slack isn't connected but its app is on your computer. For files Nod uses local files, and for other websites its own browser.
Turn it on
Section titled “Turn it on”- Open Settings, Computer use, and turn on Let Nod use apps on this Mac (on this computer on Windows and Linux).
- On macOS, select Allow next to Accessibility. macOS opens System Settings, Privacy & Security, Accessibility. Turn on Nod there.
- On macOS, optionally select Allow next to Screen Recording the same way. Nod then can take a picture of one app window when its controls don't show what it needs, for example formatting.
Windows needs no permission. On Linux, the desktop's accessibility service must be running; Settings tells you when Nod can't reach it.
Turning computer use off stops it at once and forgets every app Nod opened.
Start with a request
Section titled “Start with a request”Tell Nod which app to use and what to do:
- "Open TextEdit and write a shopping list: milk, bread, eggs."
- "Make a table of these numbers in Numbers."
- "In the reply to Lena that's open in Mail, write that I'll be there on Friday. Don't send it."
Nod opens an app only when your words name it or ask for work that needs it. Opening one counts like opening a file: when your words don't cover it, Nod asks first. The app stays open to Nod for the rest of that request, and a task started from it, but not for later requests. To let Nod use an app whenever it needs it, add a rule, such as "Nod may use Numbers without asking".
What Nod can do
Section titled “What Nod can do”| Action | What it does |
|---|---|
| List apps | Lists running apps. It shows window titles only for apps Nod opened in this request. |
| Open | Launches an app in the background, or picks one that is already running. |
| Read a window | Reads the window's controls, labels and text, or the app's menu bar. A busy window comes back as an outline first. |
| Picture a window | Takes a picture of that one window, never the whole screen. It needs Screen Recording. |
| Press, choose | Presses a button or chooses a menu item. |
| Type | Sets or types the text of a field, or picks an option. |
| Key | Sends a shortcut, such as Cmd+N, to that app only. |
Each step that can change content goes through the same trust check as a connected app action. The check receives the app, window, control, proposed input, and current accessible window content. This includes existing recipients and message text, not only what Nod typed. Text entry is checked too: it can replace a selection or save at once. Only reading and moving focus run without this check.
Before input, Nod reads the window again. It refuses the step if the window content or control changed after the check. It checks again after waiting to bring an app forward. Keyboard input also stays bound to the focused control. In a list, table, outline, grid, tree or menu of more than 20 items, such as an inbox or a month view, the check sees only the item Nod acts on and the selected item, so new messages arriving elsewhere don't stop the step. When list items are left out, a send or submission runs without asking only when the checked window itself shows its recipients and message and your words cover them. A step can't run when the accessibility service returns an incomplete window, when the control is no longer in the window, or when the checked content exceeds 24,000 characters.
What Nod never does
Section titled “What Nod never does”Nod refuses these, without a judgment call. It recognizes apps by their ID and program, so an app that isn't on its list isn't refused automatically; keep Nod out of it instead:
- Terminals and apps that run scripts or commands, such as Terminal, iTerm, Script Editor, Automator, Shortcuts, Raycast, Windows Terminal, Command Prompt, PowerShell and GNOME Terminal.
- System settings and security, such as System Settings, Keychain Access, Activity Monitor, Disk Utility and macOS security prompts, Windows Settings, Control Panel, Registry Editor and Task Manager, and GNOME or KDE Settings, Passwords and Keys, and Disks.
- File managers: Finder, File Explorer, Files (Nautilus) and Dolphin. Nod works with your files only through local files, with its protections. An app Nod may use can still open and save files through its own Open and Save panels, which local files would refuse; keep Nod out of that app if that matters.
- Password managers, such as Passwords and 1Password, and crypto wallets.
- Nod itself.
- On macOS, the Apple menu, with Restart, Shut Down, Log Out and System Settings, and each app's own menu, with Services. Nod never shows them to the model.
- System shortcuts, such as Spotlight, Force Quit, Log Out and Lock Screen, any shortcut with the Windows or Super key, Alt+Tab, Ctrl+Alt+Delete and Ctrl+Alt+T.
- Any app you keep Nod out of.
Web browsers, such as Chrome and Safari, and code editors, such as VS Code, are view-only: Nod can read them but never presses, types or chooses anything there. For websites Nod uses its own browser, with your Vault and its safety checks.
Nod never reads or types into password fields: it checks the field again right before input, and sends no shortcut and takes no picture of an app while a password field has focus. To sign in somewhere, Nod uses Vault in its own browser.
See when Nod uses an app
Section titled “See when Nod uses an app”Nod works in the background where it can, so you can keep working. While it reads or acts in an app behind your windows, a small pill at the top of your screen says Nod is working in and the app's name. It stays until a few seconds after Nod's last step there. Select Stop on the pill, or press Cmd+Shift+Esc anywhere (Ctrl+Alt+Shift+Esc on Windows and Linux), to stop all of Nod's work at once.
When Nod brings an app to the front
Section titled “When Nod brings an app to the front”Some steps only work with the app in front: keyboard shortcuts, typing into a message body such as in Mail, and on macOS anything in apps built on Chromium or Electron, such as Slack, Notion or Teams, which don't update while they're behind other windows. On Windows, typing always needs the app in front.
For those steps, Nod waits until you stop typing or moving the pointer for a moment, then brings only that window to the front. While it works there:
- A pink glow frames the window, and a pill below it says Nod is using and the app's name.
- Select Stop on the pill, or press Cmd+Shift+Esc anywhere (Ctrl+Alt+Shift+Esc on Windows and Linux), to stop all of Nod's work at once.
- Keep your hands off the keyboard: what you type goes to the app in front. If you keep typing, Nod doesn't take over and the step doesn't run.
Afterwards Nod gives focus back to the window you were using, unless you've already switched to another one. To type into a message body, or into an app such as Slack, Nod pastes the text and then puts back what was on your clipboard. Clipboard history apps can still record the pasted text.
Windows and Linux
Section titled “Windows and Linux”The checks and refusals on Windows and Linux are the same as on macOS. What differs:
- App IDs. Nod names apps by their program name on Windows, such as
notepad.exe, and by their desktop ID on Linux, such asorg.gnome.TextEditor. On Linux it opens only installed desktop apps, never a command, a terminal, or a system, settings or file manager app; an app that's already open is checked only against Nod's list. On Windows it starts only windowed programs, never a command-line tool. - Windows: Nod can read but not operate an app that runs as administrator.
- Linux on Wayland: Nod can't bring a window to the front, so steps that need it don't run, and it shows only the pill, without the glow. The Ctrl+Alt+Shift+Esc shortcut may not work there; select Stop on the pill instead.
- Linux Flatpak: computer use doesn't work in the Flatpak app yet. agent-desktop identifies the desktop's accessibility service through the host's process list, which the Flatpak sandbox hides, so it can't reach other apps (agent-desktop issue #593). Settings shows this when you turn computer use on.
Keep Nod out of an app
Section titled “Keep Nod out of an app”Tell Nod, for example "never use Messages", in a chat or a task you started. Nod adds the app to a list of up to 100 apps it always refuses. Only you can take an app off the list again, in Settings, Computer use. Nod can't remove one.
Only work you started
Section titled “Only work you started”Nod uses apps only in work you started: a message you sent, a task that started from one, or a schedule you set up. Work Nod starts on its own, such as on new email, can't use apps at all, and neither can helpers Nod starts inside a task. So a message from a stranger can't make Nod use your apps.
Limits
Section titled “Limits”- Text in app windows reaches Nod as data, not instructions. A window can still contain text written to mislead Nod, like any web page or email. The trust check limits what such text can make Nod do, but it can't recognize every trick, so keep apps with untrusted content out of Nod's reach when you don't need them.
- The list of refused apps is by app. An app that isn't on it but can run commands or reach your secrets, such as a database tool, is not recognized; keep such apps out of Nod.
- Window text and pictures go to your model provider like any other tool result, and are part of conversation traces when you share them. Pictures are replaced with
[image]there. Window pictures aren't redacted: whatever is visible in the window, private content included, reaches the model. Only Vault entry in Nod's own browser keeps secrets out. - The check can see only what the accessibility service provides. Apps can hide content from that service. A window can also change between the last check and the operating system receiving input.
- Apps that draw their own controls, such as some games, show little to accessibility. Nod can't use them.