@devries-cameron20 / t3code-1 / commits / d26066000d
Fork 0

The best way to control Claude Code, Codex and more from any computer or phone

docs(codex): explain Chrome extension connection errors (#38429)

Co-authored-by: maria-rcks <maria@kuuro.net>

DukMaxxi committed Nov 19, 2026 at 21:10 UTC d26066000d31146070a94a178e2cebe5513bb279
1 file changed +16
docs/user/providers-codex.md
+16
@@ -128,6 +128,22 @@ in the thread on web, desktop, or mobile. Some tools offer access for one reques
128 the current session, or permanently. See [Permission modes](./permission-modes.md)
129 for command and file approvals.
130
131 +## Use the OpenAI Chrome extension
132 +
133 +Connecting ChatGPT in **Settings → Providers** signs in the Codex provider.
134 +Using your signed-in Chrome profile through the extension requires a browser
135 +connection for the current Codex thread.
136 +
137 +If a T3 Code thread reports `The browser access host is unavailable`, its browser
138 +host is unavailable; this does not identify an extension connection failure.
139 +For a task that requested Chrome, follow [OpenAI's setup guide](https://learn.chatgpt.com/docs/chrome-extension),
140 +then select Chrome in a Codex chat in the ChatGPT desktop app.
141 +If the task runs on a remote environment, `localhost` in the desktop browser
142 +refers to your computer. Forward the remote page's port or use a URL reachable
143 +from your computer before repeating the task. Connecting to T3 Code through a
144 +relay or tunnel does not by itself expose that page. T3 Code's built-in browser
145 +preview uses its own browser session.
146 +
147 ## Use Daybreak
148
149 Models with cyber access programs show a Cyber Access option in the model