langchain-anthropic==1.5.4 リリースlangchain-anthropic==1.5.4

The LangChain project has published langchain-anthropic 1.5.4, a maintenance update to the package that links the LangChain framework with Anthropic's Claude models. The release is a patch on top of 1.5.3 and concentrates on bug fixes related to tool calling rather than new capabilities, which makes it most relevant to developers building agents and tool-using applications on Claude who want smoother, more predictable behavior.

At the center of the release is a fix for how the library handles tool schemas that use unsupported top-level composition (#39273). When developers expose tools to a model, they describe each tool's expected inputs with a JSON Schema. That schema can include composition operators such as anyOf, oneOf, and allOf, which combine or constrain several sub-schemas into one definition. Anthropic's tool-use API appears to place limits on such operators when they sit at the top level of a tool's input schema. The updated code is intended to handle these cases more gracefully rather than forwarding a schema the API would reject, which should reduce runtime errors when a tool definition includes constructs the provider does not accept.

The second bug fix preserves caller context, listed in the changelog as "preserve caller." While the excerpt does not spell out every detail, the accompanying summary describes it as preservation of caller context, meaning information supplied by the calling code is likely retained through the request path rather than being dropped or overwritten. Fixes of this kind typically matter for observability, tracing, and correct propagation of metadata across a chain or agent invocation, where losing caller-provided values can make debugging harder.

Rounding out the release is a routine dependency update. A chore bumped the minor-and-patch group across three directories with seven updates (#39187), keeping the package's transitive dependencies current. Changes like this are largely invisible to end users but help the package stay compatible with the wider Python ecosystem and pick up upstream security and stability fixes.

For context, langchain-anthropic is one of several provider integration packages that LangChain maintains separately from its core library. This modular structure lets each integration follow its own release cadence, so a fix specific to Claude can ship without waiting for a broader framework release. Anthropic's Claude family is a common choice for agentic workloads, and tool calling, sometimes called function calling, is the mechanism that lets a model request a structured action, such as querying a database or calling an external API, by returning arguments that conform to a declared schema. Because that schema is the contract between the application and the model, correct schema translation is essential to reliable tool use, which is why fixes in this area carry practical weight even in a small patch.

The emphasis on JSON Schema handling also reflects a broader challenge across the agent tooling landscape. Different model providers support overlapping but not identical subsets of JSON Schema, and frameworks like LangChain must translate a developer's tool definitions into whatever each provider accepts. Adjacent efforts, including the Model Context Protocol and various structured-output and function-calling features offered by other vendors, face similar edge cases around nested schemas and composition operators. A fix that handles unsupported top-level composition is a small but concrete example of the ongoing work to reconcile these differences so that the same tool definition behaves consistently regardless of the underlying model.

Users on 1.5.3 who rely on tool calling with Claude, particularly those whose tools use anyOf, oneOf, or allOf at the top level of an input schema, are the most likely to benefit from upgrading. As with any patch release, reviewing the linked pull requests and testing against existing tool definitions before deploying to production is advisable, since the exact behavior of the caller-context change and the schema handling may vary depending on how an application constructs its tools. The release notes point to the individual pull requests, numbered 39277, 39273, and 39187, for developers who want to inspect the specific code changes and confirm the scope of each fix.