Read the live interface
Inspect controls and explicitly read visible text, selected text, page content, or a URL when the task needs it.
APIs, MCP servers, and native agent tools come first. When a task only exists behind buttons, forms, or menus, Super Voice Mode lets your chosen assistant inspect and operate the real Mac app or website by voice.
Use an API, MCP server, or the agent's native tools when one fits the task.
Resolve controls through macOS Accessibility before relying on pixels.
Use a screenshot only when the interface cannot be understood another way.
The Computer Use beta gives connected assistants a guarded set of actions for apps and websites that would otherwise be inaccessible.
“Download last week's detailed usage report as a CSV.”
Inspect controls and explicitly read visible text, selected text, page content, or a URL when the task needs it.
Click buttons, fill text, choose menu values, scroll, and press keys through bounded Computer Use actions.
Target a specific app and window without moving your pointer, switching Spaces, or typing into the wrong foreground app.
Reinspect after meaningful actions. A posted click or keystroke is not treated as success on its own.
Standard mode asks once for a new app or website, then interrupts only for genuine external consequences. YOLO removes routine prompts while protected banking, password-manager, identity, security, and explicit block boundaries remain.
Background-safe routes preserve the app and pointer you are using.
Text delivery fills or drafts; it does not silently press Send, Submit, or Enter.
Choose scoped confirmation or no-prompt execution from the Computer Use dashboard.
Freshness checks and verification make failures visible and bounded.
Each Playbook explains how to operate an app or website effectively. Successful runs contribute reusable capabilities, not a brittle recipe for one document.
Complete a real task with Computer Use and verify the outcome.
Keep the reliable ways to navigate, edit, commit, verify, and recover, not the artifact's literal values.
Review capabilities under one app or website Playbook, with evidence kept separately.
Apply those capabilities to a different task, or save a stable goal as an optional workflow.
Select a cell or range · Enter a value or formula · Verify visible results
Confirm the committed value and inspect formula results.
Chosen browser · docs.google.com/spreadsheets · current spreadsheet
Inspect again after every selection or committed edit.
A successful run can improve an app Playbook without turning that one output into the Playbook. Consequential actions still follow the active approval policy.
Planned Playbook definitions, versions, evidence, and run metadata stay on your Mac. Screenshots are not stored in a Playbook or run history by default.
Local Playbooks do not make every assistant local. If you choose a cloud-backed assistant, content explicitly read or captured for the task follows that provider's handling. Choose a local model when the entire agent path must stay on your Mac.
Included in in-app Assistant turns with weekly Pro uses, or unlimited with Pro Lifetime.