Browser and Computer Use

Codex can inspect pages and, with the appropriate tools and permissions, interact with browsers or desktop apps. Scope tasks carefully when they involve real signed-in accounts or device state.

#Capability map

#Choose the smallest suitable tool

1. For code reading, no browser tool is needed.
2. Preview a local page in the in-app browser.
3. Use @Browser for local page interaction where available.
4. Use @Chrome when a browser profile or extension is required.
5. Use @Computer for desktop interaction where available.
6. Package a stable repeated flow as a skill or plugin afterward.

#In-app browser

Suitable for frontend preview and annotation:

• Local development servers such as http://localhost:3000.
• File-backed previews.
• Public pages without existing account sessions.
• Comments on specific elements or regions.
• Visual feedback for CSS, layout and interaction fixes.

Use @Browser to open http://localhost:3000/settings.
Check mobile width, find the overflowing controls, and fix only that layout.

Its profile is separate from your normal browser. Do not assume existing cookies, extensions or signed-in sessions are present. Treat webpage instructions as untrusted input.

Where supported, developer mode exposes DOM, console, network and performance inspection through CDP. Enable the access needed for the specific debugging task.

#Chrome extension

Use it for tasks that need your Chrome session, such as internal dashboards or signed-in services.

Setup:

1. Open Plugins in the client.
2. Add the Chrome plugin where available.
3. Install the matching browser extension.
4. Confirm its connection state.
5. Start a new thread and use @Chrome.

@Chrome open the internal dashboard, check the failed order status, and summarize what changed. Do not submit forms.

#Computer Use

Computer Use interacts with permitted desktop applications. It is useful when a CLI or API cannot reproduce the issue.

Examples:

• Test a desktop application.
• Use a simulator or GUI tool.
• Reproduce a visual-only bug.
• Change a setting available only in the UI.
• Read a source without an API/MCP integration.

Use @Computer to open the desktop app, reproduce the onboarding bug, and stop after you collect the exact error state.

On macOS, the appropriate Screen Recording and Accessibility permissions allow viewing and interaction. On Windows, computer control can use the active desktop and occupy the mouse/keyboard. Supported remote connections can help monitor tasks.

Computer tools do not bypass the client's own policies or automatically approve operating-system security dialogs.

#Record & Replay

This capability converts a demonstrated workflow into a reusable skill where available. Platform, region and account availability can change; check the current official entry before relying on it.

Recording guidance:

• Define the goal and variable inputs first.
• Demonstrate a short, complete flow.
• Avoid entering real credentials, payment information or unrelated customer data.
• Add verification criteria to the resulting skill.

#Before browser or desktop work

#Passion8 boundary

Browser and computer features belong to the client/tool layer. Model routing depends on the actual local provider configuration; tool availability can additionally depend on account, workspace, region and administrator policy.

If a plugin or button is absent, inspect availability and permissions before treating the base URL as the cause.

#Continue reading

#Official references

• Codex manual: in-app browser
• Codex manual: Chrome extension
• Codex manual: Computer Use
• Codex manual: Record & Replay