v1.3.0-upstream8.0.16 - 2026-10-14

Summary

Improve cross-provider deferred tool loading for official Codex and Claude Code through CLIProxyAPI, with stricter declaration, identity, replay, and terminal-state handling.
Ship reusable performance reproduction tools and consolidated implementation, compatibility, and per-request token reports. Client and model coverage remains explicitly bounded.
No configuration migration or automatic installation is required; existing operator configuration and running services are not changed by this release.

Upstream release: v8.0.16
Previous baseline: v8.0.16
Intake record: absorbed.md
Ported: No new upstream work. This release contains fork fixes and compatible additions on the baseline already shipped in v1.2.0-upstream8.0.16.
Skipped: No newer upstream release was assessed or absorbed for this release; prior intake exclusions remain unchanged.

None for supported requests and configurations. Previously tolerated malformed or over-budget requests can now be rejected before upstream dispatch.

Unified handling of Claude deferred declarations and Responses Lite additional_tools, including cumulative activation and active declaration budgets.
Structured preparation, replay, and failure diagnostics, plus SDK observers for controlled HTTP-attempt accounting.
Reusable tools for installed official Codex and Claude Code, real stdio MCP coding tasks, bounded eager/lazy comparisons, and numeric usage export; no client source build is required.

Active declaration budgets are checked after pruning and across discovery rounds; tools announced as active must have valid declarations.
Protocol handling uses actual declaration and history positions, preserving ordinary schema and argument data that resembles tool protocol markers.
Final tool-loading evidence is consolidated into three reports; one-off probes and private runtime artifacts are excluded from repository deliverables.

GPT Responses Lite search call formatting, Muse activation and aliases, and Lite additional-tool promotion, namespace merging, and description recovery.
Tool identity collisions, Unicode information loss, escaped custom-tool handling, buffered bridge-alias restoration, and native multi-result argument/replay validation.
Final outbound declaration checks for Claude routes, forced tool choices, hosted identities, retries, and WebSocket preparation/error ordering.
Reasoning-only responses with an explicit source finish now terminate correctly; genuinely truncated streams or missing source termination still fail instead of fabricating completion.
CI fixtures now synchronize WebSocket upload completion, match TTFT usage to the correct execution, and reserve retry connection order before the upgrade handshake. The performance dependency manifest no longer recursively includes itself.

Invalid tool declarations, choices, identities, and replay arguments are rejected before dispatch in the covered paths. Gateway declaration validation does not replace client or MCP execution authorization.
No credential, default operator configuration, or deprecated management endpoint migration is included.

The post-merge main CI passed on 9269d6c2: maintenance checks, offline accounting and model catalog checks, tracked formatting, go vet, full Go tests, and server build with Go 1.26.4 (CI run).
The local GOTOOLCHAIN=go1.26.4 bash ops/upstream-intake/verify-absorb.sh gate passed on the merged runtime source, including all seven race-sensitive packages; release preparation changes only documentation.
Official Codex 0.160.0 and Claude Code 2.1.289 were tested against fixed GPT, Muse, GLM, and Gemini routes on the documented frozen candidate: 15 cases finished, 7 strictly passed, and 10 passed independent code checks. Three successful comparable pairs reduced cumulative input, including cached input, by 71.84%–91.02%; these are fixed-task observations, not a reliability or billing guarantee. All failures, retries, unknown usage, and budget stops remain in the reports.
Publication is gated on the full maintenance regression gate, including race-sensitive packages, and successful verification of all ten platform archives and their checksums. Platform archive builds do not certify live behavior on every operating system.

Compatibility depends on client version, effective mode, model, and route. Gemini/Antigravity Code Mode history and authoritative usage remain unverified; Claude/Gemini encountered upstream HTTP 429. Muse/Codex lazy loading order and GLM tool execution did not satisfy all acceptance checks, and one planned case was not started after the budget was exhausted.
Complete dynamic permission revocation, all cancellation entry points, hosted execution authorization, broad live WebSocket coverage, and representative long-task quality/cost benefits are not certified. The documented official Codex cancellation propagation gap remains a client boundary.
See the implementation report, verification and compatibility report, and complete token report for exact versions, route results, metric definitions, and all 76 final physical attempts.

CLIProxyAPI_<version>_linux_<arch>.tar.gz is the default Linux build. It supports dynamic library plugins and targets a GLIBC 2.17 baseline.
CLIProxyAPI_<version>_linux_<arch>_no-plugin.tar.gz is the portable Linux build for musl-based or older systems such as OpenWrt. It does not support dynamic library plugins.
CLIProxyAPI_<version>_freebsd_aarch64_no-plugin.tar.gz is the FreeBSD arm64 build. It is built without CGO and does not support dynamic library plugins.