Use computer use for GUI work
When files and commands are not enough
After this, you'll be able to choose between in-app browser, Chrome extension, computer use, plugin, MCP, and manual review for GUI tasks.
Before you start
Complete Use mobile review without losing control first.
The idea
Computer use is for work that has to happen in a graphical interface. Codex can read files, run commands, use structured tools, and preview local web pages. Use computer use when those paths cannot prove the task.
Here is the before and after: before, Codex is guessing from a loose request. After, you can choose between in-app browser, Chrome extension, computer use, plugin, MCP, and manual review for GUI tasks.
Now try it use the exercise prompt on one real repo task. Keep the output small enough to check before you accept the change.
You are ready when the Codex action, boundary, and proof all match the task.
Try it (12 min)
Watch out for
- Using computer use when a test, file diff, or in-app browser check would prove the task.
- Allowing every app when one target app is enough.
- Letting Codex use a signed-in browser without reviewing the site action.
- Keeping unrelated sensitive apps open during a computer-use task.
Paste this into Claude
Choose the right GUI path for this Codex task: Task: [describe task] Target surface: [local web app, signed-in website, desktop app, system setting, data app, unknown] Can files or tests prove it: [yes/no/unknown] Needs signed-in browser state: [yes/no/unknown] Sensitive content visible: [yes/no] Choose one: in-app browser, Chrome extension, computer use, plugin, MCP, or manual review. Return the reason, the permission boundary, and the proof Codex should capture before you accept the result.
What a good response looks like
Use the in-app browser first. The task is a local checkout page and does not require a signed-in Chrome profile. Proof: run the dev server, open /checkout, capture the failing state, fix the code, and repeat the same browser path.
What good looks like
- Local public web checks start with the in-app browser
- Signed-in browser tasks choose Chrome extension only when needed
- Desktop-app tasks choose computer use with one target app
- Sensitive flows require presence and narrow approval
When this breaks
- Breaks when Codex interacts with the wrong window because the target app was not named.
- Breaks when website content gives misleading instructions and the signed-in browser action is treated as safe.
AI can help with this
Use Codex to help you you can choose between in-app browser, Chrome extension, computer use, plugin, MCP, and manual review for GUI tasks. Start with the exercise prompt and your real input. Ask for one draft, then check it against this proof: Local public web checks start with the in-app browser. Accept only the version you can verify yourself.
You can now
You can name when computer use is appropriate
- You can prefer structured integrations when they fit
- You can keep app permission narrow
- You can require screenshot or flow proof
Key takeaways
Computer use is for one visible app flow when code, tests, or structured tools cannot prove the work.
- Use the in-app browser first for local web apps.
- Use Chrome extension only when signed-in Chrome state is required.
- Use computer use for scoped GUI tasks in desktop apps or browsers.
- Visible screen and clipboard content can become task context.