Windows desktop: cua.getState fails with nodeRepl.fetch request failed while built-in browser is visible

Summary

On Windows, the desktop app can display the built-in browser, but the browser automation tool cannot enumerate or control it. This blocks an authorized website deployment workflow.

Reproduction

1. Open a page in the built-in browser.
2. Run await cua.getState(); through mcp__cua_repl.js.

Actual result

After approximately 21 seconds, the tool returns:

{"apps":[],"browsers":[],"errors":["Browsers: Error: nodeRepl.fetch request failed"]}

The tool also reports Error: nodeRepl.fetch request failed.

Expected result

The tool enumerates the visible built-in browser tab and allows browser interaction.

Environment and attempts

• Windows, PowerShell workspace.
• Reproduced on 2026-09-14.
• Exact desktop app version not verified.
• Resetting the CUA JavaScript session and retrying did not restore browser enumeration in this session.
• The app's open-in-panel tool can queue a browser URL, but this does not restore automation access.
• No root cause is confirmed.

This report intentionally excludes account information, session identifiers, screenshots, credentials, browser storage and raw logs.

Start by reproducing the failure with cua.getState() through mcp__cua_repl.js on Windows, then trace the reported nodeRepl.fetch request failed path. Done means the visible built-in browser is enumerated and can be controlled without the request failure.