jlcodes99/cockpit-tools v1.3.68 on GitHub

更新日志（中文）

内置网关支持选择兼容 Images API 的 API Key 账号作为生图来源。按 gpt-image-2 或 gpt-image-2.5 模型族筛选，并在账号行选择包含后缀的完整上游型号，其他自定义型号按完整 ID 匹配；支持同步单张图片生成与编辑，使用所选供应商及型号，对话继续沿用原有路由。
从已保存账号目录发现的生图型号及手动添加的型号会在本地保留，直到手动删除，删除后不会自动加回。账号行使用适配长名称和小窗口的紧凑型号下拉，缺少型号时可跨分页和筛选定位账号。型号目录操作超时后可重试；在用型号不能删除，实例网关准备期间删除会提示稍后重试。
API Key 生图校验参考图片、蒙版及返回图片，阻止从本机或内网地址下载；公网 CDN 跳转在校验目标地址后仍可使用。图片获取失败或取消后，仍记录上游已返回的用量。

Codex API Key 账号统一显示自定义名称或请求地址的主机名，缺失时使用供应商名称或本地化账号标签。账号视图、启动预览、生图来源选择、请求记录、托盘菜单及额度通知沿用同一命名规则。
添加 Codex API Key 账号时默认选择「自定义」，请求地址留空；赞助供应商加载完成后不再自动选中供应商。
生图主模型设置增加醒目说明，明确其用于官方生图转发，与出图模型选择区分；保留官方主模型变化时的手动更新入口。
Codex 推理档位在编辑器、保存／导入配置及生成的客户端目录中统一按 Low → Medium → High → XHigh → Max → Ultra 排列，并保留有效的显式默认值及旧配置的隐含默认值。
API 服务请求详情区分可识别的流打开超时、流中空闲超时与客户端取消；记录中的超时阈值可定位到「超时与重试」对应字段，其他 HTTP 504 保留上游诊断。默认超时及重试策略保持不变。
API 服务重启入口明确为「仅重启 API 服务」，说明会保留 Codex 窗口，但正在进行的 API 请求可能中断。重复点击不再重复排队重启，失败后可重试。

API 服务切换标准／快速后，无需重启网关，后续 HTTP 请求与同一 WebSocket 连接的新请求使用新默认档位；正在进行的请求保留原档位，客户端显式档位仍优先。运行中的服务未确认更新时，提示偏好已保存并可重试。
API 服务请求记录使用无前缀的快速／标准短标签，快速采用橙色闪电样式；详情分别保留请求档位与上游原始回报。Codex OAuth 响应中的 default 不再把快速请求覆盖为标准，缺少档位证据时保持未确认。因关闭 WebSocket 而被拒绝的握手保留诊断，不再计为推理失败。
API 服务快捷面板打开时优先显示用量统计；请求正文记录设置移至服务配置区末尾，并默认折叠，保留既有统计卡片布局及记录开关状态。

API Key accounts with compatible Images API endpoints can now be selected as image sources in the built-in gateway. Choose a gpt-image-2 or gpt-image-2.5 family, then select each account's complete upstream model ID, including suffixes; other custom models match exact IDs. Synchronous single-image generation and editing use the selected provider and model; conversation routing remains unchanged.
Image models discovered from saved account catalogs or added manually are kept locally until deleted, and deleted models are not rediscovered automatically. Account rows use compact model selectors that fit long names and small windows; missing model selections can be located across pages and filters. Model-directory operations can be retried after a timeout. Models in use cannot be deleted, and deletion during instance-gateway preparation prompts a retry.
API Key image generation validates reference images, masks and returned images, and blocks downloads from local or private addresses. Public CDN redirects remain supported after destination checks. Upstream-reported usage remains recorded when image retrieval fails or is canceled.

Codex API Key accounts consistently display a custom name or the request URL's host, with a provider or localized account label as fallback. Account views, launch previews, image-source selection, request records, tray menus and quota notifications use the same naming rules.
Adding a Codex API Key account defaults to Custom with an empty request URL. Loading sponsor providers no longer automatically selects a provider.
Image main-model settings now prominently explain their role in the official image relay and distinguish them from the model that generates the image. Manual updates remain available when the official main model changes.
Codex reasoning levels use the same Low → Medium → High → XHigh → Max → Ultra order in the editor, saved/imported configurations and generated client catalogs, while preserving valid explicit defaults and existing implicit defaults.
API Service request details distinguish identifiable stream-open timeouts, stream idle timeouts and client cancellation. Recorded timeout thresholds can link to the corresponding field in Timeouts & Retries; other HTTP 504 errors retain their upstream diagnostics. Default timeout and retry policies are unchanged.
The API Service restart action is labeled “Restart API service only” and explains that Codex windows stay open while active API requests may be interrupted. Repeated clicks no longer queue duplicate restarts, and failures remain retryable.

API Service standard/fast changes apply to subsequent HTTP requests and new requests on the same WebSocket connection without restarting the gateway. Requests already in progress keep their original tier, and explicit client tiers still take precedence. If the running service cannot confirm the update, a localized message explains that the preference was saved and allows retrying.
API Service request logs show compact Fast/Standard badges without prefixes; Fast uses an amber lightning badge. Details retain the requested tier and raw upstream report separately. Codex OAuth responses reporting default no longer overwrite a Fast request as Standard, and unavailable tier evidence remains unconfirmed. WebSocket handshakes rejected because the transport is disabled remain in diagnostics without counting as inference failures.
The API Service quick panel shows usage statistics first. Request-body recording settings are grouped at the end of the service configuration in a section that is collapsed by default, preserving the existing statistics-card layout and recording preferences.