›_ Codex Issues
Codex Issues / #13747

Codex App bundles codex-cli 0.108.0-alpha.12 and fails on macOS, while standalone codex-cli 0.105.0 works on the same machine

Resolved 💬 14 comments Opened Mar 6, 2026 by jlala Closed Mar 13, 2026
💡 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 App with bundled codex-cli 0.108.0-alpha.12

What subscription do you have?

ChatGPT Plus

What platform is your computer?

macOS (Apple Silicon)

What issue are you seeing?

Codex App does not work correctly on my Mac, while the standalone Codex CLI works normally on the same machine.

I verified that the two are using different versions:

codex --version
codex-cli 0.105.0
/Applications/Codex.app/Contents/Resources/codex --version
codex-cli 0.108.0-alpha.12

The standalone CLI version 0.105.0 works, but the Codex App does not.
I already tried uninstalling, removing local caches/preferences, and reinstalling the app, but the problem remains.

This makes it look like the issue is related to the Codex App bundled version (0.108.0-alpha.12) rather than my local machine setup in general.

What steps can reproduce the bug?

Install and use standalone Codex CLI version 0.105.0

Confirm that it works normally on this Mac

Launch Codex App on the same machine

Check the app-bundled Codex version:

/Applications/Codex.app/Contents/Resources/codex --version

It reports:

codex-cli 0.108.0-alpha.12

Use Codex App normally

The app fails / does not work correctly, while standalone codex-cli 0.105.0 continues to work on the same machine

Additional version check:

codex --version
codex-cli 0.105.0

At the moment I do not have a minimal code snippet, because this does not appear to be project-code-specific. It seems to be an app/runtime version regression on the same environment.

What is the expected behavior?

Codex App should work correctly on the same Mac where standalone codex-cli 0.105.0 works correctly.

More specifically, I would expect either:

the app-bundled version to work normally on this machine, or

the app and standalone CLI to behave consistently on the same environment

Additional information

The key point is that this does not look like a general install problem:

Standalone CLI: 0.105.0 → works

App bundled CLI: 0.108.0-alpha.12 → fails

I also already tried uninstalling and cleaning local app data, but that did not resolve the issue.

This looks like a version-specific regression in the Codex App bundled runtime rather than a general local configuration failure.

View original on GitHub ↗

14 Comments

github-actions[bot] contributor · 4 months ago

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

  • #13709

Powered by Codex Action

etraut-openai contributor · 4 months ago

Thanks for the bug report. We haven't had any other reports of this issue, so it must be something specific to your machine. You may need to do additional investigation to determine the cause.

I'll note that 0.105.0 is quite old at this point. Please update to the latest version and see if that works.

ZizhenWang · 4 months ago

same here

jlala · 4 months ago
same here

你那边也是codex cli 旧版本正常，但是0.105.0之后的不行吗？并且一直提示正在思考。
并且codex app更新到最新版本后也是一直提示正在思考。
完全卸载重装也不行。

hermitchen1124 · 4 months ago
> same here 你那边也是codex cli 旧版本正常，但是0.105.0之后的不行吗？并且一直提示正在思考。 并且codex app更新到最新版本后也是一直提示正在思考。 完全卸载重装也不行。

你现在解决了吗
这里可以解决
1.https://github.com/openai/codex/issues/13682
2.https://github.com/openai/codex/issues/13709
应该是网络代理问题

jlala · 4 months ago
> > same here > > > 你那边也是codex cli 旧版本正常，但是0.105.0之后的不行吗？并且一直提示正在思考。 并且codex app更新到最新版本后也是一直提示正在思考。 完全卸载重装也不行。 你现在解决了吗 这里可以解决 1.#13682 2.#13709 应该是网络代理问题

我看下是否是网络代理的问题，正常终端使用codex cli是没问题的，但0.105.0以后的不能用就奇怪的

hermitchen1124 · 4 months ago
> > > 同样在这里 > > > > > > 你这边也codex cli旧版本正常，但是0.105.0之后不行吗？并且一直提示正在思考。并且codex app更新到最新版本后也一直提示正在思考。完全卸载重装也不行。 > > > 你现在解决了吗 这里可以解决 1. #13682 2. #13709应该是网络代理问题 我看下是否是网络代理的问题，正常终端使用codex cli是没问题的，但0.105.0以后的不能用就奇怪了

你相同的环境下直接codex如果能 这个桌面端原生版本应该也能 /Applications/Codex.app/Contents/Resources/codex 如果都能的话但是ui不行 应该是网络问题

