Most people set up Codex, connect their plugins, and start issuing tasks — without ever turning on the two settings that determine whether Codex can actually navigate their environment. Computer Use and Browser Use are not advanced features for power users. They are baseline requirements for any business owner who wants Codex to operate without hand-holding.
If these are toggled off, Codex can think but it cannot move. It can plan but it cannot execute anything that requires clicking, navigating, or finding things on your machine or the web. For non-technical business owners especially, these two settings are the difference between an agent that acts and an agent that explains.
This post covers exactly what both settings do, why they matter, how to configure them correctly, and what happens if you skip this step.
For the complete framework, read the full guide.
What Computer Use and Browser Use Actually Do
These are two separate toggles inside Codex settings, and they control two different types of autonomous navigation.
Computer Use gives Codex control of your cursor. When this is on, Codex can move around your computer on your behalf — opening folders, clicking through menus, navigating interfaces, and executing actions that would otherwise require you to sit at the keyboard and click manually. It is the equivalent of handing an assistant your mouse.
Browser Use (Google Chrome) gives Codex the ability to navigate the web autonomously. It can open Chrome, visit URLs, interact with web interfaces, log into platforms, click through multi-step processes, and retrieve information from sites you'd normally have to browse manually.
Neither of these is a novelty setting. For any workflow that involves navigating your machine or the internet — which is most workflows — these are operational requirements.
Why Non-Technical Business Owners Need These On First
There is a specific pattern I see repeatedly: a business owner who does not have a technical background gives Codex a task that requires finding something — a file, a settings panel, a web page — and because Computer Use is off, Codex either tells them where to look (which means they still have to do it) or it stalls.
The entire value proposition for a non-technical user is that Codex can navigate on their behalf. Not explain the path. Navigate it.
Think about the friction that typically stops business owners from doing certain tasks:
- "I don't know where that setting is."
- "I'm not sure which folder that file ended up in."
- "I'd have to click through six screens to get there and I'll probably get it wrong."
With Computer Use on, these are not obstacles. Codex finds the setting, locates the file, clicks through the screens. You describe the outcome you want. Codex handles the navigation.
With Browser Use on, the same principle extends to the web. Codex can research, retrieve, and interact with online tools without you opening a tab.
Turning these off because they seem overly powerful is a common mistake that results in an agent with excellent judgment and no ability to act on it.
How to Set This Up Correctly
The configuration is straightforward, but the permission setup requires attention.
Step 1: Toggle both settings on in Codex settings.
- Computer Use: find it in settings, toggle on.
- Google Chrome (Browser Use): find it in settings, toggle on.
Step 2: Set permissions to "always include" and "always allow." This prevents Codex from pausing at every action to ask for your approval. The goal is autonomous operation. Requiring confirmation on each micro-step defeats that entirely. Learn why full access is the correct default.
Step 3: Handle macOS permission pop-ups carefully. On Mac, enabling Computer Use may trigger macOS accessibility or screen recording permission prompts. Do not approve these automatically. Read the exact wording before clicking anything.
If the wording in the pop-up does not match what Codex described it would do, stop. Ask Codex to tell you what the pop-up says first, then verify. A mismatch means something is happening you didn't authorize. The security implication here is real — macOS accessibility permissions grant significant system access, and you should only approve them when you understand exactly what you are approving.
Step 4: Run the Permissions Audit skill immediately after setup. The Permissions Audit skill (the first skill in the Skills Dashboard) verifies that Codex can run commands and modify files without being blocked. Running it after you enable Computer Use and Browser Use confirms the configuration is active and functional. See how permissions work across the full setup.
Watch me explain this live to see how this looks in a real setup session.
What "Always Include" and "Always Allow" Actually Mean
These two settings govern how Codex handles permission checks during task execution.
| Setting | What It Controls | Correct Configuration |
|---|---|---|
| Always Include | Whether Computer Use and Browser Use are available by default in every task | On — Codex should not have to request these per session |
| Always Allow | Whether Codex proceeds with authorized actions without pausing for confirmation | On — autonomous operation requires trusted execution |
| Failure / Untrusted | Restricted modes that block Codex from executing actions without per-step approval | Off — these modes paralyze the agent |
| Read-Only | Prevents Codex from writing or modifying anything | Off for operational use — read-only blocks most productive tasks |
If you leave either setting on a restricted mode, Codex will interrupt itself constantly. The user experience becomes worse than doing the task manually — every minute of Codex's autonomous processing interrupted by a permission prompt you have to dismiss before it can continue.
The intent behind restricted modes is oversight. The actual effect is paralysis. Full trusted access is the only configuration that makes autonomous operation possible.
Common Mistakes at This Step
Toggling Computer Use on without handling the macOS pop-ups. The permissions don't activate cleanly until the OS-level authorization is granted. If you dismiss the pop-up or miss it, Codex will behave as if Computer Use is off despite the toggle showing on. Complete the macOS authorization carefully — it's a one-time step, but it must be done correctly.
Leaving permissions at the default instead of setting "always allow." The default permission setting in Codex is not "always allow." Most business owners never change it and never understand why Codex keeps pausing to ask for confirmation. Change it manually during setup. It will not configure itself.
Enabling Browser Use without verifying Chrome is the active default browser. Codex's Browser Use is specifically configured for Google Chrome. If Chrome is not installed or is not the default browser, the integration may not function as expected. Verify Chrome is installed and available before testing any web navigation tasks.
Assuming the toggles are on because the UI shows them as active. Especially on Mac, there is a layer of OS-level permissions underneath the in-app toggle. Both have to be in place. The Permissions Audit skill will surface any gaps — run it, and if it flags issues, use Codex to resolve them rather than trying to trace the problem manually.
Why This Step Connects to Everything Else
Computer Use and Browser Use are not isolated settings. They are the execution layer that makes every other step in the setup process function at its intended capability level.
When you run the File Organization and Cleanup Skill (see that step here), Codex navigating your actual folder structure requires Computer Use. When plugins have shallow integration and you need Codex to access something via a web interface instead, Browser Use covers the gap. When you instruct Codex to run a goal that involves retrieving information, navigating settings, or interacting with tools, both settings are in the background making those actions possible.
A Codex installation with these toggled off is a capable agent operating in a physical restraint. Every task that requires clicking something will either fail, require you to do the clicking yourself, or generate an explanation instead of an action.
For non-technical business owners, that is the version of Codex that disappoints. Turn both on, configure the permissions correctly, and it becomes the version that operates.
Autonomous action requires autonomous access. An agent that has to ask permission to click is not autonomous — it's narrating.
The measure of whether this step is done correctly is whether Codex can complete a multi-step task on your machine without you touching the keyboard once.
— Shanee
p.s. If you hit a macOS permission issue and cannot get Computer Use to activate, paste the exact error message into a Codex chat and let it walk you through the fix from the terminal. It can resolve its own permission gaps — but only if you give it the exact wording of what's blocking it.
--
Use the prompts behind this system
The Growth Academy Skills Dashboard includes 100+ Codex skills and prompts for SMB owners.
See the Skills Dashboard →