Its theme's rank, 14 days: 3 on the Codex sheet
3 people reported
All time, since Oct 30, including 1 thumbs-up on GitHub.
Chrome browser access unavailable
“The browser access host is unavailable”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/23311/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Chrome access fails with "browser access host is unavailable" in Codex CLI. Chrome works in a local Work chat, but a Codex project chat reports Computer Use was not approved to use Google Chrome.
Is this your bug?
File my report- Where
- Chrome extension
- Error text
The browser access host is unavailable- Versions
- 0.166.0
- Platforms
- macOS
- How bad
- Breaks a normal workflow.
Part of: Browser control fails to connect36 bugs
- Request-header policy load failure16 people
- Chrome extension not detected16 people
- Browser control times out12 people
- Chrome tab operations fail8 people
- Browser disabled despite toggle11 people
- Browser access host unavailable12 people
- Browser tab control fails4 people
- Agent finds no browser5 people
- Browser access host unavailable9 people
- Chrome tab control timeoutMs error7 people
Show all 35Show only the largest 10
- Browser unavailable to assistant4 people
- Embedded browser unusable when sidebar keeps client-new-thread conversation ID5 people
- Browser tab access lost5 people
- In-app browser not available4 people
- Browser service module missing3 people
- In-app browser policy check fails2 people
- Browser tools missing in chat4 people
- Chrome connection drops2 people
- Browser ID unavailable2 people
- Built-in Browser unreachable2 people
- Chrome native host not registered2 people
- Chrome tab listing fails2 people
- Chrome not available to runtime2 people
- Chrome debugger detaches, CDP timeouts3 people
- Browser Use policy check fails3 people
- Side-panel browser control fails2 people
- Chrome page loads stall while browser control resolves paused document responses4 people
- Browser access host unavailable15 people
- Chrome missing from @ menu3 people
- Browser context error in Chrome4 people
- Browser access host unavailable3 people
- Lost cua_repl browser tool2 people
- Browser extension connection lost5 people
- Browser.list_tabs context error4 people
- Browser reported disabled in chat4 people