Files
langchain/libs
Mason Daugherty c669da7662 fix(groq): use qwen for tool choice integration tests (#38380)
Groq's `openai/gpt-oss-20b` can return reasoning content instead of
honoring forced tool choice in live integration tests. The forced
tool-choice coverage now uses Groq's recommended `qwen/qwen3.6-27b`
replacement with reasoning disabled, while leaving gpt-oss coverage in
place for reasoning-specific tests.

## Changes
- Add a dedicated tool-calling model constant for forced tool-choice
integration coverage.
- Update sync and async tool-choice tests to use `qwen/qwen3.6-27b` with
`reasoning_effort="none"`.
- Remove stale xfail markers from streaming tool-call tests and assert
the normalized aggregated stream output, including preserved tool-call
IDs.
2026-06-22 21:10:25 -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.