Platform-neutral guidance for using Open Computer Use, the open-source Computer Use MCP server and CLI for macOS, Linux, and Windows. Use when an agent needs to install, verify, troubleshoot, configure, or operate Open Computer Use through its native CLI, stdio MCP server, or direct Computer Use too

Open Computer Use Overview Open Computer Use exposes Computer Use as a local CLI and stdio MCP server. It is not Codex.app specific; adapt the commands and MCP config to the agent runtime you are operating in. The macOS runtime requires macOS 14.0 or later. Windows and Linux use their own platform runtimes and are not subject to this macOS minimum. It supports the same core tool surface across macOS, Linux, and Windows: list apps , get app state , click , perform secondary action , scroll , drag , type text , press key , and set value . Core Workflow 1. On macOS, run sw vers productVersion before invoking the CLI and require macOS 14.0 or later. On older versions, explain that the runtime cannot launch; do not recommend doctor or permission changes as a fix for binary incompatibility. 2. Check the CLI is installed with open computer use h or ocu h . If installation or setup is missing, read [references/installation.md](references/installation.md). 3. On supported macOS versions, run open computer use doctor before the first real GUI task. If permissions are missing, ask the user to approve Accessibility and Screen Recording in the onboarding UI. 4. Inspect available apps before acting: open computer use call list apps . 5. Capture current UI state with open computer use call get app state args '{"app":"TextEdit"}' . The default state is usually enough for UI operation. 6. When the task needs longer semantic text, such as chat history, email bodies, document text, or long form content, call get app state with text limit: 1000 or text limit: "max" . 7. When visible long pages or lists appear incomplete even after scrolling, call get app state with a larger max tree nodes or max tree depth . 8. Prefer element targeted actions using element index from the latest get app state result. 9. For multi step CLI work, use open computer use call calls '<json array ' so one process can reuse the latest element index mapping. 10. For agent runtimes that support local MCP servers, configure open computer use mcp or ocu mcp and call the exposed Computer Use tools directly. Read [references/usage.md](references/usage.md). 11. If communication, permission, or desktop session access fails, read [references/troubleshooting.md](references/troubleshooting.md). Operating Rules Treat the target desktop as the user's real session. Do not inspect password managers, unrelated private content, or sensitive apps unless the user explicitly asked for that task. Ask before sending, deleting, purchasing, approving, uploading, or making other externally visible changes. Do not assume Codex.app plugin helpers are available. Use the installed open computer use / ocu CLI or an explicit MCP config. Always run get app state before using element index ; do not guess indexes across sessions or after large UI changes. Prefer semantic actions and set value for editable controls. Use coordinate click , scroll , and drag only when the element tree does not expose a safer target. On macOS, do not enable OPEN COMPUTER USE ALLOW GLOBAL POINTER FALLBACKS=1 unless the user explicitly requested click method: "global" , a drag that must drive a window server drag session (window move, drag select text, Finder drag and drop), or other diagnostic behavior that may move the real pointer. Without it drag reports Drag delivered via app post and those operations have no effect; see references/usage.md for alternatives. On Windows and Linux, confirm the command is running inside the logged in desktop session before assuming GUI automation is available. Common CLI Actions For a short sequence that reuses state in one process: MCP Usage For runtimes that can launch local MCP servers over stdio, use: Read [references/usage.md](references/usage.md) for JSON config examples, direct tool call patterns, and platform notes. References [references/installation.md](references/installation.md): one time CLI install, agent MCP install commands, and macOS permissions. [references/usage.md](references/usage.md): MCP config, direct CLI calls, sequencing, and platform behavior. [references/troubleshooting.md](references/troubleshooting.md): permission, desktop session, app discovery, and action failures.

open-computer-use