Codex App GUI no longer works with Clash Verge macOS system proxy, while bundled TUI works with env proxy

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

26.305.950 (863)

What subscription do you have?

business team

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

After updating Codex App, the GUI chat cannot connect when using Clash Verge in macOS System Proxy mode. This setup worked correctly before the update.

The issue appears only in the App GUI. The bundled CLI inside the app works normally when proxy environment variables are set manually.

Important comparison:

• App bundled binary: /Applications/Codex.app/Contents/Resources/codex
• In terminal, with explicit proxy env vars, the bundled TUI works normally.
• In the App GUI, connection fails.

This suggests a regression in GUI proxy handling rather than a network, account, or proxy endpoint issue.

Environment:

• OS: macOS
• Codex bundled version: codex-cli 0.108.0-alpha.12
• Proxy tool: Clash Verge
• Proxy mode: macOS System Proxy
• Proxy endpoints:
• http://127.0.0.1:7897
• socks5://127.0.0.1:7897

What steps can reproduce the bug?

1. Enable Clash Verge with macOS System Proxy mode.
2. Open Codex App GUI.
3. Start a chat/session.
4. Observe that the GUI fails to connect.

Control test:

1. Open terminal and run:

export https_proxy=http://127.0.0.1:7897
export http_proxy=http://127.0.0.1:7897
export all_proxy=socks5://127.0.0.1:7897
/Applications/Codex.app/Contents/Resources/codex

1. Start a chat in the TUI.

Result:

• TUI works normally
• GUI fails to connect

What is the expected behavior?

Codex App GUI should work with macOS system proxy settings (such as Clash Verge system proxy mode), as it did before the update, without requiring manual proxy environment variables.

Additional information

Additional context:

This worked correctly before the recent Codex App update. The regression appears specific to GUI proxy detection.

Since the bundled CLI works when proxy environment variables are provided manually, the issue likely relates to GUI proxy auto-detection or system proxy integration on macOS.