jlcodes99/cockpit-tools v1.3.55

Cockpit Tools v1.3.55

on GitHub

更新日志（中文）

[1.3.55] - 2026-09-16

修复

• 修复 DeepSeek 账号在实例网关或 API 服务下上下文压缩失败：1.3.53 起托管 provider 的名字被写成 OpenAI，客户端因此按官方上游处理，把压缩请求发往没有该能力的 DeepSeek，压缩必然失败并让会话无法继续（表现为压缩处报错）。现在名字改回非 OpenAI，DeepSeek 等第三方上游恢复本地压缩，功能与 1.3.51 / 1.3.52 一致；已经写成旧名字的实例配置会在下次启动时自动修正，不需要重新绑定。相应地，官方账号经本地网关或 API 服务时也和 1.3.52 一样使用本地压缩。
• 修复唤醒与鹈鹕测试改走 API 服务后不可用：1.3.54 起定时/手动唤醒与鹈鹕测试统一交给本地 API 服务进程处理，但内部请求沿用了直连上游时的路径处理，把客户端路径（/v1/responses）裁剪成上游路径（/responses）后才发给 API 服务。API 服务只注册 /v1/* 路由，唤醒因此直接返回 404 endpoint not supported，鹈鹕测试更早一步在本地就报「仅支持 /v1 或 /backend-api/codex 路径」。现在内部请求保留 API 服务的对外路径，唤醒与鹈鹕测试恢复正常，仍然共用 API 服务的账号选择、Token 续期、并发与额度冷却调度。

Changelog (English)

[1.3.55] - 2026-09-16

Fixed

• Fixed context compaction failing for DeepSeek accounts behind an instance gateway or the API Service: starting with 1.3.53 the managed provider was written with the name OpenAI, so the client treated the upstream as official and sent compaction to DeepSeek, which does not support it — compaction always failed and the conversation could not continue, showing an error where compaction happens. The name is no longer OpenAI, so DeepSeek and other third-party upstreams use local compaction again, matching 1.3.51 and 1.3.52; configurations that already carry the old name are corrected automatically on the next start, and no rebinding is needed. Accordingly, official accounts behind the local gateway or the API Service use local compaction as they did in 1.3.52.
• Fixed wakeups and Pelican tests failing after they were routed through the API Service: starting with 1.3.54 scheduled and manual wakeups and Pelican test runs are handled by the same local API Service process, but the internal request still applied the direct-upstream path handling and turned the client path (/v1/responses) into the upstream path (/responses) before sending it to the service. The service only registers /v1/* routes, so wakeups ended in a 404 endpoint not supported and Pelican tests failed one step earlier, locally, with "only /v1 or /backend-api/codex paths are supported". Internal requests now keep the API Service's public path, so wakeups and Pelican tests work again while still sharing the service's account selection, token refresh, concurrency and quota-cooldown scheduling.