v0.4.14

AgentHub 0.4.14 sends a text-only tool result as a plain string on every Responses client the SDK ships, so a strictly validating DeepSeek Responses endpoint no longer rejects every request after a tool call.

Highlights

• deepseek_v4 and gpt6 send a text-only tool result as a plain string. The two first-party Responses clients still wrapped every tool result in a content-part list, the multimodal form. A strictly validating DeepSeek Responses endpoint answers that list with 400 {"code":"invalid_json"} on every request that replays a tool call, so a session died on the request after its first tool call (penguin-harness #404). Both clients now keep the list only for a result that carries images — the rule the generic openai_responses / openai_chat clients took in 0.4.11 — so every Responses and Chat Completions client in the SDK behaves alike: gpt6, deepseek_v4, minimax_m3, openai_responses; openai_chat, openai_chat_vllm_adapter, kimi_k3, glm5_3. deepseek_v4 keeps refusing images on the ids whose model reads none.

Both the Python and TypeScript implementations changed the same way. The message-order suites now assert the plain string on every Responses and Chat Completions client.

Install

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

Full detail: changelog/0.4.14/README.md.