更新日志（中文）
[0.24.2] - 2026-05-21
修复
- 紧急修复 v0.24.1 后 Codex 本地 API 服务代理路由异常：API 代理地址为空时会依次回退到 Cockpit 全局代理和显式环境代理变量（
HTTPS_PROXY、HTTP_PROXY或ALL_PROXY）；没有可用代理地址时，网关会拒绝官方上游请求，避免意外直连官方上游。 - Codex 本地 API 服务上游失败诊断现标明实际代理来源：502 诊断与日志会标明使用的是 API 服务代理、Cockpit 全局代理、环境代理或缺少代理配置，便于快速修正网络出口。
Changelog (English)
[0.24.2] - 2026-05-21
Fixed
- Emergency fix for Codex Local API Service proxy routing after v0.24.1: empty API proxy URLs now fall back to the Cockpit global proxy and then explicit environment proxy variables (
HTTPS_PROXY,HTTP_PROXY, orALL_PROXY), and the gateway refuses official upstream requests when no proxy URL is available instead of falling back to unintended direct upstream access. - Codex Local API Service upstream failures now identify the active proxy source: 502 diagnostics and logs report whether the API service proxy, Cockpit global proxy, environment proxy, or missing proxy configuration was used so users can correct network routing quickly.