Failed to update connection

Open 💬 5 comments Opened Jun 3, 2026 by oscarhugopaz

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

26.601.21317

What subscription do you have?

Plus

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

I am experiencing this issue between two Macs.

After revoking one Mac from the "Control Other Devices" section on another Mac, I tried to add it again. However, the Mac now appears as a failed connection, and I receive the following error message:

"Failed to update connections."

As a result, I am unable to reconnect or manage the device properly.

What steps can reproduce the bug?

On a Mac, open the "Control Other Devices" section.
Revoke/remove another Mac that was previously connected.
Attempt to add the same Mac again.
The Mac appears as a failed connection.
An error message is displayed: "Failed to update connections."

This issue occurs between two Macs.

Feedback ID: no-active-thread-019e8e4c-da61-71d1-8479-6631b1942700

What is the expected behavior?

After revoking a Mac, I should be able to add and reconnect the same Mac again successfully. The connection should be updated without errors, and the device should appear in the "Devices That Can Control This Mac" list as an active, connected device.

This behavior is expected when connecting one Mac to another Mac.

Additional information

_No response_

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#25532

Powered by Codex Action

afuchshofer-png · 2 months ago

I am seeing the same issue, but in both directions between two Macs.

Both Macs are signed into the same account/workspace. They see each other as online, and adding/removing the connection works, but Mac-to-Mac remote control fails with:

"Verbindung konnte nicht aktualisiert werden"
"Verbindung fehlgeschlagen"

Important detail:
Remote control from the iPhone app to both Macs works immediately. So account/workspace/relay and host-side remote access appear to be working. The problem seems specific to Mac-to-Mac remote control in the Codex macOS app.

I already tried:

rebooting both Macs
signing out and back in
quitting and reopening Codex
deleting and re-adding the connections
resetting local Codex app data

Feedback ID:
no-active-thread-019eada2-293a-7c60-ae61-f340fea91a45

oscarhugopaz · 2 months ago

Update

Removing the remote connection records from the local database did not fix the issue.

The only successful workaround was a full Codex reset on both Macs: deleting the app and all Codex-related data under Application Support, Caches, Logs, Preferences, and HTTPStorages, then setting up Remote Control again from scratch.

Simply uninstalling and reinstalling Codex was not enough. The issue only disappeared after removing all persisted Codex state, which suggests there may be some stale connection/enrollment state stored outside the remote connection records themselves.

After performing a complete reset on both Macs and re-enrolling the devices, Remote Control started working normally again.

outie · 2 months ago

## Update Removing the remote connection records from the local database did not fix the issue. The only successful workaround was a full Codex reset on both Macs: deleting the app and all Codex-related data under Application Support, Caches, Logs, Preferences, and HTTPStorages, then setting up Remote Control again from scratch. Simply uninstalling and reinstalling Codex was not enough. The issue only disappeared after removing all persisted Codex state, which suggests there may be some stale connection/enrollment state stored outside the remote connection records themselves. After performing a complete reset on both Macs and re-enrolling the devices, Remote Control started working normally again.

Would this reset clear my existing Codex desktop app chats/context?

oscarhugopaz · 2 months ago

Would this reset clear my existing Codex desktop app chats/context?

I can't say whether preserving ~/.codex would still resolve the issue, since I didn't test that.

What I can say is that the full reset procedure I followed will remove local chat history, since Codex stores conversations and metadata locally under ~/.codex (including sessions/ and state_5.sqlite), as well as application data under ~/Library/Application Support/Codex/.

Because I removed all of that data as part of the reset, any locally stored chats/context were also removed.

I don't know whether keeping ~/.codex while clearing the rest of the application state would have been sufficient to fix the Remote Control issue.