4 people reported
All time, since Oct 3.
Browser tab control fails
“Codex Desktop recognizes available browser backends but cannot successfully interact with Chrome or Edge tabs.”
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/11355/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 fails with nodeRepl.fetch request failed on Windows. Chrome and Edge are detected but tab state returns empty tabs; the in-app browser times out reading tabs.
Is this your bug?
File my report- Where
- Browser automation
- Error text
nodeRepl.fetch request failed- Versions
- 26.1007.21434
- Platforms
- Windows
- How bad
- Stops work: a core feature can't be used. Some reports say it used to work. 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
- Browser control times out12 people
- Chrome tab operations fail8 people
- Browser disabled despite toggle11 people
- Browser access host unavailable12 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 reports5, newest first
- Windows browser control still times out after Browser reinstall: Chrome tab listing fetch failure and IAB external-page hangsOn GitHub#54481
- Windows browser control fails across Chrome, Edge and in-app browser after update; nodeRepl.fetch request failedOn GitHub#53056
- Windows Codex Desktop: Browser automation fails with nodeRepl.fetch request failedOn GitHub#52898
- Windows Edge Browser Use fails: extension detected but no tabs and nodeRepl.fetch request failedOn GitHub#50682
- Windows Edge Browser Use fails: extension detected but no tabs and nodeRepl.fetch request failedOn GitHub#50681