jlcodes99/cockpit-tools v0.24.8 on GitHub

更新日志（中文）

Codex API 服务现支持 Sidecar 与 Legacy 网关模式切换：可在账号卡片和完整 API 服务页切换网关模式，请求日志会记录并按模式筛选，日志也会以 [sidecar] 或 [legacy] 标记来源，便于定位问题。
Codex API 服务新增调试日志开关：开启后会记录 legacy 网关请求阶段、sidecar executor trace、上游耗时、已选账号、流式完成状态和超时诊断，同时保留常规请求日志。
Codex API 服务两种网关模式均支持隐藏的 codex-auto-review 审查模型：Sidecar 与 Legacy 网关都会在本地 /v1/models 暴露该内部审查模型，在 Codex 客户端模型目录中标记为隐藏，并原样转发 /v1/responses 审查请求，避免 Codex 自动审批审查在本地模型策略校验阶段失败。
Codex API 服务现会在账号卡片引导用户切换网关：首次显示不透明引导浮层，指向账号卡片的新旧网关选择器，同时不再把切换入口放回快速配置弹框。

Codex API 服务现使用 localhost 写入本地客户端 Base URL：生成的 Codex provider 配置改为 http://localhost:<port>/v1，不再使用 127.0.0.1，降低本机代理栈误拦截客户端到 sidecar 回环请求的概率。
Cockpit 启动的 Codex 进程现注入受管本机代理绕过设置：Codex CLI 与官方 app-server 启动时会合并继承的 NO_PROXY / no_proxy 与 Cockpit 管理的回环地址，包括 127.0.0.1、127.0.0.0/8、localhost、::1 和 ::1/128。
Sidecar 代理选择现与旧网关优先级对齐：API 服务代理、Cockpit 全局代理、继承的环境代理与系统/默认代理发现会按旧网关同一套优先级解析。
Codex API 服务快速配置弹框现保持配置定位：新旧网关切换已从弹框移除，完整 API 服务页和账号卡片继续负责网关模式切换。

Codex API 服务降低了回环请求被本机代理工具误转发的概率：Cockpit 现在会注入回环地址绕过规则，健康诊断也能识别 Clash/FlyingBird 等本机代理是否拦截了 localhost 或 127.0.0.1 的 API 服务流量。
Sidecar 流式请求在启动和空闲卡住时会更快失败：首包超时、重试处理、空闲超时、完成状态校验与更清晰诊断可避免首字节前或半截流式响应后的长时间静默挂起。
Sidecar 启动跨平台稳定性提升：Cockpit 会等待 sidecar stdout ready 事件，开发构建优先解析本地 sidecar 二进制，Tauri 构建脚本会跟踪 Go sidecar 源码，Windows sidecar 也不再依赖不可靠的父进程 PID 检查退出。
旧网关流式与 WebSocket 处理增强了超时和断开行为：上游连接超时、流式空闲超时、总超时、心跳刷新、broken pipe 分类与首包/完成诊断让长请求更容易恢复和排查。
Codex API 服务请求日志现稳定保留网关模式与诊断字段：数据库迁移会补充网关模式字段和相关索引，完整功能页请求日志可区分 Sidecar 与 Legacy 流量。

Codex API Service now supports gateway mode switching between Sidecar and Legacy modes: gateway mode can be changed from the account card and the full API Service page, request logs record and filter by mode, and logs are tagged as [sidecar] or [legacy] for easier diagnosis.
Codex API Service now exposes a debug log switch: when enabled, Cockpit records legacy gateway request phases, sidecar executor traces, upstream timing, selected account details, stream completion state, and timeout diagnostics while keeping normal request logs available.
Codex API Service now supports the hidden codex-auto-review reviewer model in both gateway modes: Sidecar and Legacy gateways expose the internal reviewer model in local /v1/models, mark it hidden in the Codex client model catalog, and forward /v1/responses reviewer requests unchanged so Codex automatic approval review no longer fails local model policy validation.
Codex API Service now guides users to the gateway switch from the account card: a one-time opaque guide highlights the new gateway selector without adding the selector back to the quick setup modal.

Codex API Service now writes the local client Base URL with localhost: generated Codex provider config uses http://localhost:<port>/v1 instead of 127.0.0.1, reducing the chance that local proxy stacks intercept the client-to-sidecar loopback request.
Codex-launched processes now receive managed loopback proxy bypass settings: launched Codex CLI and official app-server processes merge inherited NO_PROXY / no_proxy values with Cockpit-managed loopback entries for 127.0.0.1, 127.0.0.0/8, localhost, ::1, and ::1/128.
Sidecar proxy selection now follows the legacy gateway priority: API Service proxy, Cockpit global proxy, inherited environment proxy, and system/default proxy discovery are resolved through the same priority model used by the old gateway.
Codex API Service quick setup modal now stays focused on service setup: the new/old gateway mode switch was removed from the modal, while the full API Service page and account card remain responsible for mode switching.

Codex API Service no longer lets loopback requests get routed through local proxy tools as easily: Cockpit now injects loopback bypass rules and health diagnostics can identify when Clash/FlyingBird-style local proxies are intercepting localhost or 127.0.0.1 API Service traffic.
Sidecar streaming now fails fast on startup and idle stalls: stream-open timeout, retry handling, idle timeout, completion-state validation, and clearer diagnostics prevent long silent hangs before the first byte or after a partial stream.
Sidecar startup is more reliable across platforms: Cockpit waits for the sidecar stdout ready event, development builds resolve the local sidecar binary first, Go sidecar sources are tracked by the Tauri build script, and Windows sidecars avoid unreliable parent-PID termination checks.
Legacy gateway streaming and WebSocket handling now has stronger timeout and disconnect behavior: upstream connect, stream idle, stream total timeout, heartbeat flush, broken-pipe classification, and first-chunk/completion diagnostics make long-running requests easier to recover from and debug.
Codex API Service request log storage now preserves gateway mode and diagnostics consistently: database migrations add the gateway mode field and related indexes so full-page request logs can distinguish Sidecar and Legacy traffic.