Tip · Last checked
Official sources were checked on 2026-09-04. This case follows the Codex and ChatGPT plans help article and Codex use cases. Extension names, installation steps, and entry points can change with the client or workspace.
Codex x Chrome: let AI operate a browser safely
This case shows how Codex can use browser capabilities to open a page, search, click a result, and return a link. The capability may appear as Chrome, Browser, a browser extension, or built-in browser access depending on the workspace.
When it is useful
- Ask Codex to search a website for reference material.
- Open a site and complete a small, reversible click path.
- Include browser work in a task without leaving the current workspace.
Check the capability first
- Confirm that the current workspace has browser access enabled.
- If this is the first use, follow the browser-side installation or authorization prompt.
- Tell Codex the target site, search words, and expected output.
A common flow
If the client provides a Chrome extension or browser tool, the flow is usually:
- Enable the browser capability in the Codex desktop app.
- Install or connect the extension using the guided flow.
- Describe the target page and desired result in the task.

The first click may open an extension installation page.

Example task
Give a precise, read-oriented request:
Use the browser capability to open Bilibili, search for "RAG knowledge base tutorial", choose one beginner-friendly video, and return its title and link.
Codex may open the site, search the phrase, inspect results, and return the selected URL.

What to check
- It opened the site you specified.
- The search phrase was not silently changed.
- The returned page is relevant and not an advertisement or unrelated redirect.
- Login state, personal data, and paid areas stay within the scope you authorized.
Risk notes
Browser capabilities have more power than a text-only task. Start with read-only, low-risk pages. Do not ask Codex to pay, delete, publish, or submit forms unless you are ready to review every action. Describe the capability and safety boundary instead of hard-coding a button location that may change.
