[Windows/iOS Remote] New mobile-created conversations time out on every first message

What version of the Codex App are you using (from the About dialog)?

• Desktop host: ChatGPT/Codex Desktop 26.803.81509
• Mobile client: ChatGPT for iOS 1.2026.209
• Host name shown in the iOS Remote view: LeX-PC

What subscription do you have?

ChatGPT Plus.

What platform are you using?

• Host: Windows desktop running ChatGPT/Codex Desktop
• Remote client: iPhone using the ChatGPT iOS app and the Codex Remote feature

What issue are you seeing?

When I use Codex Remote from my iPhone to control my Windows desktop host, every new conversation created from the iPhone fails on its first request, even when the message is only Hi.

The failure is independent of the message content and appears independent of the selected reasoning model/effort.

The important difference is:

• iPhone Remote -> create a new conversation -> send any message: request times out.
• Desktop -> create the conversation first -> open that same conversation from iPhone Remote -> send a message: works.

This makes the failure look specific to the mobile-created new-thread path, rather than a general inability of the host to process remote turns.

What steps can reproduce the bug?

1. Pair ChatGPT on iOS with the Windows ChatGPT/Codex Desktop host using Remote.
2. From the iPhone Remote view, create a new Codex conversation on the host.
3. Send a minimal message such as:

   Hola
   

4. Wait for the request to complete.
5. Observe that the user message remains visible but the request eventually fails with:

   La solicitud a Codex ha excedido el tiempo de espera.
   

6. Repeat with different message content and reasoning-model settings; the same timeout occurs.
7. As a control, create a new conversation from the Windows Desktop app first.
8. Open that desktop-created conversation from iPhone Remote and send a message; this path works.

What is the expected behavior?

A new conversation created through iPhone Remote should start normally and complete a simple first request.

If the Remote connection or host data plane is unhealthy, the mobile client should show a useful diagnostic and provide a reliable retry/recovery path rather than timing out every new conversation.

What is the actual behavior?

Every new conversation started from iPhone Remote times out on the first request, including a one-word message. Restarting both the Desktop and iOS apps does not resolve the problem.

Remote turns can also show extremely slow reasoning before failing; it is unclear whether that is part of the same issue.

Troubleshooting and host-side observation

• Restarted ChatGPT/Codex Desktop and the ChatGPT iOS app; no change.
• Tested different message contents, including Hola; no change.
• Tested different reasoning-model settings; no change.
• The Windows host is otherwise usable, and a desktop-created conversation can receive a message from iPhone Remote successfully.
• Checked for the proxy-process accumulation described in #30791. At the time of the check, no matching process was present:

Get-CimInstance Win32_Process |
  Where-Object {
    $_.Name -ieq 'powershell.exe' -and
    $_.CommandLine -match 'codex\\.ps1 app-server proxy'
  } |
  Measure-Object

Count : 0

This was a point-in-time check; it does not establish whether a proxy process existed during the failed request.

Related issues

• #27592 discusses iOS Remote latency and backpressure in the remote-control transport.
• #28340 discusses iOS failing to open an already-running task conversation.
• #30791 discusses Windows Remote failures with accumulating codex.ps1 app-server proxy processes; that process evidence is not present in this report.

No credentials, tokens, auth files, or private logs are included. I can provide additional sanitized diagnostics if maintainers specify what is useful.

Feedback ID: not captured.

Start by reproducing the iPhone Remote flow and compare a mobile-created conversation with a desktop-created one. Read related issues #27592, #28340, and #30791, and use the reported PowerShell proxy-process check as context. Done means a mobile-created conversation completes its first simple request or presents a useful diagnostic and recovery path.