Browser Use reports CLI disconnected despite healthy bundled Codex CLI (macOS 27 beta)

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

runtime version: 0.144.0-alpha.4 latest version: 0.144.1 latest version status: current version is not older

What subscription do you have?

Pro

What platform is your computer?

MacOS 27 beta 3

What issue are you seeing?

Issue

After updating to the latest ChatGPT Desktop on macOS 27 Developer Beta (Apple Silicon), Browser Use/Codex intermittently reports that the CLI is disconnected and previously displayed errors such as "Command not found: codex" and "Could not create a new process and open a pseudo-tty."

I performed extensive troubleshooting and believe the problem is not with the Codex CLI itself, but with the Desktop application's Browser Use/IPC integration.

What steps can reproduce the bug?

Findings
The bundled CLI exists at:
/Applications/ChatGPT.app/Contents/Resources/codex
The executable is valid, correctly signed, and launches successfully.

Running:

/Applications/ChatGPT.app/Contents/Resources/codex doctor

reports:

17 OK
1 Idle (Background Server in ephemeral mode)
0 Warnings
0 Failures
Authentication succeeds.
WebSocket connection succeeds (HTTP 101 Switching Protocols).
HTTPS reachability succeeds.

Runtime diagnostics report:

installed=true
problemCount=0

Desktop logs correctly resolve the bundled CLI path:

codexCliPath=/Applications/ChatGPT.app/Contents/Resources/codex
There are no CLI launch failures, permission errors, download failures, TLS failures, or runtime corruption reported.

The only recurring errors I found in the Desktop logs are renderer/state related:

Received turn/started for unknown conversation
Received turn/completed for unknown conversation
ResizeObserver loop completed with undelivered notifications
ShikiError: Language text not found

Based on the investigation, it appears the bundled CLI is healthy, but the Desktop application is losing Browser Use session/conversation state or failing during its IPC orchestration with the bundled Codex runtime.

What is the expected behavior?

Expected behavior

Browser Use should successfully launch and maintain communication with the bundled Codex runtime.

Since the bundled CLI is present, executable, authenticated, and passes all codex doctor diagnostics (17 OK / 0 WARN / 0 FAIL), the Desktop application should recognize the CLI as connected and Browser Use should function normally without reporting CLI disconnects or pseudo-terminal errors.

The Desktop application should correctly maintain Browser Use conversation/session state throughout execution and should not emit "Received turn/started for unknown conversation" or "Received turn/completed for unknown conversation" during normal operation.

Additional information

_No response_