›_ Codex Issues
Codex Issues / #14782

codex cli , codex Destop, vscode codex ，all can not send any message and no response

Resolved 💬 3 comments Opened Mar 16, 2026 by Frank1e0927 Closed Mar 16, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

codex-cli 0.114.0

What subscription do you have?

chatgpt plus oauth

Which model were you using?

_No response_

What platform is your computer?

_No response_

What terminal emulator and version are you using (if applicable)?

_No response_

What issue are you seeing?

<img width="570" height="458" alt="Image" src="https://github.com/user-attachments/assets/7696bc2b-8582-4f5c-9507-888bad04220f" />

<img width="1280" height="820" alt="Image" src="https://github.com/user-attachments/assets/d9ce8cfc-64a9-4928-937a-736ffb3edf54" />

<img width="1061" height="555" alt="Image" src="https://github.com/user-attachments/assets/20579179-2b84-4c12-8b78-d64d8dd72b5c" />

<img width="310" height="319" alt="Image" src="https://github.com/user-attachments/assets/4013ea88-fdaf-4a01-8d58-a8dda178afb8" />

What steps can reproduce the bug?

Uploaded thread: 019cf4c7-c2a4-7161-83aa-3ad9b6970bf1

I use the Codex CLI, the Codex desktop app, and the Codex VSCode plugin, and none of them respond. As shown in the image, after sending a message it just freezes. I’ve confirmed that my subscription still has balance, but when I log in to the ChatGPT web official site I can send messages normally.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 5 months ago

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

  • #14317
  • #14085
  • #13666
  • #13420
  • #13328

Powered by Codex Action

etraut-openai contributor · 5 months ago

From the logs, it looks like a network proxy or configuration issue, not a codex bug.

Frank1e0927 · 5 months ago
From the logs, it looks like a network proxy or configuration issue, not a codex bug.

I used Codex Desktop to fix the Codex CLI—an exciting hour. In the past I couldn’t have imagined how tricky this would be. Here’s the summary:

Codex Desktop, the codex CLI in the terminal, and the Codex plugin in Antigravity do not run in the same execution environment. We eventually identified that the real failure point was unstable support for Codex’s websocket/streaming requests in the proxy chain. When relying solely on the system proxy, both the CLI and the IDE plugin could end up in a state where they “start successfully but freeze when sending messages.”

Solution:

For the codex in the terminal, I created a wrapper function in .zshrc that explicitly injects HTTP_PROXY / HTTPS_PROXY / ALL_PROXY / NO_PROXY, while also preserving --no-alt-screen to handle terminal compatibility issues. For the Codex plugin in Antigravity, I created a separate proxy wrapper script codex-antigravity-proxy.sh, and pointed to it in settings.json via chatgpt.cliExecutable. This way, Codex on both the terminal and IDE sides can explicitly obtain the proxy environment instead of relying on automatic discovery through the system proxy.

Result:

The CLI is now usable again, and the Codex plugin in Antigravity has also been switched to a Codex launch path that includes the proxy. Going forward, we only need to update these two configurations if the proxy port or the Codex installation path changes.