Chrome control became read-only despite a valid native host, then recovered after a session reset / clean restart

ChatGPT Bugs
,
1

I am sharing a troubleshooting case in case it helps other Codex / ChatGPT Desktop users experiencing a Chrome integration that can read pages but cannot interact with them.

Environment

  • macOS on Apple Silicon
  • ChatGPT / Codex Desktop 26.818.31338
  • ChatGPT Chrome extension 1.2.27268.51612

Symptom

The extension could read page content and identify visible elements, but it could not click, type, or otherwise interact with the page. Depending on the attempt, the UI reported that the Chrome control connection was unavailable or that the native component was outdated.

What we verified

  • The Native Messaging manifest (com.openai.codexextension.json) existed and was valid.
  • Its allowed extension origins and path were correct.
  • The path resolved through the latest symlink to the installed 26.818.31338 Chrome plugin bundle.
  • The ChatGPT for Chrome native host existed, was executable, and launched successfully.
  • The binary was a native ARM64 Mach-O executable.
  • Its code signature was valid and identified OpenAI OpCo, LLC as the signing authority.
  • Reinstalling the Chrome extension, fully restarting Chrome and ChatGPT Desktop, and removing/regenerating the bundled Chrome plugin cache did not restore interaction immediately.

Recovery timeline

After logging out of and back into ChatGPT Desktop, browser interaction started working for one webmail site, while other sites still remained effectively read-only. The next day, without identifying one additional definitive fix, Chrome control worked normally again across other sites as well, including complex authenticated web apps.

Cautious interpretation

This looks consistent with a temporary session or handshake problem between ChatGPT Desktop, the Chrome extension, and the native bridge. However, we did not prove that as the root cause. It is also possible that the eventual recovery depended on a clean process restart, refreshed authentication state, or another transient condition.

The main takeaway is that the installation itself appeared healthy, and no single reinstall or cache reset was demonstrably the fix. If the same symptom recurs, I would first try:

  1. Log out of and back into ChatGPT Desktop.
  2. Fully quit both Chrome and ChatGPT Desktop.
  3. Reopen Chrome, then ChatGPT Desktop.
  4. Test in a fresh tab.
  5. Check for duplicate or stale ChatGPT for Chrome bridge processes.

Has anyone else seen this partial recovery pattern, where one site becomes interactive first and full Chrome control returns only later?

2

Yes, that happened to me but it also could not be connected to any action taken. It’s random.

3

Maybe I have a solution for you, see my comment at github… (I can’t put link to OpenAI github issue here :slightly_smiling_face: )

Start new chat and before requesting any work send this request:
Use Chrome computer control.
Initialize the Chrome browser-control runtime and run
agent.browsers.list().
Do not use getTabContext as a substitute.

It initializes chrome browser control and then you can send all your requests for interaction with your current chrome tab.

PS: Next time I recommend you to state also exact message string the AI gives you. In my case it was message:
Chrome control is unavailable—the Codex Chrome native host is out of date. Please update or reinstall the Codex Chrome plugin