CODEX / 28 · DAY 17 · PERSONAL EXPERIENCE

One voice. Part of the picture.

Codex Remote Control is broken when using VPN/proxy on macOS I’m using Codex on macOS with a VPN/proxy (such as Clash or Surge). Regular Codex functionality works, but Remote Control fails to enable, displaying errors including “Couldn’t update remote control availability” and “Could not enable remote control.” I tried changing proxy settings and troubleshooting from Terminal, but the problem persisted. One configuration change even prevented Codex from launching, so I had to revert it. Please ensure that Remote Control and all its background processes correctly respect macOS system proxy settings, including HTTP(S)/SOCKS proxies, TUN mode, and WebSocket connections. Remote Control should work reliably behind a VPN without requiring manual environment-variable workarounds. Please also provide meaningful connection diagnostics rather than generic errors. This is particularly important for users on networks where direct connections to OpenAI services are unavailable.

0 other browsers said ‘same here’. Anonymous feedback, not verified identities.