hermitchen1124 · 4 months ago
Thanks for the bug report. We haven't had any other reports of this issue, so it must be something specific to your machine. You may need to do additional investigation to determine the cause. I'll note that 0.105.0 is quite old at this point. Please update to the latest version and see if that works.

@etraut-openai Hi ! I completed a full investigation.

I confirmed the root cause is that on macOS (including Clash Verge setups), Codex Desktop does not correctly load system proxy settings into runtime environment variables, which leads to request timeouts and the persistent “thinking” state.

I’m an active Codex user and I really want to help improve Codex. So I ran repeated end-to-end tests and recorded concrete results:

1) Baseline

  • This is not “standalone CLI always works”.
  • What I confirmed is: with correct proxy env, /Applications/Codex.app/Contents/Resources/codex runs normally in terminal.

2) Desktop binary path switching is not the root fix

  • I switched desktop app-server path via launchctl setenv CODEX_CLI_PATH ... and restarted the app.
  • Without launchctl-level proxy env, desktop conversation gets stuck (keeps thinking / timeout), independent of the selected binary path.

3) Bundled binary works after proxy env is configured

  • After configuring launchctl proxy env correctly, the app-bundled binary works and conversations recover.

4) Logs show timeout/connect failures during stuck sessions

  • I checked ~/Library/Logs/com.openai.codex/... for each run.
  • stdio_transport_spawned + executablePath confirms exact spawned binary.
  • In stuck sessions, logs contain timeout/connect-failure patterns, which matches proxy/network path failure.

5) Env evidence is direct

  • Shell echo shows full proxy vars.
  • In failing desktop runtime path, proxy env/aliases are missing.
  • This missing-env runtime state directly corresponds to “thinking forever” + timeout behavior.

6) Fix validation on my test branch

  • I implemented startup proxy bootstrap on macOS via /usr/sbin/scutil --proxy.
  • Missing env aliases are backfilled safely without overriding existing non-empty values:
  • HTTP_PROXY/http_proxy
  • HTTPS_PROXY/https_proxy
  • ALL_PROXY/all_proxy
  • With this patch, desktop works without manual launchctl proxy preconfiguration in the tested setup.
  • Repeated switching between bundled and debug binaries gives consistent success after the fix.

Code/test status:

  • Added unit tests for parsing + alias backfill.
  • Passed:
  • cargo test -p codex-app-server macos_proxy_env -- --nocapture
  • cargo check -p codex-cli
  • cargo clippy -p codex-app-server -p codex-cli -- -D warnings

If this direction matches maintainer expectations, I’m ready to help with an invited PR for #13747.
If you have any additional suggestions, I’m very happy to continue and help with follow-up fixes.

jlala · 4 months ago

codex app和codex cli使用的不是同一个版本

jlala · 4 months ago

但我另外一个电脑只有codex app就能正常使用

hermitchen1124 · 4 months ago
但我另外一个电脑只有codex app就能正常使用

这个不是codex底层服务的问题 codexapp实际是一个前端壳 壳子是调用的底层的codex服务 codex后台服务执行时会读取http_proxy这些环境变量 但是现在更新后当codex app启动时并没有把http_proxy这些环境变量加载到环境中 所以 codex后台服务执行（回复时）时也就无法正确读取并使用这些环境变量进行代理访问 根本问题在于环境变量没有被正确加载到codex后台服务执行的环境中 像我之前提到的那些issue中就有添加环境变量后（launchctl setenv）就可以解决的案例 而且我试了试确实是这样

hermitchen1124 · 4 months ago
> > > same here > > > > > > 你那边也是codex cli 旧版本正常，但是0.105.0之后的不行吗？并且一直提示正在思考。 并且codex app更新到最新版本后也是一直提示正在思考。 完全卸载重装也不行。 > > > 你现在解决了吗 这里可以解决 1.#13682 2.#13709 应该是网络代理问题 我看下是否是网络代理的问题，正常终端使用codex cli是没问题的，但0.105.0以后的不能用就奇怪的

你是用终端时 配置终端的代理变量了吗 如果没有配置正常codexcli也是无法访问才对 HTTP_PROXY HTTPS_PROXY ALL_PROXY这些环境变量 如果配置后 你也可以直接使用app原生的那个codex版本直接在cli中正常运行：/Applications/Codex.app/Contents/Resources/codex

calves07 · 4 months ago

Noticing something similar...

codex --version
codex-cli 0.111.0

But on my observability dashboard, I see logs with:
app.version: 0.108.0-alpha.12

jlala · 4 months ago

确实是 代理 问题 感谢！！