YouTip

Computer Use is a feature provided by Codex that allows Codex to view and operate graphical user interfaces (GUI) on macOS or Windows. When command-line tools or structured integrations cannot meet your needs, you can use this feature to complete tasks such as desktop application operations, browser interactions, and application settings adjustments. Computer Use gives Codex the ability to "see" and "operate" desktop applications. Unlike command-line tools, Computer Use can directly interact with graphical interfaces, including clicking buttons, typing text, browsing menus, and other operations. Computer Use is suitable for scenarios that require visual verification or graphical interface interaction, such as testing desktop applications, reproducing bugs that only appear in GUI, or operating data sources that don't provide plugins. > Computer Use can affect applications and system states outside of the project workspace. It is recommended to use it only for tasks with clear scope and pay attention to permission prompts during execution. * * * ## Environment Setup Before using Computer Use, you need to complete the necessary plugin installation and permission configuration. ### Installing the Computer Use Plugin Open Codex settings, find the Computer Use option, and click Install to install the Computer Use plugin. After installation is complete, Codex can start operating desktop applications. !(https://example.com/wp-content/uploads/2026/06/cs_1781008475673.png) ### macOS Permission Configuration On macOS, you need to grant the following two system permissions: | Permission | Purpose | | --- | --- | | Screen Recording | Allows Codex to view the interface content of the target application | | Accessibility | Allows Codex to perform interactive operations such as clicking, typing, and navigation | The system will pop up a permission request on first use. Simply authorize according to the prompts. ### Windows Usage Instructions On Windows, Computer Use needs to run on the active desktop. During task execution, the target application must remain visible on the current active desktop. Codex will take over the mouse pointer and keyboard input. > On Windows, Computer Use cannot run in the background. If you need to continue using the desktop at the same time, it is recommended to use a virtual machine or a second device. Next, we only need to ask it to open a website in the conversation window, and it will use Computer Use: !(https://example.com/wp-content/uploads/2026/06/cs_1781008617639.png) * * * ## Use Cases When a task depends on the graphical user interface and cannot be verified solely through files or command-line output, Computer Use should be chosen. ### Scenarios Suitable for Computer Use | Scenario | Description | | --- | --- | | Desktop Application Testing | Testing macOS applications, Windows applications, iOS simulator flows, or other desktop applications that Codex is building | | Browser Operations | Executing tasks that need to be completed through a web browser | | Bug Reproduction | Reproducing bugs that only appear in graphical interfaces | | Application Settings Adjustment | Modifying application settings that can only be completed through UI clicks | | Non-Plugin Data Sources | Viewing or operating information in applications or data sources that don't provide plugins | | macOS Background Tasks | Running limited-scope background tasks on macOS while continuing to work elsewhere | | Cross-Application Workflows | Executing automation processes involving multiple applications | > For locally built web applications, prioritize using Codex's built-in browser (in-app browser) instead of Computer Use. ### Windows Foreground Usage On Windows, Computer Use runs on the current active desktop. It cannot run in the background, so during task execution, Codex will move the mouse pointer, type text, and take over foreground operations. If you need Windows tasks to continue running while you are away, there are two options: * Keep the Windows device unlocked and connected to the internet, and use your phone's remote control feature to check progress or send follow-up instructions. * Run Codex in a Windows virtual machine, so Computer Use takes over the virtual machine instead of your main desktop. * * * ## Starting Computer Use Tasks Mention @Computer or @AppName in the prompt, or directly ask Codex to use Computer Use. You need to clearly describe the specific application, window, or process that Codex should operate on. !(https://example.com/wp-content/uploads/2026/06/cs_1781008777336.png) You can enter the following in the input box to invoke it: Use Computer Use to open the application, reproduce the bug in the login flow, and fix the minimal code path that causes the bug. After each modification, rerun the same UI flow to verify. You can use @Chrome in the input box to invoke the browser: !(https://example.com/wp-content/uploads/2026/06/cs_1781008810452.png) For example: Open @Chrome and verify that the checkout page still works correctly after the latest changes. > If the target application provides a dedicated plugin or MCP server, prioritize using these structured integrations for data access and repeatable operations. Only choose Computer Use when visual inspection or operation of the application is required. * * * ## Permissions and Approvals System permissions for Computer Use are separate from application approvals in Codex. On macOS, screen recording and accessibility permissions allow Codex to view and operate applications. Application approvals determine which applications you allow Codex to use. File reading, file editing, and shell commands still follow the thread's sandbox and approval settings. ### Application Permission Management When using Computer Use, Codex can only view and operate applications you allow. During task execution, Codex will request your permission before using an application. You can choose Always allow, so Codex won't ask again when using that application in the future. You can remove applications from the "Always allow" list in the Computer Use section of Codex settings. ### Sensitive Operation Approval For sensitive or destructive operations, Codex may additionally request permission. ### Troubleshooting If Codex cannot view or control an application, please check the following: * On macOS, open System Settings > Privacy & Security, and check whether the "Screen Recording" and "Accessibility" permissions for the Codex app are enabled. * On Windows, ensure the target application is visible in the current active desktop session. * * * ## Locked Use (macOS) Locked Use is a macOS-exclusive feature. It allows Codex to continue using Computer Use after your Mac is locked, but requires you to manually enable it in advance. Use case: Initiate a Codex task from a connected device, the task needs to use desktop applications, but the Mac is already locked. ### How It Works After enabling Locked Use, Codex will install an Apple-authorized plug-in that participates in the macOS unlock process. The scope of Locked Use is very limited: it is not a general remote unlock path, and does not allow other applications or local processes to unlock the computer. ### Enabling Steps 1. Open Codex settings > Computer Use. 2. Enable "Locked computer use". 3. Start a task using Computer Use from a connected device (after the Mac screen is locked). ### Security Mechanism When a Codex task accesses applications through Computer Use after the Mac is locked, Codex will temporarily unlock the Mac while blocking local use and retaining the lock screen protection. Before unlocking, Codex will verify whether the unlock request belongs to an active and trusted Computer Use session. Outside of that brief authorization window, Codex will refuse to unlock and prompt you to manually unlock. ### Security Protections for Locked Use | Protection | Description | | --- | --- | | Short Authorization Window | The authorization window is only valid for the current unlock attempt and lasts for a very short time | | Codex Auto-Unlock Only | Auto-unlock is only available to Codex in active Computer Use sessions | | Covers All Monitors | During temporary desktop unlock, Codex will cover all monitor screens | | Local Input Detection | If local keyboard or pointer input is detected, Codex will immediately relock the Mac and pause auto-unlock until you manually unlock | * * * ## Security Guidelines When using Computer Use, Codex can view screen content, take screenshots, and interact with windows, menus, keyboard input, and clipboard states in the target application. Application content visible in the target application, browser pages, screenshots, and open files may all be processed as context by Codex during task execution. ### Security Operation Recommendations | Recommendation | Description | | --- | --- | | One Target at a Time | Give Codex only one clear target application or process at a time | | Interruptible Anytime | You can stop the task or take over computer control at any time | | Close Unnecessary Sensitive Apps | Keep sensitive applications closed unless the task requires them | | Pay Attention to Windows Foreground Occupancy | On Windows, Codex will take over foreground input; it is recommended to use a second device, virtual machine, or stop the task before personally using the desktop | | Avoid Tasks Involving Keys | Avoid executing tasks that require keys unless you are present and can approve each step | | Review Application Permission Prompts | Carefully review permission prompts before allowing Codex to use an application | | Use "Always Allow" Carefully | Only choose "Always allow" for applications you trust Codex to automatically use in future