Codex Chrome Extension: Setup, and Why It May Be Missing
Codex chrome extension setup is three clicks in theory. In practice a lot of people open the plugin directory, scroll to C, and find no Chrome entry at all.
What the codex chrome extension governs
OpenAI's developer documentation describes it in a single line: use Chrome with Codex while managing browser permissions, website approvals and browsing data. That phrasing is worth reading twice, because it frames the feature as a control surface rather than a convenience. The value is not that an agent can open a tab; it is that you decide which sites it may touch, what it is allowed to do there, and what happens to the browsing data it sees along the way. Anyone evaluating this for a work machine should start from that sentence and work outward, because permissions and approvals are where the decision actually gets made, not in the feature list.
The documented path is short
Per the official page at developers.openai.com/codex/app/chrome-extension, you open Codex, go to Plugins, and add the Chrome plugin from the directory. There is a parallel documentation page under learn.chatgpt.com covering the same ground, and like the rest of that site it can be read as plain markdown by appending .md to the URL. Nothing about the instructions is unusual, which is precisely why the failure is disorienting: there is no configuration file to get wrong and no command to mistype. Either the entry is in your plugin directory or it is not, and if it is not, the instructions give you nothing further to try. That is a strange place for documentation to leave a reader, and it is why the community thread below ends up being the more useful reference.
The missing-entry report, with receipts
On 12 May a user posted to OpenAI's developer community under the Codex category, saying they had followed the official documentation and could not find any Chrome plugin in their directory. They had sorted the list alphabetically and named the neighbours they did see around the letter C, Channel99, Circleback and CircleCI, with no Chrome entry between them. They had also searched the forum first and found no existing report. The thread ran to six posts, drew roughly seven thousand views and a handful of likes, and OpenAI support appeared in it. That is a useful amount of corroboration: it establishes the gap is real and that other people arrived at the same dead end.
Checks worth running before a support ticket
Start by confirming which Codex surface you are in, since plugin directories are not necessarily identical between the desktop app, the web experience and an IDE integration. Then confirm the account and workspace: plugin availability commonly depends on workspace settings and administrator permissions rather than on your install, and a workspace admin can answer in a minute what a support queue will take days to reach. Check whether the directory is filtered or searched rather than fully listed, since a stale search term hides entries convincingly. If it still is not there, the forum thread is the better first stop, because a documented public report carries more weight than a fresh individual one.
Not the same thing as the ChatGPT browser extension
Search this term and the Chrome Web Store listing for ChatGPT appears alongside the Codex documentation. They are different objects with different purposes: a store listing you install into Chrome from the browser side, versus a plugin you add from inside Codex to grant it controlled access to your browser. Mixing them up produces a frustrating half hour in which the store item installs perfectly and none of the documented Codex behaviour appears, because nothing was ever connected. Confirm which one the guide you are following actually means before you install anything, and expect the answer to be the Codex plugin whenever the instructions begin inside Codex. One quick test settles it: if step one happens in the browser, you are installing the store item, and if step one happens inside Codex, you are adding the plugin.
Orientation
Permissions are the feature
The documentation frames it around managing browser permissions, website approvals and browsing data. If you are writing a case for a work machine, that sentence is the whole argument, not the tab automation.
A public report exists
A May thread in OpenAI's developer forum documents the plugin missing from the directory, names the alphabetical neighbours around C, and received a support reply. Cite it rather than starting from scratch.
Two different Chrome things
The ChatGPT listing in the Chrome Web Store and the Chrome plugin added from inside Codex are separate. Installing one does not configure the other, and the instructions rarely say so.
Workspace settings gate a lot
Plugin availability commonly follows workspace configuration and admin permissions. Asking your administrator is faster than a support queue and answers the question in most organisations.
What you are trying to do
| What you want | Codex Chrome plugin | Begin.sh |
|---|---|---|
| Give an agent controlled browser access | The documented purpose, with per-site approvals and browsing-data controls | Out of scope; it does not drive your browser |
| Install it | Open Codex, go to Plugins, add the Chrome plugin | Nothing to install or approve |
| When the entry is absent | Check surface, account and workspace settings, then the forum thread | Not applicable |
| Reproduce a page you like | Browser access plus your own implementation work | Paste the URL and get a static site zip back |
| Start a new project | Better suited to an existing repository | A prompt returns a static site or Expo app |
| Hosting and accounts | Runs against your own browser and machine | None included; you get files, not a deployment |
| Where the docs live | developers.openai.com/codex/app/chrome-extension | On the product site |
A short troubleshooting order
- Confirm the surface
Note whether you are in the desktop app, the web experience or an IDE integration. Directories are not guaranteed to be identical, and the documentation assumes you are inside Codex itself. - Clear the filter
Sort the plugin directory alphabetically and clear any search box before concluding an entry is absent. A leftover search term is the cheapest possible explanation, so eliminate it first. - Ask the workspace admin
Availability frequently depends on workspace settings and role permissions rather than your machine. An administrator can confirm in minutes whether the plugin is enabled for your organisation. - Point at the existing thread
If it is genuinely missing, reference the May community report rather than filing a blank ticket. A corroborated public case with named neighbouring entries is far easier for support to act on.
Questions from the forum and elsewhere
Why is the codex chrome extension not in my plugin directory?
That was reported publicly in May by a user who followed the official documentation, sorted the directory alphabetically, and found Channel99, Circleback and CircleCI with no Chrome entry between them. OpenAI support joined the thread. Availability can depend on surface and workspace configuration, so check both before assuming a fault.
What does the plugin actually let Codex do?
The developer documentation describes using Chrome with Codex while managing browser permissions, website approvals and browsing data. In other words, browser access under explicit controls over which sites are approved and what happens to the data seen there. The emphasis on approvals suggests access is meant to be scoped site by site rather than granted once and forgotten about.
Is this the same as the ChatGPT extension in the Chrome Web Store?
No. The store listing is a browser extension installed from Chrome, while the Codex Chrome plugin is added from inside Codex through the plugin directory. Installing the store item does not complete the Codex setup, and the two are frequently confused.
Where is the official setup guide?
At developers.openai.com/codex/app/chrome-extension, with parallel documentation under learn.chatgpt.com. On that documentation site you can append .md to a page URL to read a markdown version, which is handy for keeping local copies of setup steps. Treat the developer site as the authority if the two ever disagree, since it is the page the setup instructions themselves point at.
Should I file a support ticket immediately?
Check the cheap causes first: the wrong Codex surface, a leftover search filter, or workspace permissions set by an administrator. If none of those explain it, referencing the existing forum thread gives support a corroborated case rather than a single fresh report.
How does Begin.sh relate to browser automation?
Only in one narrow way. If the reason you wanted browser control was to reproduce a page you liked, Begin.sh accepts a URL to clone and returns a static site as a downloadable zip, with no extension, no permissions prompt, and no hosting, backend or auth included.
Clone a page without approving anything
Paste the URL of a layout you want, or describe the site in a sentence, and Begin.sh returns a working static site or Expo app as a zip. No plugin directory, no site approvals, no browsing data to manage.
Clone a page →