v0.4.13

AgentHub 0.4.13 keeps a tool-calling turn replayable when the model produced no chain of thought, so a DeepSeek tool chain does not die part-way through behind an endpoint that reissues tool_call ids.

Highlights

• A tool-calling turn with no chain of thought still carries its reasoning field. openai-chat attached the reasoning field only when the assistant turn had thinking text, so a turn that made tool calls and thought nothing went back with the field absent. DeepSeek refuses such a request with 400 The `reasoning_content` in the thinking mode must be passed back to the API. whenever that turn is part of the tool-call chain still being continued — and it produces exactly those turns itself, answering with a bare tool call once a chain runs past its first few steps. The rejection is waived only for tool_call ids DeepSeek issued, so an endpoint that reissues ids removes the waiver, and a run died mid-task on a provider 4xx that no retry could fix. The client now records the reasoning field the upstream has produced in the conversation and sends that field as an empty string on such a message, following the same fidelity rule as a non-empty replay (reasoning_content, reasoning, or both when the origin is ambiguous). A conversation that never produced a reasoning field never receives one, so a server that does not speak one is untouched. openai-chat-vllm-adapter inherits the transform.

Both the Python and TypeScript implementations changed the same way.

claude5, ant_messages, gpt6, openai_responses, glm5_3, kimi_k3, minimax_m3 and gemini3_8 were probed live against their own endpoints and need no equivalent change: none of them omits the reasoning carrier for a thinking-free tool turn, and none of those providers rejects one.

Install

pip install agenthub-python==0.4.13
npm install @prismshadow/agenthub@0.4.13