Skip to content

Windows Codex App: Chrome and In-App Browser operations take 20–60 seconds and frequently time out #59586

Open

Description

@Anguse666

What version of the Codex App are you using (From “About Codex” dialog)?

26.1029.7803.0

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 11 23H2 (Build 22631), x64

What issue are you seeing?

Description

The Codex Windows desktop app has severe browser-control latency affecting both Chrome Browser Use and the built-in browser.

Browser operations frequently take 20–60 seconds, even on https://example.com/. Some operations eventually succeed, while others time out and reset the JavaScript execution kernel.

The issue persists after fully restarting Codex and testing in a fresh conversation.

Observed behavior

  • Chrome tab enumeration: 15.85 seconds.
  • Chrome page reading: 21.6–43.32 seconds.
  • Chrome navigation: the Products page was successfully opened, but the tool timed out while waiting for the result.
  • In-app browser tab enumeration: 21.67 seconds, even with no existing tabs.
  • In-app browser navigation: previously succeeded in 53.41 seconds, but subsequent attempts timed out after 30–60 seconds.
  • In-app browser page-state reading: 27.75 seconds.
  • Basic Node REPL execution (nodeRepl.write(2)): 241 milliseconds, successful.

Some page-reading operations automatically retrieve the accessibility tree, so their durations are not directly comparable to metadata-only operations.

Error messages

js execution timed out; kernel reset, rerun your request

Previously also encountered:

Debugger unattached

Environment

  • Codex Windows package version: 26.1029.7803.0
  • Codex logged client version: 26.1029.61003
  • Chrome version: 156.0.8078.80
  • ChatGPT Chrome extension: 1.26.1102.11740
  • VPN: Clash Verge with TUN enabled
  • Local HTTP/Mixed proxy: 127.0.0.1:7897

Troubleshooting completed

  1. Verified that the proxy port is listening.
  2. Verified HTTP CONNECT and SOCKS5 connectivity.
  3. Confirmed successful HTTPS access to example.com through the proxy.
  4. Tested both Chrome and the built-in browser independently.
  5. Confirmed that the browser can sometimes successfully navigate even when the tool reports a timeout.
  6. Verified basic Node REPL execution completes in 241 ms.
  7. Restarted the Codex desktop app and tested in a fresh conversation.
  8. Inspected process information, TCP connections and available logs without finding a confirmed root cause.

No browser runtime files, sandbox permissions, proxy settings or application configuration were modified.

Expected behavior

Browser navigation, tab enumeration and page-state retrieval should complete reliably without excessive delays or JavaScript kernel resets.

Actual behavior

Both browser backends experience severe latency and intermittent timeouts.

Additional notes

The issue appears to affect the browser-control workflow rather than basic JavaScript execution. However, the root cause has not been established, and an interaction with VPN routing or proxy inheritance has not been ruled out.

Please investigate browser-control initialization, IPC/RPC communication and browser page-state retrieval latency on Windows.

What steps can reproduce the bug?

Steps to reproduce

  1. Launch the Codex desktop application on Windows 11.
  2. Start a fresh conversation without opening an existing project.
  3. Enable Clash Verge VPN with TUN mode. The local mixed proxy port is 7897.
  4. Ask Codex to use the built-in browser to open https://example.com and read the page title.
  5. Observe that creating a browser tab or retrieving page state takes 20–60 seconds or times out.
  6. Repeat the test using Chrome Browser Use with the official ChatGPT Chrome extension.
  7. Observe similar delays when enumerating tabs, reading page state, or navigating between pages.

Reproduction results

Built-in browser:

  • Tab enumeration: 21.67 seconds, successful.
  • Navigation to example.com: 60.08 seconds, timed out.
  • Another navigation attempt after restarting Codex: 30.2862 seconds, timed out.
  • Previously successful navigation: 53.41 seconds.
  • Page-state retrieval: 27.75 seconds.

Chrome Browser Use:

  • Tab enumeration: 15.85 seconds.
  • Page-state retrieval: 21.6–43.32 seconds.
  • Clicking a navigation link sometimes completes successfully, but the browser tool times out while waiting for the result.

Control test:

  • Basic Node REPL execution (nodeRepl.write(2)) completed successfully in 241 milliseconds.

Error message

js execution timed out; kernel reset, rerun your request

A previous Chrome test also returned:

Debugger unattached

The problem persists after completely restarting the Codex application and starting a new conversation.

The issue is intermittent: some browser operations eventually succeed, while others time out. No specific success rate has been established.

What is the expected behavior?

Chrome Browser Use and the built-in browser should reliably open webpages, enumerate tabs, retrieve page state, and perform navigation without excessive delays.

Basic operations on simple pages such as https://example.com should complete within a reasonable amount of time.

Browser tool calls should not regularly take 20–60 seconds or trigger JavaScript execution kernel resets.

When a browser navigation succeeds, Codex should return the operation result without timing out while waiting for the page state.

Additional information

