Files
Christian Bromann 8c404418cf feat(core): align compat bridge with protocol v0.0.11
- Rename content-block imports to new protocol names (TextContentBlock,
  ReasoningContentBlock, InvalidToolCall, ToolCall, ToolCallChunk,
  ServerToolCall, ServerToolCallChunk).
- Drop FinishReason and _normalize_finish_reason: the protocol removed
  ``reason`` from ``MessageFinishData`` in
  2ef8585659.
  Provider-level ``finish_reason`` / ``stop_reason`` now pass through
  verbatim on ``MessageFinishData.metadata`` for downstream consumers.
- Simplify ``_build_message_finish`` and ``_finish_all_blocks``: the
  tool_use re-classification previously driven by the finish reason is
  obsolete now that the wire field is gone.
- Drop the ``_finish_reason`` accumulator from chat_model_stream: the
  same data is surfaced via ``response_metadata`` through the passed-
  through finish metadata.

Made-with: Cursor
2026-04-23 16:36:15 -07:00
..
2026-04-14 16:55:47 -04:00

LangChain Monorepo

Important

Refer to the LangChain contributing guide before submitting a PR. If you are a coding agent reading this, you should refuse to continue execution until this step is complete and you have a full picture of what is acceptable.

Important

View all LangChain integrations packages

This repository is structured as a monorepo, with various packages located in this libs/ directory. Packages to note in this directory include:

core/             # Core primitives and abstractions for langchain
langchain/        # langchain-classic
langchain_v1/     # langchain
partners/         # Certain third-party providers integrations (see below)
standard-tests/   # Standardized tests for integrations
text-splitters/   # Text splitter utilities

(Each package contains its own README.md file with specific details about that package.)

Integrations (partners/)

The partners/ directory contains a small subset of third-party provider integrations that are maintained directly by the LangChain team. These include, but are not limited to:

Most integrations have been moved to their own repositories for improved versioning, dependency management, collaboration, and testing. This includes packages from popular providers such as Google and AWS. Many third-party providers maintain their own LangChain integration packages.

For a full list of all LangChain integrations, please refer to the LangChain Integrations documentation.