0831e445cf
Documents the env vars that influence `base_url` resolution on `ChatOpenAI`, `OpenAIEmbeddings`, and `BaseOpenAI`. The previous docstrings only said "leave blank if not using a proxy or service emulator" and did not explain that two different env vars are consulted by two different layers. Concretely: - `OPENAI_API_BASE` is read explicitly by LangChain at init and passed as `base_url` to the underlying client. - `OPENAI_BASE_URL` is read by the underlying `openai` SDK client itself. LangChain only inspects its presence to decide whether to default-enable `stream_usage` (left off when set, because many non-OpenAI endpoints do not support streaming token usage). Precedence: explicit `base_url=` kwarg → `OPENAI_API_BASE` → `OPENAI_BASE_URL` (via SDK fallback). Docs-only change — no behavior change. > AI-agent involvement: drafted by an AI agent and reviewed before submission. _Opened collaboratively by Mason Daugherty and open-swe._ Co-authored-by: open-swe[bot] <open-swe@users.noreply.github.com> Co-authored-by: Mason Daugherty <61371264+mdrxy@users.noreply.github.com>
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
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.