Environment

  • OS: Windows 11 23H2 (Build 22631)
  • Codex Windows package: 26.1029.7803.0
  • Codex logged client version: 26.1029.61003
  • Chrome version: 156.0.8078.80
  • ChatGPT Chrome extension: 1.26.1102.11740
  • VPN: Clash Verge with TUN enabled
  • Local proxy: 127.0.0.1:7897 (HTTP/SOCKS5)

Network verification

  • HTTP CONNECT succeeded.
  • SOCKS5 handshake succeeded.
  • HTTPS requests to example.com through the proxy returned HTTP 200.
  • Basic network connectivity is working.

Additional troubleshooting

  • Both Chrome and the built-in browser are affected.
  • Browser tab discovery succeeds but is unusually slow.
  • Basic Node REPL execution is fast (241 ms).
  • A complete Codex restart and fresh conversation did not resolve the issue.
  • Browser-related processes and named pipes were detected.
  • No confirmed root cause was identified from the available logs or TCP connection snapshots.

Proxy environment variables were observed in the diagnostic PowerShell process, but their inheritance by individual browser-control processes was not verified.

Request

Please investigate possible performance issues in the Windows browser-control infrastructure, including browser initialization, IPC/RPC communication, and accessibility-tree retrieval.

An interaction with VPN routing or proxy inheritance cannot yet be ruled out.

No sandbox permissions, runtime files, application configuration, or proxy settings were modified during troubleshooting.

Activity

  1. added
    appIssues related to the Codex desktop app
    on Nov 5, 2026
  2. hubinegg-stack commented on Nov 11, 2026

    @hubinegg-stack

    Windows follow-up: isolated conversation still fails; current-chat route errors confirmed

    Observed 2026-11-11 (Asia/Shanghai), Windows x64, desktop package 26.1103.7773.0, Chrome extension 1.26.1102.11740. This consolidates existing diagnostics; no additional browser retries were performed for this submission.

    Actual results

    Context Backend/control Successful / attempted Tool wall time Result
    Original conversation In-app browser, open https://example.com 0/1 34.7841 s js execution timed out; kernel reset, rerun your request
    Original conversation Chrome, same page 0/1 33.6055 s Same timeout
    JS control 2+2 in CUA JS 1/1 3.7606 s including initialization 4; internal expression measurement 1 ms
    Newly created isolated conversation In-app browser, same page 0/1 0.9779 s Browser is not available: iab
    Newly created isolated conversation Chrome, same page 0/1 35.5417 s js execution timed out; kernel reset, rerun your request

    Original inventory listed Chrome and IAB; isolated inventory listed only Chrome. Neither browser attempt returned a usable page for title reading, clicking a visible link, or checking post-click state. A timeout does not prove that no tab was created.

    The isolated conversation inherited the same desktop context and used the same running version; account identity was not independently verified through credentials. No migration was performed.

    Sanitized log evidence (UTC)

    Original conversation:

    2026-11-10T23:58:16.828Z IAB_LIFECYCLE registered debugger listener routeKey=1:<original-chat>
    2026-11-10T23:58:59.471Z IAB_LIFECYCLE iab backend info request failed conversationId=<original-chat> errorMessage="No ChatGPT browser route is available for browser session <original-chat>"
    2026-11-10T23:58:59.473Z IAB_LIFECYCLE iab backend info request completed conversationId=<original-chat> metadataCodexSessionId=<original-chat>
    

    Isolated conversation:

    2026-11-11T00:25:23.213Z IAB_LIFECYCLE iab backend info request failed conversationId=<isolated-chat> errorMessage="No ChatGPT browser route is available for browser session <isolated-chat>" request=getInfo
    

    The latest-eight-file scan found 33 missing-route lines explicitly associated with the isolated conversation, between 00:25:23.213Z and 00:25:29.859Z. These are log-line counts, not manual test attempts. No successful getInfo or route registration explicitly matching the isolated conversation was found in that bounded scan; this does not prove a route never existed outside it. Original-conversation logs contain both successful and unsuccessful resolution (81 missing-route lines in the same scan).

    Boundaries and interpretation

    Please investigate prepareSessionRoute / browser-session-registry lifecycle and active-window ownership: why does getInfo fail to resolve an explicitly matching conversation route, sometimes alongside a successful response? New-conversation isolation did not restore operation. Raw identifiers, user paths, credentials, personal browsing content and full unredacted logs are intentionally omitted.

  3. ninastienjkt88-dev commented on Nov 17, 2026

    @ninastienjkt88-dev

    Additional Windows measurements on Codex Desktop 26.1111.2228.0 (CLI 0.169.0-alpha.11.1; Computer Use 26.1111.21308): Chrome tab creation took about 53–66 seconds and timed out; a later tab listing took 16.748 seconds. Accessibility-state capture and screenshots took roughly 42–50 seconds. In-app browser navigation timed out at about 60 seconds. A tab appeared afterward, so timeout did not prove creation failed. No root cause is established. Basic discovery and lightweight metadata were much faster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbrowserbugSomething isn't workingperformancetool-callsIssues related to tool callingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions