Ollama 0.40.14 applies cloud-model output limits when launching Claude Code, verifies ChatGPT routing before Codex setup, retries ChatGPT disconnects, preserves packaged sampler defaults on OpenAI-compatible endpoints and keeps readable input and refusal history in Responses requests.
Why it matters: The fixes close silent configuration drift between local and cloud paths: model limits, sampling and prior refusals now survive compatibility layers more predictably. They also make broken ChatGPT routing fail earlier.
AWS now documents GPT-5.6 Terra and Luna on the Bedrock Runtime endpoint in AWS GovCloud (US), with Responses, Chat Completions and Converse APIs plus cross-region inference across both GovCloud regions. The earlier managed-device route for ChatGPT desktop, Work and Codex remains; model calls can now use Bedrock invocation logs, CloudWatch metrics and AWS cost attribution.
Why it matters: The GovCloud path now covers direct application APIs and automatic capacity routing, not only an OpenAI-compatible managed-device configuration. That improves redundancy and observability while making exact region routing, identity, logging and billing…
LiteLLM released signed stable version 1.103.5 with two backported Responses-bridge repairs. Non-streamed replies containing multiple message items and a function call are folded into choices[0], and bridged tool calls receive sequential indexes so clients that read the first choice can execute the intended tool.
Why it matters: The bug could turn an agent action into an apparently complete text answer because common clients never saw the tool call on a later choice. The stable backport gives production users a bounded repair without requiring a prerelease branch.
Ollama's 0.40.5 stable release adds Nemotron 3.5 Super and Bolt support, exposes Clef decision models through Ollama Cloud, fixes continuation of OpenAI-compatible Responses conversations with custom tool calls, clarifies cloud and gateway failures, and updates llama.cpp and MLX.
Why it matters: The release turns a monitored prerelease into a stable boundary and combines local runtime changes with optional cloud execution. Teams need to decide which tasks may leave the device and verify that tool-call history survives the Responses path without…
LiteLLM 1.102.0-rc.2 backports three request-filtering fixes so internal LiteLLM parameters, extra_headers and bridged Responses kwargs stay out of provider request bodies. The project reproduces an OpenAI 400 caused by model_alias_map reaching a GPT-5.4 chat request and says RC2 removes the gateway-only fields.
Why it matters: A gateway can break otherwise valid provider calls when its own routing or transport metadata leaks into the upstream schema. The release candidate narrows that boundary before stable promotion, but it does not remove the need to compare outbound request…