Its theme's rank, 14 days: 3 on the Codex sheet
12 people reported
All time, since Sep 20, including 4 thumbs-up on GitHub.
Browser control times out
“The built-in browser is sometimes detected, but creating a tab, opening a page, or reading page content can time out.”
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/14290/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
Browser control times out in Codex Desktop on macOS. Built-in browser and Chrome extension are detected, but listing tabs, opening a page or reading content times out, while the desktop log reports no ChatGPT browser route.
Is this your bug?
File my report- Where
- Browser Use
- Error text
No ChatGPT browser route is available for browser session- Versions
- 26.911.61220 to 26.1029.61003
- Platforms
- macOS
- How bad
- Some reports say it blocks them completely.
Part of: Browser control fails to connect36 bugs
- Request-header policy load failure16 people
- Chrome extension not detected16 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
- 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 reports9, newest first
- Codex Desktop for macOS: In-App Browser and Chrome Extension Control Time OutOn GitHub#59543
- Codex Desktop for macOS: In-App Browser and Chrome Extension Control Time OutOn GitHub#59542
- In-app browser unavailable and Chrome extension won’t connectOn GitHub#52619
- @Chrome: session route captured then revoked within ~374 ms by a client-new-thread browser host (Desktop 26.1002.52244)On GitHub#52472
- [macOS] Built-in browser is visible, but Browser Use tools are unavailable across chatsOn GitHub#52035
- [macOS Intel][26.930.21537] Chrome discovered but tab enumeration fails after ~31 secondsOn GitHub#50382
- macOS: Chrome browser control times out with “No ChatGPT browser route is available”On GitHub#48322
- [Desktop][Browser Use] No ChatGPT browser route prevents Chrome and built-in browser tab discoveryOn GitHub#47270
- codex can not open or control the chrome tab pageOn GitHub#46757