Cockpit Tools v1.3.42

更新日志（中文）

[1.3.42] - 2026-09-07

修复

• 恢复 Codex API 服务首输出前的容量错误重试：HTTP 与 WebSocket 请求暂存初始握手事件，在现有重试预算内重试临时模型容量错误；开始输出后的失败直接报告，不重放已生成内容。
• 区分容量错误与账号额度耗尽：临时容量错误不再让正常账号进入冷却，并返回可重试的服务端错误；额度、认证和策略错误保持原有处理。
• 统一 Codex API 服务 OAuth 身份头版本：出站 Version 与 User-Agent 的版本保持一致，不改变 API Key 透传与实例专属 provider gateway。
• 保留仍有可用 Credits 的 Codex 账号：常规额度窗口为 0 但 Credits 仍有余额或未限额时，账号继续参与 API 服务调度；确认常规额度耗尽且无可用 Credits 的账号才进入额度冷却。
• 扩大本地账号池恢复范围：账号池没有可选账号时可恢复可恢复的调度和额度冷却状态，手动恢复可以清理选中账号的本地冷却状态；账号移出 API 服务后会清理其运行时调度和额度状态。
• 增强 Codex 配置文件容错：config.toml 损坏时优先从有效的同目录备份恢复，无法恢复时隔离坏文件并继续使用空配置；有效 UTF-16 配置会改写为 UTF-8，避免阻断切号、启动和 Provider 配置。
• 及时释放已退出进程遗留的 Codex 刷新锁：Token 刷新锁检测到持有进程已退出后立即回收，同时继续保护仍在运行的持有进程不被抢锁。

Changelog (English)

[1.3.42] - 2026-09-07

Fixed

• Recover Codex API Service capacity failures before output starts: HTTP and WebSocket requests retain their initial handshake events while retrying temporary model-capacity failures within the existing retry budget. Failures after output starts are reported without replaying generated content.
• Keep capacity failures separate from account quota exhaustion: temporary capacity failures no longer cool down healthy accounts and are returned as retryable server errors; quota, authentication, and policy failures retain their existing handling.
• Keep Codex API Service OAuth identity headers consistent: the outgoing Version header now matches the User-Agent version. API Key passthrough and instance-specific provider gateways remain unchanged.
• Recover Codex accounts with usable Credits: accounts with positive or unlimited Credits remain eligible when regular quota windows report zero, while accounts with confirmed exhausted regular quota and no usable Credits enter API Service cooldown.
• Expand local account-pool recovery: recoverable scheduler and quota-cooldown states can be restored when the pool has no selectable account, manual recovery can clear the selected account's local cooldown state, and removing an account from API Service clears its runtime scheduler and quota state.
• Repair Codex profile configuration safely: invalid config.toml files are restored from a valid sibling backup when possible, quarantined when recovery is unavailable, and valid UTF-16 files are rewritten as UTF-8 so account switching, launch, and provider configuration can continue.
• Release abandoned Codex refresh locks promptly: a token-refresh lock whose owner process has exited is reclaimed immediately, while a live owner is still protected from lock stealing.