Repository navigation
The issue of ocx doctor displaying different results for HTTP_PROXY #59
Description
Currently, the proxy server configuration is automatically extracted from environment variables. At startup, the following environment variables must be present for the proxy server to take effect: HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, and NO_PROXY.
However, I encountered a problem: during startup, if I execute ocx doctor in the terminal that started ocx start or ocx service start, these variables correctly show as set. But if I create a new terminal and execute ocx doctor, it shows as unset.
Activity
Ingwannu commentedon Jul 3, 2026
Thanks for the report. This is expected shell/process behavior, but the current
ocx doctoroutput is misleading.ocx doctorcurrently reports the proxy variables visible to theocx doctorprocess itself. Environment variables are inherited by child processes, not shared globally between existing terminals, so a new terminal will not automatically see variables that were exported only in the terminal that launchedocx start/ocx service start.I opened #60 to make this clearer. The PR splits the doctor output into:
config.proxystate, with values hiddenThis should let users distinguish “this terminal has no proxy env” from “the running proxy process has no proxy env” without printing proxy URLs or credentials.
Ingwannu commentedon Jul 3, 2026
Merged the doctor proxy-env diagnostics fix into dev via #60. Closing this for now; please reopen or comment if the new doctor output still looks misleading.
guigeng commentedon Jul 3, 2026
There's a setting 'proxy' in config.json that wasn't mentioned in the documentation (https://lidge-jun.github.io/opencodex/reference/configuration/).
I added
"proxy": "http://127.0.0.1:7890"to the top-level field of ~/.opencodex/config.json and then restarted the service. This seems to work a bit better.