Regression: Remote conversations from Intel Mac fail to load on Apple Silicon Mac after 26.730.61639 update

Open 💬 0 comments Opened Aug 6, 2026 by agustinbarrientos

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

26.730.61639 on both computers

What subscription do you have?

Max

What platform is your computer?

Computer A, Apple Silicon: Darwin 25.6.0 arm64 arm | Computer B, Intel: Darwin 24.6.0 x86_64 i386

What issue are you seeing?

After updating Codex to version 26.730.61639 on both computers, remote conversations associated with Computer B, an Intel Mac, stopped loading on Computer A, an Apple Silicon Mac.

This setup worked as expected before the update, without connection issues.

When I try to open a remote conversation from Computer B on Computer A, Codex repeatedly cycles through the following messages:

Loading task
Couldn't connect to {computer name}
Connection to {computer name} was lost. Reconnecting...

The connection never recovers, and the same sequence repeats indefinitely.

Computer B still appears to be reachable. I also have Computer B connected through the Codex app on my iPhone (1.2026.202, 30140022279), and its remote conversations continue to load and work there without any issues. This suggests that the problem is specific to the connection between the two desktop computers, rather than Computer B being completely unavailable.

What steps can reproduce the bug?

  1. Install or update Codex to version 26.730.61639 on two Macs:
  • Computer A: Apple Silicon
  • Computer B: Intel
  1. Have remote conversations associated with Computer B.
  2. Open Codex on Computer A.
  3. Select or open one of the remote conversations from Computer B.
  4. Observe that the conversation does not load.
  5. Codex enters an indefinite loop showing:

``text
Loading task
Couldn't connect to {computer name}
Connection to {computer name} was lost. Reconnecting...
``

  1. Open the same Computer B connection from the Codex mobile app.
  2. Observe that it continues to connect and work correctly from the phone.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