After going to Settings → Connections → Control This Mac, the page immediately jumps back

Open 💬 5 comments Opened Jul 6, 2026 by jiangxu0826
💡 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)?

Codex macOS 版本:26.623.101652

What subscription do you have?

plus

What platform is your computer?

mac客户端app

What issue are you seeing?

问题:
进入 设置 → 连接 → 控制这台 Mac 后,页面立即跳回。
此前点击“允许”时显示“无法启用远程控制,请重试”。

已尝试:

  1. 确认 Mac 和手机使用相同邮箱及工作区
  2. 退出并重新登录两端账号
  3. VPN 切换为 Global Proxy
  4. 重启 Mac
  5. 完全卸载并重新安装 Codex
  6. 仍可稳定复现

What steps can reproduce the bug?

Feedback ID: no-active-thread-019f36cc-0638-7573-9b25-bbb1e18d61fe

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 1 month ago

English translation:

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

Codex macOS version: 26.623.101652

What subscription do you have?

plus

What platform is your computer?

Mac client app

What issue are you seeing?

Issue:
After going to Settings → Connections → Control This Mac, the page immediately jumps back.
Previously, when clicking “Allow,” it displayed “Unable to enable remote control, please try again.”

Already tried:

  1. Confirmed that the Mac and phone are using the same email address and workspace
  2. Logged out and back into the accounts on both devices
  3. Switched the VPN to Global Proxy
  4. Restarted the Mac
  5. Completely uninstalled and reinstalled Codex
  6. Still can reproduce consistently

What steps can reproduce the bug?

Feedback ID: no-active-thread-019f36cc-0638-7573-9b25-bbb1e18d61fe

What is the expected behavior?

_No response_

Additional information

_No response_

<!-- codex-issue-translator -->

github-actions[bot] contributor · 1 month ago

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

  • #31161

Powered by Codex Action

freyfwt · 1 month ago

same problem

freyfwt · 1 month ago

I fixed the issue where enabling Codex Remote Control immediately showed “Failed to update remote-control status” and switched itself off.

There were two causes:

  1. The Codex background process failed to connect to wss://chatgpt.com/backend-api/wham/remote/control/server with TLS handshake EOF. I use Clash through Proxifier (127.0.0.1:7897), but Proxifier was resolving DNS locally. Disabling automatic DNS detection and enabling “Resolve hostnames through proxy,” followed by restarting Clash, Proxifier, and Codex, fixed the relay connection.
  1. Codex incorrectly discovered my GitHub SSH configuration as a remote development host. Changing:
Host github.com

to:

Host github.*

preserved GitHub SSH access while preventing Codex from treating it as a concrete SSH host.

After restarting Codex again, Remote Control enabled successfully.

jiangxu0826 · 1 month ago

你好,现在有一个新的问题,见附件,请看一下这个需要怎么解决,谢谢

Jason Jiang

freyfwt @.***>于2026年7月10日 周五11:50写道:

freyfwt left a comment (openai/codex#31231) <https://github.com/openai/codex/issues/31231#issuecomment-4931802981> I fixed the issue where enabling Codex Remote Control immediately showed “Failed to update remote-control status” and switched itself off. There were two causes: 1. The Codex background process failed to connect to wss:// chatgpt.com/backend-api/wham/remote/control/server with TLS handshake EOF. I use Clash through Proxifier (127.0.0.1:7897), but Proxifier was resolving DNS locally. Disabling automatic DNS detection and enabling “Resolve hostnames through proxy,” followed by restarting Clash, Proxifier, and Codex, fixed the relay connection. 2. Codex incorrectly discovered my GitHub SSH configuration as a remote development host. Changing: Host github.com to: Host github. preserved GitHub SSH access while preventing Codex from treating it as a concrete SSH host. After restarting Codex again, Remote Control enabled successfully. — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/31231?email_source=notifications&email_token=CG3PH64JOOPHIWTNIUTX2TL5EBRXJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJTGE4DAMRZHAY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4931802981>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CG3PH65IC2IK4MCND666H735EBRXJAVCNFSNUABFKJSXA33TNF2G64TZHM4TMNJUGE2TMNBZHNEXG43VMU5TIOBRG44TCNJZGYYKC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CG3PH674FCDGQYXMLPFXS6L5EBRXJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJTGE4DAMRZHAY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/CG3PH6255KR4SS3J5EXQOQ35EBRXJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJTGE4DAMRZHAY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: @.**>