jlcodes99/cockpit-tools v0.25.3 on GitHub

更新日志（中文）

Codex Chat Completions 供应商改为实例级独立本地网关：配置为 Chat Completions 的 API Key 账号会为目标 Codex profile 启动专属 provider gateway，并使用独立本地端口，避免与全局 API 服务网关或其他 Codex 实例互相冲突。
Codex 默认实例进程匹配对齐官方客户端启动形态：默认桌面实例识别不再要求 CODEX_HOME 或受管 profile 目录，提升官方默认实例的启动状态、停止行为、PID 跟踪和窗口定位准确性。
Codex config.toml 清理不再误删用户管理的供应商配置：Cockpit 现在只移除自身写入的 provider gateway 模型目录和模型覆盖，保留外部 model_catalog_json、自定义 provider 以及其他用户配置。
Windows provider gateway 后台 sidecar 不再弹出可见控制台窗口：Codex 供应商网关启动的后台 sidecar 会继续使用隐藏控制台窗口的启动方式。

APIKEY.FUN 供应商配置保持 Responses 直连模式：APIKEY.FUN 赞助模板和已保存的 APIKEY.FUN 供应商会使用 Responses 协议，不再走 Chat Completions 网关路径。

Codex Chat Completions providers now use isolated local gateways per instance: API Key accounts configured for Chat Completions start a dedicated provider gateway for the target Codex profile with its own local port, avoiding conflicts with the global API Service gateway or other Codex instances.
Codex default-instance process matching now follows the official client launch shape: the default desktop instance is detected without requiring CODEX_HOME or a managed profile directory, improving launch state, stop behavior, PID tracking, and window focus for the official default instance.
Codex config.toml cleanup no longer removes user-managed provider settings: Cockpit now only removes its own provider-gateway model catalog and model override, preserving external model_catalog_json, custom providers, and other user configuration.
Windows provider-gateway sidecars no longer open visible console windows: background sidecars launched for Codex provider gateways keep the Windows hidden-console startup behavior.

APIKEY.FUN provider configuration now stays on Responses direct mode: sponsored APIKEY.FUN templates and existing saved APIKEY.FUN providers use Responses instead of the Chat Completions gateway path.