Its theme's rank, 14 days: 3 on the Codex sheet
2 people reported

All time, since Oct 28.

Lost cua_repl browser tool

“A thread that was running during an automatic app update permanently loses the browser tool.”

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/22579/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

Resumed threads lose cua_repl browser tool after app restart or update. After the app updates or restarts, the resumed thread is told "mcp__cua_repl" is no longer available and it does not come back.

Is this your bug?

File my report
Where
Desktop app
Error text
The following namespaces are no longer available. Do not call tools in them unless those tools are declared in a later update:
Versions
26.1027.6604
Platforms
macOS, Windows
How bad
Breaks a normal workflow.

Part of: Browser control fails to connect36 bugs

  1. Request-header policy load failure16 people
  2. Chrome extension not detected16 people
  3. Browser control times out12 people
  4. Chrome tab operations fail8 people
  5. Browser disabled despite toggle11 people
  6. Browser access host unavailable12 people
  7. Browser tab control fails4 people
  8. Agent finds no browser5 people
  9. Browser access host unavailable9 people
  10. Chrome tab control timeoutMs error7 people
Show all 35Show only the largest 10
  1. Browser unavailable to assistant4 people
  2. Embedded browser unusable when sidebar keeps client-new-thread conversation ID5 people
  3. Browser tab access lost5 people
  4. In-app browser not available4 people
  5. Browser service module missing3 people
  6. In-app browser policy check fails2 people
  7. Browser tools missing in chat4 people
  8. Chrome connection drops2 people
  9. Browser ID unavailable2 people
  10. Built-in Browser unreachable2 people
  11. Chrome native host not registered2 people
  12. Chrome tab listing fails2 people
  13. Chrome not available to runtime2 people
  14. Chrome debugger detaches, CDP timeouts3 people
  15. Browser Use policy check fails3 people
  16. Side-panel browser control fails2 people
  17. Chrome page loads stall while browser control resolves paused document responses4 people
  18. Browser access host unavailable15 people
  19. Chrome missing from @ menu3 people
  20. Browser context error in Chrome4 people
  21. Browser access host unavailable3 people
  22. Chrome browser access unavailable3 people
  23. Browser extension connection lost5 people
  24. Browser.list_tabs context error4 people
  25. Browser reported disabled in chat4 people

Not quite your bug?

  1. Existing tasks lose browser tools2 people
  2. Delegated tasks missing browser tools15 people

Original reports2, newest first

  1. Thread running during an app update loses the cua_repl browser tool permanentlyOn GitHub#59191
  2. macOS: resumed chat loses cua_repl browser controls after app restart despite browser backend being readyOn GitHub#57826

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.