#@Chrome browser controls no longer working for Codex chrome extension

13 messages · Page 1 of 1 (latest)

torpid fulcrumBOT
#

Reported by @misty yacht

Bug Report: @Chrome browser controls no longer working for Codex chrome extension
`Steps to Reproduce`

Steps to reproduce
Launch ChatGPT desktop 26.818.31338 and Chrome.
Confirm the official ChatGPT extension is enabled.
Open an ordinary authenticated site in Chrome.
Open the ChatGPT extension side panel.
Ask the side-panel thread to read the selected tab; URL, title, and visible text are returned.
Ask it to click a link, navigate, open a result card, or observe a new tab.
Interactive control is unavailable and the thread reports that the native host did not provide the browser-client path / is o

`Expected Result`

@chrome plugin will use browser controls and click through UI as expected

`Actual Result`

The official ChatGPT Chrome extension can read the active tab's URL, title, and visible text, but a side-panel session cannot initialize interactive Chrome control. Clicking, typing, navigation, opening result cards, following redirects, and observing newly opened tabs are unavailable. The session reports a capability state equivalent to: the native host did not provide a browser-client path / the host is out of date.

`Environment`

macOS 26.6.2 (build 25G83) arm64, ChatGPT desktop 26.818.31338 (build 6892), bundled Chrome plugin/native host 26.818.31338.

#
Additional Information

Please provide relevant details to help resolve the issue, such as:

  • ChatGPT Shared Link (if applicable).
  • Screenshots or videos demonstrating the problem.

-# ➜ Need to contact support? Visit the OpenAI Help Center.

vast root
#

Having the same issue in the Chrome ChatGPT extension as well | Mac.

misty yacht
vast root
#

Can anyone have a look at this issue or open source the chrome extension, happy to raised a fix

misty yacht
misty yacht
#

@vast root I asked chatgpt who might be the best people at openai the help get this fixed and send linkedin in-mails to the following people:

  1. Alexander Embiricos, Codex Product Lead at OpenAI
    He is my strongest recommendation. He publicly announced the Chrome integration himself, saying the Codex team had shipped the Chrome extension and specifically describing multi-tab browser control. That puts him very close to the product ownership for the feature that is broken.

  2. Dominik Kundel, OpenAI
    Dominik appears to have been directly involved with launching and demonstrating the functionality. Alexander’s launch announcement specifically points to Dominik’s demonstration, and Dominik separately described the Chrome feature’s ability to connect to existing authenticated web apps, script browser interactions, work across pages, and automate actions.

vast root
#

Can’t we tag them here ?

misty yacht
#

Idk their discord @‘s unfortunately

old pebble
#

Same issue for me

weak ridge
#

use work/codex for fix that

misty yacht