Repository navigation
Replies: 2 comments
|
The browser host error can't be fixed from T3 Code today, but the Chrome approval error should go away once the thread is out of Full access. "The browser access host is unavailable" comes from OpenAI's bundled browser plugin, the part that talks to the ChatGPT Chrome extension. The ChatGPT/Codex desktop app hands an access pipe and a verifying identity only to the "Computer Use was not approved to use Google Chrome" is the native Computer Use path being declined. Full access, the default for new threads, starts Codex turns with
If no card shows up, start a new thread with Supervised picked in the draft. This only fixes the native path, which controls Chrome as an app on screen. Tab access through the extension still needs the upstream fix. |

Uh oh!
There was an error while loading. Please reload this page.
Sol has trouble accessing my Chrome tabs in T3 Code, in Codex everything works no problem. I got this from the model:
Right—the failure persists across threads, so another new thread isn’t useful.
We have two concrete errors in T3:
Since ChatGPT can list the tabs, the next useful step is checking T3’s connection to Computer Use and its approval handling. That’s a suspected integration issue, not a confirmed cause. I found no exposed T3 tool to inspect or repair that connection.
I’d report those two errors to T3, alongside “works in ChatGPT; fails in a fresh T3 thread,” rather than change Chrome or macOS permissions.
Any ideas how to fix this?
All reactions