v1.6.1

AgentGate 1.6.1 — Responses pass-through fixes

What's new

• Pass-through no longer drops tools. Codex gpt-5.6+ ships tool definitions inside input.additional_tools; native Responses pass-through forwarded the raw body without hoisting them, so upstreams saw no tools and the model wrote fake tool calls into its answer.
• Pass-through records tokens and cost again. Responses-shaped usage (response.usage with input_tokens / output_tokens) is now parsed alongside the Chat Completions shape.
• Capability gate before pass-through. When the target model or a requested custom tool is outside what the upstream Responses API accepts, the request falls back to protocol conversion instead of failing upstream.
• DeepSeek guidance. The Codex + DeepSeek guides explain, with measured evidence, why AgentGate keeps protocol conversion as the default instead of connecting directly to DeepSeek's Responses API.

本次更新

• 直通不再丢工具。 Codex gpt-5.6+ 把工具定义放在 input.additional_tools 里，而原生 Responses 直通转发 body 原文时没有做提升，上游收不到任何工具，模型只能在正文里编造工具调用。
• 直通恢复 token 与成本统计。 Responses 形态的 usage（response.usage 下的 input_tokens / output_tokens）现已与 Chat Completions 形态一并解析。
• 直通前的能力判定。 目标模型或请求中的自定义工具超出上游 Responses API 的接受范围时，自动回落到协议转换，不再把注定失败的请求发出去。
• DeepSeek 说明。 Codex + DeepSeek 教程补充实测依据，说明为什么默认保持协议转换、而不是直连 DeepSeek 的 Responses API。