jlcodes99/cockpit-tools v1.3.31

Cockpit Tools v1.3.31

on GitHub

更新日志（中文）

[1.3.31] - 2026-08-25

修复

• 修复 Codex 账号删除后重新出现、重新授权仍使用旧凭据的问题：删除结果不再被稍后完成的旧额度或资料任务写回覆盖，后端成功返回空账号列表时会同步清理前端本地缓存；新授权凭据也不会再被旧账号快照或原运行态的 auth.json 覆盖。删除后重新授权同一账号会稳定保留新 Token，后续切号不再因旧凭据返回 401。
• 修复官方账号检查影响 Codex 实例启动的问题：accounts/check 现在只在实际切号时调用，包括 OAuth 重新授权完成后的自动继续切号；已有实例启动保持原来的本地凭据准备逻辑，不再因该检查的 401 被误判为需要重新授权。
• 修复新版 Codex API Service 无法生图的问题：恢复官方 image_gen 与托管 image_generation 同时出现时的冲突处理，并覆盖顶层工具、嵌套 additional_tools、历史 response 和 tool_choice；HTTP、流式请求与 Responses WebSocket 现在都能正确选择生图能力，不再因重复发送两套工具而被上游拒绝。
• 修复 API Service 实验模型目录导致生图模型被提前拦截的问题：当选定账号存在可用的 OAuth 生图能力时，即使实验模型目录未列出 gpt-image-2，网关也会恢复其可见性并继续执行账号路由；账号能力不足或显式模型过滤时仍会按原规则隐藏。
• 修复 Codex Responses Lite 与 WebSocket 的非生图工具兼容问题：恢复 Lite 模型目录判定及 function、custom、客户端 tool_search、namespace 和 allowed_tools 的递归过滤，移除不受支持的 web_search、服务端 tool_search、空工具选择和无效 input namespace；HTTP 与 WebSocket 请求保持一致，协作工具和其他受支持工具不再因代理重构出现异常。
• 修复 Gemini CLI 来源的 Payload 规则无法匹配的问题：重新将 gemini-cli 来源协议归一为 gemini，已有按 Gemini 来源配置的默认、覆盖和过滤规则会继续正常生效。
• 修复 Cursor 悬浮卡不显示 API Usage 的问题：悬浮卡现在会完整显示 Cursor 的 Total Usage、Auto + Composer 和 API Usage 三条主要配额，其他平台原有的两条展示上限保持不变。

Changelog (English)

[1.3.31] - 2026-08-25

Fixed

• Fixed deleted Codex accounts reappearing and reauthorization continuing with stale credentials: deletion now remains authoritative even when an older quota or profile task finishes later, successful empty account lists clear the local UI cache, and newly authorized credentials cannot be overwritten by an older account snapshot or the previous live auth.json. Deleting and authorizing the same account again now keeps the new Token and no longer causes a stale-credential 401 during the following switch.
• Fixed the official account check affecting Codex instance startup: accounts/check now runs only for actual account switches, including the automatic continuation after OAuth reauthorization; starting an existing instance keeps the previous local credential preparation behavior and is no longer turned into a 401 reauthorization failure by this check.
• Fixed image generation being unavailable in the new Codex API Service version: conflict handling is restored when the official image_gen tool and hosted image_generation tool are both present, including top-level tools, nested additional_tools, historical response metadata, and tool_choice. HTTP, streaming, and Responses WebSocket requests now select the correct image capability instead of sending both tool systems and being rejected upstream.
• Fixed the API Service experimental model catalog preemptively blocking image generation: when the selected accounts have OAuth image-generation capacity, the gateway restores gpt-image-2 visibility even if the experimental model catalog omits it, then continues normal account routing; the model remains hidden when capacity is unavailable or explicit model filters exclude it.
• Fixed non-image tool compatibility for Codex Responses Lite and WebSocket requests: Lite catalog detection and recursive filtering are restored for function, custom, client-side tool_search, namespaces, and allowed_tools, while unsupported web_search, server-side tool_search, empty tool choices, and invalid input namespaces are removed. HTTP and WebSocket requests now behave consistently, preserving collaboration and other supported tools after the proxy refactor.
• Fixed Payload rules not matching Gemini CLI sources: the gemini-cli source protocol is normalized to gemini again, so existing Gemini-scoped default, override, and filter rules continue to apply.
• Fixed Cursor API usage being hidden in the floating card: the floating card now shows Cursor's three primary quota bars—Total Usage, Auto + Composer, and API Usage—without changing the two-bar limit for other platforms.