[Linux][Desktop] No response with Clash system proxy, CLI works; TUN or launching with an explicit proxy restores functionality
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 22/100
Research direction
The bug is in the desktop app's proxy handling on native Linux, where the Clash system proxy works for the CLI but not for local desktop conversations. The payload names no source files, so the first step is to locate where the desktop build reads proxy settings, including Chromium's --proxy-server flag and the upper- and lower-case HTTP_PROXY variables. Done means the desktop conversation completes through the system proxy without TUN, which needs a reproduction on Linux with Clash Verge.
Written by the indexing model from the issue text.
Description
What version of the Codex App are you using (From “About Codex” dialog)?
ChatGPT 桌面安装包版本 26.930.61225（从本机安装包元数据读取），自带 Codex 0.160.1。这里报告的是 Codex 本地桌面对话。验证日期：2026-10-08。
What subscription do you have?
Pro
What platform is your computer?
Ubuntu 24.04.5 LTS，原生 Linux，不是 WSL。
Linux 7.0.0-34-generic x86_64 x86_64
What issue are you seeing?
我使用 Clash Verge，HTTP/mixed 端口是 127.0.0.1:7897。只开系统代理、关掉 TUN 时，CLI 可以正常回复，但桌面本地对话一直等待，没有输出；打开 TUN 才恢复。有时从原版菜单启动还会出现登录界面。因为还需要使用内网 VPN，不希望一直开着 TUN。
What steps can reproduce the bug?
- 开启 Clash Verge 系统代理，关闭 TUN。
- 保存任务，完全退出桌面程序，再从原版菜单启动。
- 在本地 Codex 对话里发送一条消息。我这边一直等待，没有回复。
- 同一网络状态下，CLI 可以正常回复。
- 打开 TUN 后，桌面对话恢复。
- 完全退出桌面程序，关闭 TUN，再用显式代理启动器启动；本地桌面对话也恢复。
What is the expected behavior?
桌面程序能够使用系统代理，或者提供明确的代理配置入口，不需要依赖 TUN 才能完成本地对话。
Additional information
目前有效的临时办法是同时传入大小写两套 HTTP_PROXY、HTTPS_PROXY、ALL_PROXY，并添加 Chromium 的 --proxy-server=http://127.0.0.1:7897。完整配置和安装方式放在独立项目：chatgpt-clash-linux。
关闭 TUN 后，命令重启的真实本地桌面对话已成功，实际后台 TCP 连接经过 Clash 端口。怀疑不同桌面组件的代理配置没有一致生效，但尚未确认准确根因。独立菜单冷启动的登录稳定性尚未完整验证，云端 durable 连接仍有 ETIMEDOUT / 1006，不声称这个办法解决了全部问题。
相关报告：#16079 的主帖连 CLI 也失败；#49921 和 #34955 是 macOS 桌面代理问题；#49829 涉及 durable 云端连接。本报告补充原生 Linux 的本地桌面对话对照结果。
- Dominant language
- Rust
- Stars
- 129k
- Forks
- 20.3k
- Avg merge
- 1m
- Merged PRs (30d)
- 998
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
bug CLI
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openai/codex#55122 · 2 comments ·
Maintainers usually reply within 1 day
-
Python SDK: CodexClient.close() leaves the app-server's stdout/stderr pipes open (and never waits after kill)Possibly taken @akhil9tiet claimed this 1 day ago. Openapp-server bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openai/codex#54908 · 2 comments ·
Maintainers usually reply within 1 day
-
bug CLI tool-calls windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug tool-calls
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Clarification about NODE_REPL_TRUSTED_BROWSER_CLIENT_SHA256S in the VS Code extension environmentOpendocumentation extension windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
openai/codex#54780 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
area:desktop priority:p2 type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
fritzprix/libr-agent#2165 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:ecosystem bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Chelis-Lang/chelis#3942 ·
Maintainers usually reply within 1 day