Repository navigation
Description
Description
Since November 20, 2026, conversations in the same Codex Windows desktop project have shown inconsistent browser tool availability. One conversation can access the in-app browser through CUA, while an existing conversation and a newly created conversation do not expose the CUA runtime. Restarting the application did not restore the capability in affected conversations.
Observed behavior
- Existing affected conversation: browser initializer lookup returned
undefined. - Working conversation:
cua.getBrowser({ id: "iab" })succeeded. - Newly created conversation: CUA runtime was absent and the initializer lookup returned
undefined. - Windows terminal execution remained functional in the diagnosed existing conversations.
- Both diagnosed existing conversations reported PowerShell 7.6.9, Windows NT 10.0.26300.0, and a
workspace-writesandbox profile. - Shell network access was restricted independently of browser access. One affected conversation resolved the target hostname but could not initialize a browser; the working conversation initialized the in-app browser despite restricted shell networking.
- Filesystem write access was not verified. The conversations reported different working directories but belonged to the same project.
Expected behavior
Conversations in the same project with equivalent permissions should have consistent access to supported browser capabilities. If a capability is intentionally unavailable, the application should explain the restriction and provide a recovery mechanism.
Reproduction and impact
The issue is intermittent across conversations; no deterministic reproduction sequence has been established. It interrupts browser-dependent development and QA workflows, including long-running conversations with accumulated context. No project files, security settings, or permissions were modified during diagnostic checks.
The user reports approximately two months of regular use without encountering this behavior before November 20. The desktop application version was not collected. The underlying cause is unconfirmed; conversation-specific tool provisioning, session initialization, and tool-state restoration are possible areas to investigate.
Related reports
- Browser control tools unavailable in existing Work conversations after Windows restart, while new conversations work #60217 describes an existing conversation losing browser tools after a Windows restart, while a new conversation worked. Here, a newly created conversation was also affected.
- [Windows] In-app browser control disappears mid-chat while browser tabs remain open #62147 describes browser control disappearing during an ongoing Windows conversation. No common root cause has been established.
Please compare provisioning between working and affected conversations, investigate the missing CUA runtime, and clarify supported recovery. Please consolidate with an existing issue if appropriate.
Private workspace paths, project identifiers, hostnames, and conversation details have been omitted.
Activity
github-actions commentedon Nov 21, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action