Repair Codex proxy connectivity
Detect the host operating system and read exactly one platform reference:
- macOS: references/macos-proxy-repair.md
- Windows: references/windows-proxy-repair.md
Required behavior
- Inspect effective proxy variables, system proxy settings, proxy processes, listening ports, and PID ownership before changing anything.
- Distinguish HTTP, SOCKS, mixed, control, DNS, and API ports. Never treat a control or DNS port as a proxy port.
- Verify a candidate HTTP or mixed proxy with a short-timeout HTTPS or HTTP CONNECT request before modification.
- Back up existing non-empty values and modify only the smallest user-scoped configuration proven to be inherited by the installed Codex build.
- Do not assume
~/.codex/.envis read. Use it only after local or official evidence verifies that behavior for the installed version. - Never reveal credentials or overwrite unrelated configuration.
- Stop when multiple candidates remain ambiguous.
- Re-read effective values, confirm the port still listens, and require a full application restart before final verification.
Writes to environment variables, launch settings, or configuration are state changes and require authorization unless already explicitly requested.