Its theme's rank, 14 days: 3 on the Codex sheet
12 people reported
All time, since Nov 4, including 6 thumbs-up on GitHub.
Browser access host unavailable
“Chrome and the desktop app are both reported as running, but the CLI returns an empty browser list.”
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/25698/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 browser control fails with host unavailable in CLI sessions. Browser discovery returns an empty list or an error while the same Chrome and extension work from the desktop app.
Is this your bug?
File my report- Where
- Chrome browser integration
- Error text
Browsers: Error: The browser access host is unavailablePasted in 2 reports- Versions
- 0.166.0 to 0.167.0. Still reported on the newest version, 0.167.0.
- Platforms
- macOS
- How bad
- Breaks a normal workflow. Some reports say it used to work.
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 tab control fails4 people
- Agent finds no browser5 people
- Browser access host unavailable9 people
- Chrome tab control timeoutMs error7 people
- Browser unavailable to assistant4 people
Show all 35Show only the largest 10
- 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
- Chrome browser access unavailable3 people
- Browser extension connection lost5 people
- Browser.list_tabs context error4 people
- Browser reported disabled in chat4 people
Original reports6, newest first
- The browser access host is unavailableOn GitHub#60151
- [macOS][CLI 0.167.0] Chrome Browser Use fails with "The browser access host is unavailable" while desktop worksOn GitHub#60130
- [macOS arm64][CLI 0.167.0][Edge] Browser access host unavailable; native app control succeedsOn GitHub#60071
- [CLI 0.167.0][macOS] Chrome plugin still fails: browser access host unavailable — please fix CLI support and stop the restart loopOn GitHub#59799
- [macOS arm64][CLI 0.166.0] codex exec cannot use the ChatGPT Chrome extension: "The browser access host is unavailable" (desktop works)On GitHub#59592
- CLI browser control fails: “The browser access host is unavailable”; desktop worksOn GitHub#59456