cr

.devcontainer/README.md

@@ -1,49 +0,0 @@
-# Dev container
-
-This project includes a [dev container](https://containers.dev/), which lets you use a container as a full-featured dev environment.
-
-You can use the dev container configuration in this folder to build and run the app without needing to install any of its tools locally! You can use it in [GitHub Codespaces](https://github.com/features/codespaces) or the [VS Code Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers).
-
-## GitHub Codespaces
-
-[![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/langchain-ai/langchain)
-
-You may use the button above, or follow these steps to open this repo in a Codespace:
-
-1. Click the **Code** drop-down menu at the top of <https://github.com/langchain-ai/langchain>.
-1. Click on the **Codespaces** tab.
-1. Click **Create codespace on master**.
-
-For more info, check out the [GitHub documentation](https://docs.github.com/en/free-pro-team@latest/github/developing-online-with-codespaces/creating-a-codespace#creating-a-codespace).
-
-## VS Code Dev Containers
-
-[![Open in Dev Containers](https://img.shields.io/static/v1?label=Dev%20Containers&message=Open&color=blue&logo=visualstudiocode)](https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/langchain-ai/langchain)
-
-> [!NOTE]
-> If you click the link above you will open the main repo (`langchain-ai/langchain`) and *not* your local cloned repo. This is fine if you only want to run and test the library, but if you want to contribute you can use the link below and replace with your username and cloned repo name:
-
-```txt
-https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/&lt;YOUR_USERNAME&gt;/&lt;YOUR_CLONED_REPO_NAME&gt;
-```
-
-Then you will have a local cloned repo where you can contribute and then create pull requests.
-
-If you already have VS Code and Docker installed, you can use the button above to get started. This will use VSCode to automatically install the Dev Containers extension if needed, clone the source code into a container volume, and spin up a dev container for use.
-
-Alternatively you can also follow these steps to open this repo in a container using the VS Code Dev Containers extension:
-
-1. If this is your first time using a development container, please ensure your system meets the pre-reqs (i.e. have Docker installed) in the [getting started steps](https://aka.ms/vscode-remote/containers/getting-started).
-
-2. Open a locally cloned copy of the code:
-
-   - Fork and Clone this repository to your local filesystem.
-   - Press <kbd>F1</kbd> and select the **Dev Containers: Open Folder in Container...** command.
-   - Select the cloned copy of this folder, wait for the container to start, and try things out!
-
-You can learn more in the [Dev Containers documentation](https://code.visualstudio.com/docs/devcontainers/containers).
-
-## Tips and tricks
-
-- If you are working with the same repository folder in a container and Windows, you'll want consistent line endings (otherwise you may see hundreds of changes in the SCM view). The `.gitattributes` file in the root of this repo will disable line ending conversion and should prevent this. See [tips and tricks](https://code.visualstudio.com/docs/devcontainers/tips-and-tricks#_resolving-git-line-ending-issues-in-containers-resulting-in-many-modified-files) for more info.
-- If you'd like to review the contents of the image used in this dev container, you can check it out in the [devcontainers/images](https://github.com/devcontainers/images/tree/main/src/python) repo.

.devcontainer/devcontainer.json

@@ -1,58 +0,0 @@
-// For format details, see https://aka.ms/devcontainer.json. For config options, see the
-// README at: https://github.com/devcontainers/templates/tree/main/src/docker-existing-docker-compose
-{
-  // Name for the dev container
-  "name": "langchain",
-  // Point to a Docker Compose file
-  "dockerComposeFile": "./docker-compose.yaml",
-  // Required when using Docker Compose. The name of the service to connect to once running
-  "service": "langchain",
-  // The optional 'workspaceFolder' property is the path VS Code should open by default when
-  // connected. This is typically a file mount in .devcontainer/docker-compose.yml
-  "workspaceFolder": "/workspaces/langchain",
-  "mounts": [
-    "source=langchain-workspaces,target=/workspaces/langchain,type=volume"
-  ],
-  // Prevent the container from shutting down
-  "overrideCommand": true,
-  // Features to add to the dev container. More info: https://containers.dev/features
-  "features": {
-    "ghcr.io/devcontainers/features/git:1": {},
-    "ghcr.io/devcontainers/features/github-cli:1": {}
-  },
-  "containerEnv": {
-    "UV_LINK_MODE": "copy"
-  },
-  // Use 'forwardPorts' to make a list of ports inside the container available locally.
-  // "forwardPorts": [],
-  // Run commands after the container is created
-  "postCreateCommand": "cd libs/langchain_v1 && uv sync && echo 'LangChain (Python) dev environment ready!'",
-  // Configure tool-specific properties.
-  "customizations": {
-    "vscode": {
-      "extensions": [
-        "ms-python.python",
-        "ms-python.debugpy",
-        "ms-python.mypy-type-checker",
-        "ms-python.isort",
-        "unifiedjs.vscode-mdx",
-        "davidanson.vscode-markdownlint",
-        "ms-toolsai.jupyter",
-        "GitHub.copilot",
-        "GitHub.copilot-chat"
-      ],
-      "settings": {
-        "python.defaultInterpreterPath": "libs/langchain_v1/.venv/bin/python",
-        "python.formatting.provider": "none",
-        "[python]": {
-          "editor.formatOnSave": true,
-          "editor.codeActionsOnSave": {
-            "source.organizeImports": true
-          }
-        }
-      }
-    }
-  }
-  // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
-  // "remoteUser": "root"
-}

.devcontainer/docker-compose.yaml

@@ -1,13 +0,0 @@
-version: '3'
-services:
-  langchain:
-    build:
-      dockerfile: libs/langchain/dev.Dockerfile
-      context: ..
-
-    networks:
-      - langchain-network
-
-networks:
-  langchain-network:
-    driver: bridge

.dockerignore

@@ -1,34 +0,0 @@
-# Git
-.git
-.github
-
-# Python
-__pycache__
-*.pyc
-*.pyo
-.venv
-.mypy_cache
-.pytest_cache
-.ruff_cache
-*.egg-info
-.tox
-
-# IDE
-.idea
-.vscode
-
-# Worktree
-worktree
-
-# Test artifacts
-.coverage
-htmlcov
-coverage.xml
-
-# Build artifacts
-dist
-build
-
-# Misc
-*.log
-.DS_Store

.editorconfig

@@ -1,52 +0,0 @@
-# top-most EditorConfig file
-root = true
-
-# All files
-[*]
-charset = utf-8
-end_of_line = lf
-insert_final_newline = true
-trim_trailing_whitespace = true
-
-# Python files
-[*.py]
-indent_style = space
-indent_size = 4
-max_line_length = 88
-
-# JSON files
-[*.json]
-indent_style = space
-indent_size = 2
-
-# YAML files
-[*.{yml,yaml}]
-indent_style = space
-indent_size = 2
-
-# Markdown files
-[*.md]
-indent_style = space
-indent_size = 2
-trim_trailing_whitespace = false
-
-# Configuration files
-[*.{toml,ini,cfg}]
-indent_style = space
-indent_size = 4
-
-# Shell scripts
-[*.sh]
-indent_style = space
-indent_size = 2
-
-# Makefile
-[Makefile]
-indent_style = tab
-indent_size = 4
-
-# Jupyter notebooks
-[*.ipynb]
-# Jupyter may include trailing whitespace in cell
-# outputs that's semantically meaningful
-trim_trailing_whitespace = false

.gitattributes

@@ -1,3 +0,0 @@
-* text=auto eol=lf
-*.{cmd,[cC][mM][dD]} text eol=crlf
-*.{bat,[bB][aA][tT]} text eol=crlf

.github/CODEOWNERS

@@ -1,3 +0,0 @@
-/.github/   @baskaryan @ccurme @eyurtsev
-/libs/core/ @eyurtsev
-/libs/partners/ @ccurme @mdrxy

.github/CONTRIBUTING.md

@@ -0,0 +1,182 @@
+# Contributing to LangChain
+
+Hi there! Thank you for even being interested in contributing to LangChain.
+As an open source project in a rapidly developing field, we are extremely open
+to contributions, whether it be in the form of a new feature, improved infra, or better documentation.
+
+To contribute to this project, please follow a ["fork and pull request"](https://docs.github.com/en/get-started/quickstart/contributing-to-projects) workflow.
+Please do not try to push directly to this repo unless you are maintainer.
+
+## 🗺️Contributing Guidelines
+
+### 🚩GitHub Issues
+
+Our [issues](https://github.com/hwchase17/langchain/issues) page is kept up to date
+with bugs, improvements, and feature requests. There is a taxonomy of labels to help
+with sorting and discovery of issues of interest. These include:
+
+- prompts: related to prompt tooling/infra.
+- llms: related to LLM wrappers/tooling/infra.
+- chains
+- utilities: related to different types of utilities to integrate with (Python, SQL, etc.).
+- agents
+- memory
+- applications: related to example applications to build
+
+If you start working on an issue, please assign it to yourself.
+
+If you are adding an issue, please try to keep it focused on a single modular bug/improvement/feature.
+If the two issues are related, or blocking, please link them rather than keep them as one single one.
+
+We will try to keep these issues as up to date as possible, though
+with the rapid rate of develop in this field some may get out of date.
+If you notice this happening, please just let us know.
+
+### 🙋Getting Help
+
+Although we try to have a developer setup to make it as easy as possible for others to contribute (see below)
+it is possible that some pain point may arise around environment setup, linting, documentation, or other.
+Should that occur, please contact a maintainer! Not only do we want to help get you unblocked,
+but we also want to make sure that the process is smooth for future contributors.
+
+In a similar vein, we do enforce certain linting, formatting, and documentation standards in the codebase.
+If you are finding these difficult (or even just annoying) to work with,
+feel free to contact a maintainer for help - we do not want these to get in the way of getting
+good code into the codebase.
+
+### 🏭Release process
+
+As of now, LangChain has an ad hoc release process: releases are cut with high frequency via by
+a developer and published to [PyPI](https://pypi.org/project/langchain/).
+
+LangChain follows the [semver](https://semver.org/) versioning standard. However, as pre-1.0 software,
+even patch releases may contain [non-backwards-compatible changes](https://semver.org/#spec-item-4).
+
+If your contribution has made its way into a release, we will want to give you credit on Twitter (only if you want though)!
+If you have a Twitter account you would like us to mention, please let us know in the PR or in another manner.
+
+## 🚀Quick Start
+
+This project uses [Poetry](https://python-poetry.org/) as a dependency manager. Check out Poetry's [documentation on how to install it](https://python-poetry.org/docs/#installation) on your system before proceeding.
+
+❗Note: If you use `Conda` or `Pyenv` as your environment / package manager, avoid dependency conflicts by doing the following first:
+1. *Before installing Poetry*, create and activate a new Conda env (e.g. `conda create -n langchain python=3.9`)
+2. Install Poetry (see above)
+3. Tell Poetry to use the virtualenv python environment (`poetry config virtualenvs.prefer-active-python true`)
+4. Continue with the following steps.
+
+To install requirements:
+
+```bash
+poetry install -E all
+```
+
+This will install all requirements for running the package, examples, linting, formatting, tests, and coverage. Note the `-E all` flag will install all optional dependencies necessary for integration testing.
+
+Now, you should be able to run the common tasks in the following section.
+
+## ✅Common Tasks
+
+Type `make` for a list of common tasks.
+
+### Code Formatting
+
+Formatting for this project is done via a combination of [Black](https://black.readthedocs.io/en/stable/) and [isort](https://pycqa.github.io/isort/).
+
+To run formatting for this project:
+
+```bash
+make format
+```
+
+### Linting
+
+Linting for this project is done via a combination of [Black](https://black.readthedocs.io/en/stable/), [isort](https://pycqa.github.io/isort/), [flake8](https://flake8.pycqa.org/en/latest/), and [mypy](http://mypy-lang.org/).
+
+To run linting for this project:
+
+```bash
+make lint
+```
+
+We recognize linting can be annoying - if you do not want to do it, please contact a project maintainer, and they can help you with it. We do not want this to be a blocker for good code getting contributed.
+
+### Coverage
+
+Code coverage (i.e. the amount of code that is covered by unit tests) helps identify areas of the code that are potentially more or less brittle.
+
+To get a report of current coverage, run the following:
+
+```bash
+make coverage
+```
+
+### Testing
+
+Unit tests cover modular logic that does not require calls to outside APIs.
+
+To run unit tests:
+
+```bash
+make test
+```
+
+If you add new logic, please add a unit test.
+
+Integration tests cover logic that requires making calls to outside APIs (often integration with other services).
+
+To run integration tests:
+
+```bash
+make integration_tests
+```
+
+If you add support for a new external API, please add a new integration test.
+
+### Adding a Jupyter Notebook
+
+If you are adding a Jupyter notebook example, you'll want to install the optional `dev` dependencies.
+
+To install dev dependencies:
+
+```bash
+poetry install --with dev
+```
+
+Launch a notebook:
+
+```bash
+poetry run jupyter notebook
+```
+
+When you run `poetry install`, the `langchain` package is installed as editable in the virtualenv, so your new logic can be imported into the notebook.
+
+## Documentation
+
+### Contribute Documentation
+
+Docs are largely autogenerated by [sphinx](https://www.sphinx-doc.org/en/master/) from the code.
+
+For that reason, we ask that you add good documentation to all classes and methods.
+
+Similar to linting, we recognize documentation can be annoying. If you do not want to do it, please contact a project maintainer, and they can help you with it. We do not want this to be a blocker for good code getting contributed.
+
+### Build Documentation Locally
+
+Before building the documentation, it is always a good idea to clean the build directory:
+
+```bash
+make docs_clean
+```
+
+Next, you can run the linkchecker to make sure all links are valid:
+
+```bash
+make docs_linkcheck
+```
+
+Finally, you can build the documentation as outlined below:
+
+```bash
+make docs_build
+```

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -1,142 +0,0 @@
-name: "\U0001F41B Bug Report"
-description: Report a bug in LangChain. To report a security issue, please instead use the security option (below). For questions, please use the LangChain forum (below).
-labels: ["bug"]
-type: bug
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thank you for taking the time to file a bug report.
-
-        For usage questions, feature requests and general design questions, please use the [LangChain Forum](https://forum.langchain.com/).
-
-        Check these before submitting to see if your issue has already been reported, fixed or if there's another way to solve your problem:
-
-        * [Documentation](https://docs.langchain.com/oss/python/langchain/overview),
-        * [API Reference Documentation](https://reference.langchain.com/python/),
-        * [LangChain ChatBot](https://chat.langchain.com/)
-        * [GitHub search](https://github.com/langchain-ai/langchain),
-        * [LangChain Forum](https://forum.langchain.com/),
-  - type: checkboxes
-    id: checks
-    attributes:
-      label: Checked other resources
-      description: Please confirm and check all the following options.
-      options:
-        - label: This is a bug, not a usage question.
-          required: true
-        - label: I added a clear and descriptive title that summarizes this issue.
-          required: true
-        - label: I used the GitHub search to find a similar question and didn't find it.
-          required: true
-        - label: I am sure that this is a bug in LangChain rather than my code.
-          required: true
-        - label: The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).
-          required: true
-        - label: This is not related to the langchain-community package.
-          required: true
-        - label: I posted a self-contained, minimal, reproducible example. A maintainer can copy it and run it AS IS.
-          required: true
-  - type: checkboxes
-    id: package
-    attributes:
-      label: Package (Required)
-      description: |
-        Which `langchain` package(s) is this bug related to? Select at least one.
-
-        Note that if the package you are reporting for is not listed here, it is not in this repository (e.g. `langchain-google-genai` is in [`langchain-ai/langchain-google`](https://github.com/langchain-ai/langchain-google/)).
-
-        Please report issues for other packages to their respective repositories.
-      options:
-        - label: langchain
-        - label: langchain-openai
-        - label: langchain-anthropic
-        - label: langchain-classic
-        - label: langchain-core
-        - label: langchain-cli
-        - label: langchain-model-profiles
-        - label: langchain-tests
-        - label: langchain-text-splitters
-        - label: langchain-chroma
-        - label: langchain-deepseek
-        - label: langchain-exa
-        - label: langchain-fireworks
-        - label: langchain-groq
-        - label: langchain-huggingface
-        - label: langchain-mistralai
-        - label: langchain-nomic
-        - label: langchain-ollama
-        - label: langchain-perplexity
-        - label: langchain-prompty
-        - label: langchain-qdrant
-        - label: langchain-xai
-        - label: Other / not sure / general
-  - type: textarea
-    id: reproduction
-    validations:
-      required: true
-    attributes:
-      label: Reproduction Steps / Example Code (Python)
-      description: |
-        Please add a self-contained, [minimal, reproducible, example](https://stackoverflow.com/help/minimal-reproducible-example) with your use case.
-
-        If a maintainer can copy it, run it, and see it right away, there's a much higher chance that you'll be able to get help.
-
-        **Important!**
-
-        * Avoid screenshots, as they are hard to read and (more importantly) don't allow others to copy-and-paste your code.
-        * Reduce your code to the minimum required to reproduce the issue if possible.
-
-        (This will be automatically formatted into code, so no need for backticks.)
-      render: python
-      placeholder: |
-        from langchain_core.runnables import RunnableLambda
-
-        def bad_code(inputs) -> int:
-          raise NotImplementedError('For demo purpose')
-
-          chain = RunnableLambda(bad_code)
-          chain.invoke('Hello!')
-  - type: textarea
-    attributes:
-      label: Error Message and Stack Trace (if applicable)
-      description: |
-        If you are reporting an error, please copy and paste the full error message and
-        stack trace.
-        (This will be automatically formatted into code, so no need for backticks.)
-      render: shell
-  - type: textarea
-    id: description
-    attributes:
-      label: Description
-      description: |
-        What is the problem, question, or error?
-
-        Write a short description telling what you are doing, what you expect to happen, and what is currently happening.
-      placeholder: |
-        * I'm trying to use the `langchain` library to do X.
-        * I expect to see Y.
-        * Instead, it does Z.
-    validations:
-      required: true
-  - type: textarea
-    id: system-info
-    attributes:
-      label: System Info
-      description: |
-        Please share your system info with us.
-
-        Run the following command in your terminal and paste the output here:
-
-        `python -m langchain_core.sys_info`
-
-        or if you have an existing python interpreter running:
-
-        ```python
-        from langchain_core import sys_info
-        sys_info.print_sys_info()
-        ```
-      placeholder: |
-        python -m langchain_core.sys_info
-    validations:
-      required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -1,15 +0,0 @@
-blank_issues_enabled: false
-version: 2.1
-contact_links:
-  - name: 💬 LangChain Forum
-    url:  https://forum.langchain.com/
-    about: General community discussions and support
-  - name: 📚 LangChain Documentation
-    url: https://docs.langchain.com/oss/python/langchain/overview
-    about: View the official LangChain documentation
-  - name: 📚 API Reference Documentation
-    url: https://reference.langchain.com/python/
-    about: View the official LangChain API reference documentation
-  - name: 📚 Documentation issue
-    url: https://github.com/langchain-ai/docs/issues/new?template=01-langchain.yml
-    about: Report an issue related to the LangChain documentation

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -1,152 +0,0 @@
-name: "✨ Feature Request"
-description: Request a new feature or enhancement for LangChain. For questions, please use the LangChain forum (below).
-labels: ["feature request"]
-type: feature
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thank you for taking the time to request a new feature.
-
-        Use this to request NEW FEATURES or ENHANCEMENTS in LangChain. For bug reports, please use the bug report template. For usage questions and general design questions, please use the [LangChain Forum](https://forum.langchain.com/).
-
-        Relevant links to check before filing a feature request to see if your request has already been made or
-        if there's another way to achieve what you want:
-
-        * [Documentation](https://docs.langchain.com/oss/python/langchain/overview),
-        * [API Reference Documentation](https://reference.langchain.com/python/),
-        * [LangChain ChatBot](https://chat.langchain.com/)
-        * [GitHub search](https://github.com/langchain-ai/langchain),
-        * [LangChain Forum](https://forum.langchain.com/),
-  - type: checkboxes
-    id: checks
-    attributes:
-      label: Checked other resources
-      description: Please confirm and check all the following options.
-      options:
-        - label: This is a feature request, not a bug report or usage question.
-          required: true
-        - label: I added a clear and descriptive title that summarizes the feature request.
-          required: true
-        - label: I used the GitHub search to find a similar feature request and didn't find it.
-          required: true
-        - label: I checked the LangChain documentation and API reference to see if this feature already exists.
-          required: true
-        - label: This is not related to the langchain-community package.
-          required: true
-  - type: checkboxes
-    id: package
-    attributes:
-      label: Package (Required)
-      description: |
-        Which `langchain` package(s) is this request related to? Select at least one.
-
-        Note that if the package you are requesting for is not listed here, it is not in this repository (e.g. `langchain-google-genai` is in `langchain-ai/langchain`).
-
-        Please submit feature requests for other packages to their respective repositories.
-      options:
-        - label: langchain
-        - label: langchain-openai
-        - label: langchain-anthropic
-        - label: langchain-classic
-        - label: langchain-core
-        - label: langchain-cli
-        - label: langchain-model-profiles
-        - label: langchain-tests
-        - label: langchain-text-splitters
-        - label: langchain-chroma
-        - label: langchain-deepseek
-        - label: langchain-exa
-        - label: langchain-fireworks
-        - label: langchain-groq
-        - label: langchain-huggingface
-        - label: langchain-mistralai
-        - label: langchain-nomic
-        - label: langchain-ollama
-        - label: langchain-perplexity
-        - label: langchain-prompty
-        - label: langchain-qdrant
-        - label: langchain-xai
-        - label: Other / not sure / general
-  - type: textarea
-    id: feature-description
-    validations:
-      required: true
-    attributes:
-      label: Feature Description
-      description: |
-        Please provide a clear and concise description of the feature you would like to see added to LangChain.
-
-        What specific functionality are you requesting? Be as detailed as possible.
-      placeholder: |
-        I would like LangChain to support...
-
-        This feature would allow users to...
-  - type: textarea
-    id: use-case
-    validations:
-      required: true
-    attributes:
-      label: Use Case
-      description: |
-        Describe the specific use case or problem this feature would solve.
-
-        Why do you need this feature? What problem does it solve for you or other users?
-      placeholder: |
-        I'm trying to build an application that...
-
-        Currently, I have to work around this by...
-
-        This feature would help me/users to...
-  - type: textarea
-    id: proposed-solution
-    validations:
-      required: false
-    attributes:
-      label: Proposed Solution
-      description: |
-        If you have ideas about how this feature could be implemented, please describe them here.
-
-        This is optional but can be helpful for maintainers to understand your vision.
-      placeholder: |
-        I think this could be implemented by...
-
-        The API could look like...
-
-        ```python
-        # Example of how the feature might work
-        ```
-  - type: textarea
-    id: alternatives
-    validations:
-      required: false
-    attributes:
-      label: Alternatives Considered
-      description: |
-        Have you considered any alternative solutions or workarounds?
-
-        What other approaches have you tried or considered?
-      placeholder: |
-        I've tried using...
-
-        Alternative approaches I considered:
-        1. ...
-        2. ...
-
-        But these don't work because...
-  - type: textarea
-    id: additional-context
-    validations:
-      required: false
-    attributes:
-      label: Additional Context
-      description: |
-        Add any other context, screenshots, examples, or references that would help explain your feature request.
-      placeholder: |
-        Related issues: #...
-
-        Similar features in other libraries:
-        - ...
-
-        Additional context or examples:
-        - ...

.github/ISSUE_TEMPLATE/privileged.yml

@@ -1,50 +0,0 @@
-name: 🔒 Privileged
-description: You are a LangChain maintainer, or was asked directly by a maintainer to create an issue here. If not, check the other options.
-body:
-  - type: markdown
-    attributes:
-      value: |
-        If you are not a LangChain maintainer, employee, or were not asked directly by a maintainer to create an issue, then please start the conversation on the [LangChain Forum](https://forum.langchain.com/) instead.
-  - type: checkboxes
-    id: privileged
-    attributes:
-      label: Privileged issue
-      description: Confirm that you are allowed to create an issue here.
-      options:
-        - label: I am a LangChain maintainer, or was asked directly by a LangChain maintainer to create an issue here.
-          required: true
-  - type: textarea
-    id: content
-    attributes:
-      label: Issue Content
-      description: Add the content of the issue here.
-  - type: checkboxes
-    id: package
-    attributes:
-      label: Package (Required)
-      description: |
-        Please select package(s) that this issue is related to.
-      options:
-        - label: langchain
-        - label: langchain-openai
-        - label: langchain-anthropic
-        - label: langchain-classic
-        - label: langchain-core
-        - label: langchain-cli
-        - label: langchain-model-profiles
-        - label: langchain-tests
-        - label: langchain-text-splitters
-        - label: langchain-chroma
-        - label: langchain-deepseek
-        - label: langchain-exa
-        - label: langchain-fireworks
-        - label: langchain-groq
-        - label: langchain-huggingface
-        - label: langchain-mistralai
-        - label: langchain-nomic
-        - label: langchain-ollama
-        - label: langchain-perplexity
-        - label: langchain-prompty
-        - label: langchain-qdrant
-        - label: langchain-xai
-        - label: Other / not sure / general

.github/ISSUE_TEMPLATE/task.yml

@@ -1,121 +0,0 @@
-name: "📋 Task"
-description: Create a task for project management and tracking by LangChain maintainers. If you are not a maintainer, please use other templates or the forum.
-labels: ["task"]
-type: task
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for creating a task to help organize LangChain development.
-
-        This template is for **maintainer tasks** such as project management, development planning, refactoring, documentation updates, and other organizational work.
-
-        If you are not a LangChain maintainer or were not asked directly by a maintainer to create a task, then please start the conversation on the [LangChain Forum](https://forum.langchain.com/) instead or use the appropriate bug report or feature request templates on the previous page.
-  - type: checkboxes
-    id: maintainer
-    attributes:
-      label: Maintainer task
-      description: Confirm that you are allowed to create a task here.
-      options:
-        - label: I am a LangChain maintainer, or was asked directly by a LangChain maintainer to create a task here.
-          required: true
-  - type: textarea
-    id: task-description
-    attributes:
-      label: Task Description
-      description: |
-        Provide a clear and detailed description of the task.
-
-        What needs to be done? Be specific about the scope and requirements.
-      placeholder: |
-        This task involves...
-
-        The goal is to...
-
-        Specific requirements:
-        - ...
-        - ...
-    validations:
-      required: true
-  - type: textarea
-    id: acceptance-criteria
-    attributes:
-      label: Acceptance Criteria
-      description: |
-        Define the criteria that must be met for this task to be considered complete.
-
-        What are the specific deliverables or outcomes expected?
-      placeholder: |
-        This task will be complete when:
-        - [ ] ...
-        - [ ] ...
-        - [ ] ...
-    validations:
-      required: true
-  - type: textarea
-    id: context
-    attributes:
-      label: Context and Background
-      description: |
-        Provide any relevant context, background information, or links to related issues/PRs.
-
-        Why is this task needed? What problem does it solve?
-      placeholder: |
-        Background:
-        - ...
-
-        Related issues/PRs:
-        - #...
-
-        Additional context:
-        - ...
-    validations:
-      required: false
-  - type: textarea
-    id: dependencies
-    attributes:
-      label: Dependencies
-      description: |
-        List any dependencies or blockers for this task.
-
-        Are there other tasks, issues, or external factors that need to be completed first?
-      placeholder: |
-        This task depends on:
-        - [ ] Issue #...
-        - [ ] PR #...
-        - [ ] External dependency: ...
-
-        Blocked by:
-        - ...
-    validations:
-      required: false
-  - type: checkboxes
-    id: package
-    attributes:
-      label: Package (Required)
-      description: |
-        Please select package(s) that this task is related to.
-      options:
-        - label: langchain
-        - label: langchain-openai
-        - label: langchain-anthropic
-        - label: langchain-classic
-        - label: langchain-core
-        - label: langchain-cli
-        - label: langchain-model-profiles
-        - label: langchain-tests
-        - label: langchain-text-splitters
-        - label: langchain-chroma
-        - label: langchain-deepseek
-        - label: langchain-exa
-        - label: langchain-fireworks
-        - label: langchain-groq
-        - label: langchain-huggingface
-        - label: langchain-mistralai
-        - label: langchain-nomic
-        - label: langchain-ollama
-        - label: langchain-perplexity
-        - label: langchain-prompty
-        - label: langchain-qdrant
-        - label: langchain-xai
-        - label: Other / not sure / general

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,30 +0,0 @@
-(Replace this entire block of text)
-
-Read the full contributing guidelines: https://docs.langchain.com/oss/python/contributing/overview
-
-Thank you for contributing to LangChain! Follow these steps to have your pull request considered as ready for review.
-
-1. PR title: Should follow the format: TYPE(SCOPE): DESCRIPTION
-
-  - Examples:
-    - fix(anthropic): resolve flag parsing error
-    - feat(core): add multi-tenant support
-    - test(openai): update API usage tests
-  - Allowed TYPE and SCOPE values: https://github.com/langchain-ai/langchain/blob/master/.github/workflows/pr_lint.yml#L15-L33
-
-2. PR description:
-
-  - Write 1-2 sentences summarizing the change.
-  - If this PR addresses a specific issue, please include "Fixes #ISSUE_NUMBER" in the description to automatically close the issue when the PR is merged.
-  - If there are any breaking changes, please clearly describe them.
-  - If this PR depends on another PR being merged first, please include "Depends on #PR_NUMBER" inthe description.
-
-3. Run `make format`, `make lint` and `make test` from the root of the package(s) you've modified.
-
-  - We will not consider a PR unless these three are passing in CI.
-
-Additional guidelines:
-
-  - We ask that if you use generative AI for your contribution, you include a disclaimer.
-  - PRs should not touch more than one package unless absolutely necessary.
-  - Do not update the `uv.lock` files unless or add dependencies to `pyproject.toml` files (even optional ones) unless you have explicit permission to do so by a maintainer.

.github/actions/uv_setup/action.yml

@@ -1,39 +0,0 @@
-# Helper to set up Python and uv with caching
-
-name: uv-install
-description: Set up Python and uv with caching
-
-inputs:
-  python-version:
-    description: Python version, supporting MAJOR.MINOR only
-    required: true
-  enable-cache:
-    description: Enable caching for uv dependencies
-    required: false
-    default: "true"
-  cache-suffix:
-    description: Custom cache key suffix for cache invalidation
-    required: false
-    default: ""
-  working-directory:
-    description: Working directory for cache glob scoping
-    required: false
-    default: "**"
-
-env:
-  UV_VERSION: "0.5.25"
-
-runs:
-  using: composite
-  steps:
-    - name: Install uv and set the python version
-      uses: astral-sh/setup-uv@v7
-      with:
-        version: ${{ env.UV_VERSION }}
-        python-version: ${{ inputs.python-version }}
-        enable-cache: ${{ inputs.enable-cache }}
-        cache-dependency-glob: |
-          ${{ inputs.working-directory }}/pyproject.toml
-          ${{ inputs.working-directory }}/uv.lock
-          ${{ inputs.working-directory }}/requirements*.txt
-        cache-suffix: ${{ inputs.cache-suffix }}

.github/dependabot.yml

@@ -1,11 +0,0 @@
-# Please see the documentation for all configuration options:
-# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
-# and
-# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
-
-version: 2
-updates:
-  - package-ecosystem: "github-actions"
-    directory: "/"
-    schedule:
-      interval: "weekly"

.github/images/logo-dark.svg

@@ -1,25 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1584.81 250">
-  <defs>
-    <style>
-      .cls-1 {
-        fill: #1c3c3c;
-        stroke-width: 0px;
-      }
-    </style>
-  </defs>
-  <g id="LanChain-logo">
-    <g id="LangChain-logotype">
-      <polygon class="cls-1" points="596.33 49.07 596.33 200.67 700.76 200.67 700.76 177.78 620.04 177.78 620.04 49.07 596.33 49.07"/>
-      <path class="cls-1" d="M1126.83,49.07c-20.53,0-37.95,7.4-50.38,21.41-12.32,13.88-18.82,33.36-18.82,56.33,0,47.23,27.25,77.75,69.41,77.75,29.71,0,52.71-15.54,61.54-41.56l2.14-6.31-23.53-8.94-2.17,7.03c-5.26,17.01-18.75,26.38-37.99,26.38-27.48,0-44.55-20.82-44.55-54.34s17.23-54.34,44.97-54.34c19.23,0,30.31,7.54,35.95,24.44l2.46,7.37,22.91-10.75-2.1-5.9c-8.96-25.22-29.65-38.56-59.85-38.56Z"/>
-      <path class="cls-1" d="M756.43,85.05c-22.76,0-39.78,10.67-46.69,29.27-.44,1.19-1.77,4.78-1.77,4.78l19.51,12.62,2.65-6.91c4.52-11.78,12.88-17.27,26.3-17.27s21.1,6.51,20.96,19.33c0,.52-.04,2.09-.04,2.09,0,0-17.76,2.88-25.08,4.43-31.23,6.6-44.31,18.52-44.31,38.02,0,10.39,5.77,21.64,16.3,27.95,6.32,3.78,14.57,5.21,23.68,5.21,5.99,0,11.81-.89,17.2-2.53,12.25-4.07,15.67-12.07,15.67-12.07v10.46h20.29v-74.78c0-25.42-16.7-40.6-44.67-40.6ZM777.46,164.85c0,7.86-8.56,18.93-28.5,18.93-5.63,0-9.62-1.49-12.28-3.71-3.56-2.97-4.73-7.24-4.24-11.01.21-1.64,1.2-5.17,4.87-8.23,3.75-3.13,10.38-5.37,20.62-7.6,8.42-1.83,19.54-3.85,19.54-3.85v15.48Z"/>
-      <path class="cls-1" d="M876.11,85.04c-2.82,0-5.57.2-8.24.57-18.17,2.73-23.49,11.96-23.49,11.96l.02-9.31h-22.74s0,112.19,0,112.19h23.71v-62.18c0-21.13,15.41-30.75,29.73-30.75,15.48,0,23,8.32,23,25.45v67.48h23.71v-70.74c0-27.56-17.51-44.67-45.69-44.67Z"/>
-      <path class="cls-1" d="M1539.12,85.04c-2.82,0-5.57.2-8.24.57-18.17,2.73-23.49,11.96-23.49,11.96v-9.32h-22.72v112.2h23.71v-62.18c0-21.13,15.41-30.75,29.73-30.75,15.48,0,23,8.32,23,25.45v67.48h23.71v-70.74c0-27.56-17.51-44.67-45.69-44.67Z"/>
-      <path class="cls-1" d="M1020.76,88.26v11.55s-5.81-14.77-32.24-14.77c-32.84,0-53.24,22.66-53.24,59.15,0,20.59,6.58,36.8,18.19,47.04,9.03,7.96,21.09,12.04,35.45,12.32,9.99.19,16.46-2.53,20.5-5.1,7.76-4.94,10.64-9.63,10.64-9.63,0,0-.33,3.67-.93,8.64-.43,3.6-1.24,6.13-1.24,6.13h0c-3.61,12.85-14.17,20.28-29.57,20.28s-24.73-5.07-26.58-15.06l-23.05,6.88c3.98,19.2,22,30.66,48.2,30.66,17.81,0,31.77-4.84,41.5-14.4,9.81-9.64,14.79-23.53,14.79-41.29v-102.41h-22.42ZM1019.26,145.21c0,22.44-10.96,35.84-29.32,35.84-19.67,0-30.95-13.44-30.95-36.86s11.28-36.66,30.95-36.66c17.92,0,29.15,13.34,29.32,34.82v2.86Z"/>
-      <path class="cls-1" d="M1259.01,85.04c-2.6,0-5.13.17-7.59.49-17.88,2.79-23.14,11.9-23.14,11.9v-2.67h-.01s0-45.69,0-45.69h-23.71v151.39h23.71v-62.18c0-21.27,15.41-30.95,29.73-30.95,15.48,0,23,8.32,23,25.45v67.68h23.71v-70.94c0-27.01-17.94-44.47-45.69-44.47Z"/>
-      <circle class="cls-1" cx="1450.93" cy="64.47" r="15.37"/>
-      <path class="cls-1" d="M1439.14,88.2v56.94h0c-6.75-5.56-14.6-9.75-23.5-12.26v-7.23c0-25.42-16.7-40.6-44.67-40.6-22.76,0-39.78,10.67-46.69,29.27-.44,1.19-1.77,4.78-1.77,4.78l19.51,12.62,2.65-6.91c4.52-11.78,12.88-17.27,26.3-17.27s21.1,6.51,20.96,19.33c0,.08,0,1.15,0,2.86-10.04-.28-19.38.69-27.77,2.66,0,0,0,0,0,0-11.06,2.5-31.6,8.85-38.94,25.36-.05.11-1.13,2.96-1.13,2.96-1.06,3.28-1.59,6.84-1.59,10.7,0,10.39,5.77,21.64,16.3,27.95,6.32,3.78,14.57,5.21,23.68,5.21,5.88,0,11.6-.86,16.91-2.44,12.49-4.04,15.96-12.16,15.96-12.16v10.47h20.29v-34.27c-5.7-3.56-14.26-5.66-23.65-5.64,0,2.65,0,4.33,0,4.33,0,7.86-8.56,18.93-28.5,18.93-5.63,0-9.62-1.49-12.28-3.71-3.56-2.97-4.73-7.24-4.24-11.01.21-1.64,1.2-5.17,4.87-8.23l-.04-.11c8.42-6.89,24.97-9.64,40.17-9.04v.03c12.94.47,22.62,3.01,29.53,7.77,1.88,1.19,3.65,2.52,5.28,3.98,6.94,6.23,9.73,13.9,10.93,18.38,1.95,7.31,1.43,18.57,1.43,18.57h23.59v-112.2h-23.59Z"/>
-    </g>
-    <path id="LangChain-symbol" class="cls-1" d="M393.52,75.2c9.66,9.66,9.66,25.38,0,35.04l-21.64,21.29-.22-1.22c-1.58-8.75-5.74-16.69-12.02-22.97-4.73-4.72-10.32-8.21-16.62-10.37-3.91,3.93-6.06,9.08-6.06,14.5,0,1.1.1,2.24.3,3.38,3.47,1.25,6.54,3.18,9.12,5.76,9.66,9.66,9.66,25.38,0,35.04l-18.84,18.84c-4.83,4.83-11.17,7.24-17.52,7.24s-12.69-2.41-17.52-7.24c-9.66-9.66-9.66-25.38,0-35.04l21.64-21.28.22,1.22c1.57,8.73,5.73,16.67,12.03,22.96,4.74,4.74,9.99,7.89,16.28,10.04l1.16-1.16c3.52-3.52,5.45-8.2,5.45-13.19,0-1.11-.1-2.22-.29-3.31-3.63-1.2-6.62-2.91-9.34-5.63-3.92-3.92-6.36-8.93-7.04-14.48-.05-.4-.08-.79-.12-1.19-.54-7.23,2.07-14.29,7.16-19.37l18.84-18.84c4.67-4.67,10.89-7.25,17.52-7.25s12.85,2.57,17.52,7.25ZM491.9,125c0,68.93-56.08,125-125,125H125C56.08,250,0,193.93,0,125S56.08,0,125,0h241.9c68.93,0,125,56.08,125,125ZM240.9,187.69c1.97-2.39-7.13-9.12-8.99-11.59-3.78-4.1-3.8-10-6.35-14.79-6.24-14.46-13.41-28.81-23.44-41.05-10.6-13.39-23.68-24.47-35.17-37.04-8.53-8.77-10.81-21.26-18.34-30.69-10.38-15.33-43.2-19.51-48.01,2.14.02.68-.19,1.11-.78,1.54-2.66,1.93-5.03,4.14-7.02,6.81-4.87,6.78-5.62,18.28.46,24.37.2-3.21.31-6.24,2.85-8.54,4.7,4.03,11.8,5.46,17.25,2.45,12.04,17.19,9.04,40.97,18.6,59.49,2.64,4.38,5.3,8.85,8.69,12.69,2.75,4.28,12.25,9.33,12.81,13.29.1,6.8-.7,14.23,3.76,19.92,2.1,4.26-3.06,8.54-7.22,8.01-5.4.74-11.99-3.63-16.72-.94-1.67,1.81-4.94-.19-6.38,2.32-.5,1.3-3.2,3.13-1.59,4.38,1.79-1.36,3.45-2.78,5.86-1.97-.36,1.96,1.19,2.24,2.42,2.81-.04,1.33-.82,2.69.2,3.82,1.19-1.2,1.9-2.9,3.79-3.4,6.28,8.37,12.67-8.47,26.26-.89-2.76-.14-5.21.21-7.07,2.48-.46.51-.85,1.11-.04,1.77,7.33-4.73,7.29,1.62,12.05-.33,3.66-1.91,7.3-4.3,11.65-3.62-4.23,1.22-4.4,4.62-6.88,7.49-.42.44-.62.94-.13,1.67,8.78-.74,9.5-3.66,16.59-7.24,5.29-3.23,10.56,4.6,15.14.14,1.01-.97,2.39-.64,3.64-.77-1.6-8.53-19.19,1.56-18.91-9.88,5.66-3.85,4.36-11.22,4.74-17.17,6.51,3.61,13.75,5.71,20.13,9.16,3.22,5.2,8.27,12.07,15,11.62.18-.52.34-.98.53-1.51,2.04.35,4.66,1.7,5.78-.88,3.05,3.19,7.53,3.03,11.52,2.21,2.95-2.4-5.55-5.82-6.69-8.29ZM419.51,92.72c0-11.64-4.52-22.57-12.73-30.78-8.21-8.21-19.14-12.73-30.79-12.73s-22.58,4.52-30.79,12.73l-18.84,18.84c-4.4,4.4-7.74,9.57-9.93,15.36l-.13.33-.34.1c-6.84,2.11-12.87,5.73-17.92,10.78l-18.84,18.84c-16.97,16.98-16.97,44.6,0,61.57,8.21,8.21,19.14,12.73,30.78,12.73h0c11.64,0,22.58-4.52,30.79-12.73l18.84-18.84c4.38-4.38,7.7-9.53,9.89-15.31l.13-.33.34-.11c6.72-2.06,12.92-5.8,17.95-10.82l18.84-18.84c8.21-8.21,12.73-19.14,12.73-30.79ZM172.38,173.6c-1.62,6.32-2.15,17.09-10.37,17.4-.68,3.65,2.53,5.02,5.44,3.85,2.89-1.33,4.26,1.05,5.23,3.42,4.46.65,11.06-1.49,11.31-6.77-6.66-3.84-8.72-11.14-11.62-17.9Z"/>
-  </g>
-</svg>

.github/images/logo-light.svg

@@ -1,25 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1584.81 250">
-  <defs>
-    <style>
-      .cls-1 {
-        fill: #fff;
-        stroke-width: 0px;
-      }
-    </style>
-  </defs>
-  <g id="LanChain-logo">
-    <g id="LangChain-logotype">
-      <polygon class="cls-1" points="596.33 49.07 596.33 200.67 700.76 200.67 700.76 177.78 620.04 177.78 620.04 49.07 596.33 49.07"/>
-      <path class="cls-1" d="M1126.83,49.07c-20.53,0-37.95,7.4-50.38,21.41-12.32,13.88-18.82,33.36-18.82,56.33,0,47.23,27.25,77.75,69.41,77.75,29.71,0,52.71-15.54,61.54-41.56l2.14-6.31-23.53-8.94-2.17,7.03c-5.26,17.01-18.75,26.38-37.99,26.38-27.48,0-44.55-20.82-44.55-54.34s17.23-54.34,44.97-54.34c19.23,0,30.31,7.54,35.95,24.44l2.46,7.37,22.91-10.75-2.1-5.9c-8.96-25.22-29.65-38.56-59.85-38.56Z"/>
-      <path class="cls-1" d="M756.43,85.05c-22.76,0-39.78,10.67-46.69,29.27-.44,1.19-1.77,4.78-1.77,4.78l19.51,12.62,2.65-6.91c4.52-11.78,12.88-17.27,26.3-17.27s21.1,6.51,20.96,19.33c0,.52-.04,2.09-.04,2.09,0,0-17.76,2.88-25.08,4.43-31.23,6.6-44.31,18.52-44.31,38.02,0,10.39,5.77,21.64,16.3,27.95,6.32,3.78,14.57,5.21,23.68,5.21,5.99,0,11.81-.89,17.2-2.53,12.25-4.07,15.67-12.07,15.67-12.07v10.46h20.29v-74.78c0-25.42-16.7-40.6-44.67-40.6ZM777.46,164.85c0,7.86-8.56,18.93-28.5,18.93-5.63,0-9.62-1.49-12.28-3.71-3.56-2.97-4.73-7.24-4.24-11.01.21-1.64,1.2-5.17,4.87-8.23,3.75-3.13,10.38-5.37,20.62-7.6,8.42-1.83,19.54-3.85,19.54-3.85v15.48Z"/>
-      <path class="cls-1" d="M876.11,85.04c-2.82,0-5.57.2-8.24.57-18.17,2.73-23.49,11.96-23.49,11.96l.02-9.31h-22.74s0,112.19,0,112.19h23.71v-62.18c0-21.13,15.41-30.75,29.73-30.75,15.48,0,23,8.32,23,25.45v67.48h23.71v-70.74c0-27.56-17.51-44.67-45.69-44.67Z"/>
-      <path class="cls-1" d="M1539.12,85.04c-2.82,0-5.57.2-8.24.57-18.17,2.73-23.49,11.96-23.49,11.96v-9.32h-22.72v112.2h23.71v-62.18c0-21.13,15.41-30.75,29.73-30.75,15.48,0,23,8.32,23,25.45v67.48h23.71v-70.74c0-27.56-17.51-44.67-45.69-44.67Z"/>
-      <path class="cls-1" d="M1020.76,88.26v11.55s-5.81-14.77-32.24-14.77c-32.84,0-53.24,22.66-53.24,59.15,0,20.59,6.58,36.8,18.19,47.04,9.03,7.96,21.09,12.04,35.45,12.32,9.99.19,16.46-2.53,20.5-5.1,7.76-4.94,10.64-9.63,10.64-9.63,0,0-.33,3.67-.93,8.64-.43,3.6-1.24,6.13-1.24,6.13h0c-3.61,12.85-14.17,20.28-29.57,20.28s-24.73-5.07-26.58-15.06l-23.05,6.88c3.98,19.2,22,30.66,48.2,30.66,17.81,0,31.77-4.84,41.5-14.4,9.81-9.64,14.79-23.53,14.79-41.29v-102.41h-22.42ZM1019.26,145.21c0,22.44-10.96,35.84-29.32,35.84-19.67,0-30.95-13.44-30.95-36.86s11.28-36.66,30.95-36.66c17.92,0,29.15,13.34,29.32,34.82v2.86Z"/>
-      <path class="cls-1" d="M1259.01,85.04c-2.6,0-5.13.17-7.59.49-17.88,2.79-23.14,11.9-23.14,11.9v-2.67h-.01s0-45.69,0-45.69h-23.71v151.39h23.71v-62.18c0-21.27,15.41-30.95,29.73-30.95,15.48,0,23,8.32,23,25.45v67.68h23.71v-70.94c0-27.01-17.94-44.47-45.69-44.47Z"/>
-      <circle class="cls-1" cx="1450.93" cy="64.47" r="15.37"/>
-      <path class="cls-1" d="M1439.14,88.2v56.94h0c-6.75-5.56-14.6-9.75-23.5-12.26v-7.23c0-25.42-16.7-40.6-44.67-40.6-22.76,0-39.78,10.67-46.69,29.27-.44,1.19-1.77,4.78-1.77,4.78l19.51,12.62,2.65-6.91c4.52-11.78,12.88-17.27,26.3-17.27s21.1,6.51,20.96,19.33c0,.08,0,1.15,0,2.86-10.04-.28-19.38.69-27.77,2.66,0,0,0,0,0,0-11.06,2.5-31.6,8.85-38.94,25.36-.05.11-1.13,2.96-1.13,2.96-1.06,3.28-1.59,6.84-1.59,10.7,0,10.39,5.77,21.64,16.3,27.95,6.32,3.78,14.57,5.21,23.68,5.21,5.88,0,11.6-.86,16.91-2.44,12.49-4.04,15.96-12.16,15.96-12.16v10.47h20.29v-34.27c-5.7-3.56-14.26-5.66-23.65-5.64,0,2.65,0,4.33,0,4.33,0,7.86-8.56,18.93-28.5,18.93-5.63,0-9.62-1.49-12.28-3.71-3.56-2.97-4.73-7.24-4.24-11.01.21-1.64,1.2-5.17,4.87-8.23l-.04-.11c8.42-6.89,24.97-9.64,40.17-9.04v.03c12.94.47,22.62,3.01,29.53,7.77,1.88,1.19,3.65,2.52,5.28,3.98,6.94,6.23,9.73,13.9,10.93,18.38,1.95,7.31,1.43,18.57,1.43,18.57h23.59v-112.2h-23.59Z"/>
-    </g>
-    <path id="LangChain-symbol" class="cls-1" d="M393.52,75.2c9.66,9.66,9.66,25.38,0,35.04l-21.64,21.29-.22-1.22c-1.58-8.75-5.74-16.69-12.02-22.97-4.73-4.72-10.32-8.21-16.62-10.37-3.91,3.93-6.06,9.08-6.06,14.5,0,1.1.1,2.24.3,3.38,3.47,1.25,6.54,3.18,9.12,5.76,9.66,9.66,9.66,25.38,0,35.04l-18.84,18.84c-4.83,4.83-11.17,7.24-17.52,7.24s-12.69-2.41-17.52-7.24c-9.66-9.66-9.66-25.38,0-35.04l21.64-21.28.22,1.22c1.57,8.73,5.73,16.67,12.03,22.96,4.74,4.74,9.99,7.89,16.28,10.04l1.16-1.16c3.52-3.52,5.45-8.2,5.45-13.19,0-1.11-.1-2.22-.29-3.31-3.63-1.2-6.62-2.91-9.34-5.63-3.92-3.92-6.36-8.93-7.04-14.48-.05-.4-.08-.79-.12-1.19-.54-7.23,2.07-14.29,7.16-19.37l18.84-18.84c4.67-4.67,10.89-7.25,17.52-7.25s12.85,2.57,17.52,7.25ZM491.9,125c0,68.93-56.08,125-125,125H125C56.08,250,0,193.93,0,125S56.08,0,125,0h241.9C435.82,0,491.9,56.08,491.9,125ZM240.9,187.69c1.97-2.39-7.13-9.12-8.99-11.59-3.78-4.1-3.8-10-6.35-14.79-6.24-14.46-13.41-28.81-23.44-41.05-10.6-13.39-23.68-24.47-35.17-37.04-8.53-8.77-10.81-21.26-18.34-30.69-10.38-15.33-43.2-19.51-48.01,2.14.02.68-.19,1.11-.78,1.54-2.66,1.93-5.03,4.14-7.02,6.81-4.87,6.78-5.62,18.28.46,24.37.2-3.21.31-6.24,2.85-8.54,4.7,4.03,11.8,5.46,17.25,2.45,12.04,17.19,9.04,40.97,18.6,59.49,2.64,4.38,5.3,8.85,8.69,12.69,2.75,4.28,12.25,9.33,12.81,13.29.1,6.8-.7,14.23,3.76,19.92,2.1,4.26-3.06,8.54-7.22,8.01-5.4.74-11.99-3.63-16.72-.94-1.67,1.81-4.94-.19-6.38,2.32-.5,1.3-3.2,3.13-1.59,4.38,1.79-1.36,3.45-2.78,5.86-1.97-.36,1.96,1.19,2.24,2.42,2.81-.04,1.33-.82,2.69.2,3.82,1.19-1.2,1.9-2.9,3.79-3.4,6.28,8.37,12.67-8.47,26.26-.89-2.76-.14-5.21.21-7.07,2.48-.46.51-.85,1.11-.04,1.77,7.33-4.73,7.29,1.62,12.05-.33,3.66-1.91,7.3-4.3,11.65-3.62-4.23,1.22-4.4,4.62-6.88,7.49-.42.44-.62.94-.13,1.67,8.78-.74,9.5-3.66,16.59-7.24,5.29-3.23,10.56,4.6,15.14.14,1.01-.97,2.39-.64,3.64-.77-1.6-8.53-19.19,1.56-18.91-9.88,5.66-3.85,4.36-11.22,4.74-17.17,6.51,3.61,13.75,5.71,20.13,9.16,3.22,5.2,8.27,12.07,15,11.62.18-.52.34-.98.53-1.51,2.04.35,4.66,1.7,5.78-.88,3.05,3.19,7.53,3.03,11.52,2.21,2.95-2.4-5.55-5.82-6.69-8.29ZM419.51,92.72c0-11.64-4.52-22.57-12.73-30.78-8.21-8.21-19.14-12.73-30.79-12.73s-22.58,4.52-30.79,12.73l-18.84,18.84c-4.4,4.4-7.74,9.57-9.93,15.36l-.13.33-.34.1c-6.84,2.11-12.87,5.73-17.92,10.78l-18.84,18.84c-16.97,16.98-16.97,44.6,0,61.57,8.21,8.21,19.14,12.73,30.78,12.73h0c11.64,0,22.58-4.52,30.79-12.73l18.84-18.84c4.38-4.38,7.7-9.53,9.89-15.31l.13-.33.34-.11c6.72-2.06,12.92-5.8,17.95-10.82l18.84-18.84c8.21-8.21,12.73-19.14,12.73-30.79ZM172.38,173.6c-1.62,6.32-2.15,17.09-10.37,17.4-.68,3.65,2.53,5.02,5.44,3.85,2.89-1.33,4.26,1.05,5.23,3.42,4.46.65,11.06-1.49,11.31-6.77-6.66-3.84-8.72-11.14-11.62-17.9Z"/>
-  </g>
-</svg>

.github/pr-file-labeler.yml

@@ -1,133 +0,0 @@
-# Label PRs (config)
-# Automatically applies labels based on changed files and branch patterns
-
-# Core packages
-core:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/core/**/*"
-
-langchain-classic:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/langchain/**/*"
-
-langchain:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/langchain_v1/**/*"
-
-cli:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/cli/**/*"
-
-standard-tests:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/standard-tests/**/*"
-
-model-profiles:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/model-profiles/**/*"
-
-text-splitters:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/text-splitters/**/*"
-
-# Partner integrations
-integration:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/partners/**/*"
-
-anthropic:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/partners/anthropic/**/*"
-
-chroma:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/partners/chroma/**/*"
-
-deepseek:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/partners/deepseek/**/*"
-
-exa:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/partners/exa/**/*"
-
-fireworks:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/partners/fireworks/**/*"
-
-groq:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/partners/groq/**/*"
-
-huggingface:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/partners/huggingface/**/*"
-
-mistralai:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/partners/mistralai/**/*"
-
-nomic:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/partners/nomic/**/*"
-
-ollama:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/partners/ollama/**/*"
-
-openai:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/partners/openai/**/*"
-
-perplexity:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/partners/perplexity/**/*"
-
-prompty:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/partners/prompty/**/*"
-
-qdrant:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/partners/qdrant/**/*"
-
-xai:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "libs/partners/xai/**/*"
-
-github_actions:
-  - changed-files:
-      - any-glob-to-any-file:
-          - ".github/workflows/**/*"
-          - ".github/actions/**/*"
-
-dependencies:
-  - changed-files:
-      - any-glob-to-any-file:
-          - "**/pyproject.toml"
-          - "uv.lock"
-          - "**/requirements*.txt"
-          - "**/poetry.lock"

.github/scripts/check_diff.py

@@ -1,340 +0,0 @@
-"""Analyze git diffs to determine which directories need to be tested.
-
-Intelligently determines which LangChain packages and directories need to be tested,
-linted, or built based on the changes. Handles dependency relationships between
-packages, maps file changes to appropriate CI job configurations, and outputs JSON
-configurations for GitHub Actions.
-
-- Maps changed files to affected package directories (libs/core, libs/partners/*, etc.)
-- Builds dependency graph to include dependent packages when core components change
-- Generates test matrix configurations with appropriate Python versions
-- Handles special cases for Pydantic version testing and performance benchmarks
-
-Used as part of the check_diffs workflow.
-"""
-
-import glob
-import json
-import os
-import sys
-from collections import defaultdict
-from pathlib import Path
-from typing import Dict, List, Set
-
-import tomllib
-from get_min_versions import get_min_version_from_toml
-from packaging.requirements import Requirement
-
-LANGCHAIN_DIRS = [
-    "libs/core",
-    "libs/text-splitters",
-    "libs/langchain",
-    "libs/langchain_v1",
-    "libs/model-profiles",
-]
-
-# When set to True, we are ignoring core dependents
-# in order to be able to get CI to pass for each individual
-# package that depends on core
-# e.g. if you touch core, we don't then add textsplitters/etc to CI
-IGNORE_CORE_DEPENDENTS = False
-
-# ignored partners are removed from dependents
-# but still run if directly edited
-IGNORED_PARTNERS = [
-    # remove huggingface from dependents because of CI instability
-    # specifically in huggingface jobs
-    # https://github.com/langchain-ai/langchain/issues/25558
-    "huggingface",
-    # prompty exhibiting issues with numpy for Python 3.13
-    # https://github.com/langchain-ai/langchain/actions/runs/12651104685/job/35251034969?pr=29065
-    "prompty",
-]
-
-
-def all_package_dirs() -> Set[str]:
-    return {
-        "/".join(path.split("/")[:-1]).lstrip("./")
-        for path in glob.glob("./libs/**/pyproject.toml", recursive=True)
-        if "libs/cli" not in path and "libs/standard-tests" not in path
-    }
-
-
-def dependents_graph() -> dict:
-    """Construct a mapping of package -> dependents
-
-    Done such that we can run tests on all dependents of a package when a change is made.
-    """
-    dependents = defaultdict(set)
-
-    for path in glob.glob("./libs/**/pyproject.toml", recursive=True):
-        if "template" in path:
-            continue
-
-        # load regular and test deps from pyproject.toml
-        with open(path, "rb") as f:
-            pyproject = tomllib.load(f)
-
-        pkg_dir = "libs" + "/".join(path.split("libs")[1].split("/")[:-1])
-        for dep in [
-            *pyproject["project"]["dependencies"],
-            *pyproject["dependency-groups"]["test"],
-        ]:
-            requirement = Requirement(dep)
-            package_name = requirement.name
-            if "langchain" in dep:
-                dependents[package_name].add(pkg_dir)
-                continue
-
-        # load extended deps from extended_testing_deps.txt
-        package_path = Path(path).parent
-        extended_requirement_path = package_path / "extended_testing_deps.txt"
-        if extended_requirement_path.exists():
-            with open(extended_requirement_path, "r") as f:
-                extended_deps = f.read().splitlines()
-                for depline in extended_deps:
-                    if depline.startswith("-e "):
-                        # editable dependency
-                        assert depline.startswith("-e ../partners/"), (
-                            "Extended test deps should only editable install partner packages"
-                        )
-                        partner = depline.split("partners/")[1]
-                        dep = f"langchain-{partner}"
-                    else:
-                        dep = depline.split("==")[0]
-
-                    if "langchain" in dep:
-                        dependents[dep].add(pkg_dir)
-
-    for k in dependents:
-        for partner in IGNORED_PARTNERS:
-            if f"libs/partners/{partner}" in dependents[k]:
-                dependents[k].remove(f"libs/partners/{partner}")
-    return dependents
-
-
-def add_dependents(dirs_to_eval: Set[str], dependents: dict) -> List[str]:
-    updated = set()
-    for dir_ in dirs_to_eval:
-        # handle core manually because it has so many dependents
-        if "core" in dir_:
-            updated.add(dir_)
-            continue
-        pkg = "langchain-" + dir_.split("/")[-1]
-        updated.update(dependents[pkg])
-        updated.add(dir_)
-    return list(updated)
-
-
-def _get_configs_for_single_dir(job: str, dir_: str) -> List[Dict[str, str]]:
-    if job == "test-pydantic":
-        return _get_pydantic_test_configs(dir_)
-
-    if job == "codspeed":
-        py_versions = ["3.13"]
-    elif dir_ == "libs/core":
-        py_versions = ["3.10", "3.11", "3.12", "3.13", "3.14"]
-    # custom logic for specific directories
-    elif dir_ in {"libs/partners/chroma"}:
-        py_versions = ["3.10", "3.13"]
-    else:
-        py_versions = ["3.10", "3.14"]
-
-    return [{"working-directory": dir_, "python-version": py_v} for py_v in py_versions]
-
-
-def _get_pydantic_test_configs(
-    dir_: str, *, python_version: str = "3.12"
-) -> List[Dict[str, str]]:
-    with open("./libs/core/uv.lock", "rb") as f:
-        core_uv_lock_data = tomllib.load(f)
-    for package in core_uv_lock_data["package"]:
-        if package["name"] == "pydantic":
-            core_max_pydantic_minor = package["version"].split(".")[1]
-            break
-
-    with open(f"./{dir_}/uv.lock", "rb") as f:
-        dir_uv_lock_data = tomllib.load(f)
-
-    for package in dir_uv_lock_data["package"]:
-        if package["name"] == "pydantic":
-            dir_max_pydantic_minor = package["version"].split(".")[1]
-            break
-
-    core_min_pydantic_version = get_min_version_from_toml(
-        "./libs/core/pyproject.toml", "release", python_version, include=["pydantic"]
-    )["pydantic"]
-    core_min_pydantic_minor = (
-        core_min_pydantic_version.split(".")[1]
-        if "." in core_min_pydantic_version
-        else "0"
-    )
-    dir_min_pydantic_version = get_min_version_from_toml(
-        f"./{dir_}/pyproject.toml", "release", python_version, include=["pydantic"]
-    ).get("pydantic", "0.0.0")
-    dir_min_pydantic_minor = (
-        dir_min_pydantic_version.split(".")[1]
-        if "." in dir_min_pydantic_version
-        else "0"
-    )
-
-    max_pydantic_minor = min(
-        int(dir_max_pydantic_minor),
-        int(core_max_pydantic_minor),
-    )
-    min_pydantic_minor = max(
-        int(dir_min_pydantic_minor),
-        int(core_min_pydantic_minor),
-    )
-
-    configs = [
-        {
-            "working-directory": dir_,
-            "pydantic-version": f"2.{v}.0",
-            "python-version": python_version,
-        }
-        for v in range(min_pydantic_minor, max_pydantic_minor + 1)
-    ]
-    return configs
-
-
-def _get_configs_for_multi_dirs(
-    job: str, dirs_to_run: Dict[str, Set[str]], dependents: dict
-) -> List[Dict[str, str]]:
-    if job == "lint":
-        dirs = add_dependents(
-            dirs_to_run["lint"] | dirs_to_run["test"] | dirs_to_run["extended-test"],
-            dependents,
-        )
-    elif job in ["test", "compile-integration-tests", "dependencies", "test-pydantic"]:
-        dirs = add_dependents(
-            dirs_to_run["test"] | dirs_to_run["extended-test"], dependents
-        )
-    elif job == "extended-tests":
-        dirs = list(dirs_to_run["extended-test"])
-    elif job == "codspeed":
-        dirs = list(dirs_to_run["codspeed"])
-    else:
-        raise ValueError(f"Unknown job: {job}")
-
-    return [
-        config for dir_ in dirs for config in _get_configs_for_single_dir(job, dir_)
-    ]
-
-
-if __name__ == "__main__":
-    files = sys.argv[1:]
-
-    dirs_to_run: Dict[str, set] = {
-        "lint": set(),
-        "test": set(),
-        "extended-test": set(),
-        "codspeed": set(),
-    }
-    docs_edited = False
-
-    if len(files) >= 300:
-        # max diff length is 300 files - there are likely files missing
-        dirs_to_run["lint"] = all_package_dirs()
-        dirs_to_run["test"] = all_package_dirs()
-        dirs_to_run["extended-test"] = set(LANGCHAIN_DIRS)
-
-    for file in files:
-        if any(
-            file.startswith(dir_)
-            for dir_ in (
-                ".github/workflows",
-                ".github/tools",
-                ".github/actions",
-                ".github/scripts/check_diff.py",
-            )
-        ):
-            # Infrastructure changes (workflows, actions, CI scripts) trigger tests on
-            # all core packages as a safety measure. This ensures that changes to CI/CD
-            # infrastructure don't inadvertently break package testing, even if the change
-            # appears unrelated (e.g., documentation build workflows). This is intentionally
-            # conservative to catch unexpected side effects from workflow modifications.
-            #
-            # Example: A PR modifying .github/workflows/api_doc_build.yml will trigger
-            # lint/test jobs for libs/core, libs/text-splitters, libs/langchain, and
-            # libs/langchain_v1, even though the workflow may only affect documentation.
-            dirs_to_run["extended-test"].update(LANGCHAIN_DIRS)
-
-        if file.startswith("libs/core"):
-            dirs_to_run["codspeed"].add("libs/core")
-        if any(file.startswith(dir_) for dir_ in LANGCHAIN_DIRS):
-            # add that dir and all dirs after in LANGCHAIN_DIRS
-            # for extended testing
-
-            found = False
-            for dir_ in LANGCHAIN_DIRS:
-                if dir_ == "libs/core" and IGNORE_CORE_DEPENDENTS:
-                    dirs_to_run["extended-test"].add(dir_)
-                    continue
-                if file.startswith(dir_):
-                    found = True
-                if found:
-                    dirs_to_run["extended-test"].add(dir_)
-        elif file.startswith("libs/standard-tests"):
-            # TODO: update to include all packages that rely on standard-tests (all partner packages)
-            # Note: won't run on external repo partners
-            dirs_to_run["lint"].add("libs/standard-tests")
-            dirs_to_run["test"].add("libs/standard-tests")
-            dirs_to_run["test"].add("libs/partners/mistralai")
-            dirs_to_run["test"].add("libs/partners/openai")
-            dirs_to_run["test"].add("libs/partners/anthropic")
-            dirs_to_run["test"].add("libs/partners/fireworks")
-            dirs_to_run["test"].add("libs/partners/groq")
-
-        elif file.startswith("libs/cli"):
-            dirs_to_run["lint"].add("libs/cli")
-            dirs_to_run["test"].add("libs/cli")
-
-        elif file.startswith("libs/partners"):
-            partner_dir = file.split("/")[2]
-            if os.path.isdir(f"libs/partners/{partner_dir}") and [
-                filename
-                for filename in os.listdir(f"libs/partners/{partner_dir}")
-                if not filename.startswith(".")
-            ] != ["README.md"]:
-                dirs_to_run["test"].add(f"libs/partners/{partner_dir}")
-                # Skip codspeed for partners without benchmarks or in IGNORED_PARTNERS
-                if partner_dir not in IGNORED_PARTNERS:
-                    dirs_to_run["codspeed"].add(f"libs/partners/{partner_dir}")
-            # Skip if the directory was deleted or is just a tombstone readme
-        elif file.startswith("libs/"):
-            # Check if this is a root-level file in libs/ (e.g., libs/README.md)
-            file_parts = file.split("/")
-            if len(file_parts) == 2:
-                # Root-level file in libs/, skip it (no tests needed)
-                continue
-            raise ValueError(
-                f"Unknown lib: {file}. check_diff.py likely needs "
-                "an update for this new library!"
-            )
-        elif file in [
-            "pyproject.toml",
-            "uv.lock",
-        ]:  # root uv files
-            docs_edited = True
-
-    dependents = dependents_graph()
-
-    # we now have dirs_by_job
-    # todo: clean this up
-    map_job_to_configs = {
-        job: _get_configs_for_multi_dirs(job, dirs_to_run, dependents)
-        for job in [
-            "lint",
-            "test",
-            "extended-tests",
-            "compile-integration-tests",
-            "dependencies",
-            "test-pydantic",
-            "codspeed",
-        ]
-    }
-
-    for key, value in map_job_to_configs.items():
-        json_output = json.dumps(value)
-        print(f"{key}={json_output}")

.github/scripts/check_prerelease_dependencies.py

@@ -1,36 +0,0 @@
-"""Check that no dependencies allow prereleases unless we're releasing a prerelease."""
-
-import sys
-
-import tomllib
-
-if __name__ == "__main__":
-    # Get the TOML file path from the command line argument
-    toml_file = sys.argv[1]
-
-    with open(toml_file, "rb") as file:
-        toml_data = tomllib.load(file)
-
-    # See if we're releasing an rc or dev version
-    version = toml_data["project"]["version"]
-    releasing_rc = "rc" in version or "dev" in version
-
-    # If not, iterate through dependencies and make sure none allow prereleases
-    if not releasing_rc:
-        dependencies = toml_data["project"]["dependencies"]
-        for dep_version in dependencies:
-            dep_version_string = (
-                dep_version["version"] if isinstance(dep_version, dict) else dep_version
-            )
-
-            if "rc" in dep_version_string:
-                raise ValueError(
-                    f"Dependency {dep_version} has a prerelease version. Please remove this."
-                )
-
-            if isinstance(dep_version, dict) and dep_version.get(
-                "allow-prereleases", False
-            ):
-                raise ValueError(
-                    f"Dependency {dep_version} has allow-prereleases set to true. Please remove this."
-                )

.github/scripts/get_min_versions.py

@@ -1,199 +0,0 @@
-"""Get minimum versions of dependencies from a pyproject.toml file."""
-
-import sys
-from collections import defaultdict
-
-if sys.version_info >= (3, 11):
-    import tomllib
-else:
-    # For Python 3.10 and below, which doesnt have stdlib tomllib
-    import tomli as tomllib
-
-import re
-from typing import List
-
-import requests
-from packaging.requirements import Requirement
-from packaging.specifiers import SpecifierSet
-from packaging.version import Version, parse
-
-MIN_VERSION_LIBS = [
-    "langchain-core",
-    "langchain",
-    "langchain-text-splitters",
-    "numpy",
-    "SQLAlchemy",
-]
-
-# some libs only get checked on release because of simultaneous changes in
-# multiple libs
-SKIP_IF_PULL_REQUEST = [
-    "langchain-core",
-    "langchain-text-splitters",
-    "langchain",
-]
-
-
-def get_pypi_versions(package_name: str) -> List[str]:
-    """Fetch all available versions for a package from PyPI.
-
-    Args:
-        package_name: Name of the package
-
-    Returns:
-        List of all available versions
-
-    Raises:
-        requests.exceptions.RequestException: If PyPI API request fails
-        KeyError: If package not found or response format unexpected
-    """
-    pypi_url = f"https://pypi.org/pypi/{package_name}/json"
-    response = requests.get(pypi_url)
-    response.raise_for_status()
-    return list(response.json()["releases"].keys())
-
-
-def get_minimum_version(package_name: str, spec_string: str) -> str | None:
-    """Find the minimum published version that satisfies the given constraints.
-
-    Args:
-        package_name: Name of the package
-        spec_string: Version specification string (e.g., ">=0.2.43,<0.4.0,!=0.3.0")
-
-    Returns:
-        Minimum compatible version or None if no compatible version found
-    """
-    # Rewrite occurrences of ^0.0.z to 0.0.z (can be anywhere in constraint string)
-    spec_string = re.sub(r"\^0\.0\.(\d+)", r"0.0.\1", spec_string)
-    # Rewrite occurrences of ^0.y.z to >=0.y.z,<0.y+1 (can be anywhere in constraint string)
-    for y in range(1, 10):
-        spec_string = re.sub(
-            rf"\^0\.{y}\.(\d+)", rf">=0.{y}.\1,<0.{y + 1}", spec_string
-        )
-    # Rewrite occurrences of ^x.y.z to >=x.y.z,<x+1.0.0 (can be anywhere in constraint string)
-    for x in range(1, 10):
-        spec_string = re.sub(
-            rf"\^{x}\.(\d+)\.(\d+)", rf">={x}.\1.\2,<{x + 1}", spec_string
-        )
-
-    spec_set = SpecifierSet(spec_string)
-    all_versions = get_pypi_versions(package_name)
-
-    valid_versions = []
-    for version_str in all_versions:
-        try:
-            version = parse(version_str)
-            if spec_set.contains(version):
-                valid_versions.append(version)
-        except ValueError:
-            continue
-
-    return str(min(valid_versions)) if valid_versions else None
-
-
-def _check_python_version_from_requirement(
-    requirement: Requirement, python_version: str
-) -> bool:
-    if not requirement.marker:
-        return True
-    else:
-        marker_str = str(requirement.marker)
-        if "python_version" in marker_str or "python_full_version" in marker_str:
-            python_version_str = "".join(
-                char
-                for char in marker_str
-                if char.isdigit() or char in (".", "<", ">", "=", ",")
-            )
-            return check_python_version(python_version, python_version_str)
-        return True
-
-
-def get_min_version_from_toml(
-    toml_path: str,
-    versions_for: str,
-    python_version: str,
-    *,
-    include: list | None = None,
-):
-    # Parse the TOML file
-    with open(toml_path, "rb") as file:
-        toml_data = tomllib.load(file)
-
-    dependencies = defaultdict(list)
-    for dep in toml_data["project"]["dependencies"]:
-        requirement = Requirement(dep)
-        dependencies[requirement.name].append(requirement)
-
-    # Initialize a dictionary to store the minimum versions
-    min_versions = {}
-
-    # Iterate over the libs in MIN_VERSION_LIBS
-    for lib in set(MIN_VERSION_LIBS + (include or [])):
-        if versions_for == "pull_request" and lib in SKIP_IF_PULL_REQUEST:
-            # some libs only get checked on release because of simultaneous
-            # changes in multiple libs
-            continue
-        # Check if the lib is present in the dependencies
-        if lib in dependencies:
-            if include and lib not in include:
-                continue
-            requirements = dependencies[lib]
-            for requirement in requirements:
-                if _check_python_version_from_requirement(requirement, python_version):
-                    version_string = str(requirement.specifier)
-                    break
-
-            # Use parse_version to get the minimum supported version from version_string
-            min_version = get_minimum_version(lib, version_string)
-
-            # Store the minimum version in the min_versions dictionary
-            min_versions[lib] = min_version
-
-    return min_versions
-
-
-def check_python_version(version_string, constraint_string):
-    """Check if the given Python version matches the given constraints.
-
-    Args:
-        version_string: A string representing the Python version (e.g. "3.8.5").
-        constraint_string: A string representing the package's Python version
-            constraints (e.g. ">=3.6, <4.0").
-
-    Returns:
-        True if the version matches the constraints
-    """
-
-    # Rewrite occurrences of ^0.0.z to 0.0.z (can be anywhere in constraint string)
-    constraint_string = re.sub(r"\^0\.0\.(\d+)", r"0.0.\1", constraint_string)
-    # Rewrite occurrences of ^0.y.z to >=0.y.z,<0.y+1.0 (can be anywhere in constraint string)
-    for y in range(1, 10):
-        constraint_string = re.sub(
-            rf"\^0\.{y}\.(\d+)", rf">=0.{y}.\1,<0.{y + 1}.0", constraint_string
-        )
-    # Rewrite occurrences of ^x.y.z to >=x.y.z,<x+1.0.0 (can be anywhere in constraint string)
-    for x in range(1, 10):
-        constraint_string = re.sub(
-            rf"\^{x}\.0\.(\d+)", rf">={x}.0.\1,<{x + 1}.0.0", constraint_string
-        )
-
-    try:
-        version = Version(version_string)
-        constraints = SpecifierSet(constraint_string)
-        return version in constraints
-    except Exception as e:
-        print(f"Error: {e}")
-        return False
-
-
-if __name__ == "__main__":
-    # Get the TOML file path from the command line argument
-    toml_file = sys.argv[1]
-    versions_for = sys.argv[2]
-    python_version = sys.argv[3]
-    assert versions_for in ["release", "pull_request"]
-
-    # Call the function to get the minimum versions
-    min_versions = get_min_version_from_toml(toml_file, versions_for, python_version)
-
-    print(" ".join([f"{lib}=={version}" for lib, version in min_versions.items()]))

.github/tools/git-restore-mtime

@@ -1,756 +0,0 @@
-#!/usr/bin/env python3
-#
-# git-restore-mtime - Change mtime of files based on commit date of last change
-#
-#    Copyright (C) 2012 Rodrigo Silva (MestreLion) <linux@rodrigosilva.com>
-#
-#    This program is free software: you can redistribute it and/or modify
-#    it under the terms of the GNU General Public License as published by
-#    the Free Software Foundation, either version 3 of the License, or
-#    (at your option) any later version.
-#
-#    This program is distributed in the hope that it will be useful,
-#    but WITHOUT ANY WARRANTY; without even the implied warranty of
-#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-#    GNU General Public License for more details.
-#
-#    You should have received a copy of the GNU General Public License
-#    along with this program. See <http://www.gnu.org/licenses/gpl.html>
-#
-# Source: https://github.com/MestreLion/git-tools
-# Version: July 13, 2023 (commit hash 5f832e72453e035fccae9d63a5056918d64476a2)
-"""
-Change the modification time (mtime) of files in work tree, based on the
-date of the most recent commit that modified the file, including renames.
-
-Ignores untracked files and uncommitted deletions, additions and renames, and
-by default modifications too.
----
-Useful prior to generating release tarballs, so each file is archived with a
-date that is similar to the date when the file was actually last modified,
-assuming the actual modification date and its commit date are close.
-"""
-
-# TODO:
-# - Add -z on git whatchanged/ls-files, so we don't deal with filename decoding
-# - When Python is bumped to 3.7, use text instead of universal_newlines on subprocess
-# - Update "Statistics for some large projects" with modern hardware and repositories.
-# - Create a README.md for git-restore-mtime alone. It deserves extensive documentation
-#   - Move Statistics there
-# - See git-extras as a good example on project structure and documentation
-
-# FIXME:
-# - When current dir is outside the worktree, e.g. using --work-tree, `git ls-files`
-#   assume any relative pathspecs are to worktree root, not the current dir. As such,
-#   relative pathspecs may not work.
-# - Renames are tricky:
-#   - R100 should not change mtime, but original name is not on filelist. Should
-#     track renames until a valid (A, M) mtime found and then set on current name.
-#   - Should set mtime for both current and original directories.
-#   - Check mode changes with unchanged blobs?
-# - Check file (A, D) for the directory mtime is not sufficient:
-#   - Renames also change dir mtime, unless rename was on a parent dir
-#   - If most recent change of all files in a dir was a Modification (M),
-#     dir might not be touched at all.
-#   - Dirs containing only subdirectories but no direct files will also
-#     not be touched. They're files' [grand]parent dir, but never their dirname().
-#   - Some solutions:
-#     - After files done, perform some dir processing for missing dirs, finding latest
-#       file (A, D, R)
-#     - Simple approach: dir mtime is the most recent child (dir or file) mtime
-#     - Use a virtual concept of "created at most at" to fill missing info, bubble up
-#       to parents and grandparents
-#   - When handling [grand]parent dirs, stay inside <pathspec>
-# - Better handling of merge commits. `-m` is plain *wrong*. `-c/--cc` is perfect, but
-#   painfully slow. First pass without merge commits is not accurate. Maybe add a new
-#   `--accurate` mode for `--cc`?
-
-if __name__ != "__main__":
-    raise ImportError("{} should not be used as a module.".format(__name__))
-
-import argparse
-import datetime
-import logging
-import os.path
-import shlex
-import signal
-import subprocess
-import sys
-import time
-
-__version__ = "2022.12+dev"
-
-# Update symlinks only if the platform supports not following them
-UPDATE_SYMLINKS = bool(os.utime in getattr(os, "supports_follow_symlinks", []))
-
-# Call os.path.normpath() only if not in a POSIX platform (Windows)
-NORMALIZE_PATHS = os.path.sep != "/"
-
-# How many files to process in each batch when re-trying merge commits
-STEPMISSING = 100
-
-# (Extra) keywords for the os.utime() call performed by touch()
-UTIME_KWS = {} if not UPDATE_SYMLINKS else {"follow_symlinks": False}
-
-
-# Command-line interface ######################################################
-
-
-def parse_args():
-    parser = argparse.ArgumentParser(description=__doc__.split("\n---")[0])
-
-    group = parser.add_mutually_exclusive_group()
-    group.add_argument(
-        "--quiet",
-        "-q",
-        dest="loglevel",
-        action="store_const",
-        const=logging.WARNING,
-        default=logging.INFO,
-        help="Suppress informative messages and summary statistics.",
-    )
-    group.add_argument(
-        "--verbose",
-        "-v",
-        action="count",
-        help="""
-        Print additional information for each processed file.
-        Specify twice to further increase verbosity.
-        """,
-    )
-
-    parser.add_argument(
-        "--cwd",
-        "-C",
-        metavar="DIRECTORY",
-        help="""
-        Run as if %(prog)s was started in directory %(metavar)s.
-        This affects how --work-tree, --git-dir and PATHSPEC arguments are handled.
-        See 'man 1 git' or 'git --help' for more information.
-        """,
-    )
-
-    parser.add_argument(
-        "--git-dir",
-        dest="gitdir",
-        metavar="GITDIR",
-        help="""
-        Path to the git repository, by default auto-discovered by searching
-        the current directory and its parents for a .git/ subdirectory.
-        """,
-    )
-
-    parser.add_argument(
-        "--work-tree",
-        dest="workdir",
-        metavar="WORKTREE",
-        help="""
-        Path to the work tree root, by default the parent of GITDIR if it's
-        automatically discovered, or the current directory if GITDIR is set.
-        """,
-    )
-
-    parser.add_argument(
-        "--force",
-        "-f",
-        default=False,
-        action="store_true",
-        help="""
-        Force updating files with uncommitted modifications.
-        Untracked files and uncommitted deletions, renames and additions are
-        always ignored.
-        """,
-    )
-
-    parser.add_argument(
-        "--merge",
-        "-m",
-        default=False,
-        action="store_true",
-        help="""
-        Include merge commits.
-        Leads to more recent times and more files per commit, thus with the same
-        time, which may or may not be what you want.
-        Including merge commits may lead to fewer commits being evaluated as files
-        are found sooner, which can improve performance, sometimes substantially.
-        But as merge commits are usually huge, processing them may also take longer.
-        By default, merge commits are only used for files missing from regular commits.
-        """,
-    )
-
-    parser.add_argument(
-        "--first-parent",
-        default=False,
-        action="store_true",
-        help="""
-        Consider only the first parent, the "main branch", when evaluating merge commits.
-        Only effective when merge commits are processed, either when --merge is
-        used or when finding missing files after the first regular log search.
-        See --skip-missing.
-        """,
-    )
-
-    parser.add_argument(
-        "--skip-missing",
-        "-s",
-        dest="missing",
-        default=True,
-        action="store_false",
-        help="""
-        Do not try to find missing files.
-        If merge commits were not evaluated with --merge and some files were
-        not found in regular commits, by default %(prog)s searches for these
-        files again in the merge commits.
-        This option disables this retry, so files found only in merge commits
-        will not have their timestamp updated.
-        """,
-    )
-
-    parser.add_argument(
-        "--no-directories",
-        "-D",
-        dest="dirs",
-        default=True,
-        action="store_false",
-        help="""
-        Do not update directory timestamps.
-        By default, use the time of its most recently created, renamed or deleted file.
-        Note that just modifying a file will NOT update its directory time.
-        """,
-    )
-
-    parser.add_argument(
-        "--test",
-        "-t",
-        default=False,
-        action="store_true",
-        help="Test run: do not actually update any file timestamp.",
-    )
-
-    parser.add_argument(
-        "--commit-time",
-        "-c",
-        dest="commit_time",
-        default=False,
-        action="store_true",
-        help="Use commit time instead of author time.",
-    )
-
-    parser.add_argument(
-        "--oldest-time",
-        "-o",
-        dest="reverse_order",
-        default=False,
-        action="store_true",
-        help="""
-        Update times based on the oldest, instead of the most recent commit of a file.
-        This reverses the order in which the git log is processed to emulate a
-        file "creation" date. Note this will be inaccurate for files deleted and
-        re-created at later dates.
-        """,
-    )
-
-    parser.add_argument(
-        "--skip-older-than",
-        metavar="SECONDS",
-        type=int,
-        help="""
-        Ignore files that are currently older than %(metavar)s.
-        Useful in workflows that assume such files already have a correct timestamp,
-        as it may improve performance by processing fewer files.
-        """,
-    )
-
-    parser.add_argument(
-        "--skip-older-than-commit",
-        "-N",
-        default=False,
-        action="store_true",
-        help="""
-        Ignore files older than the timestamp it would be updated to.
-        Such files may be considered "original", likely in the author's repository.
-        """,
-    )
-
-    parser.add_argument(
-        "--unique-times",
-        default=False,
-        action="store_true",
-        help="""
-        Set the microseconds to a unique value per commit.
-        Allows telling apart changes that would otherwise have identical timestamps,
-        as git's time accuracy is in seconds.
-        """,
-    )
-
-    parser.add_argument(
-        "pathspec",
-        nargs="*",
-        metavar="PATHSPEC",
-        help="""
-        Only modify paths matching %(metavar)s, relative to current directory.
-        By default, update all but untracked files and submodules.
-        """,
-    )
-
-    parser.add_argument(
-        "--version",
-        "-V",
-        action="version",
-        version="%(prog)s version {version}".format(version=get_version()),
-    )
-
-    args_ = parser.parse_args()
-    if args_.verbose:
-        args_.loglevel = max(logging.TRACE, logging.DEBUG // args_.verbose)
-    args_.debug = args_.loglevel <= logging.DEBUG
-    return args_
-
-
-def get_version(version=__version__):
-    if not version.endswith("+dev"):
-        return version
-    try:
-        cwd = os.path.dirname(os.path.realpath(__file__))
-        return Git(cwd=cwd, errors=False).describe().lstrip("v")
-    except Git.Error:
-        return "-".join((version, "unknown"))
-
-
-# Helper functions ############################################################
-
-
-def setup_logging():
-    """Add TRACE logging level and corresponding method, return the root logger"""
-    logging.TRACE = TRACE = logging.DEBUG // 2
-    logging.Logger.trace = lambda _, m, *a, **k: _.log(TRACE, m, *a, **k)
-    return logging.getLogger()
-
-
-def normalize(path):
-    r"""Normalize paths from git, handling non-ASCII characters.
-
-    Git stores paths as UTF-8 normalization form C.
-    If path contains non-ASCII or non-printable characters, git outputs the UTF-8
-    in octal-escaped notation, escaping double-quotes and backslashes, and then
-    double-quoting the whole path.
-    https://git-scm.com/docs/git-config#Documentation/git-config.txt-corequotePath
-
-    This function reverts this encoding, so:
-    normalize(r'"Back\\slash_double\"quote_a\303\247a\303\255"') =>
-        r'Back\slash_double"quote_açaí')
-
-    Paths with invalid UTF-8 encoding, such as single 0x80-0xFF bytes (e.g, from
-    Latin1/Windows-1251 encoding) are decoded using surrogate escape, the same
-    method used by Python for filesystem paths. So 0xE6 ("æ" in Latin1, r'\\346'
-    from Git) is decoded as "\udce6". See https://peps.python.org/pep-0383/ and
-    https://vstinner.github.io/painful-history-python-filesystem-encoding.html
-
-    Also see notes on `windows/non-ascii-paths.txt` about path encodings on
-    non-UTF-8 platforms and filesystems.
-    """
-    if path and path[0] == '"':
-        # Python 2: path = path[1:-1].decode("string-escape")
-        # Python 3: https://stackoverflow.com/a/46650050/624066
-        path = (
-            path[1:-1]  # Remove enclosing double quotes
-            .encode("latin1")  # Convert to bytes, required by 'unicode-escape'
-            .decode("unicode-escape")  # Perform the actual octal-escaping decode
-            .encode("latin1")  # 1:1 mapping to bytes, UTF-8 encoded
-            .decode("utf8", "surrogateescape")
-        )  # Decode from UTF-8
-    if NORMALIZE_PATHS:
-        # Make sure the slash matches the OS; for Windows we need a backslash
-        path = os.path.normpath(path)
-    return path
-
-
-def dummy(*_args, **_kwargs):
-    """No-op function used in dry-run tests"""
-
-
-def touch(path, mtime):
-    """The actual mtime update"""
-    os.utime(path, (mtime, mtime), **UTIME_KWS)
-
-
-def touch_ns(path, mtime_ns):
-    """The actual mtime update, using nanoseconds for unique timestamps"""
-    os.utime(path, None, ns=(mtime_ns, mtime_ns), **UTIME_KWS)
-
-
-def isodate(secs: int):
-    # time.localtime() accepts floats, but discards fractional part
-    return time.strftime("%Y-%m-%d %H:%M:%S", time.localtime(secs))
-
-
-def isodate_ns(ns: int):
-    # for integers fromtimestamp() is equivalent and ~16% slower than isodate()
-    return datetime.datetime.fromtimestamp(ns / 1000000000).isoformat(sep=" ")
-
-
-def get_mtime_ns(secs: int, idx: int):
-    # Time resolution for filesystems and functions:
-    # ext-4 and other POSIX filesystems: 1 nanosecond
-    # NTFS (Windows default): 100 nanoseconds
-    # datetime.datetime() (due to 64-bit float epoch): 1 microsecond
-    us = idx % 1000000  # 10**6
-    return 1000 * (1000000 * secs + us)
-
-
-def get_mtime_path(path):
-    return os.path.getmtime(path)
-
-
-# Git class and parse_log(), the heart of the script ##########################
-
-
-class Git:
-    def __init__(self, workdir=None, gitdir=None, cwd=None, errors=True):
-        self.gitcmd = ["git"]
-        self.errors = errors
-        self._proc = None
-        if workdir:
-            self.gitcmd.extend(("--work-tree", workdir))
-        if gitdir:
-            self.gitcmd.extend(("--git-dir", gitdir))
-        if cwd:
-            self.gitcmd.extend(("-C", cwd))
-        self.workdir, self.gitdir = self._get_repo_dirs()
-
-    def ls_files(self, paths: list = None):
-        return (normalize(_) for _ in self._run("ls-files --full-name", paths))
-
-    def ls_dirty(self, force=False):
-        return (
-            normalize(_[3:].split(" -> ", 1)[-1])
-            for _ in self._run("status --porcelain")
-            if _[:2] != "??" and (not force or (_[0] in ("R", "A") or _[1] == "D"))
-        )
-
-    def log(
-        self,
-        merge=False,
-        first_parent=False,
-        commit_time=False,
-        reverse_order=False,
-        paths: list = None,
-    ):
-        cmd = "whatchanged --pretty={}".format("%ct" if commit_time else "%at")
-        if merge:
-            cmd += " -m"
-        if first_parent:
-            cmd += " --first-parent"
-        if reverse_order:
-            cmd += " --reverse"
-        return self._run(cmd, paths)
-
-    def describe(self):
-        return self._run("describe --tags", check=True)[0]
-
-    def terminate(self):
-        if self._proc is None:
-            return
-        try:
-            self._proc.terminate()
-        except OSError:
-            # Avoid errors on OpenBSD
-            pass
-
-    def _get_repo_dirs(self):
-        return (
-            os.path.normpath(_)
-            for _ in self._run(
-                "rev-parse --show-toplevel --absolute-git-dir", check=True
-            )
-        )
-
-    def _run(self, cmdstr: str, paths: list = None, output=True, check=False):
-        cmdlist = self.gitcmd + shlex.split(cmdstr)
-        if paths:
-            cmdlist.append("--")
-            cmdlist.extend(paths)
-        popen_args = dict(universal_newlines=True, encoding="utf8")
-        if not self.errors:
-            popen_args["stderr"] = subprocess.DEVNULL
-        log.trace("Executing: %s", " ".join(cmdlist))
-        if not output:
-            return subprocess.call(cmdlist, **popen_args)
-        if check:
-            try:
-                stdout: str = subprocess.check_output(cmdlist, **popen_args)
-                return stdout.splitlines()
-            except subprocess.CalledProcessError as e:
-                raise self.Error(e.returncode, e.cmd, e.output, e.stderr)
-        self._proc = subprocess.Popen(cmdlist, stdout=subprocess.PIPE, **popen_args)
-        return (_.rstrip() for _ in self._proc.stdout)
-
-    def __del__(self):
-        self.terminate()
-
-    class Error(subprocess.CalledProcessError):
-        """Error from git executable"""
-
-
-def parse_log(filelist, dirlist, stats, git, merge=False, filterlist=None):
-    mtime = 0
-    datestr = isodate(0)
-    for line in git.log(
-        merge, args.first_parent, args.commit_time, args.reverse_order, filterlist
-    ):
-        stats["loglines"] += 1
-
-        # Blank line between Date and list of files
-        if not line:
-            continue
-
-        # Date line
-        if line[0] != ":":  # Faster than `not line.startswith(':')`
-            stats["commits"] += 1
-            mtime = int(line)
-            if args.unique_times:
-                mtime = get_mtime_ns(mtime, stats["commits"])
-            if args.debug:
-                datestr = isodate(mtime)
-            continue
-
-        # File line: three tokens if it describes a renaming, otherwise two
-        tokens = line.split("\t")
-
-        # Possible statuses:
-        # M: Modified (content changed)
-        # A: Added (created)
-        # D: Deleted
-        # T: Type changed: to/from regular file, symlinks, submodules
-        # R099: Renamed (moved), with % of unchanged content. 100 = pure rename
-        # Not possible in log: C=Copied, U=Unmerged, X=Unknown, B=pairing Broken
-        status = tokens[0].split(" ")[-1]
-        file = tokens[-1]
-
-        # Handles non-ASCII chars and OS path separator
-        file = normalize(file)
-
-        def do_file():
-            if args.skip_older_than_commit and get_mtime_path(file) <= mtime:
-                stats["skip"] += 1
-                return
-            if args.debug:
-                log.debug(
-                    "%d\t%d\t%d\t%s\t%s",
-                    stats["loglines"],
-                    stats["commits"],
-                    stats["files"],
-                    datestr,
-                    file,
-                )
-            try:
-                touch(os.path.join(git.workdir, file), mtime)
-                stats["touches"] += 1
-            except Exception as e:
-                log.error("ERROR: %s: %s", e, file)
-                stats["errors"] += 1
-
-        def do_dir():
-            if args.debug:
-                log.debug(
-                    "%d\t%d\t-\t%s\t%s",
-                    stats["loglines"],
-                    stats["commits"],
-                    datestr,
-                    "{}/".format(dirname or "."),
-                )
-            try:
-                touch(os.path.join(git.workdir, dirname), mtime)
-                stats["dirtouches"] += 1
-            except Exception as e:
-                log.error("ERROR: %s: %s", e, dirname)
-                stats["direrrors"] += 1
-
-        if file in filelist:
-            stats["files"] -= 1
-            filelist.remove(file)
-            do_file()
-
-        if args.dirs and status in ("A", "D"):
-            dirname = os.path.dirname(file)
-            if dirname in dirlist:
-                dirlist.remove(dirname)
-                do_dir()
-
-        # All files done?
-        if not stats["files"]:
-            git.terminate()
-            return
-
-
-# Main Logic ##################################################################
-
-
-def main():
-    start = time.time()  # yes, Wall time. CPU time is not realistic for users.
-    stats = {
-        _: 0
-        for _ in (
-            "loglines",
-            "commits",
-            "touches",
-            "skip",
-            "errors",
-            "dirtouches",
-            "direrrors",
-        )
-    }
-
-    logging.basicConfig(level=args.loglevel, format="%(message)s")
-    log.trace("Arguments: %s", args)
-
-    # First things first: Where and Who are we?
-    if args.cwd:
-        log.debug("Changing directory: %s", args.cwd)
-        try:
-            os.chdir(args.cwd)
-        except OSError as e:
-            log.critical(e)
-            return e.errno
-    # Using both os.chdir() and `git -C` is redundant, but might prevent side effects
-    # `git -C` alone could be enough if we make sure that:
-    # - all paths, including args.pathspec, are processed by git: ls-files, rev-parse
-    # - touch() / os.utime() path argument is always prepended with git.workdir
-    try:
-        git = Git(workdir=args.workdir, gitdir=args.gitdir, cwd=args.cwd)
-    except Git.Error as e:
-        # Not in a git repository, and git already informed user on stderr. So we just...
-        return e.returncode
-
-    # Get the files managed by git and build file list to be processed
-    if UPDATE_SYMLINKS and not args.skip_older_than:
-        filelist = set(git.ls_files(args.pathspec))
-    else:
-        filelist = set()
-        for path in git.ls_files(args.pathspec):
-            fullpath = os.path.join(git.workdir, path)
-
-            # Symlink (to file, to dir or broken - git handles the same way)
-            if not UPDATE_SYMLINKS and os.path.islink(fullpath):
-                log.warning(
-                    "WARNING: Skipping symlink, no OS support for updates: %s", path
-                )
-                continue
-
-            # skip files which are older than given threshold
-            if (
-                args.skip_older_than
-                and start - get_mtime_path(fullpath) > args.skip_older_than
-            ):
-                continue
-
-            # Always add files relative to worktree root
-            filelist.add(path)
-
-    # If --force, silently ignore uncommitted deletions (not in the filesystem)
-    # and renames / additions (will not be found in log anyway)
-    if args.force:
-        filelist -= set(git.ls_dirty(force=True))
-    # Otherwise, ignore any dirty files
-    else:
-        dirty = set(git.ls_dirty())
-        if dirty:
-            log.warning(
-                "WARNING: Modified files in the working directory were ignored."
-                "\nTo include such files, commit your changes or use --force."
-            )
-            filelist -= dirty
-
-    # Build dir list to be processed
-    dirlist = set(os.path.dirname(_) for _ in filelist) if args.dirs else set()
-
-    stats["totalfiles"] = stats["files"] = len(filelist)
-    log.info("{0:,} files to be processed in work dir".format(stats["totalfiles"]))
-
-    if not filelist:
-        # Nothing to do. Exit silently and without errors, just like git does
-        return
-
-    # Process the log until all files are 'touched'
-    log.debug("Line #\tLog #\tF.Left\tModification Time\tFile Name")
-    parse_log(filelist, dirlist, stats, git, args.merge, args.pathspec)
-
-    # Missing files
-    if filelist:
-        # Try to find them in merge logs, if not done already
-        # (usually HUGE, thus MUCH slower!)
-        if args.missing and not args.merge:
-            filterlist = list(filelist)
-            missing = len(filterlist)
-            log.info(
-                "{0:,} files not found in log, trying merge commits".format(missing)
-            )
-            for i in range(0, missing, STEPMISSING):
-                parse_log(
-                    filelist,
-                    dirlist,
-                    stats,
-                    git,
-                    merge=True,
-                    filterlist=filterlist[i : i + STEPMISSING],
-                )
-
-        # Still missing some?
-        for file in filelist:
-            log.warning("WARNING: not found in the log: %s", file)
-
-    # Final statistics
-    # Suggestion: use git-log --before=mtime to brag about skipped log entries
-    def log_info(msg, *a, width=13):
-        ifmt = "{:%d,}" % (width,)  # not using 'n' for consistency with ffmt
-        ffmt = "{:%d,.2f}" % (width,)
-        # %-formatting lacks a thousand separator, must pre-render with .format()
-        log.info(msg.replace("%d", ifmt).replace("%f", ffmt).format(*a))
-
-    log_info(
-        "Statistics:\n%f seconds\n%d log lines processed\n%d commits evaluated",
-        time.time() - start,
-        stats["loglines"],
-        stats["commits"],
-    )
-
-    if args.dirs:
-        if stats["direrrors"]:
-            log_info("%d directory update errors", stats["direrrors"])
-        log_info("%d directories updated", stats["dirtouches"])
-
-    if stats["touches"] != stats["totalfiles"]:
-        log_info("%d files", stats["totalfiles"])
-    if stats["skip"]:
-        log_info("%d files skipped", stats["skip"])
-    if stats["files"]:
-        log_info("%d files missing", stats["files"])
-    if stats["errors"]:
-        log_info("%d file update errors", stats["errors"])
-
-    log_info("%d files updated", stats["touches"])
-
-    if args.test:
-        log.info("TEST RUN - No files modified!")
-
-
-# Keep only essential, global assignments here. Any other logic must be in main()
-log = setup_logging()
-args = parse_args()
-
-# Set the actual touch() and other functions based on command-line arguments
-if args.unique_times:
-    touch = touch_ns
-    isodate = isodate_ns
-
-# Make sure this is always set last to ensure --test behaves as intended
-if args.test:
-    touch = dummy
-
-# UI done, it's showtime!
-try:
-    sys.exit(main())
-except KeyboardInterrupt:
-    log.info("\nAborting")
-    signal.signal(signal.SIGINT, signal.SIG_DFL)
-    os.kill(os.getpid(), signal.SIGINT)

.github/workflows/_compile_integration_test.yml

@@ -1,65 +0,0 @@
-# Validates that a package's integration tests compile without syntax or import errors.
-#
-# (If an integration test fails to compile, it won't run.)
-#
-# Called as part of check_diffs.yml workflow
-#
-# Runs pytest with compile marker to check syntax/imports.
-
-name: "🔗 Compile Integration Tests"
-
-on:
-  workflow_call:
-    inputs:
-      working-directory:
-        required: true
-        type: string
-        description: "From which folder this pipeline executes"
-      python-version:
-        required: true
-        type: string
-        description: "Python version to use"
-
-permissions:
-  contents: read
-
-env:
-  UV_FROZEN: "true"
-
-jobs:
-  build:
-    defaults:
-      run:
-        working-directory: ${{ inputs.working-directory }}
-    runs-on: ubuntu-latest
-    timeout-minutes: 20
-    name: "Python ${{ inputs.python-version }}"
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: "🐍 Set up Python ${{ inputs.python-version }} + UV"
-        uses: "./.github/actions/uv_setup"
-        with:
-          python-version: ${{ inputs.python-version }}
-          cache-suffix: compile-integration-tests-${{ inputs.working-directory }}
-          working-directory: ${{ inputs.working-directory }}
-
-      - name: "📦 Install Integration Dependencies"
-        shell: bash
-        run: uv sync --group test --group test_integration
-
-      - name: "🔗 Check Integration Tests Compile"
-        shell: bash
-        run: uv run pytest -m compile tests/integration_tests
-
-      - name: "🧹 Verify Clean Working Directory"
-        shell: bash
-        run: |
-          set -eu
-
-          STATUS="$(git status)"
-          echo "$STATUS"
-
-          # grep will exit non-zero if the target message isn't found,
-          # and `set -e` above will cause the step to fail.
-          echo "$STATUS" | grep 'nothing to commit, working tree clean'

.github/workflows/_lint.yml

@@ -1,81 +0,0 @@
-# Runs linting.
-#
-# Uses the package's Makefile to run the checks, specifically the
-# `lint_package` and `lint_tests` targets.
-#
-# Called as part of check_diffs.yml workflow.
-
-name: "🧹 Linting"
-
-on:
-  workflow_call:
-    inputs:
-      working-directory:
-        required: true
-        type: string
-        description: "From which folder this pipeline executes"
-      python-version:
-        required: true
-        type: string
-        description: "Python version to use"
-
-permissions:
-  contents: read
-
-env:
-  WORKDIR: ${{ inputs.working-directory == '' && '.' || inputs.working-directory }}
-
-  # This env var allows us to get inline annotations when ruff has complaints.
-  RUFF_OUTPUT_FORMAT: github
-
-  UV_FROZEN: "true"
-
-jobs:
-  # Linting job - runs quality checks on package and test code
-  build:
-    name: "Python ${{ inputs.python-version }}"
-    runs-on: ubuntu-latest
-    timeout-minutes: 20
-    steps:
-      - name: "📋 Checkout Code"
-        uses: actions/checkout@v6
-
-      - name: "🐍 Set up Python ${{ inputs.python-version }} + UV"
-        uses: "./.github/actions/uv_setup"
-        with:
-          python-version: ${{ inputs.python-version }}
-          cache-suffix: lint-${{ inputs.working-directory }}
-          working-directory: ${{ inputs.working-directory }}
-
-      # - name: "🔒 Verify Lockfile is Up-to-Date"
-      #   working-directory: ${{ inputs.working-directory }}
-      #   run: |
-      #     unset UV_FROZEN
-      #     uv lock --check
-
-      - name: "📦 Install Lint & Typing Dependencies"
-        working-directory: ${{ inputs.working-directory }}
-        run: |
-          uv sync --group lint --group typing
-
-      - name: "🔍 Analyze Package Code with Linters"
-        working-directory: ${{ inputs.working-directory }}
-        run: |
-          make lint_package
-
-      - name: "📦 Install Test Dependencies (non-partners)"
-        # (For directories NOT starting with libs/partners/)
-        if: ${{ ! startsWith(inputs.working-directory, 'libs/partners/') }}
-        working-directory: ${{ inputs.working-directory }}
-        run: |
-          uv sync --inexact --group test
-      - name: "📦 Install Test Dependencies"
-        if: ${{ startsWith(inputs.working-directory, 'libs/partners/') }}
-        working-directory: ${{ inputs.working-directory }}
-        run: |
-          uv sync --inexact --group test --group test_integration
-
-      - name: "🔍 Analyze Test Code with Linters"
-        working-directory: ${{ inputs.working-directory }}
-        run: |
-          make lint_tests

.github/workflows/_release.yml

@@ -1,557 +0,0 @@
-# Builds and publishes LangChain packages to PyPI.
-#
-# Manually triggered, though can be used as a reusable workflow (workflow_call).
-#
-# Handles version bumping, building, and publishing to PyPI with authentication.
-
-name: "🚀 Package Release"
-run-name: "Release ${{ inputs.working-directory }} ${{ inputs.release-version }}"
-on:
-  workflow_call:
-    inputs:
-      working-directory:
-        required: true
-        type: string
-        description: "From which folder this pipeline executes"
-  workflow_dispatch:
-    inputs:
-      working-directory:
-        required: true
-        type: string
-        description: "From which folder this pipeline executes"
-        default: "libs/langchain_v1"
-      release-version:
-        required: true
-        type: string
-        default: "0.1.0"
-        description: "New version of package being released"
-      dangerous-nonmaster-release:
-        required: false
-        type: boolean
-        default: false
-        description: "Release from a non-master branch (danger!) - Only use for hotfixes"
-
-env:
-  PYTHON_VERSION: "3.11"
-  UV_FROZEN: "true"
-  UV_NO_SYNC: "true"
-
-permissions:
-  contents: write # Required for creating GitHub releases
-
-jobs:
-  # Build the distribution package and extract version info
-  # Runs in isolated environment with minimal permissions for security
-  build:
-    if: github.ref == 'refs/heads/master' || inputs.dangerous-nonmaster-release
-    environment: Scheduled testing
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-
-    outputs:
-      pkg-name: ${{ steps.check-version.outputs.pkg-name }}
-      version: ${{ steps.check-version.outputs.version }}
-
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: Set up Python + uv
-        uses: "./.github/actions/uv_setup"
-        with:
-          python-version: ${{ env.PYTHON_VERSION }}
-
-      # We want to keep this build stage *separate* from the release stage,
-      # so that there's no sharing of permissions between them.
-      # (Release stage has trusted publishing and GitHub repo contents write access,
-      #
-      # Otherwise, a malicious `build` step (e.g. via a compromised dependency)
-      # could get access to our GitHub or PyPI credentials.
-      #
-      # Per the trusted publishing GitHub Action:
-      # > It is strongly advised to separate jobs for building [...]
-      # > from the publish job.
-      # https://github.com/pypa/gh-action-pypi-publish#non-goals
-      - name: Build project for distribution
-        run: uv build
-        working-directory: ${{ inputs.working-directory }}
-
-      - name: Upload build
-        uses: actions/upload-artifact@v6
-        with:
-          name: dist
-          path: ${{ inputs.working-directory }}/dist/
-
-      - name: Check version
-        id: check-version
-        shell: python
-        working-directory: ${{ inputs.working-directory }}
-        run: |
-          import os
-          import tomllib
-          with open("pyproject.toml", "rb") as f:
-              data = tomllib.load(f)
-          pkg_name = data["project"]["name"]
-          version = data["project"]["version"]
-          with open(os.environ["GITHUB_OUTPUT"], "a") as f:
-              f.write(f"pkg-name={pkg_name}\n")
-              f.write(f"version={version}\n")
-  release-notes:
-    needs:
-      - build
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    outputs:
-      release-body: ${{ steps.generate-release-body.outputs.release-body }}
-    steps:
-      - uses: actions/checkout@v6
-        with:
-          repository: langchain-ai/langchain
-          path: langchain
-          sparse-checkout: | # this only grabs files for relevant dir
-            ${{ inputs.working-directory }}
-          ref: ${{ github.ref }} # this scopes to just ref'd branch
-          fetch-depth: 0 # this fetches entire commit history
-      - name: Check tags
-        id: check-tags
-        shell: bash
-        working-directory: langchain/${{ inputs.working-directory }}
-        env:
-          PKG_NAME: ${{ needs.build.outputs.pkg-name }}
-          VERSION: ${{ needs.build.outputs.version }}
-        run: |
-          # Handle regular versions and pre-release versions differently
-          if [[ "$VERSION" == *"-"* ]]; then
-            # This is a pre-release version (contains a hyphen)
-            # Extract the base version without the pre-release suffix
-            BASE_VERSION=${VERSION%%-*}
-            # Look for the latest release of the same base version
-            REGEX="^$PKG_NAME==$BASE_VERSION\$"
-            PREV_TAG=$(git tag --sort=-creatordate | (grep -P "$REGEX" || true) | head -1)
-
-            # If no exact base version match, look for the latest release of any kind
-            if [ -z "$PREV_TAG" ]; then
-              REGEX="^$PKG_NAME==\\d+\\.\\d+\\.\\d+\$"
-              PREV_TAG=$(git tag --sort=-creatordate | (grep -P "$REGEX" || true) | head -1)
-            fi
-          else
-            # Regular version handling
-            PREV_TAG="$PKG_NAME==${VERSION%.*}.$(( ${VERSION##*.} - 1 ))"; [[ "${VERSION##*.}" -eq 0 ]] && PREV_TAG=""
-
-            # backup case if releasing e.g. 0.3.0, looks up last release
-            # note if last release (chronologically) was e.g. 0.1.47 it will get
-            # that instead of the last 0.2 release
-            if [ -z "$PREV_TAG" ]; then
-              REGEX="^$PKG_NAME==\\d+\\.\\d+\\.\\d+\$"
-              echo $REGEX
-              PREV_TAG=$(git tag --sort=-creatordate | (grep -P $REGEX || true) | head -1)
-            fi
-          fi
-
-          # if PREV_TAG is empty or came out to 0.0.0, let it be empty
-          if [ -z "$PREV_TAG" ] || [ "$PREV_TAG" = "$PKG_NAME==0.0.0" ]; then
-            echo "No previous tag found - first release"
-          else
-            # confirm prev-tag actually exists in git repo with git tag
-            GIT_TAG_RESULT=$(git tag -l "$PREV_TAG")
-            if [ -z "$GIT_TAG_RESULT" ]; then
-              echo "Previous tag $PREV_TAG not found in git repo"
-              exit 1
-            fi
-          fi
-
-
-          TAG="${PKG_NAME}==${VERSION}"
-          if [ "$TAG" == "$PREV_TAG" ]; then
-            echo "No new version to release"
-            exit 1
-          fi
-          echo tag="$TAG" >> $GITHUB_OUTPUT
-          echo prev-tag="$PREV_TAG" >> $GITHUB_OUTPUT
-      - name: Generate release body
-        id: generate-release-body
-        working-directory: langchain
-        env:
-          WORKING_DIR: ${{ inputs.working-directory }}
-          PKG_NAME: ${{ needs.build.outputs.pkg-name }}
-          TAG: ${{ steps.check-tags.outputs.tag }}
-          PREV_TAG: ${{ steps.check-tags.outputs.prev-tag }}
-        run: |
-          PREAMBLE="Changes since $PREV_TAG"
-          # if PREV_TAG is empty or 0.0.0, then we are releasing the first version
-          if [ -z "$PREV_TAG" ] || [ "$PREV_TAG" = "$PKG_NAME==0.0.0" ]; then
-            PREAMBLE="Initial release"
-            PREV_TAG=$(git rev-list --max-parents=0 HEAD)
-          fi
-          {
-            echo 'release-body<<EOF'
-            echo $PREAMBLE
-            echo
-            git log --format="%s" "$PREV_TAG"..HEAD -- $WORKING_DIR
-            echo EOF
-          } >> "$GITHUB_OUTPUT"
-
-  test-pypi-publish:
-    needs:
-      - build
-      - release-notes
-    runs-on: ubuntu-latest
-    permissions:
-      # This permission is used for trusted publishing:
-      # https://blog.pypi.org/posts/2023-04-20-introducing-trusted-publishers/
-      #
-      # Trusted publishing has to also be configured on PyPI for each package:
-      # https://docs.pypi.org/trusted-publishers/adding-a-publisher/
-      id-token: write
-
-    steps:
-      - uses: actions/checkout@v6
-
-      - uses: actions/download-artifact@v7
-        with:
-          name: dist
-          path: ${{ inputs.working-directory }}/dist/
-
-      - name: Publish to test PyPI
-        uses: pypa/gh-action-pypi-publish@release/v1
-        with:
-          packages-dir: ${{ inputs.working-directory }}/dist/
-          verbose: true
-          print-hash: true
-          repository-url: https://test.pypi.org/legacy/
-          # We overwrite any existing distributions with the same name and version.
-          # This is *only for CI use* and is *extremely dangerous* otherwise!
-          # https://github.com/pypa/gh-action-pypi-publish#tolerating-release-package-file-duplicates
-          skip-existing: true
-          # Temp workaround since attestations are on by default as of gh-action-pypi-publish v1.11.0
-          attestations: false
-
-  pre-release-checks:
-    needs:
-      - build
-      - release-notes
-      - test-pypi-publish
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    timeout-minutes: 20
-    steps:
-      - uses: actions/checkout@v6
-
-      # We explicitly *don't* set up caching here. This ensures our tests are
-      # maximally sensitive to catching breakage.
-      #
-      # For example, here's a way that caching can cause a falsely-passing test:
-      # - Make the langchain package manifest no longer list a dependency package
-      #   as a requirement. This means it won't be installed by `pip install`,
-      #   and attempting to use it would cause a crash.
-      # - That dependency used to be required, so it may have been cached.
-      #   When restoring the venv packages from cache, that dependency gets included.
-      # - Tests pass, because the dependency is present even though it wasn't specified.
-      # - The package is published, and it breaks on the missing dependency when
-      #   used in the real world.
-
-      - name: Set up Python + uv
-        uses: "./.github/actions/uv_setup"
-        id: setup-python
-        with:
-          python-version: ${{ env.PYTHON_VERSION }}
-
-      - uses: actions/download-artifact@v7
-        with:
-          name: dist
-          path: ${{ inputs.working-directory }}/dist/
-
-      - name: Import dist package
-        shell: bash
-        working-directory: ${{ inputs.working-directory }}
-        env:
-          PKG_NAME: ${{ needs.build.outputs.pkg-name }}
-          VERSION: ${{ needs.build.outputs.version }}
-        # Here we use:
-        # - The default regular PyPI index as the *primary* index, meaning
-        #   that it takes priority (https://pypi.org/simple)
-        # - The test PyPI index as an extra index, so that any dependencies that
-        #   are not found on test PyPI can be resolved and installed anyway.
-        #   (https://test.pypi.org/simple). This will include the PKG_NAME==VERSION
-        #   package because VERSION will not have been uploaded to regular PyPI yet.
-        # - attempt install again after 5 seconds if it fails because there is
-        #   sometimes a delay in availability on test pypi
-        run: |
-          uv venv
-          VIRTUAL_ENV=.venv uv pip install dist/*.whl
-
-          # Replace all dashes in the package name with underscores,
-          # since that's how Python imports packages with dashes in the name.
-          # also remove _official suffix
-          IMPORT_NAME="$(echo "$PKG_NAME" | sed s/-/_/g | sed s/_official//g)"
-
-          uv run python -c "import $IMPORT_NAME; print(dir($IMPORT_NAME))"
-
-      - name: Import test dependencies
-        run: uv sync --group test
-        working-directory: ${{ inputs.working-directory }}
-
-      # Overwrite the local version of the package with the built version
-      - name: Import published package (again)
-        working-directory: ${{ inputs.working-directory }}
-        shell: bash
-        env:
-          PKG_NAME: ${{ needs.build.outputs.pkg-name }}
-          VERSION: ${{ needs.build.outputs.version }}
-        run: |
-          VIRTUAL_ENV=.venv uv pip install dist/*.whl
-
-      - name: Check for prerelease versions
-        # Block release if any dependencies allow prerelease versions
-        # (unless this is itself a prerelease version)
-        working-directory: ${{ inputs.working-directory }}
-        run: |
-          uv run python $GITHUB_WORKSPACE/.github/scripts/check_prerelease_dependencies.py pyproject.toml
-
-      - name: Run unit tests
-        run: make tests
-        working-directory: ${{ inputs.working-directory }}
-
-      - name: Get minimum versions
-        # Find the minimum published versions that satisfies the given constraints
-        working-directory: ${{ inputs.working-directory }}
-        id: min-version
-        run: |
-          VIRTUAL_ENV=.venv uv pip install packaging requests
-          python_version="$(uv run python --version | awk '{print $2}')"
-          min_versions="$(uv run python $GITHUB_WORKSPACE/.github/scripts/get_min_versions.py pyproject.toml release $python_version)"
-          echo "min-versions=$min_versions" >> "$GITHUB_OUTPUT"
-          echo "min-versions=$min_versions"
-
-      - name: Run unit tests with minimum dependency versions
-        if: ${{ steps.min-version.outputs.min-versions != '' }}
-        env:
-          MIN_VERSIONS: ${{ steps.min-version.outputs.min-versions }}
-        run: |
-          VIRTUAL_ENV=.venv uv pip install --force-reinstall --editable .
-          VIRTUAL_ENV=.venv uv pip install --force-reinstall $MIN_VERSIONS
-          make tests
-        working-directory: ${{ inputs.working-directory }}
-
-      - name: Import integration test dependencies
-        run: uv sync --group test --group test_integration
-        working-directory: ${{ inputs.working-directory }}
-
-      - name: Run integration tests
-        # Uses the Makefile's `integration_tests` target for the specified package
-        if: ${{ startsWith(inputs.working-directory, 'libs/partners/') }}
-        env:
-          AI21_API_KEY: ${{ secrets.AI21_API_KEY }}
-          GOOGLE_API_KEY: ${{ secrets.GOOGLE_API_KEY }}
-          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
-          MISTRAL_API_KEY: ${{ secrets.MISTRAL_API_KEY }}
-          TOGETHER_API_KEY: ${{ secrets.TOGETHER_API_KEY }}
-          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
-          AZURE_OPENAI_API_VERSION: ${{ secrets.AZURE_OPENAI_API_VERSION }}
-          AZURE_OPENAI_API_BASE: ${{ secrets.AZURE_OPENAI_API_BASE }}
-          AZURE_OPENAI_API_KEY: ${{ secrets.AZURE_OPENAI_API_KEY }}
-          AZURE_OPENAI_CHAT_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_CHAT_DEPLOYMENT_NAME }}
-          AZURE_OPENAI_LEGACY_CHAT_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_LEGACY_CHAT_DEPLOYMENT_NAME }}
-          AZURE_OPENAI_LLM_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_LLM_DEPLOYMENT_NAME }}
-          AZURE_OPENAI_EMBEDDINGS_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_EMBEDDINGS_DEPLOYMENT_NAME }}
-          NVIDIA_API_KEY: ${{ secrets.NVIDIA_API_KEY }}
-          GOOGLE_SEARCH_API_KEY: ${{ secrets.GOOGLE_SEARCH_API_KEY }}
-          GOOGLE_CSE_ID: ${{ secrets.GOOGLE_CSE_ID }}
-          GROQ_API_KEY: ${{ secrets.GROQ_API_KEY }}
-          HUGGINGFACEHUB_API_TOKEN: ${{ secrets.HUGGINGFACEHUB_API_TOKEN }}
-          EXA_API_KEY: ${{ secrets.EXA_API_KEY }}
-          NOMIC_API_KEY: ${{ secrets.NOMIC_API_KEY }}
-          WATSONX_APIKEY: ${{ secrets.WATSONX_APIKEY }}
-          WATSONX_PROJECT_ID: ${{ secrets.WATSONX_PROJECT_ID }}
-          ASTRA_DB_API_ENDPOINT: ${{ secrets.ASTRA_DB_API_ENDPOINT }}
-          ASTRA_DB_APPLICATION_TOKEN: ${{ secrets.ASTRA_DB_APPLICATION_TOKEN }}
-          ASTRA_DB_KEYSPACE: ${{ secrets.ASTRA_DB_KEYSPACE }}
-          ES_URL: ${{ secrets.ES_URL }}
-          ES_CLOUD_ID: ${{ secrets.ES_CLOUD_ID }}
-          ES_API_KEY: ${{ secrets.ES_API_KEY }}
-          MONGODB_ATLAS_URI: ${{ secrets.MONGODB_ATLAS_URI }}
-          UPSTAGE_API_KEY: ${{ secrets.UPSTAGE_API_KEY }}
-          FIREWORKS_API_KEY: ${{ secrets.FIREWORKS_API_KEY }}
-          XAI_API_KEY: ${{ secrets.XAI_API_KEY }}
-          DEEPSEEK_API_KEY: ${{ secrets.DEEPSEEK_API_KEY }}
-          PPLX_API_KEY: ${{ secrets.PPLX_API_KEY }}
-          LANGCHAIN_TESTS_USER_AGENT: ${{ secrets.LANGCHAIN_TESTS_USER_AGENT }}
-        run: make integration_tests
-        working-directory: ${{ inputs.working-directory }}
-
-  # Test select published packages against new core
-  # Done when code changes are made to langchain-core
-  test-prior-published-packages-against-new-core:
-    # Installs the new core with old partners: Installs the new unreleased core
-    # alongside the previously published partner packages and runs integration tests
-    needs:
-      - build
-      - release-notes
-      - test-pypi-publish
-      - pre-release-checks
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    if: false # temporarily skip
-    strategy:
-      matrix:
-        partner: [openai, anthropic]
-      fail-fast: false # Continue testing other partners if one fails
-    env:
-      ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
-      ANTHROPIC_FILES_API_IMAGE_ID: ${{ secrets.ANTHROPIC_FILES_API_IMAGE_ID }}
-      ANTHROPIC_FILES_API_PDF_ID: ${{ secrets.ANTHROPIC_FILES_API_PDF_ID }}
-      OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
-      AZURE_OPENAI_API_VERSION: ${{ secrets.AZURE_OPENAI_API_VERSION }}
-      AZURE_OPENAI_API_BASE: ${{ secrets.AZURE_OPENAI_API_BASE }}
-      AZURE_OPENAI_API_KEY: ${{ secrets.AZURE_OPENAI_API_KEY }}
-      AZURE_OPENAI_CHAT_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_CHAT_DEPLOYMENT_NAME }}
-      AZURE_OPENAI_LEGACY_CHAT_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_LEGACY_CHAT_DEPLOYMENT_NAME }}
-      AZURE_OPENAI_LLM_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_LLM_DEPLOYMENT_NAME }}
-      AZURE_OPENAI_EMBEDDINGS_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_EMBEDDINGS_DEPLOYMENT_NAME }}
-      LANGCHAIN_TESTS_USER_AGENT: ${{ secrets.LANGCHAIN_TESTS_USER_AGENT }}
-    steps:
-      - uses: actions/checkout@v6
-
-      # We implement this conditional as Github Actions does not have good support
-      # for conditionally needing steps. https://github.com/actions/runner/issues/491
-      # TODO: this seems to be resolved upstream, so we can probably remove this workaround
-      - name: Check if libs/core
-        run: |
-          if [ "${{ startsWith(inputs.working-directory, 'libs/core') }}" != "true" ]; then
-            echo "Not in libs/core. Exiting successfully."
-            exit 0
-          fi
-
-      - name: Set up Python + uv
-        if: startsWith(inputs.working-directory, 'libs/core')
-        uses: "./.github/actions/uv_setup"
-        with:
-          python-version: ${{ env.PYTHON_VERSION }}
-
-      - uses: actions/download-artifact@v7
-        if: startsWith(inputs.working-directory, 'libs/core')
-        with:
-          name: dist
-          path: ${{ inputs.working-directory }}/dist/
-
-      - name: Test against ${{ matrix.partner }}
-        if: startsWith(inputs.working-directory, 'libs/core')
-        run: |
-          # Identify latest tag, excluding pre-releases
-          LATEST_PACKAGE_TAG="$(
-            git ls-remote --tags origin "langchain-${{ matrix.partner }}*" \
-            | awk '{print $2}' \
-            | sed 's|refs/tags/||' \
-            | grep -E '[0-9]+\.[0-9]+\.[0-9]+$' \
-            | sort -Vr \
-            | head -n 1
-          )"
-          echo "Latest package tag: $LATEST_PACKAGE_TAG"
-
-          # Shallow-fetch just that single tag
-          git fetch --depth=1 origin tag "$LATEST_PACKAGE_TAG"
-
-          # Checkout the latest package files
-          rm -rf $GITHUB_WORKSPACE/libs/partners/${{ matrix.partner }}/*
-          rm -rf $GITHUB_WORKSPACE/libs/standard-tests/*
-          cd $GITHUB_WORKSPACE/libs/
-          git checkout "$LATEST_PACKAGE_TAG" -- standard-tests/
-          git checkout "$LATEST_PACKAGE_TAG" -- partners/${{ matrix.partner }}/
-          cd partners/${{ matrix.partner }}
-
-          # Print as a sanity check
-          echo "Version number from pyproject.toml: "
-          cat pyproject.toml | grep "version = "
-
-          # Run tests
-          uv sync --group test --group test_integration
-          uv pip install ../../core/dist/*.whl
-          make integration_tests
-
-  publish:
-    # Publishes the package to PyPI
-    needs:
-      - build
-      - release-notes
-      - test-pypi-publish
-      - pre-release-checks
-      # - test-prior-published-packages-against-new-core
-    runs-on: ubuntu-latest
-    permissions:
-      # This permission is used for trusted publishing:
-      # https://blog.pypi.org/posts/2023-04-20-introducing-trusted-publishers/
-      #
-      # Trusted publishing has to also be configured on PyPI for each package:
-      # https://docs.pypi.org/trusted-publishers/adding-a-publisher/
-      id-token: write
-
-    defaults:
-      run:
-        working-directory: ${{ inputs.working-directory }}
-
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: Set up Python + uv
-        uses: "./.github/actions/uv_setup"
-        with:
-          python-version: ${{ env.PYTHON_VERSION }}
-
-      - uses: actions/download-artifact@v7
-        with:
-          name: dist
-          path: ${{ inputs.working-directory }}/dist/
-
-      - name: Publish package distributions to PyPI
-        uses: pypa/gh-action-pypi-publish@release/v1
-        with:
-          packages-dir: ${{ inputs.working-directory }}/dist/
-          verbose: true
-          print-hash: true
-          # Temp workaround since attestations are on by default as of gh-action-pypi-publish v1.11.0
-          attestations: false
-
-  mark-release:
-    # Marks the GitHub release with the new version tag
-    needs:
-      - build
-      - release-notes
-      - test-pypi-publish
-      - pre-release-checks
-      - publish
-    runs-on: ubuntu-latest
-    permissions:
-      # This permission is needed by `ncipollo/release-action` to
-      # create the GitHub release/tag
-      contents: write
-
-    defaults:
-      run:
-        working-directory: ${{ inputs.working-directory }}
-
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: Set up Python + uv
-        uses: "./.github/actions/uv_setup"
-        with:
-          python-version: ${{ env.PYTHON_VERSION }}
-
-      - uses: actions/download-artifact@v7
-        with:
-          name: dist
-          path: ${{ inputs.working-directory }}/dist/
-
-      - name: Create Tag
-        uses: ncipollo/release-action@v1
-        with:
-          artifacts: "dist/*"
-          token: ${{ secrets.GITHUB_TOKEN }}
-          generateReleaseNotes: false
-          tag: ${{needs.build.outputs.pkg-name}}==${{ needs.build.outputs.version }}
-          body: ${{ needs.release-notes.outputs.release-body }}
-          commit: ${{ github.sha }}
-          makeLatest: ${{ needs.build.outputs.pkg-name == 'langchain-core'}}

.github/workflows/_test.yml

@@ -1,85 +0,0 @@
-# Runs unit tests with both current and minimum supported dependency versions
-# to ensure compatibility across the supported range.
-
-name: "🧪 Unit Testing"
-
-on:
-  workflow_call:
-    inputs:
-      working-directory:
-        required: true
-        type: string
-        description: "From which folder this pipeline executes"
-      python-version:
-        required: true
-        type: string
-        description: "Python version to use"
-
-permissions:
-  contents: read
-
-env:
-  UV_FROZEN: "true"
-  UV_NO_SYNC: "true"
-
-jobs:
-  # Main test job - runs unit tests with current deps, then retests with minimum versions
-  build:
-    defaults:
-      run:
-        working-directory: ${{ inputs.working-directory }}
-    runs-on: ubuntu-latest
-    timeout-minutes: 20
-    name: "Python ${{ inputs.python-version }}"
-    steps:
-      - name: "📋 Checkout Code"
-        uses: actions/checkout@v6
-
-      - name: "🐍 Set up Python ${{ inputs.python-version }} + UV"
-        uses: "./.github/actions/uv_setup"
-        id: setup-python
-        with:
-          python-version: ${{ inputs.python-version }}
-          cache-suffix: test-${{ inputs.working-directory }}
-          working-directory: ${{ inputs.working-directory }}
-
-      - name: "📦 Install Test Dependencies"
-        shell: bash
-        run: uv sync --group test --dev
-
-      - name: "🧪 Run Core Unit Tests"
-        shell: bash
-        run: |
-          make test
-
-      - name: "🔍 Calculate Minimum Dependency Versions"
-        working-directory: ${{ inputs.working-directory }}
-        id: min-version
-        shell: bash
-        run: |
-          VIRTUAL_ENV=.venv uv pip install packaging tomli requests
-          python_version="$(uv run python --version | awk '{print $2}')"
-          min_versions="$(uv run python $GITHUB_WORKSPACE/.github/scripts/get_min_versions.py pyproject.toml pull_request $python_version)"
-          echo "min-versions=$min_versions" >> "$GITHUB_OUTPUT"
-          echo "min-versions=$min_versions"
-
-      - name: "🧪 Run Tests with Minimum Dependencies"
-        if: ${{ steps.min-version.outputs.min-versions != '' }}
-        env:
-          MIN_VERSIONS: ${{ steps.min-version.outputs.min-versions }}
-        run: |
-          VIRTUAL_ENV=.venv uv pip install $MIN_VERSIONS
-          make tests
-        working-directory: ${{ inputs.working-directory }}
-
-      - name: "🧹 Verify Clean Working Directory"
-        shell: bash
-        run: |
-          set -eu
-
-          STATUS="$(git status)"
-          echo "$STATUS"
-
-          # grep will exit non-zero if the target message isn't found,
-          # and `set -e` above will cause the step to fail.
-          echo "$STATUS" | grep 'nothing to commit, working tree clean'

.github/workflows/_test_pydantic.yml

@@ -1,73 +0,0 @@
-# Facilitate unit testing against different Pydantic versions for a provided package.
-
-name: "🐍 Pydantic Version Testing"
-
-on:
-  workflow_call:
-    inputs:
-      working-directory:
-        required: true
-        type: string
-        description: "From which folder this pipeline executes"
-      python-version:
-        required: false
-        type: string
-        description: "Python version to use"
-        default: "3.12"
-      pydantic-version:
-        required: true
-        type: string
-        description: "Pydantic version to test."
-
-permissions:
-  contents: read
-
-env:
-  UV_FROZEN: "true"
-  UV_NO_SYNC: "true"
-
-jobs:
-  build:
-    defaults:
-      run:
-        working-directory: ${{ inputs.working-directory }}
-    runs-on: ubuntu-latest
-    timeout-minutes: 20
-    name: "Pydantic ~=${{ inputs.pydantic-version }}"
-    steps:
-      - name: "📋 Checkout Code"
-        uses: actions/checkout@v6
-
-      - name: "🐍 Set up Python ${{ inputs.python-version }} + UV"
-        uses: "./.github/actions/uv_setup"
-        with:
-          python-version: ${{ inputs.python-version }}
-          cache-suffix: test-pydantic-${{ inputs.working-directory }}
-          working-directory: ${{ inputs.working-directory }}
-
-      - name: "📦 Install Test Dependencies"
-        shell: bash
-        run: uv sync --group test
-
-      - name: "🔄 Install Specific Pydantic Version"
-        shell: bash
-        env:
-          PYDANTIC_VERSION: ${{ inputs.pydantic-version }}
-        run: VIRTUAL_ENV=.venv uv pip install "pydantic~=$PYDANTIC_VERSION"
-
-      - name: "🧪 Run Core Tests"
-        shell: bash
-        run: |
-          make test
-
-      - name: "🧹 Verify Clean Working Directory"
-        shell: bash
-        run: |
-          set -eu
-
-          STATUS="$(git status)"
-          echo "$STATUS"
-
-          # grep will exit non-zero if the target message isn't found,
-          # and `set -e` above will cause the step to fail.
-          echo "$STATUS" | grep 'nothing to commit, working tree clean'

.github/workflows/auto-label-by-package.yml

@@ -1,107 +0,0 @@
-name: Auto Label Issues by Package
-
-on:
-  issues:
-    types: [opened, edited]
-
-jobs:
-  label-by-package:
-    permissions:
-      issues: write
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Sync package labels
-        uses: actions/github-script@v8
-        with:
-          script: |
-            const body = context.payload.issue.body || "";
-
-            // Extract text under "### Package" (handles " (Required)" suffix and being last section)
-            const match = body.match(/### Package[^\n]*\n([\s\S]*?)(?:\n###|$)/i);
-            if (!match) return;
-
-            const packageSection = match[1].trim();
-
-            // Mapping table for package names to labels
-            const mapping = {
-              "langchain": "langchain",
-              "langchain-openai": "openai",
-              "langchain-anthropic": "anthropic",
-              "langchain-classic": "langchain-classic",
-              "langchain-core": "core",
-              "langchain-cli": "cli",
-              "langchain-model-profiles": "model-profiles",
-              "langchain-tests": "standard-tests",
-              "langchain-text-splitters": "text-splitters",
-              "langchain-chroma": "chroma",
-              "langchain-deepseek": "deepseek",
-              "langchain-exa": "exa",
-              "langchain-fireworks": "fireworks",
-              "langchain-groq": "groq",
-              "langchain-huggingface": "huggingface",
-              "langchain-mistralai": "mistralai",
-              "langchain-nomic": "nomic",
-              "langchain-ollama": "ollama",
-              "langchain-perplexity": "perplexity",
-              "langchain-prompty": "prompty",
-              "langchain-qdrant": "qdrant",
-              "langchain-xai": "xai",
-            };
-
-            // All possible package labels we manage
-            const allPackageLabels = Object.values(mapping);
-            const selectedLabels = [];
-
-            // Check if this is checkbox format (multiple selection)
-            const checkboxMatches = packageSection.match(/- \[x\]\s+([^\n\r]+)/gi);
-            if (checkboxMatches) {
-              // Handle checkbox format
-              for (const match of checkboxMatches) {
-                const packageName = match.replace(/- \[x\]\s+/i, '').trim();
-                const label = mapping[packageName];
-                if (label && !selectedLabels.includes(label)) {
-                  selectedLabels.push(label);
-                }
-              }
-            } else {
-              // Handle dropdown format (single selection)
-              const label = mapping[packageSection];
-              if (label) {
-                selectedLabels.push(label);
-              }
-            }
-
-            // Get current issue labels
-            const issue = await github.rest.issues.get({
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              issue_number: context.issue.number
-            });
-
-            const currentLabels = issue.data.labels.map(label => label.name);
-            const currentPackageLabels = currentLabels.filter(label => allPackageLabels.includes(label));
-
-            // Determine labels to add and remove
-            const labelsToAdd = selectedLabels.filter(label => !currentPackageLabels.includes(label));
-            const labelsToRemove = currentPackageLabels.filter(label => !selectedLabels.includes(label));
-
-            // Add new labels
-            if (labelsToAdd.length > 0) {
-              await github.rest.issues.addLabels({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                issue_number: context.issue.number,
-                labels: labelsToAdd
-              });
-            }
-
-            // Remove old labels
-            for (const label of labelsToRemove) {
-              await github.rest.issues.removeLabel({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                issue_number: context.issue.number,
-                name: label
-              });
-            }

.github/workflows/check_core_versions.yml

@@ -1,51 +0,0 @@
-# Ensures version numbers in pyproject.toml and version.py stay in sync.
-#
-# (Prevents releases with mismatched version numbers)
-
-name: "🔍 Check Version Equality"
-
-on:
-  pull_request:
-    paths:
-      - "libs/core/pyproject.toml"
-      - "libs/core/langchain_core/version.py"
-
-permissions:
-  contents: read
-
-jobs:
-  check_version_equality:
-    runs-on: ubuntu-latest
-
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: "✅ Verify pyproject.toml & version.py Match"
-        run: |
-          # Check core versions
-          CORE_PYPROJECT_VERSION=$(grep -Po '(?<=^version = ")[^"]*' libs/core/pyproject.toml)
-          CORE_VERSION_PY_VERSION=$(grep -Po '(?<=^VERSION = ")[^"]*' libs/core/langchain_core/version.py)
-
-          # Compare core versions
-          if [ "$CORE_PYPROJECT_VERSION" != "$CORE_VERSION_PY_VERSION" ]; then
-            echo "langchain-core versions in pyproject.toml and version.py do not match!"
-            echo "pyproject.toml version: $CORE_PYPROJECT_VERSION"
-            echo "version.py version: $CORE_VERSION_PY_VERSION"
-            exit 1
-          else
-            echo "Core versions match: $CORE_PYPROJECT_VERSION"
-          fi
-
-          # Check langchain_v1 versions
-          LANGCHAIN_PYPROJECT_VERSION=$(grep -Po '(?<=^version = ")[^"]*' libs/langchain_v1/pyproject.toml)
-          LANGCHAIN_INIT_PY_VERSION=$(grep -Po '(?<=^__version__ = ")[^"]*' libs/langchain_v1/langchain/__init__.py)
-
-          # Compare langchain_v1 versions
-          if [ "$LANGCHAIN_PYPROJECT_VERSION" != "$LANGCHAIN_INIT_PY_VERSION" ]; then
-            echo "langchain_v1 versions in pyproject.toml and __init__.py do not match!"
-            echo "pyproject.toml version: $LANGCHAIN_PYPROJECT_VERSION"
-            echo "version.py version: $LANGCHAIN_INIT_PY_VERSION"
-            exit 1
-          else
-            echo "Langchain v1 versions match: $LANGCHAIN_PYPROJECT_VERSION"
-          fi

.github/workflows/check_diffs.yml

@@ -1,261 +0,0 @@
-# Primary CI workflow.
-#
-# Only runs against packages that have changed files.
-#
-# Runs:
-# - Linting (_lint.yml)
-# - Unit Tests (_test.yml)
-# - Pydantic compatibility tests (_test_pydantic.yml)
-# - Integration test compilation checks (_compile_integration_test.yml)
-# - Extended test suites that require additional dependencies
-# - Codspeed benchmarks (if not labeled 'codspeed-ignore')
-#
-# Reports status to GitHub checks and PR status.
-
-name: "🔧 CI"
-
-on:
-  push:
-    branches: [master]
-  pull_request:
-  merge_group:
-
-# Optimizes CI performance by canceling redundant workflow runs
-# If another push to the same PR or branch happens while this workflow is still running,
-# cancel the earlier run in favor of the next run.
-#
-# There's no point in testing an outdated version of the code. GitHub only allows
-# a limited number of job runners to be active at the same time, so it's better to
-# cancel pointless jobs early so that more useful jobs can run sooner.
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
-
-permissions:
-  contents: read
-
-env:
-  UV_FROZEN: "true"
-  UV_NO_SYNC: "true"
-
-jobs:
-  # This job analyzes which files changed and creates a dynamic test matrix
-  # to only run tests/lints for the affected packages, improving CI efficiency
-  build:
-    name: "Detect Changes & Set Matrix"
-    runs-on: ubuntu-latest
-    if: ${{ !contains(github.event.pull_request.labels.*.name, 'ci-ignore') }}
-    steps:
-      - name: "📋 Checkout Code"
-        uses: actions/checkout@v6
-      - name: "🐍 Setup Python 3.11"
-        uses: actions/setup-python@v6
-        with:
-          python-version: "3.11"
-      - name: "📂 Get Changed Files"
-        id: files
-        uses: Ana06/get-changed-files@v2.3.0
-      - name: "🔍 Analyze Changed Files & Generate Build Matrix"
-        id: set-matrix
-        run: |
-          python -m pip install packaging requests
-          python .github/scripts/check_diff.py ${{ steps.files.outputs.all }} >> $GITHUB_OUTPUT
-    outputs:
-      lint: ${{ steps.set-matrix.outputs.lint }}
-      test: ${{ steps.set-matrix.outputs.test }}
-      extended-tests: ${{ steps.set-matrix.outputs.extended-tests }}
-      compile-integration-tests: ${{ steps.set-matrix.outputs.compile-integration-tests }}
-      dependencies: ${{ steps.set-matrix.outputs.dependencies }}
-      test-pydantic: ${{ steps.set-matrix.outputs.test-pydantic }}
-      codspeed: ${{ steps.set-matrix.outputs.codspeed }}
-  # Run linting only on packages that have changed files
-  lint:
-    needs: [build]
-    if: ${{ needs.build.outputs.lint != '[]' }}
-    strategy:
-      matrix:
-        job-configs: ${{ fromJson(needs.build.outputs.lint) }}
-      fail-fast: false
-    uses: ./.github/workflows/_lint.yml
-    with:
-      working-directory: ${{ matrix.job-configs.working-directory }}
-      python-version: ${{ matrix.job-configs.python-version }}
-    secrets: inherit
-
-  # Run unit tests only on packages that have changed files
-  test:
-    needs: [build]
-    if: ${{ needs.build.outputs.test != '[]' }}
-    strategy:
-      matrix:
-        job-configs: ${{ fromJson(needs.build.outputs.test) }}
-      fail-fast: false
-    uses: ./.github/workflows/_test.yml
-    with:
-      working-directory: ${{ matrix.job-configs.working-directory }}
-      python-version: ${{ matrix.job-configs.python-version }}
-    secrets: inherit
-
-  # Test compatibility with different Pydantic versions for affected packages
-  test-pydantic:
-    needs: [build]
-    if: ${{ needs.build.outputs.test-pydantic != '[]' }}
-    strategy:
-      matrix:
-        job-configs: ${{ fromJson(needs.build.outputs.test-pydantic) }}
-      fail-fast: false
-    uses: ./.github/workflows/_test_pydantic.yml
-    with:
-      working-directory: ${{ matrix.job-configs.working-directory }}
-      pydantic-version: ${{ matrix.job-configs.pydantic-version }}
-    secrets: inherit
-
-  # Verify integration tests compile without actually running them (faster feedback)
-  compile-integration-tests:
-    name: "Compile Integration Tests"
-    needs: [build]
-    if: ${{ needs.build.outputs.compile-integration-tests != '[]' }}
-    strategy:
-      matrix:
-        job-configs: ${{ fromJson(needs.build.outputs.compile-integration-tests) }}
-      fail-fast: false
-    uses: ./.github/workflows/_compile_integration_test.yml
-    with:
-      working-directory: ${{ matrix.job-configs.working-directory }}
-      python-version: ${{ matrix.job-configs.python-version }}
-    secrets: inherit
-
-  # Run extended test suites that require additional dependencies
-  extended-tests:
-    name: "Extended Tests"
-    needs: [build]
-    if: ${{ needs.build.outputs.extended-tests != '[]' }}
-    strategy:
-      matrix:
-        # note different variable for extended test dirs
-        job-configs: ${{ fromJson(needs.build.outputs.extended-tests) }}
-      fail-fast: false
-    runs-on: ubuntu-latest
-    timeout-minutes: 20
-    defaults:
-      run:
-        working-directory: ${{ matrix.job-configs.working-directory }}
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: "🐍 Set up Python ${{ matrix.job-configs.python-version }} + UV"
-        uses: "./.github/actions/uv_setup"
-        with:
-          python-version: ${{ matrix.job-configs.python-version }}
-          cache-suffix: extended-tests-${{ matrix.job-configs.working-directory }}
-          working-directory: ${{ matrix.job-configs.working-directory }}
-
-      - name: "📦 Install Dependencies & Run Extended Tests"
-        shell: bash
-        run: |
-          echo "Running extended tests, installing dependencies with uv..."
-          uv venv
-          uv sync --group test
-          VIRTUAL_ENV=.venv uv pip install -r extended_testing_deps.txt
-          VIRTUAL_ENV=.venv make extended_tests
-
-      - name: "🧹 Verify Clean Working Directory"
-        shell: bash
-        run: |
-          set -eu
-
-          STATUS="$(git status)"
-          echo "$STATUS"
-
-          # grep will exit non-zero if the target message isn't found,
-          # and `set -e` above will cause the step to fail.
-          echo "$STATUS" | grep 'nothing to commit, working tree clean'
-
-  # Run codspeed benchmarks only on packages that have changed files
-  codspeed:
-    name: "⚡ CodSpeed Benchmarks"
-    needs: [build]
-    if: ${{ needs.build.outputs.codspeed != '[]' && !contains(github.event.pull_request.labels.*.name, 'codspeed-ignore') }}
-    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        job-configs: ${{ fromJson(needs.build.outputs.codspeed) }}
-      fail-fast: false
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: "📦 Install UV Package Manager"
-        uses: astral-sh/setup-uv@v7
-        with:
-          python-version: "3.13"
-
-      - uses: actions/setup-python@v6
-        with:
-          python-version: "3.13"
-
-      - name: "📦 Install Test Dependencies"
-        run: uv sync --group test
-        working-directory: ${{ matrix.job-configs.working-directory }}
-
-      - name: "⚡ Run Benchmarks: ${{ matrix.job-configs.working-directory }}"
-        uses: CodSpeedHQ/action@v4
-        env:
-          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
-          ANTHROPIC_FILES_API_IMAGE_ID: ${{ secrets.ANTHROPIC_FILES_API_IMAGE_ID }}
-          ANTHROPIC_FILES_API_PDF_ID: ${{ secrets.ANTHROPIC_FILES_API_PDF_ID }}
-          AZURE_OPENAI_API_VERSION: ${{ secrets.AZURE_OPENAI_API_VERSION }}
-          AZURE_OPENAI_API_BASE: ${{ secrets.AZURE_OPENAI_API_BASE }}
-          AZURE_OPENAI_API_KEY: ${{ secrets.AZURE_OPENAI_API_KEY }}
-          AZURE_OPENAI_CHAT_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_CHAT_DEPLOYMENT_NAME }}
-          AZURE_OPENAI_LEGACY_CHAT_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_LEGACY_CHAT_DEPLOYMENT_NAME }}
-          AZURE_OPENAI_LLM_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_LLM_DEPLOYMENT_NAME }}
-          AZURE_OPENAI_EMBEDDINGS_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_EMBEDDINGS_DEPLOYMENT_NAME }}
-          COHERE_API_KEY: ${{ secrets.COHERE_API_KEY }}
-          DEEPSEEK_API_KEY: ${{ secrets.DEEPSEEK_API_KEY }}
-          EXA_API_KEY: ${{ secrets.EXA_API_KEY }}
-          FIREWORKS_API_KEY: ${{ secrets.FIREWORKS_API_KEY }}
-          GROQ_API_KEY: ${{ secrets.GROQ_API_KEY }}
-          HUGGINGFACEHUB_API_TOKEN: ${{ secrets.HUGGINGFACEHUB_API_TOKEN }}
-          MISTRAL_API_KEY: ${{ secrets.MISTRAL_API_KEY }}
-          NOMIC_API_KEY: ${{ secrets.NOMIC_API_KEY }}
-          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
-          PPLX_API_KEY: ${{ secrets.PPLX_API_KEY }}
-          XAI_API_KEY: ${{ secrets.XAI_API_KEY }}
-        with:
-          token: ${{ secrets.CODSPEED_TOKEN }}
-          run: |
-            cd ${{ matrix.job-configs.working-directory }}
-            if [ "${{ matrix.job-configs.working-directory }}" = "libs/core" ]; then
-              uv run --no-sync pytest ./tests/benchmarks --codspeed
-            else
-              uv run --no-sync pytest ./tests/ --codspeed
-            fi
-          mode: ${{ matrix.job-configs.working-directory == 'libs/core' && 'walltime' || 'instrumentation' }}
-
-  # Final status check - ensures all required jobs passed before allowing merge
-  ci_success:
-    name: "✅ CI Success"
-    needs:
-      [
-        build,
-        lint,
-        test,
-        compile-integration-tests,
-        extended-tests,
-        test-pydantic,
-        codspeed,
-      ]
-    if: |
-      always()
-    runs-on: ubuntu-latest
-    env:
-      JOBS_JSON: ${{ toJSON(needs) }}
-      RESULTS_JSON: ${{ toJSON(needs.*.result) }}
-      EXIT_CODE: ${{!contains(needs.*.result, 'failure') && !contains(needs.*.result, 'cancelled') && '0' || '1'}}
-    steps:
-      - name: "🎉 All Checks Passed"
-        run: |
-          echo $JOBS_JSON
-          echo $RESULTS_JSON
-          echo "Exiting with $EXIT_CODE"
-          exit $EXIT_CODE

.github/workflows/integration_tests.yml

@@ -1,181 +0,0 @@
-# Routine integration tests against partner libraries with live API credentials.
-#
-# Uses `make integration_tests` for each library in the matrix.
-#
-# Runs daily. Can also be triggered manually for immediate updates.
-
-name: "⏰ Integration Tests"
-run-name: "Run Integration Tests - ${{ inputs.working-directory-force || 'all libs' }} (Python ${{ inputs.python-version-force || '3.10, 3.13' }})"
-
-on:
-  workflow_dispatch:
-    inputs:
-      working-directory-force:
-        type: string
-        description: "From which folder this pipeline executes - defaults to all in matrix - example value: libs/partners/anthropic"
-      python-version-force:
-        type: string
-        description: "Python version to use - defaults to 3.10 and 3.13 in matrix - example value: 3.11"
-  schedule:
-    - cron: "0 13 * * *" # Runs daily at 1PM UTC (9AM EDT/6AM PDT)
-
-permissions:
-  contents: read
-
-env:
-  UV_FROZEN: "true"
-  DEFAULT_LIBS: '["libs/partners/openai", "libs/partners/anthropic", "libs/partners/fireworks", "libs/partners/groq", "libs/partners/mistralai", "libs/partners/xai", "libs/partners/google-vertexai", "libs/partners/google-genai", "libs/partners/aws"]'
-
-jobs:
-  # Generate dynamic test matrix based on input parameters or defaults
-  # Only runs on the main repo (for scheduled runs) or when manually triggered
-  compute-matrix:
-    if: github.repository_owner == 'langchain-ai' || github.event_name != 'schedule'
-    runs-on: ubuntu-latest
-    name: "📋 Compute Test Matrix"
-    outputs:
-      matrix: ${{ steps.set-matrix.outputs.matrix }}
-    steps:
-      - name: "🔢 Generate Python & Library Matrix"
-        id: set-matrix
-        env:
-          DEFAULT_LIBS: ${{ env.DEFAULT_LIBS }}
-          WORKING_DIRECTORY_FORCE: ${{ github.event.inputs.working-directory-force || '' }}
-          PYTHON_VERSION_FORCE: ${{ github.event.inputs.python-version-force || '' }}
-        run: |
-          # echo "matrix=..." where matrix is a json formatted str with keys python-version and working-directory
-          # python-version should default to 3.10 and 3.13, but is overridden to [PYTHON_VERSION_FORCE] if set
-          # working-directory should default to DEFAULT_LIBS, but is overridden to [WORKING_DIRECTORY_FORCE] if set
-          python_version='["3.10", "3.13"]'
-          working_directory="$DEFAULT_LIBS"
-          if [ -n "$PYTHON_VERSION_FORCE" ]; then
-            python_version="[\"$PYTHON_VERSION_FORCE\"]"
-          fi
-          if [ -n "$WORKING_DIRECTORY_FORCE" ]; then
-            working_directory="[\"$WORKING_DIRECTORY_FORCE\"]"
-          fi
-          matrix="{\"python-version\": $python_version, \"working-directory\": $working_directory}"
-          echo $matrix
-          echo "matrix=$matrix" >> $GITHUB_OUTPUT
-  # Run integration tests against partner libraries with live API credentials
-  build:
-    if: github.repository_owner == 'langchain-ai' || github.event_name != 'schedule'
-    name: "🐍 Python ${{ matrix.python-version }}: ${{ matrix.working-directory }}"
-    runs-on: ubuntu-latest
-    needs: [compute-matrix]
-    timeout-minutes: 30
-    strategy:
-      fail-fast: false
-      matrix:
-        python-version: ${{ fromJSON(needs.compute-matrix.outputs.matrix).python-version }}
-        working-directory: ${{ fromJSON(needs.compute-matrix.outputs.matrix).working-directory }}
-
-    steps:
-      - uses: actions/checkout@v6
-        with:
-          path: langchain
-      - uses: actions/checkout@v6
-        with:
-          repository: langchain-ai/langchain-google
-          path: langchain-google
-      - uses: actions/checkout@v6
-        with:
-          repository: langchain-ai/langchain-aws
-          path: langchain-aws
-
-      - name: "📦 Organize External Libraries"
-        run: |
-          rm -rf \
-            langchain/libs/partners/google-genai \
-            langchain/libs/partners/google-vertexai
-          mv langchain-google/libs/genai langchain/libs/partners/google-genai
-          mv langchain-google/libs/vertexai langchain/libs/partners/google-vertexai
-          mv langchain-aws/libs/aws langchain/libs/partners/aws
-
-      - name: "🐍 Set up Python ${{ matrix.python-version }} + UV"
-        uses: "./langchain/.github/actions/uv_setup"
-        with:
-          python-version: ${{ matrix.python-version }}
-
-      - name: "🔐 Authenticate to Google Cloud"
-        id: "auth"
-        uses: google-github-actions/auth@v3
-        with:
-          credentials_json: "${{ secrets.GOOGLE_CREDENTIALS }}"
-
-      - name: "🔐 Configure AWS Credentials"
-        uses: aws-actions/configure-aws-credentials@v5
-        with:
-          aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
-          aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
-          aws-region: ${{ secrets.AWS_REGION }}
-
-      - name: "📦 Install Dependencies"
-        run: |
-          echo "Running scheduled tests, installing dependencies with uv..."
-          cd langchain/${{ matrix.working-directory }}
-          uv sync --group test --group test_integration
-
-      - name: "🚀 Run Integration Tests"
-        env:
-          AI21_API_KEY: ${{ secrets.AI21_API_KEY }}
-          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
-          ANTHROPIC_FILES_API_IMAGE_ID: ${{ secrets.ANTHROPIC_FILES_API_IMAGE_ID }}
-          ANTHROPIC_FILES_API_PDF_ID: ${{ secrets.ANTHROPIC_FILES_API_PDF_ID }}
-          ASTRA_DB_API_ENDPOINT: ${{ secrets.ASTRA_DB_API_ENDPOINT }}
-          ASTRA_DB_APPLICATION_TOKEN: ${{ secrets.ASTRA_DB_APPLICATION_TOKEN }}
-          ASTRA_DB_KEYSPACE: ${{ secrets.ASTRA_DB_KEYSPACE }}
-          AZURE_OPENAI_API_VERSION: ${{ secrets.AZURE_OPENAI_API_VERSION }}
-          AZURE_OPENAI_API_BASE: ${{ secrets.AZURE_OPENAI_API_BASE }}
-          AZURE_OPENAI_API_KEY: ${{ secrets.AZURE_OPENAI_API_KEY }}
-          AZURE_OPENAI_CHAT_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_CHAT_DEPLOYMENT_NAME }}
-          AZURE_OPENAI_LEGACY_CHAT_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_LEGACY_CHAT_DEPLOYMENT_NAME }}
-          AZURE_OPENAI_LLM_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_LLM_DEPLOYMENT_NAME }}
-          AZURE_OPENAI_EMBEDDINGS_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_EMBEDDINGS_DEPLOYMENT_NAME }}
-          COHERE_API_KEY: ${{ secrets.COHERE_API_KEY }}
-          DEEPSEEK_API_KEY: ${{ secrets.DEEPSEEK_API_KEY }}
-          ES_URL: ${{ secrets.ES_URL }}
-          ES_CLOUD_ID: ${{ secrets.ES_CLOUD_ID }}
-          ES_API_KEY: ${{ secrets.ES_API_KEY }}
-          EXA_API_KEY: ${{ secrets.EXA_API_KEY }}
-          FIREWORKS_API_KEY: ${{ secrets.FIREWORKS_API_KEY }}
-          GOOGLE_API_KEY: ${{ secrets.GOOGLE_API_KEY }}
-          GOOGLE_SEARCH_API_KEY: ${{ secrets.GOOGLE_SEARCH_API_KEY }}
-          GOOGLE_CSE_ID: ${{ secrets.GOOGLE_CSE_ID }}
-          GROQ_API_KEY: ${{ secrets.GROQ_API_KEY }}
-          HUGGINGFACEHUB_API_TOKEN: ${{ secrets.HUGGINGFACEHUB_API_TOKEN }}
-          MISTRAL_API_KEY: ${{ secrets.MISTRAL_API_KEY }}
-          MONGODB_ATLAS_URI: ${{ secrets.MONGODB_ATLAS_URI }}
-          NOMIC_API_KEY: ${{ secrets.NOMIC_API_KEY }}
-          NVIDIA_API_KEY: ${{ secrets.NVIDIA_API_KEY }}
-          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
-          PPLX_API_KEY: ${{ secrets.PPLX_API_KEY }}
-          TOGETHER_API_KEY: ${{ secrets.TOGETHER_API_KEY }}
-          UPSTAGE_API_KEY: ${{ secrets.UPSTAGE_API_KEY }}
-          WATSONX_APIKEY: ${{ secrets.WATSONX_APIKEY }}
-          WATSONX_PROJECT_ID: ${{ secrets.WATSONX_PROJECT_ID }}
-          XAI_API_KEY: ${{ secrets.XAI_API_KEY }}
-          LANGCHAIN_TESTS_USER_AGENT: ${{ secrets.LANGCHAIN_TESTS_USER_AGENT }}
-        run: |
-          cd langchain/${{ matrix.working-directory }}
-          make integration_tests
-
-      - name: "🧹 Clean up External Libraries"
-        # Clean up external libraries to avoid affecting the following git status check
-        run: |
-          rm -rf \
-            langchain/libs/partners/google-genai \
-            langchain/libs/partners/google-vertexai \
-            langchain/libs/partners/aws
-
-      - name: "🧹 Verify Clean Working Directory"
-        working-directory: langchain
-        run: |
-          set -eu
-
-          STATUS="$(git status)"
-          echo "$STATUS"
-
-          # grep will exit non-zero if the target message isn't found,
-          # and `set -e` above will cause the step to fail.
-          echo "$STATUS" | grep 'nothing to commit, working tree clean'

.github/workflows/linkcheck.yml

@@ -0,0 +1,36 @@
+name: linkcheck
+
+on:
+  push:
+    branches: [master]
+  pull_request:
+
+env:
+  POETRY_VERSION: "1.3.1"
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version:
+          - "3.11"
+    steps:
+      - uses: actions/checkout@v3
+      - name: Install poetry
+        run: |
+          pipx install poetry==$POETRY_VERSION
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v4
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: poetry
+      - name: Install dependencies
+        run: |
+          poetry install --with docs
+      - name: Build the docs
+        run: |
+          make docs_build
+      - name: Analyzing the docs with linkcheck
+        run: |
+          make docs_linkcheck

.github/workflows/lint.yml

@@ -0,0 +1,36 @@
+name: lint
+
+on:
+  push:
+    branches: [master]
+  pull_request:
+
+env:
+  POETRY_VERSION: "1.3.1"
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version:
+          - "3.8"
+          - "3.9"
+          - "3.10"
+          - "3.11"
+    steps:
+      - uses: actions/checkout@v3
+      - name: Install poetry
+        run: |
+          pipx install poetry==$POETRY_VERSION
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v4
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: poetry
+      - name: Install dependencies
+        run: |
+          poetry install
+      - name: Analysing the code with our lint
+        run: |
+          make lint

.github/workflows/pr_labeler_file.yml

@@ -1,28 +0,0 @@
-# Label PRs based on changed files.
-#
-# See `.github/pr-file-labeler.yml` to see rules for each label/directory.
-
-name: "🏷️ Pull Request Labeler"
-
-on:
-  # Safe since we're not checking out or running the PR's code
-  # Never check out the PR's head in a pull_request_target job
-  pull_request_target:
-    types: [opened, synchronize, reopened]
-
-jobs:
-  labeler:
-    name: "label"
-    permissions:
-      contents: read
-      pull-requests: write
-      issues: write
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Label Pull Request
-        uses: actions/labeler@v6
-        with:
-          repo-token: "${{ secrets.GITHUB_TOKEN }}"
-          configuration-path: .github/pr-file-labeler.yml
-          sync-labels: false

.github/workflows/pr_labeler_title.yml

@@ -1,44 +0,0 @@
-# Label PRs based on their titles.
-#
-# Uses conventional commit types from PR titles to apply labels.
-# Note: Scope-based labeling (e.g., integration labels) is handled by pr_labeler_file.yml
-
-name: "🏷️ PR Title Labeler"
-
-on:
-  # Safe since we're not checking out or running the PR's code
-  # Never check out the PR's head in a pull_request_target job
-  pull_request_target:
-    types: [opened, edited]
-
-jobs:
-  pr-title-labeler:
-    name: "label"
-    permissions:
-      contents: read
-      pull-requests: write
-      issues: write
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Label PR based on title
-        uses: bcoe/conventional-release-labels@v1
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          type_labels: >-
-            {
-              "feat": "feature",
-              "fix": "fix",
-              "docs": "documentation",
-              "style": "linting",
-              "refactor": "refactor",
-              "perf": "performance",
-              "test": "tests",
-              "build": "infra",
-              "ci": "infra",
-              "chore": "infra",
-              "revert": "revert",
-              "release": "release",
-              "breaking": "breaking"
-            }
-          ignored_types: '[]'

.github/workflows/pr_lint.yml

@@ -1,111 +0,0 @@
-# PR title linting.
-#
-# FORMAT (Conventional Commits 1.0.0):
-#
-#   <type>[optional scope]: <description>
-#   [optional body]
-#   [optional footer(s)]
-#
-# Examples:
-#     feat(core): add multi‐tenant support
-#     fix(cli): resolve flag parsing error
-#     docs: update API usage examples
-#     docs(openai): update API usage examples
-#
-# Allowed Types:
-#   * feat       — a new feature (MINOR)
-#   * fix        — a bug fix (PATCH)
-#   * docs       — documentation only changes
-#   * style      — formatting, linting, etc.; no code change or typing refactors
-#   * refactor   — code change that neither fixes a bug nor adds a feature
-#   * perf       — code change that improves performance
-#   * test       — adding tests or correcting existing
-#   * build      — changes that affect the build system/external dependencies
-#   * ci         — continuous integration/configuration changes
-#   * chore      — other changes that don't modify source or test files
-#   * revert     — reverts a previous commit
-#   * release    — prepare a new release
-#
-# Allowed Scope(s) (optional):
-#   core, cli, langchain, langchain-classic, model-profiles,
-#   standard-tests, text-splitters, docs, anthropic, chroma, deepseek, exa,
-#   fireworks, groq, huggingface, mistralai, nomic, ollama, openai,
-#   perplexity, prompty, qdrant, xai, infra, deps
-#
-# Multiple scopes can be used by separating them with a comma.
-#
-# Rules:
-#   1. The 'Type' must start with a lowercase letter.
-#   2. Breaking changes: append "!" after type/scope (e.g., feat!: drop x support)
-#   3. When releasing (updating the pyproject.toml and uv.lock), the commit message
-#      should be: `release(scope): x.y.z` (e.g., `release(core): 1.2.0` with no
-#      body, footer, or preceeding/proceeding text).
-#
-# Enforces Conventional Commits format for pull request titles to maintain a clear and
-# machine-readable change history.
-
-name: "🏷️ PR Title Lint"
-
-permissions:
-  pull-requests: read
-
-on:
-  pull_request:
-    types: [opened, edited, synchronize]
-
-jobs:
-  # Validates that PR title follows Conventional Commits 1.0.0 specification
-  lint-pr-title:
-    name: "validate format"
-    runs-on: ubuntu-latest
-    steps:
-      - name: "✅ Validate Conventional Commits Format"
-        uses: amannn/action-semantic-pull-request@v6
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        with:
-          types: |
-            feat
-            fix
-            docs
-            style
-            refactor
-            perf
-            test
-            build
-            ci
-            chore
-            revert
-            release
-          scopes: |
-            core
-            cli
-            langchain
-            langchain-classic
-            model-profiles
-            standard-tests
-            text-splitters
-            docs
-            anthropic
-            chroma
-            deepseek
-            exa
-            fireworks
-            groq
-            huggingface
-            mistralai
-            nomic
-            ollama
-            openai
-            perplexity
-            prompty
-            qdrant
-            xai
-            infra
-            deps
-          requireScope: false
-          disallowScopes: |
-            release
-            [A-Z]+
-          ignoreLabels: |
-            ignore-lint-pr-title

.github/workflows/release.yml

@@ -0,0 +1,49 @@
+name: release
+
+on:
+  pull_request:
+    types:
+      - closed
+    branches:
+      - master
+    paths:
+      - 'pyproject.toml'
+
+env:
+  POETRY_VERSION: "1.3.1"
+
+jobs:
+  if_release:
+    if: |
+        ${{ github.event.pull_request.merged == true }}
+        && ${{ contains(github.event.pull_request.labels.*.name, 'release') }}
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - name: Install poetry
+        run: pipx install poetry==$POETRY_VERSION
+      - name: Set up Python 3.10
+        uses: actions/setup-python@v4
+        with:
+          python-version: "3.10"
+          cache: "poetry"
+      - name: Build project for distribution
+        run: poetry build
+      - name: Check Version
+        id: check-version
+        run: |
+          echo version=$(poetry version --short) >> $GITHUB_OUTPUT
+      - name: Create Release
+        uses: ncipollo/release-action@v1
+        with:
+          artifacts: "dist/*"
+          token: ${{ secrets.GITHUB_TOKEN }}
+          draft: false
+          generateReleaseNotes: true
+          tag: v${{ steps.check-version.outputs.version }}
+          commit: master
+      - name: Publish to PyPI
+        env:
+          POETRY_PYPI_TOKEN_PYPI: ${{ secrets.PYPI_API_TOKEN }}
+        run: | 
+          poetry publish

.github/workflows/test.yml

@@ -0,0 +1,34 @@
+name: test
+
+on:
+  push:
+    branches: [master]
+  pull_request:
+
+env:
+  POETRY_VERSION: "1.3.1"
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version:
+          - "3.8"
+          - "3.9"
+          - "3.10"
+          - "3.11"
+    steps:
+      - uses: actions/checkout@v3
+      - name: Install poetry
+        run: pipx install poetry==$POETRY_VERSION
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v4
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: "poetry"
+      - name: Install dependencies
+        run: poetry install
+      - name: Run unit tests
+        run: |
+          make test

.github/workflows/v03_api_doc_build.yml

@@ -1,164 +0,0 @@
-# Build the API reference documentation for v0.3 branch.
-#
-# Manual trigger only.
-#
-# Built HTML pushed to langchain-ai/langchain-api-docs-html.
-#
-# Looks for langchain-ai org repos in packages.yml and checks them out.
-# Calls prep_api_docs_build.py.
-
-name: "📚 API Docs (v0.3)"
-run-name: "Build & Deploy API Reference (v0.3)"
-
-on:
-  workflow_dispatch:
-
-env:
-  PYTHON_VERSION: "3.11"
-
-jobs:
-  build:
-    if: github.repository == 'langchain-ai/langchain' || github.event_name != 'schedule'
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    steps:
-      - uses: actions/checkout@v6
-        with:
-          ref: v0.3
-          path: langchain
-
-      - uses: actions/checkout@v6
-        with:
-          repository: langchain-ai/langchain-api-docs-html
-          path: langchain-api-docs-html
-          token: ${{ secrets.TOKEN_GITHUB_API_DOCS_HTML }}
-
-      - name: "📋 Extract Repository List with yq"
-        id: get-unsorted-repos
-        uses: mikefarah/yq@master
-        with:
-          cmd: |
-            # Extract repos from packages.yml that are in the langchain-ai org
-            # (excluding 'langchain' itself)
-            yq '
-              .packages[]
-              | select(
-                  (
-                    (.repo | test("^langchain-ai/"))
-                    and
-                    (.repo != "langchain-ai/langchain")
-                  )
-                  or
-                  (.include_in_api_ref // false)
-                )
-              | .repo
-            ' langchain/libs/packages.yml
-
-      - name: "📋 Parse YAML & Checkout Repositories"
-        env:
-          REPOS_UNSORTED: ${{ steps.get-unsorted-repos.outputs.result }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          # Get unique repositories
-          REPOS=$(echo "$REPOS_UNSORTED" | sort -u)
-          # Checkout each unique repository
-          for repo in $REPOS; do
-            # Validate repository format (allow any org with proper format)
-            if [[ ! "$repo" =~ ^[a-zA-Z0-9_.-]+/[a-zA-Z0-9_.-]+$ ]]; then
-              echo "Error: Invalid repository format: $repo"
-              exit 1
-            fi
-
-            REPO_NAME=$(echo $repo | cut -d'/' -f2)
-
-            # Additional validation for repo name
-            if [[ ! "$REPO_NAME" =~ ^[a-zA-Z0-9_.-]+$ ]]; then
-              echo "Error: Invalid repository name: $REPO_NAME"
-              exit 1
-            fi
-            echo "Checking out $repo to $REPO_NAME"
-
-            # Special handling for langchain-tavily: checkout by commit hash
-            if [[ "$REPO_NAME" == "langchain-tavily" ]]; then
-              git clone https://github.com/$repo.git $REPO_NAME
-              cd $REPO_NAME
-              git checkout f3515654724a9e87bdfe2c2f509d6cdde646e563
-              cd ..
-            else
-              git clone --depth 1 --branch v0.3 https://github.com/$repo.git $REPO_NAME
-            fi
-          done
-
-      - name: "🐍 Setup Python ${{ env.PYTHON_VERSION }}"
-        uses: actions/setup-python@v6
-        id: setup-python
-        with:
-          python-version: ${{ env.PYTHON_VERSION }}
-
-      - name: "📦 Install Initial Python Dependencies using uv"
-        working-directory: langchain
-        run: |
-          python -m pip install -U uv
-          python -m uv pip install --upgrade --no-cache-dir pip setuptools pyyaml
-
-      - name: "📦 Organize Library Directories"
-        # Places cloned partner packages into libs/partners structure
-        run: python langchain/.github/scripts/prep_api_docs_build.py
-
-      - name: "🧹 Clear Prior Build"
-        run:
-          # Remove artifacts from prior docs build
-          rm -rf langchain-api-docs-html/api_reference_build/html
-
-      - name: "📦 Install Documentation Dependencies using uv"
-        working-directory: langchain
-        run: |
-          # Install all partner packages in editable mode with overrides
-          python -m uv pip install $(ls ./libs/partners | grep -v azure-ai | xargs -I {} echo "./libs/partners/{}") --overrides ./docs/vercel_overrides.txt --prerelease=allow
-
-          # Install langchain-azure-ai with tools extra
-          python -m uv pip install "./libs/partners/azure-ai[tools]" --overrides ./docs/vercel_overrides.txt --prerelease=allow
-
-          # Install core langchain and other main packages
-          python -m uv pip install libs/core libs/langchain libs/text-splitters libs/community libs/experimental libs/standard-tests
-
-          # Install Sphinx and related packages for building docs
-          python -m uv pip install -r docs/api_reference/requirements.txt
-
-      - name: "🔧 Configure Git Settings"
-        working-directory: langchain
-        run: |
-          git config --local user.email "actions@github.com"
-          git config --local user.name "Github Actions"
-
-      - name: "📚 Build API Documentation"
-        working-directory: langchain
-        run: |
-          # Generate the API reference RST files
-          python docs/api_reference/create_api_rst.py
-
-          # Build the HTML documentation using Sphinx
-          # -T: show full traceback on exception
-          # -E: don't use cached environment (force rebuild, ignore cached doctrees)
-          # -b html: build HTML docs (vs PDS, etc.)
-          # -d: path for the cached environment (parsed document trees / doctrees)
-          #     - Separate from output dir for faster incremental builds
-          # -c: path to conf.py
-          # -j auto: parallel build using all available CPU cores
-          python -m sphinx -T -E -b html -d ../langchain-api-docs-html/_build/doctrees -c docs/api_reference docs/api_reference ../langchain-api-docs-html/api_reference_build/html -j auto
-
-          # Post-process the generated HTML
-          python docs/api_reference/scripts/custom_formatter.py ../langchain-api-docs-html/api_reference_build/html
-
-          # Default index page is blank so we copy in the actual home page.
-          cp ../langchain-api-docs-html/api_reference_build/html/{reference,index}.html
-
-          # Removes Sphinx's intermediate build artifacts after the build is complete.
-          rm -rf ../langchain-api-docs-html/_build/
-
-      # Commit and push changes to langchain-api-docs-html repo
-      - uses: EndBug/add-and-commit@v9
-        with:
-          cwd: langchain-api-docs-html
-          message: "Update API docs build from v0.3 branch"

.gitignore

@@ -1,8 +1,5 @@
-.vs/
-.claude/
+.vscode/
 .idea/
-#Emacs backup
-*~
 # Byte-compiled / optimized / DLL files
 __pycache__/
 *.py[cod]
@@ -32,12 +29,6 @@ share/python-wheels/
 *.egg
 MANIFEST
 
-# Google GitHub Actions credentials files created by:
-# https://github.com/google-github-actions/auth
-#
-# That action recommends adding this gitignore to prevent accidentally committing keys.
-gha-creds-*.json
-
 # PyInstaller
 #  Usually these files are written by a python script from a template
 #  before PyInstaller builds the exe, so as to inject date/other infos into it.
@@ -61,7 +52,6 @@ coverage.xml
 *.py,cover
 .hypothesis/
 .pytest_cache/
-.codspeed/
 
 # Translations
 *.mo
@@ -80,6 +70,9 @@ instance/
 # Scrapy stuff:
 .scrapy
 
+# Sphinx documentation
+docs/_build/
+
 # PyBuilder
 target/
 
@@ -114,11 +107,13 @@ celerybeat.pid
 # Environments
 .env
 .envrc
-.venv*
-venv*
+.venv
+.venvs
 env/
+venv/
 ENV/
 env.bak/
+venv.bak/
 
 # Spyder project settings
 .spyderproject
@@ -132,7 +127,6 @@ env.bak/
 
 # mypy
 .mypy_cache/
-.mypy_cache_test/
 .dmypy.json
 dmypy.json
 
@@ -142,27 +136,5 @@ dmypy.json
 # macOS display setting files
 .DS_Store
 
-# Wandb directory
-wandb/
-
 # asdf tool versions
-.tool-versions
-/.ruff_cache/
-
-*.pkl
-*.bin
-
-# integration test artifacts
-data_map*
-\[('_type', 'fake'), ('stop', None)]
-
-# Replit files
-*replit*
-
-node_modules
-
-prof
-virtualenv/
-scratch/
-
-.langgraph_api/
+.tool-versions

.markdownlint.json

@@ -1,14 +0,0 @@
-{
-  "MD013": false,
-  "MD024": {
-    "siblings_only": true
-  },
-  "MD025": false,
-  "MD033": false,
-  "MD034": false,
-  "MD036": false,
-  "MD041": false,
-  "MD046": {
-    "style": "fenced"
-  }
-}

.mcp.json

@@ -1,8 +0,0 @@
-{
-  "mcpServers": {
-    "docs-langchain": {
-      "type": "http",
-      "url": "https://docs.langchain.com/mcp"
-    }
-  }
-}

.pre-commit-config.yaml

@@ -1,119 +0,0 @@
-repos:
-  - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v4.3.0
-    hooks:
-      - id: no-commit-to-branch # prevent direct commits to protected branches
-        args: ["--branch", "master"]
-      - id: check-yaml # validate YAML syntax
-        args: ["--unsafe"] # allow custom tags
-      - id: check-toml # validate TOML syntax
-      - id: end-of-file-fixer # ensure files end with a newline
-      - id: trailing-whitespace # remove trailing whitespace from lines
-        exclude: \.ambr$
-
-  # Text normalization hooks for consistent formatting
-  - repo: https://github.com/sirosen/texthooks
-    rev: 0.6.8
-    hooks:
-      - id: fix-smartquotes # replace curly quotes with straight quotes
-      - id: fix-spaces # replace non-standard spaces (e.g., non-breaking) with regular spaces
-
-  # Per-package format and lint hooks for the monorepo
-  - repo: local
-    hooks:
-      - id: core
-        name: format and lint core
-        language: system
-        entry: make -C libs/core format lint
-        files: ^libs/core/
-        pass_filenames: false
-      - id: langchain
-        name: format and lint langchain
-        language: system
-        entry: make -C libs/langchain format lint
-        files: ^libs/langchain/
-        pass_filenames: false
-      - id: standard-tests
-        name: format and lint standard-tests
-        language: system
-        entry: make -C libs/standard-tests format lint
-        files: ^libs/standard-tests/
-        pass_filenames: false
-      - id: text-splitters
-        name: format and lint text-splitters
-        language: system
-        entry: make -C libs/text-splitters format lint
-        files: ^libs/text-splitters/
-        pass_filenames: false
-      - id: anthropic
-        name: format and lint partners/anthropic
-        language: system
-        entry: make -C libs/partners/anthropic format lint
-        files: ^libs/partners/anthropic/
-        pass_filenames: false
-      - id: chroma
-        name: format and lint partners/chroma
-        language: system
-        entry: make -C libs/partners/chroma format lint
-        files: ^libs/partners/chroma/
-        pass_filenames: false
-      - id: exa
-        name: format and lint partners/exa
-        language: system
-        entry: make -C libs/partners/exa format lint
-        files: ^libs/partners/exa/
-        pass_filenames: false
-      - id: fireworks
-        name: format and lint partners/fireworks
-        language: system
-        entry: make -C libs/partners/fireworks format lint
-        files: ^libs/partners/fireworks/
-        pass_filenames: false
-      - id: groq
-        name: format and lint partners/groq
-        language: system
-        entry: make -C libs/partners/groq format lint
-        files: ^libs/partners/groq/
-        pass_filenames: false
-      - id: huggingface
-        name: format and lint partners/huggingface
-        language: system
-        entry: make -C libs/partners/huggingface format lint
-        files: ^libs/partners/huggingface/
-        pass_filenames: false
-      - id: mistralai
-        name: format and lint partners/mistralai
-        language: system
-        entry: make -C libs/partners/mistralai format lint
-        files: ^libs/partners/mistralai/
-        pass_filenames: false
-      - id: nomic
-        name: format and lint partners/nomic
-        language: system
-        entry: make -C libs/partners/nomic format lint
-        files: ^libs/partners/nomic/
-        pass_filenames: false
-      - id: ollama
-        name: format and lint partners/ollama
-        language: system
-        entry: make -C libs/partners/ollama format lint
-        files: ^libs/partners/ollama/
-        pass_filenames: false
-      - id: openai
-        name: format and lint partners/openai
-        language: system
-        entry: make -C libs/partners/openai format lint
-        files: ^libs/partners/openai/
-        pass_filenames: false
-      - id: prompty
-        name: format and lint partners/prompty
-        language: system
-        entry: make -C libs/partners/prompty format lint
-        files: ^libs/partners/prompty/
-        pass_filenames: false
-      - id: qdrant
-        name: format and lint partners/qdrant
-        language: system
-        entry: make -C libs/partners/qdrant format lint
-        files: ^libs/partners/qdrant/
-        pass_filenames: false

.vscode/extensions.json

@@ -1,19 +0,0 @@
-{
-  "recommendations": [
-    "ms-python.python",
-    "charliermarsh.ruff",
-    "ms-python.mypy-type-checker",
-    "ms-toolsai.jupyter",
-    "ms-toolsai.jupyter-keymap",
-    "ms-toolsai.jupyter-renderers",
-    "yzhang.markdown-all-in-one",
-    "davidanson.vscode-markdownlint",
-    "bierner.markdown-mermaid",
-    "bierner.markdown-preview-github-styles",
-    "eamodio.gitlens",
-    "github.vscode-pull-request-github",
-    "github.vscode-github-actions",
-    "redhat.vscode-yaml",
-    "editorconfig.editorconfig",
-  ],
-}

.vscode/settings.json

@@ -1,78 +0,0 @@
-{
-  "python.analysis.include": [
-    "libs/**",
-  ],
-  "python.analysis.exclude": [
-    "**/node_modules",
-    "**/__pycache__",
-    "**/.pytest_cache",
-    "**/.*",
-  ],
-  "python.analysis.autoImportCompletions": true,
-  "python.analysis.typeCheckingMode": "basic",
-  "python.testing.cwd": "${workspaceFolder}",
-  "python.linting.enabled": true,
-  "python.linting.ruffEnabled": true,
-  "[python]": {
-    "editor.formatOnSave": true,
-    "editor.codeActionsOnSave": {
-      "source.organizeImports.ruff": "explicit",
-      "source.fixAll": "explicit"
-    },
-    "editor.defaultFormatter": "charliermarsh.ruff"
-  },
-  "editor.rulers": [
-    88
-  ],
-  "editor.tabSize": 4,
-  "editor.insertSpaces": true,
-  "editor.trimAutoWhitespace": true,
-  "files.trimTrailingWhitespace": true,
-  "files.insertFinalNewline": true,
-  "files.exclude": {
-    "**/__pycache__": true,
-    "**/.pytest_cache": true,
-    "**/*.pyc": true,
-    "**/.mypy_cache": true,
-    "**/.ruff_cache": true,
-    "_dist/**": true,
-    "**/node_modules": true,
-    "**/.git": false
-  },
-  "search.exclude": {
-    "**/__pycache__": true,
-    "**/*.pyc": true,
-    "_dist/**": true,
-    "**/node_modules": true,
-    "**/.git": true,
-    "uv.lock": true,
-    "yarn.lock": true
-  },
-  "git.autofetch": true,
-  "git.enableSmartCommit": true,
-  "jupyter.askForKernelRestart": false,
-  "jupyter.interactiveWindow.textEditor.executeSelection": true,
-  "[markdown]": {
-    "editor.wordWrap": "on",
-    "editor.quickSuggestions": {
-      "comments": "off",
-      "strings": "off",
-      "other": "off"
-    }
-  },
-  "[yaml]": {
-    "editor.tabSize": 2,
-    "editor.insertSpaces": true
-  },
-  "[json]": {
-    "editor.tabSize": 2,
-    "editor.insertSpaces": true
-  },
-  "python.terminal.activateEnvironment": false,
-  "python.defaultInterpreterPath": "./.venv/bin/python",
-  "github.copilot.chat.commitMessageGeneration.instructions": [
-    {
-      "file": ".github/workflows/pr_lint.yml"
-    }
-  ]
-}

AGENTS.md

@@ -1,181 +0,0 @@
-# Global development guidelines for the LangChain monorepo
-
-This document provides context to understand the LangChain Python project and assist with development.
-
-## Project architecture and context
-
-### Monorepo structure
-
-This is a Python monorepo with multiple independently versioned packages that use `uv`.
-
-```txt
-langchain/
-├── libs/
-│   ├── core/             # `langchain-core` primitives and base abstractions
-│   ├── langchain/        # `langchain-classic` (legacy, no new features)
-│   ├── langchain_v1/     # Actively maintained `langchain` package
-│   ├── partners/         # Third-party integrations
-│   │   ├── openai/       # OpenAI models and embeddings
-│   │   ├── anthropic/    # Anthropic (Claude) integration
-│   │   ├── ollama/       # Local model support
-│   │   └── ... (other integrations maintained by the LangChain team)
-│   ├── text-splitters/   # Document chunking utilities
-│   ├── standard-tests/   # Shared test suite for integrations
-│   ├── model-profiles/   # Model configuration profiles
-│   └── cli/              # Command-line interface tools
-├── .github/              # CI/CD workflows and templates
-├── .vscode/              # VSCode IDE standard settings and recommended extensions
-└── README.md             # Information about LangChain
-```
-
-- **Core layer** (`langchain-core`): Base abstractions, interfaces, and protocols. Users should not need to know about this layer directly.
-- **Implementation layer** (`langchain`): Concrete implementations and high-level public utilities
-- **Integration layer** (`partners/`): Third-party service integrations. Note that this monorepo is not exhaustive of all LangChain integrations; some are maintained in separate repos, such as `langchain-ai/langchain-google` and `langchain-ai/langchain-aws`. Usually these repos are cloned at the same level as this monorepo, so if needed, you can refer to their code directly by navigating to `../langchain-google/` from this monorepo.
-- **Testing layer** (`standard-tests/`): Standardized integration tests for partner integrations
-
-### Development tools & commands**
-
-- `uv` – Fast Python package installer and resolver (replaces pip/poetry)
-- `make` – Task runner for common development commands. Feel free to look at the `Makefile` for available commands and usage patterns.
-- `ruff` – Fast Python linter and formatter
-- `mypy` – Static type checking
-- `pytest` – Testing framework
-
-This monorepo uses `uv` for dependency management. Local development uses editable installs: `[tool.uv.sources]`
-
-Each package in `libs/` has its own `pyproject.toml` and `uv.lock`.
-
-```bash
-# Run unit tests (no network)
-make test
-
-# Run specific test file
-uv run --group test pytest tests/unit_tests/test_specific.py
-```
-
-```bash
-# Lint code
-make lint
-
-# Format code
-make format
-
-# Type checking
-uv run --group lint mypy .
-```
-
-#### Key config files
-
-- pyproject.toml: Main workspace configuration with dependency groups
-- uv.lock: Locked dependencies for reproducible builds
-- Makefile: Development tasks
-
-#### Commit standards
-
-Suggest PR titles that follow Conventional Commits format. Refer to .github/workflows/pr_lint for allowed types and scopes.
-
-#### Pull request guidelines
-
-- Always add a disclaimer to the PR description mentioning how AI agents are involved with the contribution.
-- Describe the "why" of the changes, why the proposed solution is the right one. Limit prose.
-- Highlight areas of the proposed changes that require careful review.
-
-## Core development principles
-
-### Maintain stable public interfaces
-
-CRITICAL: Always attempt to preserve function signatures, argument positions, and names for exported/public methods. Do not make breaking changes.
-
-**Before making ANY changes to public APIs:**
-
-- Check if the function/class is exported in `__init__.py`
-- Look for existing usage patterns in tests and examples
-- Use keyword-only arguments for new parameters: `*, new_param: str = "default"`
-- Mark experimental features clearly with docstring warnings (using MkDocs Material admonitions, like `!!! warning`)
-
-Ask: "Would this change break someone's code if they used it last week?"
-
-### Code quality standards
-
-All Python code MUST include type hints and return types.
-
-```python title="Example"
-def filter_unknown_users(users: list[str], known_users: set[str]) -> list[str]:
-    """Single line description of the function.
-
-    Any additional context about the function can go here.
-
-    Args:
-        users: List of user identifiers to filter.
-        known_users: Set of known/valid user identifiers.
-
-    Returns:
-        List of users that are not in the known_users set.
-    """
-```
-
-- Use descriptive, self-explanatory variable names.
-- Follow existing patterns in the codebase you're modifying
-- Attempt to break up complex functions (>20 lines) into smaller, focused functions where it makes sense
-
-### Testing requirements
-
-Every new feature or bugfix MUST be covered by unit tests.
-
-- Unit tests: `tests/unit_tests/` (no network calls allowed)
-- Integration tests: `tests/integration_tests/` (network calls permitted)
-- We use `pytest` as the testing framework; if in doubt, check other existing tests for examples.
-- The testing file structure should mirror the source code structure.
-
-**Checklist:**
-
-- [ ] Tests fail when your new logic is broken
-- [ ] Happy path is covered
-- [ ] Edge cases and error conditions are tested
-- [ ] Use fixtures/mocks for external dependencies
-- [ ] Tests are deterministic (no flaky tests)
-- [ ] Does the test suite fail if your new logic is broken?
-
-### Security and risk assessment
-
-- No `eval()`, `exec()`, or `pickle` on user-controlled input
-- Proper exception handling (no bare `except:`) and use a `msg` variable for error messages
-- Remove unreachable/commented code before committing
-- Race conditions or resource leaks (file handles, sockets, threads).
-- Ensure proper resource cleanup (file handles, connections)
-
-### Documentation standards
-
-Use Google-style docstrings with Args section for all public functions.
-
-```python title="Example"
-def send_email(to: str, msg: str, *, priority: str = "normal") -> bool:
-    """Send an email to a recipient with specified priority.
-
-    Any additional context about the function can go here.
-
-    Args:
-        to: The email address of the recipient.
-        msg: The message body to send.
-        priority: Email priority level.
-
-    Returns:
-        `True` if email was sent successfully, `False` otherwise.
-
-    Raises:
-        InvalidEmailError: If the email address format is invalid.
-        SMTPConnectionError: If unable to connect to email server.
-    """
-```
-
-- Types go in function signatures, NOT in docstrings
-  - If a default is present, DO NOT repeat it in the docstring unless there is post-processing or it is set conditionally.
-- Focus on "why" rather than "what" in descriptions
-- Document all parameters, return values, and exceptions
-- Keep descriptions concise but clear
-- Ensure American English spelling (e.g., "behavior", not "behaviour")
-
-## Additional resources
-
-- **Documentation:** https://docs.langchain.com/oss/python/langchain/overview and source at https://github.com/langchain-ai/docs or `../docs/`. Prefer the local install and use file search tools for best results. If needed, use the docs MCP server as defined in `.mcp.json` for programmatic access.
-- **Contributing Guide:** [`.github/CONTRIBUTING.md`](https://docs.langchain.com/oss/python/contributing/overview)

CITATION.cff

@@ -5,4 +5,4 @@ authors:
   given-names: "Harrison"
 title: "LangChain"
 date-released: 2022-10-17
-url: "https://github.com/langchain-ai/langchain"
+url: "https://github.com/hwchase17/langchain"

CLAUDE.md

@@ -1,181 +0,0 @@
-# Global development guidelines for the LangChain monorepo
-
-This document provides context to understand the LangChain Python project and assist with development.
-
-## Project architecture and context
-
-### Monorepo structure
-
-This is a Python monorepo with multiple independently versioned packages that use `uv`.
-
-```txt
-langchain/
-├── libs/
-│   ├── core/             # `langchain-core` primitives and base abstractions
-│   ├── langchain/        # `langchain-classic` (legacy, no new features)
-│   ├── langchain_v1/     # Actively maintained `langchain` package
-│   ├── partners/         # Third-party integrations
-│   │   ├── openai/       # OpenAI models and embeddings
-│   │   ├── anthropic/    # Anthropic (Claude) integration
-│   │   ├── ollama/       # Local model support
-│   │   └── ... (other integrations maintained by the LangChain team)
-│   ├── text-splitters/   # Document chunking utilities
-│   ├── standard-tests/   # Shared test suite for integrations
-│   ├── model-profiles/   # Model configuration profiles
-│   └── cli/              # Command-line interface tools
-├── .github/              # CI/CD workflows and templates
-├── .vscode/              # VSCode IDE standard settings and recommended extensions
-└── README.md             # Information about LangChain
-```
-
-- **Core layer** (`langchain-core`): Base abstractions, interfaces, and protocols. Users should not need to know about this layer directly.
-- **Implementation layer** (`langchain`): Concrete implementations and high-level public utilities
-- **Integration layer** (`partners/`): Third-party service integrations. Note that this monorepo is not exhaustive of all LangChain integrations; some are maintained in separate repos, such as `langchain-ai/langchain-google` and `langchain-ai/langchain-aws`. Usually these repos are cloned at the same level as this monorepo, so if needed, you can refer to their code directly by navigating to `../langchain-google/` from this monorepo.
-- **Testing layer** (`standard-tests/`): Standardized integration tests for partner integrations
-
-### Development tools & commands**
-
-- `uv` – Fast Python package installer and resolver (replaces pip/poetry)
-- `make` – Task runner for common development commands. Feel free to look at the `Makefile` for available commands and usage patterns.
-- `ruff` – Fast Python linter and formatter
-- `mypy` – Static type checking
-- `pytest` – Testing framework
-
-This monorepo uses `uv` for dependency management. Local development uses editable installs: `[tool.uv.sources]`
-
-Each package in `libs/` has its own `pyproject.toml` and `uv.lock`.
-
-```bash
-# Run unit tests (no network)
-make test
-
-# Run specific test file
-uv run --group test pytest tests/unit_tests/test_specific.py
-```
-
-```bash
-# Lint code
-make lint
-
-# Format code
-make format
-
-# Type checking
-uv run --group lint mypy .
-```
-
-#### Key config files
-
-- pyproject.toml: Main workspace configuration with dependency groups
-- uv.lock: Locked dependencies for reproducible builds
-- Makefile: Development tasks
-
-#### Commit standards
-
-Suggest PR titles that follow Conventional Commits format. Refer to .github/workflows/pr_lint for allowed types and scopes.
-
-#### Pull request guidelines
-
-- Always add a disclaimer to the PR description mentioning how AI agents are involved with the contribution.
-- Describe the "why" of the changes, why the proposed solution is the right one. Limit prose.
-- Highlight areas of the proposed changes that require careful review.
-
-## Core development principles
-
-### Maintain stable public interfaces
-
-CRITICAL: Always attempt to preserve function signatures, argument positions, and names for exported/public methods. Do not make breaking changes.
-
-**Before making ANY changes to public APIs:**
-
-- Check if the function/class is exported in `__init__.py`
-- Look for existing usage patterns in tests and examples
-- Use keyword-only arguments for new parameters: `*, new_param: str = "default"`
-- Mark experimental features clearly with docstring warnings (using MkDocs Material admonitions, like `!!! warning`)
-
-Ask: "Would this change break someone's code if they used it last week?"
-
-### Code quality standards
-
-All Python code MUST include type hints and return types.
-
-```python title="Example"
-def filter_unknown_users(users: list[str], known_users: set[str]) -> list[str]:
-    """Single line description of the function.
-
-    Any additional context about the function can go here.
-
-    Args:
-        users: List of user identifiers to filter.
-        known_users: Set of known/valid user identifiers.
-
-    Returns:
-        List of users that are not in the known_users set.
-    """
-```
-
-- Use descriptive, self-explanatory variable names.
-- Follow existing patterns in the codebase you're modifying
-- Attempt to break up complex functions (>20 lines) into smaller, focused functions where it makes sense
-
-### Testing requirements
-
-Every new feature or bugfix MUST be covered by unit tests.
-
-- Unit tests: `tests/unit_tests/` (no network calls allowed)
-- Integration tests: `tests/integration_tests/` (network calls permitted)
-- We use `pytest` as the testing framework; if in doubt, check other existing tests for examples.
-- The testing file structure should mirror the source code structure.
-
-**Checklist:**
-
-- [ ] Tests fail when your new logic is broken
-- [ ] Happy path is covered
-- [ ] Edge cases and error conditions are tested
-- [ ] Use fixtures/mocks for external dependencies
-- [ ] Tests are deterministic (no flaky tests)
-- [ ] Does the test suite fail if your new logic is broken?
-
-### Security and risk assessment
-
-- No `eval()`, `exec()`, or `pickle` on user-controlled input
-- Proper exception handling (no bare `except:`) and use a `msg` variable for error messages
-- Remove unreachable/commented code before committing
-- Race conditions or resource leaks (file handles, sockets, threads).
-- Ensure proper resource cleanup (file handles, connections)
-
-### Documentation standards
-
-Use Google-style docstrings with Args section for all public functions.
-
-```python title="Example"
-def send_email(to: str, msg: str, *, priority: str = "normal") -> bool:
-    """Send an email to a recipient with specified priority.
-
-    Any additional context about the function can go here.
-
-    Args:
-        to: The email address of the recipient.
-        msg: The message body to send.
-        priority: Email priority level.
-
-    Returns:
-        `True` if email was sent successfully, `False` otherwise.
-
-    Raises:
-        InvalidEmailError: If the email address format is invalid.
-        SMTPConnectionError: If unable to connect to email server.
-    """
-```
-
-- Types go in function signatures, NOT in docstrings
-  - If a default is present, DO NOT repeat it in the docstring unless there is post-processing or it is set conditionally.
-- Focus on "why" rather than "what" in descriptions
-- Document all parameters, return values, and exceptions
-- Keep descriptions concise but clear
-- Ensure American English spelling (e.g., "behavior", not "behaviour")
-
-## Additional resources
-
-- **Documentation:** https://docs.langchain.com/oss/python/langchain/overview and source at https://github.com/langchain-ai/docs or `../docs/`. Prefer the local install and use file search tools for best results. If needed, use the docs MCP server as defined in `.mcp.json` for programmatic access.
-- **Contributing Guide:** [`.github/CONTRIBUTING.md`](https://docs.langchain.com/oss/python/contributing/overview)

LICENSE

@@ -1,6 +1,6 @@
-MIT License
+The MIT License
 
-Copyright (c) LangChain, Inc.
+Copyright (c) Harrison Chase
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -9,13 +9,13 @@ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 copies of the Software, and to permit persons to whom the Software is
 furnished to do so, subject to the following conditions:
 
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

Makefile

@@ -0,0 +1,53 @@
+.PHONY: all clean format lint test tests test_watch integration_tests help
+
+all: help
+	
+coverage:
+	poetry run pytest --cov \
+		--cov-config=.coveragerc \
+		--cov-report xml \
+		--cov-report term-missing:skip-covered
+
+clean: docs_clean
+
+docs_build:
+	cd docs && poetry run make html
+
+docs_clean:
+	cd docs && poetry run make clean
+
+docs_linkcheck:
+	poetry run linkchecker docs/_build/html/index.html
+
+format:
+	poetry run black .
+	poetry run ruff --select I --fix .
+
+lint:
+	poetry run mypy .
+	poetry run black . --check
+	poetry run ruff .
+
+test:
+	poetry run pytest tests/unit_tests
+
+tests:
+	poetry run pytest tests/unit_tests
+
+test_watch:
+	poetry run ptw --now . -- tests/unit_tests
+
+integration_tests:
+	poetry run pytest tests/integration_tests
+
+help:
+	@echo '----'
+	@echo 'coverage            - run unit tests and generate coverage report'
+	@echo 'docs_build          - build the documentation'
+	@echo 'docs_clean          - clean the documentation build artifacts'
+	@echo 'docs_linkcheck      - run linkchecker on the documentation'
+	@echo 'format              - run code formatters'
+	@echo 'lint                - run linters'
+	@echo 'test                - run unit tests'
+	@echo 'test_watch          - run unit tests in watch mode'
+	@echo 'integration_tests   - run integration tests'

README.md

@@ -1,75 +1,82 @@
-<div align="center">
-  <a href="https://www.langchain.com/">
-    <picture>
-      <source media="(prefers-color-scheme: light)" srcset=".github/images/logo-dark.svg">
-      <source media="(prefers-color-scheme: dark)" srcset=".github/images/logo-light.svg">
-      <img alt="LangChain Logo" src=".github/images/logo-dark.svg" width="80%">
-    </picture>
-  </a>
-</div>
+# 🦜️🔗 LangChain
 
-<div align="center">
-  <h3>The platform for reliable agents.</h3>
-</div>
+⚡ Building applications with LLMs through composability ⚡
 
-<div align="center">
-  <a href="https://opensource.org/licenses/MIT" target="_blank"><img src="https://img.shields.io/pypi/l/langchain" alt="PyPI - License"></a>
-  <a href="https://pypistats.org/packages/langchain" target="_blank"><img src="https://img.shields.io/pepy/dt/langchain" alt="PyPI - Downloads"></a>
-  <a href="https://pypi.org/project/langchain/#history" target="_blank"><img src="https://img.shields.io/pypi/v/langchain?label=%20" alt="Version"></a>
-  <a href="https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/langchain-ai/langchain" target="_blank"><img src="https://img.shields.io/static/v1?label=Dev%20Containers&message=Open&color=blue&logo=visualstudiocode" alt="Open in Dev Containers"></a>
-  <a href="https://codespaces.new/langchain-ai/langchain" target="_blank"><img src="https://github.com/codespaces/badge.svg" alt="Open in Github Codespace" title="Open in Github Codespace" width="150" height="20"></a>
-  <a href="https://codspeed.io/langchain-ai/langchain" target="_blank"><img src="https://img.shields.io/endpoint?url=https://codspeed.io/badge.json" alt="CodSpeed Badge"></a>
-  <a href="https://x.com/langchain" target="_blank"><img src="https://img.shields.io/twitter/url/https/twitter.com/langchain.svg?style=social&label=Follow%20%40LangChain" alt="Twitter / X"></a>
-</div>
+[![lint](https://github.com/hwchase17/langchain/actions/workflows/lint.yml/badge.svg)](https://github.com/hwchase17/langchain/actions/workflows/lint.yml) [![test](https://github.com/hwchase17/langchain/actions/workflows/test.yml/badge.svg)](https://github.com/hwchase17/langchain/actions/workflows/test.yml) [![linkcheck](https://github.com/hwchase17/langchain/actions/workflows/linkcheck.yml/badge.svg)](https://github.com/hwchase17/langchain/actions/workflows/linkcheck.yml) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) [![Twitter](https://img.shields.io/twitter/url/https/twitter.com/langchainai.svg?style=social&label=Follow%20%40LangChainAI)](https://twitter.com/langchainai) [![](https://dcbadge.vercel.app/api/server/6adMQxSpJS?compact=true&style=flat)](https://discord.gg/6adMQxSpJS)
 
-LangChain is a framework for building agents and LLM-powered applications. It helps you chain together interoperable components and third-party integrations to simplify AI application development – all while future-proofing decisions as the underlying technology evolves.
+**Production Support:** As you move your LangChains into production, we'd love to offer more comprehensive support.
+Please fill out [this form](https://forms.gle/57d8AmXBYp8PP8tZA) and we'll set up a dedicated support Slack channel.
 
-```bash
-pip install langchain
-```
+## Quick Install
 
-If you're looking for more advanced customization or agent orchestration, check out [LangGraph](https://docs.langchain.com/oss/python/langgraph/overview), our framework for building controllable agent workflows.
+`pip install langchain`
 
----
+## 🤔 What is this?
 
-**Documentation**:
+Large language models (LLMs) are emerging as a transformative technology, enabling
+developers to build applications that they previously could not.
+But using these LLMs in isolation is often not enough to
+create a truly powerful app - the real power comes when you can combine them with other sources of computation or knowledge.
 
-- [docs.langchain.com](https://docs.langchain.com/oss/python/langchain/overview) – Comprehensive documentation, including conceptual overviews and guides
-- [reference.langchain.com/python](https://reference.langchain.com/python) – API reference docs for LangChain packages
+This library is aimed at assisting in the development of those types of applications. Common examples of these types of applications include:
 
-**Discussions**: Visit the [LangChain Forum](https://forum.langchain.com) to connect with the community and share all of your technical questions, ideas, and feedback.
+**❓ Question Answering over specific documents**
 
-> [!NOTE]
-> Looking for the JS/TS library? Check out [LangChain.js](https://github.com/langchain-ai/langchainjs).
+- [Documentation](https://langchain.readthedocs.io/en/latest/use_cases/question_answering.html)
+- End-to-end Example: [Question Answering over Notion Database](https://github.com/hwchase17/notion-qa)
 
-## Why use LangChain?
+**💬 Chatbots**
 
-LangChain helps developers build applications powered by LLMs through a standard interface for models, embeddings, vector stores, and more.
+- [Documentation](https://langchain.readthedocs.io/en/latest/use_cases/chatbots.html)
+- End-to-end Example: [Chat-LangChain](https://github.com/hwchase17/chat-langchain)
 
-Use LangChain for:
+**🤖 Agents**
 
-- **Real-time data augmentation**. Easily connect LLMs to diverse data sources and external/internal systems, drawing from LangChain's vast library of integrations with model providers, tools, vector stores, retrievers, and more.
-- **Model interoperability**. Swap models in and out as your engineering team experiments to find the best choice for your application's needs. As the industry frontier evolves, adapt quickly – LangChain's abstractions keep you moving without losing momentum.
-- **Rapid prototyping**. Quickly build and iterate on LLM applications with LangChain's modular, component-based architecture. Test different approaches and workflows without rebuilding from scratch, accelerating your development cycle.
-- **Production-ready features**. Deploy reliable applications with built-in support for monitoring, evaluation, and debugging through integrations like LangSmith. Scale with confidence using battle-tested patterns and best practices.
-- **Vibrant community and ecosystem**. Leverage a rich ecosystem of integrations, templates, and community-contributed components. Benefit from continuous improvements and stay up-to-date with the latest AI developments through an active open-source community.
-- **Flexible abstraction layers**. Work at the level of abstraction that suits your needs - from high-level chains for quick starts to low-level components for fine-grained control. LangChain grows with your application's complexity.
+- [Documentation](https://langchain.readthedocs.io/en/latest/use_cases/agents.html)
+- End-to-end Example: [GPT+WolframAlpha](https://huggingface.co/spaces/JavaFXpert/Chat-GPT-LangChain)
 
-## LangChain ecosystem
+## 📖 Documentation
 
-While the LangChain framework can be used standalone, it also integrates seamlessly with any LangChain product, giving developers a full suite of tools when building LLM applications.
+Please see [here](https://langchain.readthedocs.io/en/latest/?) for full documentation on:
 
-To improve your LLM application development, pair LangChain with:
+- Getting started (installation, setting up the environment, simple examples)
+- How-To examples (demos, integrations, helper functions)
+- Reference (full API docs)
+- Resources (high-level explanation of core concepts)
 
-- [LangGraph](https://docs.langchain.com/oss/python/langgraph/overview) – Build agents that can reliably handle complex tasks with LangGraph, our low-level agent orchestration framework. LangGraph offers customizable architecture, long-term memory, and human-in-the-loop workflows – and is trusted in production by companies like LinkedIn, Uber, Klarna, and GitLab.
-- [Integrations](https://docs.langchain.com/oss/python/integrations/providers/overview) – List of LangChain integrations, including chat & embedding models, tools & toolkits, and more
-- [LangSmith](https://www.langchain.com/langsmith) – Helpful for agent evals and observability. Debug poor-performing LLM app runs, evaluate agent trajectories, gain visibility in production, and improve performance over time.
-- [LangSmith Deployment](https://docs.langchain.com/langsmith/deployments) – Deploy and scale agents effortlessly with a purpose-built deployment platform for long-running, stateful workflows. Discover, reuse, configure, and share agents across teams – and iterate quickly with visual prototyping in [LangSmith Studio](https://docs.langchain.com/langsmith/studio).
-- [Deep Agents](https://github.com/langchain-ai/deepagents) *(new!)* – Build agents that can plan, use subagents, and leverage file systems for complex tasks
+## 🚀 What can this help with?
 
-## Additional resources
+There are six main areas that LangChain is designed to help with.
+These are, in increasing order of complexity:
 
-- [API Reference](https://reference.langchain.com/python) – Detailed reference on navigating base packages and integrations for LangChain.
-- [Contributing Guide](https://docs.langchain.com/oss/python/contributing/overview) – Learn how to contribute to LangChain projects and find good first issues.
-- [Code of Conduct](https://github.com/langchain-ai/langchain/?tab=coc-ov-file) – Our community guidelines and standards for participation.
-- [LangChain Academy](https://academy.langchain.com/) – Comprehensive, free courses on LangChain libraries and products, made by the LangChain team.
+**📃 LLMs and Prompts:**
+
+This includes prompt management, prompt optimization, generic interface for all LLMs, and common utilities for working with LLMs.
+
+**🔗 Chains:**
+
+Chains go beyond just a single LLM call, and are sequences of calls (whether to an LLM or a different utility). LangChain provides a standard interface for chains, lots of integrations with other tools, and end-to-end chains for common applications.
+
+**📚 Data Augmented Generation:**
+
+Data Augmented Generation involves specific types of chains that first interact with an external datasource to fetch data to use in the generation step. Examples of this include summarization of long pieces of text and question/answering over specific data sources.
+
+**🤖 Agents:**
+
+Agents involve an LLM making decisions about which Actions to take, taking that Action, seeing an Observation, and repeating that until done. LangChain provides a standard interface for agents, a selection of agents to choose from, and examples of end to end agents.
+
+**🧠 Memory:**
+
+Memory is the concept of persisting state between calls of a chain/agent. LangChain provides a standard interface for memory, a collection of memory implementations, and examples of chains/agents that use memory.
+
+**🧐 Evaluation:**
+
+[BETA] Generative models are notoriously hard to evaluate with traditional metrics. One new way of evaluating them is using language models themselves to do the evaluation. LangChain provides some prompts/chains for assisting in this.
+
+For more information on these concepts, please see our [full documentation](https://langchain.readthedocs.io/en/latest/?).
+
+## 💁 Contributing
+
+As an open source project in a rapidly developing field, we are extremely open to contributions, whether it be in the form of a new feature, improved infra, or better documentation.
+
+For detailed information on how to contribute, see [here](.github/CONTRIBUTING.md).

docs/Makefile

@@ -0,0 +1,21 @@
+# Minimal makefile for Sphinx documentation
+#
+
+# You can set these variables from the command line, and also
+# from the environment for the first two.
+SPHINXOPTS    ?= 
+SPHINXBUILD   ?= sphinx-build
+SPHINXAUTOBUILD   ?= sphinx-autobuild
+SOURCEDIR     = .
+BUILDDIR      = _build
+
+# Put it first so that "make" without argument is like "make help".
+help:
+	@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
+
+.PHONY: help Makefile
+
+# Catch-all target: route all unknown targets to Sphinx using the new
+# "make mode" option.  $(O) is meant as a shortcut for $(SPHINXOPTS).
+%: Makefile
+	@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)

docs/_static/css/custom.css

@@ -0,0 +1,13 @@
+pre {
+  white-space: break-spaces;
+}
+
+@media (min-width: 1200px) {
+  .container,
+  .container-lg,
+  .container-md,
+  .container-sm,
+  .container-xl {
+    max-width: 2560px !important;
+  }
+}

docs/conf.py

@@ -0,0 +1,107 @@
+"""Configuration file for the Sphinx documentation builder."""
+# Configuration file for the Sphinx documentation builder.
+#
+# This file only contains a selection of the most common options. For a full
+# list see the documentation:
+# https://www.sphinx-doc.org/en/master/usage/configuration.html
+
+# -- Path setup --------------------------------------------------------------
+
+# If extensions (or modules to document with autodoc) are in another directory,
+# add these directories to sys.path here. If the directory is relative to the
+# documentation root, use os.path.abspath to make it absolute, like shown here.
+#
+# import os
+# import sys
+# sys.path.insert(0, os.path.abspath('.'))
+
+import toml
+
+with open("../pyproject.toml") as f:
+    data = toml.load(f)
+
+# -- Project information -----------------------------------------------------
+
+project = "🦜🔗 LangChain"
+copyright = "2023, Harrison Chase"
+author = "Harrison Chase"
+
+version = data["tool"]["poetry"]["version"]
+release = version
+
+html_title = project + " " + version
+html_last_updated_fmt = "%b %d, %Y"
+
+
+# -- General configuration ---------------------------------------------------
+
+# Add any Sphinx extension module names here, as strings. They can be
+# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
+# ones.
+extensions = [
+    "sphinx.ext.autodoc",
+    "sphinx.ext.autodoc.typehints",
+    "sphinx.ext.autosummary",
+    "sphinx.ext.napoleon",
+    "sphinx.ext.viewcode",
+    "sphinxcontrib.autodoc_pydantic",
+    "myst_nb",
+    "sphinx_copybutton",
+    "sphinx_panels",
+    "IPython.sphinxext.ipython_console_highlighting",
+]
+source_suffix = [".ipynb", ".html", ".md", ".rst"]
+
+autodoc_pydantic_model_show_json = False
+autodoc_pydantic_field_list_validators = False
+autodoc_pydantic_config_members = False
+autodoc_pydantic_model_show_config_summary = False
+autodoc_pydantic_model_show_validator_members = False
+autodoc_pydantic_model_show_field_summary = False
+autodoc_pydantic_model_members = False
+autodoc_pydantic_model_undoc_members = False
+# autodoc_typehints = "signature"
+# autodoc_typehints = "description"
+
+# Add any paths that contain templates here, relative to this directory.
+templates_path = ["_templates"]
+
+# List of patterns, relative to source directory, that match files and
+# directories to ignore when looking for source files.
+# This pattern also affects html_static_path and html_extra_path.
+exclude_patterns = ["_build", "Thumbs.db", ".DS_Store"]
+
+
+# -- Options for HTML output -------------------------------------------------
+
+# The theme to use for HTML and HTML Help pages.  See the documentation for
+# a list of builtin themes.
+#
+html_theme = "sphinx_book_theme"
+
+html_theme_options = {
+    "path_to_docs": "docs",
+    "repository_url": "https://github.com/hwchase17/langchain",
+    "use_repository_button": True,
+}
+
+html_context = {
+    "display_github": True,  # Integrate GitHub
+    "github_user": "hwchase17",  # Username
+    "github_repo": "langchain",  # Repo name
+    "github_version": "master",  # Version
+    "conf_py_path": "/docs/",  # Path in the checkout to the docs root
+}
+
+# Add any paths that contain custom static files (such as style sheets) here,
+# relative to this directory. They are copied after the builtin static files,
+# so a file named "default.css" will overwrite the builtin "default.css".
+html_static_path = ["_static"]
+
+# These paths are either relative to html_static_path
+# or fully qualified paths (eg. https://...)
+html_css_files = [
+    "css/custom.css",
+]
+nb_execution_mode = "off"
+myst_enable_extensions = ["colon_fence"]

docs/deployments.md

@@ -0,0 +1,39 @@
+# Deployments
+
+So you've made a really cool chain - now what? How do you deploy it and make it easily sharable with the world?
+
+This section covers several options for that.
+Note that these are meant as quick deployment options for prototypes and demos, and not for production systems.
+If you are looking for help with deployment of a production system, please contact us directly.
+
+What follows is a list of template GitHub repositories aimed that are intended to be
+very easy to fork and modify to use your chain.
+This is far from an exhaustive list of options, and we are EXTREMELY open to contributions here.
+
+## [Streamlit](https://github.com/hwchase17/langchain-streamlit-template)
+
+This repo serves as a template for how to deploy a LangChain with Streamlit.
+It implements a chatbot interface.
+It also contains instructions for how to deploy this app on the Streamlit platform.
+
+## [Gradio (on Hugging Face)](https://github.com/hwchase17/langchain-gradio-template)
+
+This repo serves as a template for how deploy a LangChain with Gradio.
+It implements a chatbot interface, with a "Bring-Your-Own-Token" approach (nice for not wracking up big bills).
+It also contains instructions for how to deploy this app on the Hugging Face platform.
+This is heavily influenced by James Weaver's [excellent examples](https://huggingface.co/JavaFXpert).
+
+## [Beam](https://github.com/slai-labs/get-beam/tree/main/examples/langchain-question-answering)
+
+This repo serves as a template for how deploy a LangChain with [Beam](https://beam.cloud).
+
+It implements a Question Answering app and contains instructions for deploying the app as a serverless REST API.
+
+## [Vercel](https://github.com/homanp/vercel-langchain)
+
+A minimal example on how to run LangChain on Vercel using Flask.
+
+
+## [SteamShip](https://github.com/steamship-core/steamship-langchain/)
+This repository contains LangChain adapters for Steamship, enabling LangChain developers to rapidly deploy their apps on Steamship.
+This includes: production ready endpoints, horizontal scaling across dependencies, persistant storage of app state, multi-tenancy support, etc.

docs/ecosystem.rst

@@ -0,0 +1,10 @@
+LangChain Ecosystem
+===================
+
+Guides for how other companies/products can be used with LangChain
+
+.. toctree::
+   :maxdepth: 1
+   :glob:
+
+   ecosystem/*

docs/ecosystem/ai21.md

@@ -0,0 +1,16 @@
+# AI21 Labs
+
+This page covers how to use the AI21 ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific AI21 wrappers.
+
+## Installation and Setup
+- Get an AI21 api key and set it as an environment variable (`AI21_API_KEY`)
+
+## Wrappers
+
+### LLM
+
+There exists an AI21 LLM wrapper, which you can access with 
+```python
+from langchain.llms import AI21
+```

docs/ecosystem/atlas.md

@@ -0,0 +1,27 @@
+# AtlasDB
+
+This page covers how to use Nomic's Atlas ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific Atlas wrappers.
+
+## Installation and Setup
+- Install the Python package with `pip install nomic`
+- Nomic is also included in langchains poetry extras `poetry install -E all`
+
+## Wrappers
+
+### VectorStore
+
+There exists a wrapper around the Atlas neural database, allowing you to use it as a vectorstore.
+This vectorstore also gives you full access to the underlying AtlasProject object, which will allow you to use the full range of Atlas map interactions, such as bulk tagging and automatic topic modeling.
+Please see [the Atlas docs](https://docs.nomic.ai/atlas_api.html) for more detailed information.
+
+
+
+
+
+To import this vectorstore:
+```python
+from langchain.vectorstores import AtlasDB
+```
+
+For a more detailed walkthrough of the AtlasDB wrapper, see [this notebook](../modules/indexes/vectorstore_examples/atlas.ipynb)

docs/ecosystem/bananadev.md

@@ -0,0 +1,79 @@
+# Banana
+
+This page covers how to use the Banana ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific Banana wrappers.
+
+## Installation and Setup
+
+- Install with `pip install banana-dev`
+- Get an Banana api key and set it as an environment variable (`BANANA_API_KEY`)
+
+## Define your Banana Template
+
+If you want to use an available language model template you can find one [here](https://app.banana.dev/templates/conceptofmind/serverless-template-palmyra-base).
+This template uses the Palmyra-Base model by [Writer](https://writer.com/product/api/).
+You can check out an example Banana repository [here](https://github.com/conceptofmind/serverless-template-palmyra-base).
+
+## Build the Banana app
+
+Banana Apps must include the "output" key in the return json. 
+There is a rigid response structure.
+
+```python
+# Return the results as a dictionary
+result = {'output': result}
+```
+
+An example inference function would be:
+
+```python
+def inference(model_inputs:dict) -> dict:
+    global model
+    global tokenizer
+
+    # Parse out your arguments
+    prompt = model_inputs.get('prompt', None)
+    if prompt == None:
+        return {'message': "No prompt provided"}
+
+    # Run the model
+    input_ids = tokenizer.encode(prompt, return_tensors='pt').cuda()
+    output = model.generate(
+        input_ids,
+        max_length=100,
+        do_sample=True,
+        top_k=50,
+        top_p=0.95,
+        num_return_sequences=1,
+        temperature=0.9,
+        early_stopping=True,
+        no_repeat_ngram_size=3,
+        num_beams=5,
+        length_penalty=1.5,
+        repetition_penalty=1.5,
+        bad_words_ids=[[tokenizer.encode(' ', add_prefix_space=True)[0]]]
+        )
+
+    result = tokenizer.decode(output[0], skip_special_tokens=True)
+    # Return the results as a dictionary
+    result = {'output': result}
+    return result
+```
+
+You can find a full example of a Banana app [here](https://github.com/conceptofmind/serverless-template-palmyra-base/blob/main/app.py).
+
+## Wrappers
+
+### LLM
+
+There exists an Banana LLM wrapper, which you can access with
+
+```python
+from langchain.llms import Banana
+```
+
+You need to provide a model key located in the dashboard:
+
+```python
+llm = Banana(model_key="YOUR_MODEL_KEY")
+```

docs/ecosystem/cerebriumai.md

@@ -0,0 +1,17 @@
+# CerebriumAI
+
+This page covers how to use the CerebriumAI ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific CerebriumAI wrappers.
+
+## Installation and Setup
+- Install with `pip install cerebrium`
+- Get an CerebriumAI api key and set it as an environment variable (`CEREBRIUMAI_API_KEY`)
+
+## Wrappers
+
+### LLM
+
+There exists an CerebriumAI LLM wrapper, which you can access with 
+```python
+from langchain.llms import CerebriumAI
+```

docs/ecosystem/chroma.md

@@ -0,0 +1,20 @@
+# Chroma
+
+This page covers how to use the Chroma ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific Chroma wrappers.
+
+## Installation and Setup
+- Install the Python package with `pip install chromadb`
+## Wrappers
+
+### VectorStore
+
+There exists a wrapper around Chroma vector databases, allowing you to use it as a vectorstore,
+whether for semantic search or example selection.
+
+To import this vectorstore:
+```python
+from langchain.vectorstores import Chroma
+```
+
+For a more detailed walkthrough of the Chroma wrapper, see [this notebook](../modules/indexes/examples/vectorstores.ipynb)

docs/ecosystem/cohere.md

@@ -0,0 +1,25 @@
+# Cohere
+
+This page covers how to use the Cohere ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific Cohere wrappers.
+
+## Installation and Setup
+- Install the Python SDK with `pip install cohere`
+- Get an Cohere api key and set it as an environment variable (`COHERE_API_KEY`)
+
+## Wrappers
+
+### LLM
+
+There exists an Cohere LLM wrapper, which you can access with 
+```python
+from langchain.llms import Cohere
+```
+
+### Embeddings
+
+There exists an Cohere Embeddings wrapper, which you can access with 
+```python
+from langchain.embeddings import CohereEmbeddings
+```
+For a more detailed walkthrough of this, see [this notebook](../modules/indexes/examples/embeddings.ipynb)

docs/ecosystem/deepinfra.md

@@ -0,0 +1,17 @@
+# DeepInfra
+
+This page covers how to use the DeepInfra ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific DeepInfra wrappers.
+
+## Installation and Setup
+- Get your DeepInfra api key from this link [here](https://deepinfra.com/).
+- Get an DeepInfra api key and set it as an environment variable (`DEEPINFRA_API_TOKEN`)
+
+## Wrappers
+
+### LLM
+
+There exists an DeepInfra LLM wrapper, which you can access with
+```python
+from langchain.llms import DeepInfra
+```

docs/ecosystem/deeplake.md

@@ -0,0 +1,25 @@
+# Deep Lake
+
+This page covers how to use the Deep Lake ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific Deep Lake wrappers. For more information.
+
+1. Here is [whitepaper](https://www.deeplake.ai/whitepaper) and [academic paper](https://arxiv.org/pdf/2209.10785.pdf) for Deep Lake
+
+2. Here is a set of additional resources available for review: [Deep Lake](https://github.com/activeloopai/deeplake), [Getting Started](https://docs.activeloop.ai/getting-started) and [Tutorials](https://docs.activeloop.ai/hub-tutorials)
+
+## Installation and Setup
+- Install the Python package with `pip install deeplake`
+
+## Wrappers
+
+### VectorStore
+
+There exists a wrapper around Deep Lake, a data lake for Deep Learning applications, allowing you to use it as a vectorstore (for now), whether for semantic search or example selection.
+
+To import this vectorstore:
+```python
+from langchain.vectorstores import DeepLake
+```
+
+
+For a more detailed walkthrough of the Deep Lake wrapper, see [this notebook](../modules/indexes/vectorstore_examples/deeplake.ipynb)

docs/ecosystem/forefrontai.md

@@ -0,0 +1,16 @@
+# ForefrontAI
+
+This page covers how to use the ForefrontAI ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific ForefrontAI wrappers.
+
+## Installation and Setup
+- Get an ForefrontAI api key and set it as an environment variable (`FOREFRONTAI_API_KEY`)
+
+## Wrappers
+
+### LLM
+
+There exists an ForefrontAI LLM wrapper, which you can access with 
+```python
+from langchain.llms import ForefrontAI
+```

docs/ecosystem/google_search.md

@@ -0,0 +1,32 @@
+# Google Search Wrapper
+
+This page covers how to use the Google Search API within LangChain.
+It is broken into two parts: installation and setup, and then references to the specific Google Search wrapper.
+
+## Installation and Setup
+- Install requirements with `pip install google-api-python-client`
+- Set up a Custom Search Engine, following [these instructions](https://stackoverflow.com/questions/37083058/programmatically-searching-google-in-python-using-custom-search)
+- Get an API Key and Custom Search Engine ID from the previous step, and set them as environment variables `GOOGLE_API_KEY` and `GOOGLE_CSE_ID` respectively
+
+## Wrappers
+
+### Utility
+
+There exists a GoogleSearchAPIWrapper utility which wraps this API. To import this utility:
+
+```python
+from langchain.utilities import GoogleSearchAPIWrapper
+```
+
+For a more detailed walkthrough of this wrapper, see [this notebook](../modules/utils/examples/google_search.ipynb).
+
+### Tool
+
+You can also easily load this wrapper as a Tool (to use with an Agent).
+You can do this with:
+```python
+from langchain.agents import load_tools
+tools = load_tools(["google-search"])
+```
+
+For more information on this, see [this page](../modules/agents/tools.md)

docs/ecosystem/google_serper.md

@@ -0,0 +1,72 @@
+# Google Serper Wrapper
+
+This page covers how to use the [Serper](https://serper.dev) Google Search API within LangChain. Serper is a low-cost Google Search API that can be used to add answer box, knowledge graph, and organic results data from Google Search. 
+It is broken into two parts: setup, and then references to the specific Google Serper wrapper.
+
+## Setup
+- Go to [serper.dev](https://serper.dev) to sign up for a free account
+- Get the api key and set it as an environment variable (`SERPER_API_KEY`)
+
+## Wrappers
+
+### Utility
+
+There exists a GoogleSerperAPIWrapper utility which wraps this API. To import this utility:
+
+```python
+from langchain.utilities import GoogleSerperAPIWrapper
+```
+
+You can use it as part of a Self Ask chain:
+
+```python
+from langchain.utilities import GoogleSerperAPIWrapper
+from langchain.llms.openai import OpenAI
+from langchain.agents import initialize_agent, Tool
+
+import os
+
+os.environ["SERPER_API_KEY"] = ""
+os.environ['OPENAI_API_KEY'] = ""
+
+llm = OpenAI(temperature=0)
+search = GoogleSerperAPIWrapper()
+tools = [
+    Tool(
+        name="Intermediate Answer",
+        func=search.run,
+        description="useful for when you need to ask with search"
+    )
+]
+
+self_ask_with_search = initialize_agent(tools, llm, agent="self-ask-with-search", verbose=True)
+self_ask_with_search.run("What is the hometown of the reigning men's U.S. Open champion?")
+```
+
+#### Output
+```
+Entering new AgentExecutor chain...
+ Yes.
+Follow up: Who is the reigning men's U.S. Open champion?
+Intermediate answer: Current champions Carlos Alcaraz, 2022 men's singles champion.
+Follow up: Where is Carlos Alcaraz from?
+Intermediate answer: El Palmar, Spain
+So the final answer is: El Palmar, Spain
+
+> Finished chain.
+
+'El Palmar, Spain'
+```
+
+For a more detailed walkthrough of this wrapper, see [this notebook](../modules/utils/examples/google_serper.ipynb).
+
+### Tool
+
+You can also easily load this wrapper as a Tool (to use with an Agent).
+You can do this with:
+```python
+from langchain.agents import load_tools
+tools = load_tools(["google-serper"])
+```
+
+For more information on this, see [this page](../modules/agents/tools.md)

docs/ecosystem/gooseai.md

@@ -0,0 +1,23 @@
+# GooseAI
+
+This page covers how to use the GooseAI ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific GooseAI wrappers.
+
+## Installation and Setup
+- Install the Python SDK with `pip install openai`
+- Get your GooseAI api key from this link [here](https://goose.ai/).
+- Set the environment variable (`GOOSEAI_API_KEY`).
+
+```python
+import os
+os.environ["GOOSEAI_API_KEY"] = "YOUR_API_KEY"
+```
+
+## Wrappers
+
+### LLM
+
+There exists an GooseAI LLM wrapper, which you can access with: 
+```python
+from langchain.llms import GooseAI
+```

docs/ecosystem/graphsignal.md

@@ -0,0 +1,38 @@
+# Graphsignal
+
+This page covers how to use the Graphsignal ecosystem to trace and monitor LangChain.
+
+## Installation and Setup
+
+- Install the Python library with `pip install graphsignal`
+- Create free Graphsignal account [here](https://graphsignal.com)
+- Get an API key and set it as an environment variable (`GRAPHSIGNAL_API_KEY`)
+
+## Tracing and Monitoring
+
+Graphsignal automatically instruments and starts tracing and monitoring chains. Traces, metrics and errors are then available in your [Graphsignal dashboard](https://app.graphsignal.com/). No prompts or other sensitive data are sent to Graphsignal cloud, only statistics and metadata.
+
+Initialize the tracer by providing a deployment name:
+
+```python
+import graphsignal
+
+graphsignal.configure(deployment='my-langchain-app-prod')
+```
+
+In order to trace full runs and see a breakdown by chains and tools, you can wrap the calling routine or use a decorator:
+
+```python
+with graphsignal.start_trace('my-chain'):
+    chain.run("some initial text")
+```
+
+Optionally, enable profiling to record function-level statistics for each trace.
+
+```python
+with graphsignal.start_trace(
+        'my-chain', options=graphsignal.TraceOptions(enable_profiling=True)):
+    chain.run("some initial text")
+```
+
+See the [Quick Start](https://graphsignal.com/docs/guides/quick-start/) guide for complete setup instructions.

docs/ecosystem/hazy_research.md

@@ -0,0 +1,19 @@
+# Hazy Research
+
+This page covers how to use the Hazy Research ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific Hazy Research wrappers.
+
+## Installation and Setup
+- To use the `manifest`, install it with `pip install manifest-ml`
+
+## Wrappers
+
+### LLM
+
+There exists an LLM wrapper around Hazy Research's `manifest` library. 
+`manifest` is a python library which is itself a wrapper around many model providers, and adds in caching, history, and more.
+
+To use this wrapper:
+```python
+from langchain.llms.manifest import ManifestWrapper
+```

docs/ecosystem/helicone.md

@@ -0,0 +1,53 @@
+# Helicone
+
+This page covers how to use the [Helicone](https://helicone.ai) ecosystem within LangChain.
+
+## What is Helicone?
+
+Helicone is an [open source](https://github.com/Helicone/helicone) observability platform that proxies your OpenAI traffic and provides you key insights into your spend, latency and usage.
+
+![Helicone](../_static/HeliconeDashboard.png)
+
+## Quick start
+
+With your LangChain environment you can just add the following parameter.
+
+```bash
+export OPENAI_API_BASE="https://oai.hconeai.com/v1"
+```
+
+Now head over to [helicone.ai](https://helicone.ai/onboarding?step=2) to create your account, and add your OpenAI API key within our dashboard to view your logs.
+
+![Helicone](../_static/HeliconeKeys.png)
+
+## How to enable Helicone caching
+
+```python
+from langchain.llms import OpenAI
+import openai
+openai.api_base = "https://oai.hconeai.com/v1"
+
+llm = OpenAI(temperature=0.9, headers={"Helicone-Cache-Enabled": "true"})
+text = "What is a helicone?"
+print(llm(text))
+```
+
+[Helicone caching docs](https://docs.helicone.ai/advanced-usage/caching)
+
+## How to use Helicone custom properties
+
+```python
+from langchain.llms import OpenAI
+import openai
+openai.api_base = "https://oai.hconeai.com/v1"
+
+llm = OpenAI(temperature=0.9, headers={
+        "Helicone-Property-Session": "24",
+        "Helicone-Property-Conversation": "support_issue_2",
+        "Helicone-Property-App": "mobile",
+      })
+text = "What is a helicone?"
+print(llm(text))
+```
+
+[Helicone property docs](https://docs.helicone.ai/advanced-usage/custom-properties)

docs/ecosystem/huggingface.md

@@ -0,0 +1,69 @@
+# Hugging Face
+
+This page covers how to use the Hugging Face ecosystem (including the [Hugging Face Hub](https://huggingface.co)) within LangChain.
+It is broken into two parts: installation and setup, and then references to specific Hugging Face wrappers.
+
+## Installation and Setup
+
+If you want to work with the Hugging Face Hub:
+- Install the Hub client library with `pip install huggingface_hub`
+- Create a Hugging Face account (it's free!)
+- Create an [access token](https://huggingface.co/docs/hub/security-tokens) and set it as an environment variable (`HUGGINGFACEHUB_API_TOKEN`)
+
+If you want work with the Hugging Face Python libraries:
+- Install `pip install transformers` for working with models and tokenizers
+- Install `pip install datasets` for working with datasets
+
+## Wrappers
+
+### LLM
+
+There exists two Hugging Face LLM wrappers, one for a local pipeline and one for a model hosted on Hugging Face Hub.
+Note that these wrappers only work for models that support the following tasks: [`text2text-generation`](https://huggingface.co/models?library=transformers&pipeline_tag=text2text-generation&sort=downloads), [`text-generation`](https://huggingface.co/models?library=transformers&pipeline_tag=text-classification&sort=downloads)
+
+To use the local pipeline wrapper:
+```python
+from langchain.llms import HuggingFacePipeline
+```
+
+To use a the wrapper for a model hosted on Hugging Face Hub:
+```python
+from langchain.llms import HuggingFaceHub
+```
+For a more detailed walkthrough of the Hugging Face Hub wrapper, see [this notebook](../modules/llms/integrations/huggingface_hub.ipynb)
+
+
+### Embeddings
+
+There exists two Hugging Face Embeddings wrappers, one for a local model and one for a model hosted on Hugging Face Hub.
+Note that these wrappers only work for [`sentence-transformers` models](https://huggingface.co/models?library=sentence-transformers&sort=downloads).
+
+To use the local pipeline wrapper:
+```python
+from langchain.embeddings import HuggingFaceEmbeddings
+```
+
+To use a the wrapper for a model hosted on Hugging Face Hub:
+```python
+from langchain.embeddings import HuggingFaceHubEmbeddings
+```
+For a more detailed walkthrough of this, see [this notebook](../modules/indexes/examples/embeddings.ipynb)
+
+### Tokenizer
+
+There are several places you can use tokenizers available through the `transformers` package.
+By default, it is used to count tokens for all LLMs.
+
+You can also use it to count tokens when splitting documents with 
+```python
+from langchain.text_splitter import CharacterTextSplitter
+CharacterTextSplitter.from_huggingface_tokenizer(...)
+```
+For a more detailed walkthrough of this, see [this notebook](../modules/indexes/examples/textsplitter.ipynb)
+
+
+### Datasets
+
+The Hugging Face Hub has lots of great [datasets](https://huggingface.co/datasets) that can be used to evaluate your LLM chains.
+
+For a detailed walkthrough of how to use them to do so, see [this notebook](../use_cases/evaluation/huggingface_datasets.ipynb)

docs/ecosystem/modal.md

@@ -0,0 +1,66 @@
+# Modal
+
+This page covers how to use the Modal ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific Modal wrappers.
+
+## Installation and Setup
+- Install with `pip install modal-client`
+- Run `modal token new`
+
+## Define your Modal Functions and Webhooks
+
+You must include a prompt. There is a rigid response structure.
+
+```python
+class Item(BaseModel):
+    prompt: str
+
+@stub.webhook(method="POST")
+def my_webhook(item: Item):
+    return {"prompt": my_function.call(item.prompt)}
+```
+
+An example with GPT2:
+
+```python
+from pydantic import BaseModel
+
+import modal
+
+stub = modal.Stub("example-get-started")
+
+volume = modal.SharedVolume().persist("gpt2_model_vol")
+CACHE_PATH = "/root/model_cache"
+
+@stub.function(
+    gpu="any",
+    image=modal.Image.debian_slim().pip_install(
+        "tokenizers", "transformers", "torch", "accelerate"
+    ),
+    shared_volumes={CACHE_PATH: volume},
+    retries=3,
+)
+def run_gpt2(text: str):
+    from transformers import GPT2Tokenizer, GPT2LMHeadModel
+    tokenizer = GPT2Tokenizer.from_pretrained('gpt2')
+    model = GPT2LMHeadModel.from_pretrained('gpt2')
+    encoded_input = tokenizer(text, return_tensors='pt').input_ids
+    output = model.generate(encoded_input, max_length=50, do_sample=True)
+    return tokenizer.decode(output[0], skip_special_tokens=True)
+
+class Item(BaseModel):
+    prompt: str
+
+@stub.webhook(method="POST")
+def get_text(item: Item):
+    return {"prompt": run_gpt2.call(item.prompt)}
+```
+
+## Wrappers
+
+### LLM
+
+There exists an Modal LLM wrapper, which you can access with 
+```python
+from langchain.llms import Modal
+```

docs/ecosystem/nlpcloud.md

@@ -0,0 +1,17 @@
+# NLPCloud
+
+This page covers how to use the NLPCloud ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific NLPCloud wrappers.
+
+## Installation and Setup
+- Install the Python SDK with `pip install nlpcloud`
+- Get an NLPCloud api key and set it as an environment variable (`NLPCLOUD_API_KEY`)
+
+## Wrappers
+
+### LLM
+
+There exists an NLPCloud LLM wrapper, which you can access with 
+```python
+from langchain.llms import NLPCloud
+```

docs/ecosystem/openai.md

@@ -0,0 +1,55 @@
+# OpenAI
+
+This page covers how to use the OpenAI ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific OpenAI wrappers.
+
+## Installation and Setup
+- Install the Python SDK with `pip install openai`
+- Get an OpenAI api key and set it as an environment variable (`OPENAI_API_KEY`)
+- If you want to use OpenAI's tokenizer (only available for Python 3.9+), install it with `pip install tiktoken`
+
+## Wrappers
+
+### LLM
+
+There exists an OpenAI LLM wrapper, which you can access with 
+```python
+from langchain.llms import OpenAI
+```
+
+If you are using a model hosted on Azure, you should use different wrapper for that:
+```python
+from langchain.llms import AzureOpenAI
+```
+For a more detailed walkthrough of the Azure wrapper, see [this notebook](../modules/llms/integrations/azure_openai_example.ipynb)
+
+
+
+### Embeddings
+
+There exists an OpenAI Embeddings wrapper, which you can access with 
+```python
+from langchain.embeddings import OpenAIEmbeddings
+```
+For a more detailed walkthrough of this, see [this notebook](../modules/indexes/examples/embeddings.ipynb)
+
+
+### Tokenizer
+
+There are several places you can use the `tiktoken` tokenizer. By default, it is used to count tokens
+for OpenAI LLMs.
+
+You can also use it to count tokens when splitting documents with 
+```python
+from langchain.text_splitter import CharacterTextSplitter
+CharacterTextSplitter.from_tiktoken_encoder(...)
+```
+For a more detailed walkthrough of this, see [this notebook](../modules/indexes/examples/textsplitter.ipynb)
+
+### Moderation
+You can also access the OpenAI content moderation endpoint with
+
+```python
+from langchain.chains import OpenAIModerationChain
+```
+For a more detailed walkthrough of this, see [this notebook](../modules/chains/examples/moderation.ipynb)

docs/ecosystem/opensearch.md

@@ -0,0 +1,21 @@
+# OpenSearch
+
+This page covers how to use the OpenSearch ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific OpenSearch wrappers.
+
+## Installation and Setup
+- Install the Python package with `pip install opensearch-py`
+## Wrappers
+
+### VectorStore
+
+There exists a wrapper around OpenSearch vector databases, allowing you to use it as a vectorstore 
+for semantic search using approximate vector search powered by lucene, nmslib and faiss engines 
+or using painless scripting and script scoring functions for bruteforce vector search.
+
+To import this vectorstore:
+```python
+from langchain.vectorstores import OpenSearchVectorSearch
+```
+
+For a more detailed walkthrough of the OpenSearch wrapper, see [this notebook](../modules/indexes/vectorstore_examples/opensearch.ipynb)

docs/ecosystem/petals.md

@@ -0,0 +1,17 @@
+# Petals
+
+This page covers how to use the Petals ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific Petals wrappers.
+
+## Installation and Setup
+- Install with `pip install petals`
+- Get a Hugging Face api key and set it as an environment variable (`HUGGINGFACE_API_KEY`)
+
+## Wrappers
+
+### LLM
+
+There exists an Petals LLM wrapper, which you can access with 
+```python
+from langchain.llms import Petals
+```

docs/ecosystem/pgvector.md

@@ -0,0 +1,29 @@
+# PGVector
+
+This page covers how to use the Postgres [PGVector](https://github.com/pgvector/pgvector) ecosystem within LangChain
+It is broken into two parts: installation and setup, and then references to specific PGVector wrappers.
+
+## Installation
+- Install the Python package with `pip install pgvector`
+
+
+## Setup
+1. The first step is to create a database with the `pgvector` extension installed.
+
+    Follow the steps at [PGVector Installation Steps](https://github.com/pgvector/pgvector#installation) to install the database and the extension. The docker image is the easiest way to get started.
+
+## Wrappers
+
+### VectorStore
+
+There exists a wrapper around Postgres vector databases, allowing you to use it as a vectorstore,
+whether for semantic search or example selection.
+
+To import this vectorstore:
+```python
+from langchain.vectorstores.pgvector import PGVector
+```
+
+### Usage
+
+For a more detailed walkthrough of the PGVector Wrapper, see [this notebook](../modules/indexes/vectorstore_examples/pgvector.ipynb)

docs/ecosystem/pinecone.md

@@ -0,0 +1,20 @@
+# Pinecone
+
+This page covers how to use the Pinecone ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific Pinecone wrappers.
+
+## Installation and Setup
+- Install the Python SDK with `pip install pinecone-client`
+## Wrappers
+
+### VectorStore
+
+There exists a wrapper around Pinecone indexes, allowing you to use it as a vectorstore,
+whether for semantic search or example selection.
+
+To import this vectorstore:
+```python
+from langchain.vectorstores import Pinecone
+```
+
+For a more detailed walkthrough of the Pinecone wrapper, see [this notebook](../modules/indexes/vectorstore_examples/pinecone.ipynb)

docs/ecosystem/promptlayer.md

@@ -0,0 +1,49 @@
+# PromptLayer
+
+This page covers how to use [PromptLayer](https://www.promptlayer.com) within LangChain.
+It is broken into two parts: installation and setup, and then references to specific PromptLayer wrappers.
+
+## Installation and Setup
+
+If you want to work with PromptLayer:
+- Install the promptlayer python library `pip install promptlayer`
+- Create a PromptLayer account
+- Create an api token and set it as an environment variable (`PROMPTLAYER_API_KEY`)
+
+## Wrappers
+
+### LLM
+
+There exists an PromptLayer OpenAI LLM wrapper, which you can access with
+```python
+from langchain.llms import PromptLayerOpenAI
+```
+
+To tag your requests, use the argument `pl_tags` when instanializing the LLM
+```python
+from langchain.llms import PromptLayerOpenAI
+llm = PromptLayerOpenAI(pl_tags=["langchain-requests", "chatbot"])
+```
+
+To get the PromptLayer request id, use the argument `return_pl_id` when instanializing the LLM
+```python
+from langchain.llms import PromptLayerOpenAI
+llm = PromptLayerOpenAI(return_pl_id=True)
+```
+This will add the PromptLayer request ID in the `generation_info` field of the `Generation` returned when using `.generate` or `.agenerate`
+
+For example:
+```python
+llm_results = llm.generate(["hello world"])
+for res in llm_results.generations:
+    print("pl request id: ", res[0].generation_info["pl_request_id"])
+```
+You can use the PromptLayer request ID to add a prompt, score, or other metadata to your request. [Read more about it here](https://magniv.notion.site/Track-4deee1b1f7a34c1680d085f82567dab9).
+
+This LLM is identical to the [OpenAI LLM](./openai), except that
+- all your requests will be logged to your PromptLayer account
+- you can add `pl_tags` when instantializing to tag your requests on PromptLayer
+- you can add `return_pl_id` when instantializing to return a PromptLayer request id to use [while tracking requests](https://magniv.notion.site/Track-4deee1b1f7a34c1680d085f82567dab9).
+
+
+PromptLayer also provides native wrappers for [`PromptLayerChatOpenAI`](../modules/chat/examples/promptlayer_chat_openai.ipynb) and `PromptLayerOpenAIChat`

docs/ecosystem/runhouse.md

@@ -0,0 +1,31 @@
+# Runhouse
+
+This page covers how to use the [Runhouse](https://github.com/run-house/runhouse) ecosystem within LangChain.
+It is broken into three parts: installation and setup, LLMs, and Embeddings.
+
+## Installation and Setup
+- Install the Python SDK with `pip install runhouse`
+- If you'd like to use on-demand cluster, check your cloud credentials with `sky check`
+
+## Self-hosted LLMs
+For a basic self-hosted LLM, you can use the `SelfHostedHuggingFaceLLM` class. For more
+custom LLMs, you can use the `SelfHostedPipeline` parent class.
+
+```python
+from langchain.llms import SelfHostedPipeline, SelfHostedHuggingFaceLLM
+```
+
+For a more detailed walkthrough of the Self-hosted LLMs, see [this notebook](../modules/llms/integrations/self_hosted_examples.ipynb)
+
+## Self-hosted Embeddings
+There are several ways to use self-hosted embeddings with LangChain via Runhouse.
+
+For a basic self-hosted embedding from a Hugging Face Transformers model, you can use 
+the `SelfHostedEmbedding` class.
+```python
+from langchain.llms import SelfHostedPipeline, SelfHostedHuggingFaceLLM
+```
+
+For a more detailed walkthrough of the Self-hosted Embeddings, see [this notebook](../modules/indexes/examples/embeddings.ipynb)
+
+##

docs/ecosystem/searx.md

@@ -0,0 +1,58 @@
+# SearxNG Search API
+
+This page covers how to use the SearxNG search API within LangChain.
+It is broken into two parts: installation and setup, and then references to the specific SearxNG API wrapper.
+
+## Installation and Setup
+
+While it is possible to utilize the wrapper in conjunction with  [public searx
+instances](https://searx.space/) these instances frequently do not permit API
+access (see note on output format below) and have limitations on the frequency
+of requests. It is recommended to opt for a self-hosted instance instead.
+
+### Self Hosted Instance:
+
+See [this page](https://searxng.github.io/searxng/admin/installation.html) for installation instructions.
+
+When you install SearxNG, the only active output format by default is the HTML format.
+You need to activate the `json` format to use the API. This can be done by adding the following line to the `settings.yml` file:
+```yaml
+search:
+    formats:
+        - html
+        - json
+```
+You can make sure that the API is working by issuing a curl request to the API endpoint:
+
+`curl -kLX GET --data-urlencode q='langchain' -d format=json http://localhost:8888`
+
+This should return a JSON object with the results.
+
+
+## Wrappers
+
+### Utility
+
+To use the wrapper we need to pass the host of the SearxNG instance to the wrapper with:
+    1. the named parameter `searx_host` when creating the instance.
+    2. exporting the environment variable `SEARXNG_HOST`.
+
+You can use the wrapper to get results from a SearxNG instance. 
+
+```python
+from langchain.utilities import SearxSearchWrapper
+s = SearxSearchWrapper(searx_host="http://localhost:8888")
+s.run("what is a large language model?")
+```
+
+### Tool
+
+You can also easily load this wrapper as a Tool (to use with an Agent).
+You can do this with:
+
+```python
+from langchain.agents import load_tools
+tools = load_tools(["searx-search"], searx_host="http://localhost:8888")
+```
+
+For more information on tools, see [this page](../modules/agents/tools.md)

docs/ecosystem/serpapi.md

@@ -0,0 +1,31 @@
+# SerpAPI
+
+This page covers how to use the SerpAPI search APIs within LangChain.
+It is broken into two parts: installation and setup, and then references to the specific SerpAPI wrapper.
+
+## Installation and Setup
+- Install requirements with `pip install google-search-results`
+- Get a SerpAPI api key and either set it as an environment variable (`SERPAPI_API_KEY`)
+
+## Wrappers
+
+### Utility
+
+There exists a SerpAPI utility which wraps this API. To import this utility:
+
+```python
+from langchain.utilities import SerpAPIWrapper
+```
+
+For a more detailed walkthrough of this wrapper, see [this notebook](../modules/utils/examples/serpapi.ipynb).
+
+### Tool
+
+You can also easily load this wrapper as a Tool (to use with an Agent).
+You can do this with:
+```python
+from langchain.agents import load_tools
+tools = load_tools(["serpapi"])
+```
+
+For more information on this, see [this page](../modules/agents/tools.md)

docs/ecosystem/stochasticai.md

@@ -0,0 +1,17 @@
+# StochasticAI
+
+This page covers how to use the StochasticAI ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific StochasticAI wrappers.
+
+## Installation and Setup
+- Install with `pip install stochasticx`
+- Get an StochasticAI api key and set it as an environment variable (`STOCHASTICAI_API_KEY`)
+
+## Wrappers
+
+### LLM
+
+There exists an StochasticAI LLM wrapper, which you can access with 
+```python
+from langchain.llms import StochasticAI
+```

docs/ecosystem/unstructured.md

@@ -0,0 +1,44 @@
+# Unstructured
+
+This page covers how to use the [`unstructured`](https://github.com/Unstructured-IO/unstructured)
+ecosystem within LangChain. The `unstructured` package from
+[Unstructured.IO](https://www.unstructured.io/) extracts clean text from raw source documents like
+PDFs and Word documents.
+
+
+This page is broken into two parts: installation and setup, and then references to specific
+`unstructured` wrappers.
+
+## Installation and Setup
+- Install the Python SDK with `pip install "unstructured[local-inference]"`
+- Install the following system dependencies if they are not already available on your system.
+  Depending on what document types you're parsing, you may not need all of these.
+    - `libmagic-dev`
+    - `poppler-utils`
+    - `tesseract-ocr`
+    - `libreoffice`
+- If you are parsing PDFs using the `"hi_res"` strategy, run the following to install the `detectron2` model, which
+  `unstructured` uses for layout detection:
+    - `pip install "detectron2@git+https://github.com/facebookresearch/detectron2.git@v0.6#egg=detectron2"`
+    - If `detectron2` is not installed, `unstructured` will fallback to processing PDFs
+      using the `"fast"` strategy, which uses `pdfminer` directly and doesn't require
+      `detectron2`.
+
+## Wrappers
+
+### Data Loaders
+
+The primary `unstructured` wrappers within `langchain` are data loaders. The following
+shows how to use the most basic unstructured data loader. There are other file-specific
+data loaders available in the `langchain.document_loaders` module.
+
+```python
+from langchain.document_loaders import UnstructuredFileLoader
+
+loader = UnstructuredFileLoader("state_of_the_union.txt")
+loader.load()
+```
+
+If you instantiate the loader with `UnstructuredFileLoader(mode="elements")`, the loader
+will track additional metadata like the page number and text type (i.e. title, narrative text)
+when that information is available.

docs/ecosystem/weaviate.md

@@ -0,0 +1,33 @@
+# Weaviate
+
+This page covers how to use the Weaviate ecosystem within LangChain.
+
+What is Weaviate?
+
+**Weaviate in a nutshell:**
+- Weaviate is an open-source ​database of the type ​vector search engine.
+- Weaviate allows you to store JSON documents in a class property-like fashion while attaching machine learning vectors to these documents to represent them in vector space.
+- Weaviate can be used stand-alone (aka bring your vectors) or with a variety of modules that can do the vectorization for you and extend the core capabilities.
+- Weaviate has a GraphQL-API to access your data easily.
+- We aim to bring your vector search set up to production to query in mere milliseconds (check our [open source benchmarks](https://weaviate.io/developers/weaviate/current/benchmarks/) to see if Weaviate fits your use case).
+- Get to know Weaviate in the [basics getting started guide](https://weaviate.io/developers/weaviate/current/core-knowledge/basics.html) in under five minutes.
+
+**Weaviate in detail:**
+
+Weaviate is a low-latency vector search engine with out-of-the-box support for different media types (text, images, etc.). It offers Semantic Search, Question-Answer Extraction, Classification, Customizable Models (PyTorch/TensorFlow/Keras), etc. Built from scratch in Go, Weaviate stores both objects and vectors, allowing for combining vector search with structured filtering and the fault tolerance of a cloud-native database. It is all accessible through GraphQL, REST, and various client-side programming languages.
+
+## Installation and Setup
+- Install the Python SDK with `pip install weaviate-client`
+## Wrappers
+
+### VectorStore
+
+There exists a wrapper around Weaviate indexes, allowing you to use it as a vectorstore,
+whether for semantic search or example selection.
+
+To import this vectorstore:
+```python
+from langchain.vectorstores import Weaviate
+```
+
+For a more detailed walkthrough of the Weaviate wrapper, see [this notebook](../modules/indexes/examples/vectorstores.ipynb)

docs/ecosystem/wolfram_alpha.md

@@ -0,0 +1,34 @@
+# Wolfram Alpha Wrapper
+
+This page covers how to use the Wolfram Alpha API within LangChain.
+It is broken into two parts: installation and setup, and then references to specific Wolfram Alpha wrappers.
+
+## Installation and Setup
+- Install requirements with `pip install wolframalpha`
+- Go to wolfram alpha and sign up for a developer account [here](https://developer.wolframalpha.com/)
+- Create an app and get your APP ID
+- Set your APP ID as an environment variable `WOLFRAM_ALPHA_APPID`
+
+
+## Wrappers
+
+### Utility
+
+There exists a WolframAlphaAPIWrapper utility which wraps this API. To import this utility:
+
+```python
+from langchain.utilities.wolfram_alpha import WolframAlphaAPIWrapper
+```
+
+For a more detailed walkthrough of this wrapper, see [this notebook](../modules/utils/examples/wolfram_alpha.ipynb).
+
+### Tool
+
+You can also easily load this wrapper as a Tool (to use with an Agent).
+You can do this with:
+```python
+from langchain.agents import load_tools
+tools = load_tools(["wolfram-alpha"])
+```
+
+For more information on this, see [this page](../modules/agents/tools.md)

docs/ecosystem/writer.md

@@ -0,0 +1,16 @@
+# Writer
+
+This page covers how to use the Writer ecosystem within LangChain.
+It is broken into two parts: installation and setup, and then references to specific Writer wrappers.
+
+## Installation and Setup
+- Get an Writer api key and set it as an environment variable (`WRITER_API_KEY`)
+
+## Wrappers
+
+### LLM
+
+There exists an Writer LLM wrapper, which you can access with 
+```python
+from langchain.llms import Writer
+```

docs/gallery.rst

@@ -0,0 +1,335 @@
+LangChain Gallery
+=============
+
+Lots of people have built some pretty awesome stuff with LangChain.
+This is a collection of our favorites.
+If you see any other demos that you think we should highlight, be sure to let us know!
+
+
+Open Source
+-----------
+
+.. panels::
+    :body: text-center
+
+    ---
+
+    .. link-button:: https://github.com/bborn/howdoi.ai
+        :type: url
+        :text: HowDoI.ai
+        :classes: stretched-link btn-lg
+
+    +++
+
+    This is an experiment in building a large-language-model-backed chatbot. It can hold a conversation, remember previous comments/questions, 
+    and answer all types of queries (history, web search, movie data, weather, news, and more).
+
+    ---
+
+    .. link-button:: https://colab.research.google.com/drive/1sKSTjt9cPstl_WMZ86JsgEqFG-aSAwkn?usp=sharing
+        :type: url
+        :text: YouTube Transcription QA with Sources
+        :classes: stretched-link btn-lg
+
+    +++
+
+    An end-to-end example of doing question answering on YouTube transcripts, returning the timestamps as sources to legitimize the answer.
+
+    ---
+
+    .. link-button:: https://github.com/normandmickey/MrsStax
+        :type: url
+        :text: QA Slack Bot
+        :classes: stretched-link btn-lg
+
+    +++
+
+    This application is a Slack Bot that uses Langchain and OpenAI's GPT3 language model to provide domain specific answers. You provide the documents.
+
+    ---
+
+    .. link-button:: https://github.com/OpenBioLink/ThoughtSource
+        :type: url
+        :text: ThoughtSource
+        :classes: stretched-link btn-lg
+
+    +++
+
+    A central, open resource and community around data and tools related to chain-of-thought reasoning in large language models.
+
+    ---
+
+    .. link-button:: https://github.com/blackhc/llm-strategy
+        :type: url
+        :text: LLM Strategy
+        :classes: stretched-link btn-lg
+    
+    +++
+
+    This Python package adds a decorator llm_strategy that connects to an LLM (such as OpenAI’s GPT-3) and uses the LLM to "implement" abstract methods in interface classes. It does this by forwarding requests to the LLM and converting the responses back to Python data using Python's @dataclasses.
+
+    ---
+
+    .. link-button:: https://github.com/JohnNay/llm-lobbyist
+        :type: url
+        :text: Zero-Shot Corporate Lobbyist
+        :classes: stretched-link btn-lg
+
+    +++
+
+    A notebook showing how to use GPT to help with the work of a corporate lobbyist.
+
+    ---
+
+    .. link-button:: https://dagster.io/blog/chatgpt-langchain
+        :type: url
+        :text: Dagster Documentation ChatBot
+        :classes: stretched-link btn-lg
+
+    +++
+
+    A jupyter notebook demonstrating how you could create a semantic search engine on documents in one of your Google Folders
+
+    ---
+
+    .. link-button:: https://github.com/venuv/langchain_semantic_search
+        :type: url
+        :text: Google Folder Semantic Search
+        :classes: stretched-link btn-lg
+
+    +++
+
+    Build a GitHub support bot with GPT3, LangChain, and Python.
+
+    ---
+
+    .. link-button:: https://huggingface.co/spaces/team7/talk_with_wind
+        :type: url
+        :text: Talk With Wind
+        :classes: stretched-link btn-lg
+
+    +++
+
+    Record sounds of anything (birds, wind, fire, train station) and chat with it.
+
+    ---
+
+    .. link-button:: https://huggingface.co/spaces/JavaFXpert/Chat-GPT-LangChain
+        :type: url
+        :text: ChatGPT LangChain
+        :classes: stretched-link btn-lg
+
+    +++
+
+    This simple application demonstrates a conversational agent implemented with OpenAI GPT-3.5 and LangChain. When necessary, it leverages tools for complex math, searching the internet, and accessing news and weather.
+
+    ---
+
+    .. link-button:: https://huggingface.co/spaces/JavaFXpert/gpt-math-techniques
+        :type: url
+        :text: GPT Math Techniques
+        :classes: stretched-link btn-lg
+
+    +++
+
+    A Hugging Face spaces project showing off the benefits of using PAL for math problems.
+
+    ---
+
+    .. link-button:: https://colab.research.google.com/drive/1xt2IsFPGYMEQdoJFNgWNAjWGxa60VXdV
+        :type: url
+        :text: GPT Political Compass
+        :classes: stretched-link btn-lg
+
+    +++
+
+    Measure the political compass of GPT.
+
+    ---
+
+    .. link-button:: https://github.com/hwchase17/notion-qa
+        :type: url
+        :text: Notion Database Question-Answering Bot
+        :classes: stretched-link btn-lg
+    
+    +++
+
+    Open source GitHub project shows how to use LangChain to create a chatbot that can answer questions about an arbitrary Notion database.
+
+    ---
+
+    .. link-button:: https://github.com/jerryjliu/gpt_index
+        :type: url
+        :text: GPT Index
+        :classes: stretched-link btn-lg
+    
+    +++
+
+    GPT Index is a project consisting of a set of data structures that are created using GPT-3 and can be traversed using GPT-3 in order to answer queries.
+
+    ---
+
+    .. link-button:: https://github.com/JavaFXpert/llm-grovers-search-party
+        :type: url
+        :text: Grover's Algorithm
+        :classes: stretched-link btn-lg
+
+    +++
+
+    Leveraging Qiskit, OpenAI and LangChain to demonstrate Grover's algorithm
+
+    ---
+
+    .. link-button:: https://huggingface.co/spaces/rituthombre/QNim
+        :type: url
+        :text: QNimGPT
+        :classes: stretched-link btn-lg
+
+    +++
+
+    A chat UI to play Nim, where a player can select an opponent, either a quantum computer or an AI
+
+    ---
+
+    .. link-button:: https://colab.research.google.com/drive/19WTIWC3prw5LDMHmRMvqNV2loD9FHls6?usp=sharing
+        :type: url
+        :text: ReAct TextWorld
+        :classes: stretched-link btn-lg
+
+    +++
+
+    Leveraging the ReActTextWorldAgent to play TextWorld with an LLM!
+
+    ---
+
+    .. link-button:: https://github.com/jagilley/fact-checker
+        :type: url
+        :text: Fact Checker
+        :classes: stretched-link btn-lg
+    
+    +++
+
+    This repo is a simple demonstration of using LangChain to do fact-checking with prompt chaining.
+    
+    ---
+
+    .. link-button:: https://github.com/arc53/docsgpt
+        :type: url
+        :text: DocsGPT
+        :classes: stretched-link btn-lg
+    
+    +++
+
+    Answer questions about the documentation of any project    
+
+Misc. Colab Notebooks
+~~~~~~~~~~~~~~~
+
+.. panels::
+    :body: text-center
+
+    ---
+
+    .. link-button:: https://colab.research.google.com/drive/1AAyEdTz-Z6ShKvewbt1ZHUICqak0MiwR?usp=sharing
+        :type: url
+        :text: Wolfram Alpha in Conversational Agent
+        :classes: stretched-link btn-lg
+    
+    +++
+
+    Give ChatGPT a WolframAlpha neural implant
+    
+    ---
+
+    .. link-button:: https://colab.research.google.com/drive/1UsCLcPy8q5PMNQ5ytgrAAAHa124dzLJg?usp=sharing
+        :type: url
+        :text: Tool Updates in Agents
+        :classes: stretched-link btn-lg
+    
+    +++
+
+    Agent improvements (6th Jan 2023)
+    
+    ---
+
+    .. link-button:: https://colab.research.google.com/drive/1UsCLcPy8q5PMNQ5ytgrAAAHa124dzLJg?usp=sharing
+        :type: url
+        :text: Conversational Agent with Tools (Langchain AGI)
+        :classes: stretched-link btn-lg
+    
+    +++
+
+    Langchain AGI (23rd Dec 2022)    
+
+Proprietary
+-----------
+
+.. panels::
+    :body: text-center
+
+    ---
+
+    .. link-button:: https://twitter.com/sjwhitmore/status/1580593217153531908?s=20&t=neQvtZZTlp623U3LZwz3bQ
+        :type: url
+        :text: Daimon
+        :classes: stretched-link btn-lg
+
+    +++
+
+    A chat-based AI personal assistant with long-term memory about you.
+
+    ---
+
+    .. link-button:: https://twitter.com/dory111111/status/1608406234646052870?s=20&t=XYlrbKM0ornJsrtGa0br-g
+        :type: url
+        :text: AI Assisted SQL Query Generator
+        :classes: stretched-link btn-lg
+
+    +++
+
+    An app to write SQL using natural language, and execute against real DB.
+
+    ---
+
+    .. link-button:: https://twitter.com/krrish_dh/status/1581028925618106368?s=20&t=neQvtZZTlp623U3LZwz3bQ
+        :type: url
+        :text: Clerkie
+        :classes: stretched-link btn-lg
+
+    +++
+
+    Stack Tracing QA Bot to help debug complex stack tracing (especially the ones that go multi-function/file deep).
+
+    ---
+
+    .. link-button:: https://twitter.com/Raza_Habib496/status/1596880140490838017?s=20&t=6MqEQYWfSqmJwsKahjCVOA
+        :type: url
+        :text: Sales Email Writer
+        :classes: stretched-link btn-lg
+
+    +++
+
+    By Raza Habib, this demo utilizes LangChain + SerpAPI + HumanLoop to write sales emails. Give it a company name and a person, this application will use Google Search (via SerpAPI) to get more information on the company and the person, and then write them a sales message.
+
+    ---
+
+    .. link-button:: https://twitter.com/chillzaza_/status/1592961099384905730?s=20&t=EhU8jl0KyCPJ7vE9Rnz-cQ
+        :type: url
+        :text: Question-Answering on a Web Browser
+        :classes: stretched-link btn-lg
+
+    +++
+
+    By Zahid Khawaja, this demo utilizes question answering to answer questions about a given website. A followup added this for `YouTube videos <https://twitter.com/chillzaza_/status/1593739682013220865?s=20&t=EhU8jl0KyCPJ7vE9Rnz-cQ>`_, and then another followup added it for `Wikipedia <https://twitter.com/chillzaza_/status/1594847151238037505?s=20&t=EhU8jl0KyCPJ7vE9Rnz-cQ>`_.
+
+    ---
+
+    .. link-button:: https://mynd.so
+        :type: url
+        :text: Mynd
+        :classes: stretched-link btn-lg
+
+    +++
+
+    A journaling app for self-care that uses AI to uncover insights and patterns over time.
+    

docs/getting_started/getting_started.md

@@ -0,0 +1,290 @@
+# Quickstart Guide
+
+
+This tutorial gives you a quick walkthrough about building an end-to-end language model application with LangChain.
+
+## Installation
+
+To get started, install LangChain with the following command:
+
+```bash
+pip install langchain
+```
+
+
+## Environment Setup
+
+Using LangChain will usually require integrations with one or more model providers, data stores, apis, etc.
+
+For this example, we will be using OpenAI's APIs, so we will first need to install their SDK:
+
+```bash
+pip install openai
+```
+
+We will then need to set the environment variable in the terminal.
+
+```bash
+export OPENAI_API_KEY="..."
+```
+
+Alternatively, you could do this from inside the Jupyter notebook (or Python script):
+
+```python
+import os
+os.environ["OPENAI_API_KEY"] = "..."
+```
+
+
+## Building a Language Model Application
+
+Now that we have installed LangChain and set up our environment, we can start building our language model application.
+
+LangChain provides many modules that can be used to build language model applications. Modules can be combined to create more complex applications, or be used individually for simple applications.
+
+
+
+`````{dropdown} LLMs: Get predictions from a language model
+
+The most basic building block of LangChain is calling an LLM on some input.
+Let's walk through a simple example of how to do this. 
+For this purpose, let's pretend we are building a service that generates a company name based on what the company makes.
+
+In order to do this, we first need to import the LLM wrapper.
+
+```python
+from langchain.llms import OpenAI
+```
+
+We can then initialize the wrapper with any arguments.
+In this example, we probably want the outputs to be MORE random, so we'll initialize it with a HIGH temperature.
+
+```python
+llm = OpenAI(temperature=0.9)
+```
+
+We can now call it on some input!
+
+```python
+text = "What would be a good company name for a company that makes colorful socks?"
+print(llm(text))
+```
+
+```pycon
+Feetful of Fun
+```
+
+For more details on how to use LLMs within LangChain, see the [LLM getting started guide](../modules/llms/getting_started.ipynb).
+`````
+
+
+`````{dropdown} Prompt Templates: Manage prompts for LLMs
+
+Calling an LLM is a great first step, but it's just the beginning.
+Normally when you use an LLM in an application, you are not sending user input directly to the LLM.
+Instead, you are probably taking user input and constructing a prompt, and then sending that to the LLM.
+
+For example, in the previous example, the text we passed in was hardcoded to ask for a name for a company that made colorful socks.
+In this imaginary service, what we would want to do is take only the user input describing what the company does, and then format the prompt with that information.
+
+This is easy to do with LangChain!
+
+First lets define the prompt template:
+
+```python
+from langchain.prompts import PromptTemplate
+
+prompt = PromptTemplate(
+    input_variables=["product"],
+    template="What is a good name for a company that makes {product}?",
+)
+```
+
+Let's now see how this works! We can call the `.format` method to format it.
+
+```python
+print(prompt.format(product="colorful socks"))
+```
+
+```pycon
+What is a good name for a company that makes colorful socks?
+```
+
+
+[For more details, check out the getting started guide for prompts.](../modules/prompts/getting_started.ipynb)
+
+`````
+
+
+
+`````{dropdown} Chains: Combine LLMs and prompts in multi-step workflows
+
+Up until now, we've worked with the PromptTemplate and LLM primitives by themselves. But of course, a real application is not just one primitive, but rather a combination of them.
+
+A chain in LangChain is made up of links, which can be either primitives like LLMs or other chains.
+
+The most core type of chain is an LLMChain, which consists of a PromptTemplate and an LLM.
+
+Extending the previous example, we can construct an LLMChain which takes user input, formats it with a PromptTemplate, and then passes the formatted response to an LLM.
+
+```python
+from langchain.prompts import PromptTemplate
+from langchain.llms import OpenAI
+
+llm = OpenAI(temperature=0.9)
+prompt = PromptTemplate(
+    input_variables=["product"],
+    template="What is a good name for a company that makes {product}?",
+)
+```
+
+We can now create a very simple chain that will take user input, format the prompt with it, and then send it to the LLM:
+
+```python
+from langchain.chains import LLMChain
+chain = LLMChain(llm=llm, prompt=prompt)
+```
+
+Now we can run that chain only specifying the product!
+
+```python
+chain.run("colorful socks")
+# -> '\n\nSocktastic!'
+```
+
+There we go! There's the first chain - an LLM Chain.
+This is one of the simpler types of chains, but understanding how it works will set you up well for working with more complex chains.
+
+[For more details, check out the getting started guide for chains.](../modules/chains/getting_started.ipynb)
+
+`````
+
+
+`````{dropdown} Agents: Dynamically call chains based on user input
+
+So far the chains we've looked at run in a predetermined order.
+
+Agents no longer do: they use an LLM to determine which actions to take and in what order. An action can either be using a tool and observing its output, or returning to the user.
+
+When used correctly agents can be extremely powerful. In this tutorial, we show you how to easily use agents through the simplest, highest level API.
+
+
+In order to load agents, you should understand the following concepts:
+
+- Tool: A function that performs a specific duty. This can be things like: Google Search, Database lookup, Python REPL, other chains. The interface for a tool is currently a function that is expected to have a string as an input, with a string as an output.
+- LLM: The language model powering the agent.
+- Agent: The agent to use. This should be a string that references a support agent class. Because this notebook focuses on the simplest, highest level API, this only covers using the standard supported agents. If you want to implement a custom agent, see the documentation for custom agents (coming soon).
+
+**Agents**: For a list of supported agents and their specifications, see [here](../modules/agents/agents.md).
+
+**Tools**: For a list of predefined tools and their specifications, see [here](../modules/agents/tools.md).
+
+For this example, you will also need to install the SerpAPI Python package.
+
+```bash
+pip install google-search-results
+```
+
+And set the appropriate environment variables.
+
+```python
+import os
+os.environ["SERPAPI_API_KEY"] = "..."
+```
+
+Now we can get started!
+
+```python
+from langchain.agents import load_tools
+from langchain.agents import initialize_agent
+from langchain.llms import OpenAI
+
+# First, let's load the language model we're going to use to control the agent.
+llm = OpenAI(temperature=0)
+
+# Next, let's load some tools to use. Note that the `llm-math` tool uses an LLM, so we need to pass that in.
+tools = load_tools(["serpapi", "llm-math"], llm=llm)
+
+
+# Finally, let's initialize an agent with the tools, the language model, and the type of agent we want to use.
+agent = initialize_agent(tools, llm, agent="zero-shot-react-description", verbose=True)
+
+# Now let's test it out!
+agent.run("Who is Olivia Wilde's boyfriend? What is his current age raised to the 0.23 power?")
+```
+
+```pycon
+Entering new AgentExecutor chain...
+ I need to find out who Olivia Wilde's boyfriend is and then calculate his age raised to the 0.23 power.
+Action: Search
+Action Input: "Olivia Wilde boyfriend"
+Observation: Jason Sudeikis
+Thought: I need to find out Jason Sudeikis' age
+Action: Search
+Action Input: "Jason Sudeikis age"
+Observation: 47 years
+Thought: I need to calculate 47 raised to the 0.23 power
+Action: Calculator
+Action Input: 47^0.23
+Observation: Answer: 2.4242784855673896
+
+Thought: I now know the final answer
+Final Answer: Jason Sudeikis, Olivia Wilde's boyfriend, is 47 years old and his age raised to the 0.23 power is 2.4242784855673896.
+> Finished AgentExecutor chain.
+"Jason Sudeikis, Olivia Wilde's boyfriend, is 47 years old and his age raised to the 0.23 power is 2.4242784855673896."
+```
+
+
+`````
+
+
+`````{dropdown} Memory: Add state to chains and agents
+
+So far, all the chains and agents we've gone through have been stateless. But often, you may want a chain or agent to have some concept of "memory" so that it may remember information about its previous interactions. The clearest and simple example of this is when designing a chatbot - you want it to remember previous messages so it can use context from that to have a better conversation. This would be a type of "short-term memory". On the more complex side, you could imagine a chain/agent remembering key pieces of information over time - this would be a form of "long-term memory". For more concrete ideas on the latter, see this [awesome paper](https://memprompt.com/).
+
+LangChain provides several specially created chains just for this purpose. This notebook walks through using one of those chains (the `ConversationChain`) with two different types of memory.
+
+By default, the `ConversationChain` has a simple type of memory that remembers all previous inputs/outputs and adds them to the context that is passed. Let's take a look at using this chain (setting `verbose=True` so we can see the prompt).
+
+```python
+from langchain import OpenAI, ConversationChain
+
+llm = OpenAI(temperature=0)
+conversation = ConversationChain(llm=llm, verbose=True)
+
+conversation.predict(input="Hi there!")
+```
+
+```pycon
+> Entering new chain...
+Prompt after formatting:
+The following is a friendly conversation between a human and an AI. The AI is talkative and provides lots of specific details from its context. If the AI does not know the answer to a question, it truthfully says it does not know.
+
+Current conversation:
+
+Human: Hi there!
+AI:
+
+> Finished chain.
+' Hello! How are you today?'
+```
+
+```python
+conversation.predict(input="I'm doing well! Just having a conversation with an AI.")
+```
+
+```pycon
+> Entering new chain...
+Prompt after formatting:
+The following is a friendly conversation between a human and an AI. The AI is talkative and provides lots of specific details from its context. If the AI does not know the answer to a question, it truthfully says it does not know.
+
+Current conversation:
+
+Human: Hi there!
+AI:  Hello! How are you today?
+Human: I'm doing well! Just having a conversation with an AI.
+AI:
+
+> Finished chain.
+" That's great! What would you like to talk about?"
+```

docs/glossary.md

@@ -0,0 +1,90 @@
+# Glossary
+
+This is a collection of terminology commonly used when developing LLM applications.
+It contains reference to external papers or sources where the concept was first introduced,
+as well as to places in LangChain where the concept is used.
+
+## Chain of Thought Prompting
+
+A prompting technique used to encourage the model to generate a series of intermediate reasoning steps.
+A less formal way to induce this behavior is to include “Let’s think step-by-step” in the prompt.
+
+Resources:
+
+- [Chain-of-Thought Paper](https://arxiv.org/pdf/2201.11903.pdf)
+- [Step-by-Step Paper](https://arxiv.org/abs/2112.00114)
+
+## Action Plan Generation
+
+A prompt usage that uses a language model to generate actions to take.
+The results of these actions can then be fed back into the language model to generate a subsequent action.
+
+Resources:
+
+- [WebGPT Paper](https://arxiv.org/pdf/2112.09332.pdf)
+- [SayCan Paper](https://say-can.github.io/assets/palm_saycan.pdf)
+
+## ReAct Prompting
+
+A prompting technique that combines Chain-of-Thought prompting with action plan generation.
+This induces the to model to think about what action to take, then take it.
+
+Resources:
+
+- [Paper](https://arxiv.org/pdf/2210.03629.pdf)
+- [LangChain Example](./modules/agents/implementations/react.ipynb)
+
+## Self-ask
+
+A prompting method that builds on top of chain-of-thought prompting.
+In this method, the model explicitly asks itself follow-up questions, which are then answered by an external search engine.
+
+Resources:
+
+- [Paper](https://ofir.io/self-ask.pdf)
+- [LangChain Example](./modules/agents/implementations/self_ask_with_search.ipynb)
+
+## Prompt Chaining
+
+Combining multiple LLM calls together, with the output of one-step being the input to the next.
+
+Resources:
+
+- [PromptChainer Paper](https://arxiv.org/pdf/2203.06566.pdf)
+- [Language Model Cascades](https://arxiv.org/abs/2207.10342)
+- [ICE Primer Book](https://primer.ought.org/)
+- [Socratic Models](https://socraticmodels.github.io/)
+
+## Memetic Proxy
+
+Encouraging the LLM to respond in a certain way framing the discussion in a context that the model knows of and that will result in that type of response. For example, as a conversation between a student and a teacher.
+
+Resources:
+
+- [Paper](https://arxiv.org/pdf/2102.07350.pdf)
+
+## Self Consistency
+
+A decoding strategy that samples a diverse set of reasoning paths and then selects the most consistent answer.
+Is most effective when combined with Chain-of-thought prompting.
+
+Resources:
+
+- [Paper](https://arxiv.org/pdf/2203.11171.pdf)
+
+## Inception
+
+Also called “First Person Instruction”.
+Encouraging the model to think a certain way by including the start of the model’s response in the prompt.
+
+Resources:
+
+- [Example](https://twitter.com/goodside/status/1583262455207460865?s=20&t=8Hz7XBnK1OF8siQrxxCIGQ)
+
+## MemPrompt
+
+MemPrompt maintains a memory of errors and user feedback, and uses them to prevent repetition of mistakes.
+
+Resources:
+
+- [Paper](https://memprompt.com/)

docs/index.rst

@@ -0,0 +1,194 @@
+Welcome to LangChain
+==========================
+
+Large language models (LLMs) are emerging as a transformative technology, enabling
+developers to build applications that they previously could not.
+But using these LLMs in isolation is often not enough to
+create a truly powerful app - the real power comes when you are able to
+combine them with other sources of computation or knowledge.
+
+This library is aimed at assisting in the development of those types of applications. Common examples of these types of applications include:
+
+**❓ Question Answering over specific documents**
+
+- `Documentation <./use_cases/question_answering.html>`_
+- End-to-end Example: `Question Answering over Notion Database <https://github.com/hwchase17/notion-qa>`_
+
+**💬 Chatbots**
+
+- `Documentation <./use_cases/chatbots.html>`_
+- End-to-end Example: `Chat-LangChain <https://github.com/hwchase17/chat-langchain>`_
+
+**🤖 Agents**
+
+- `Documentation <./use_cases/agents.html>`_
+- End-to-end Example: `GPT+WolframAlpha <https://huggingface.co/spaces/JavaFXpert/Chat-GPT-LangChain>`_
+
+Getting Started
+----------------
+
+Checkout the below guide for a walkthrough of how to get started using LangChain to create an Language Model application.
+
+- `Getting Started Documentation <./getting_started/getting_started.html>`_
+
+.. toctree::
+   :maxdepth: 1
+   :caption: Getting Started
+   :name: getting_started
+   :hidden:
+
+   getting_started/getting_started.md
+
+Modules
+-----------
+
+There are several main modules that LangChain provides support for.
+For each module we provide some examples to get started, how-to guides, reference docs, and conceptual guides.
+These modules are, in increasing order of complexity:
+
+
+- `Prompts <./modules/prompts.html>`_: This includes prompt management, prompt optimization, and prompt serialization.
+
+- `LLMs <./modules/llms.html>`_: This includes a generic interface for all LLMs, and common utilities for working with LLMs.
+
+- `Document Loaders <./modules/document_loaders.html>`_: This includes a standard interface for loading documents, as well as specific integrations to all types of text data sources.
+
+- `Utils <./modules/utils.html>`_: Language models are often more powerful when interacting with other sources of knowledge or computation. This can include Python REPLs, embeddings, search engines, and more. LangChain provides a large collection of common utils to use in your application.
+
+- `Chains <./modules/chains.html>`_: Chains go beyond just a single LLM call, and are sequences of calls (whether to an LLM or a different utility). LangChain provides a standard interface for chains, lots of integrations with other tools, and end-to-end chains for common applications.
+
+- `Indexes <./modules/indexes.html>`_: Language models are often more powerful when combined with your own text data - this module covers best practices for doing exactly that.
+
+- `Agents <./modules/agents.html>`_: Agents involve an LLM making decisions about which Actions to take, taking that Action, seeing an Observation, and repeating that until done. LangChain provides a standard interface for agents, a selection of agents to choose from, and examples of end to end agents.
+
+- `Memory <./modules/memory.html>`_: Memory is the concept of persisting state between calls of a chain/agent. LangChain provides a standard interface for memory, a collection of memory implementations, and examples of chains/agents that use memory.
+
+- `Chat <./modules/chat.html>`_: Chat models are a variation on Language Models that expose a different API - rather than working with raw text, they work with messages. LangChain provides a standard interface for working with them and doing all the same things as above.
+
+
+.. toctree::
+   :maxdepth: 1
+   :caption: Modules
+   :name: modules
+   :hidden:
+
+   ./modules/prompts.md
+   ./modules/llms.md
+   ./modules/document_loaders.md
+   ./modules/utils.md
+   ./modules/indexes.md
+   ./modules/chains.md
+   ./modules/agents.md
+   ./modules/memory.md
+   ./modules/chat.md
+
+Use Cases
+----------
+
+The above modules can be used in a variety of ways. LangChain also provides guidance and assistance in this. Below are some of the common use cases LangChain supports.
+
+- `Agents <./use_cases/agents.html>`_: Agents are systems that use a language model to interact with other tools. These can be used to do more grounded question/answering, interact with APIs, or even take actions.
+
+- `Chatbots <./use_cases/chatbots.html>`_: Since language models are good at producing text, that makes them ideal for creating chatbots.
+
+- `Data Augmented Generation <./use_cases/combine_docs.html>`_: Data Augmented Generation involves specific types of chains that first interact with an external datasource to fetch data to use in the generation step. Examples of this include summarization of long pieces of text and question/answering over specific data sources.
+
+- `Question Answering <./use_cases/question_answering.html>`_: Answering questions over specific documents, only utilizing the information in those documents to construct an answer. A type of Data Augmented Generation.
+
+- `Summarization <./use_cases/summarization.html>`_: Summarizing longer documents into shorter, more condensed chunks of information. A type of Data Augmented Generation.
+
+- `Querying Tabular Data <./use_cases/tabular.html>`_: If you want to understand how to use LLMs to query data that is stored in a tabular format (csvs, SQL, dataframes, etc) you should read this page.
+
+- `Evaluation <./use_cases/evaluation.html>`_: Generative models are notoriously hard to evaluate with traditional metrics. One new way of evaluating them is using language models themselves to do the evaluation. LangChain provides some prompts/chains for assisting in this.
+
+- `Generate similar examples <./use_cases/generate_examples.html>`_: Generating similar examples to a given input. This is a common use case for many applications, and LangChain provides some prompts/chains for assisting in this.
+
+- `Compare models <./use_cases/model_laboratory.html>`_: Experimenting with different prompts, models, and chains is a big part of developing the best possible application. The ModelLaboratory makes it easy to do so.
+
+
+
+.. toctree::
+   :maxdepth: 1
+   :caption: Use Cases
+   :name: use_cases
+   :hidden:
+
+   ./use_cases/agents.md
+   ./use_cases/chatbots.md
+   ./use_cases/generate_examples.ipynb
+   ./use_cases/combine_docs.md
+   ./use_cases/question_answering.md
+   ./use_cases/summarization.md
+   ./use_cases/tabular.rst
+   ./use_cases/evaluation.rst
+   ./use_cases/model_laboratory.ipynb
+
+
+Reference Docs
+---------------
+
+All of LangChain's reference documentation, in one place. Full documentation on all methods, classes, installation methods, and integration setups for LangChain.
+
+
+- `Reference Documentation <./reference.html>`_
+.. toctree::
+   :maxdepth: 1
+   :caption: Reference
+   :name: reference
+   :hidden:
+
+   ./reference/installation.md
+   ./reference/integrations.md
+   ./reference.rst
+
+
+LangChain Ecosystem
+-------------------
+
+Guides for how other companies/products can be used with LangChain
+
+- `LangChain Ecosystem <./ecosystem.html>`_
+
+.. toctree::
+   :maxdepth: 1
+   :glob:
+   :caption: Ecosystem
+   :name: ecosystem
+   :hidden:
+
+   ./ecosystem.rst
+
+
+Additional Resources
+---------------------
+
+Additional collection of resources we think may be useful as you develop your application!
+
+- `LangChainHub <https://github.com/hwchase17/langchain-hub>`_: The LangChainHub is a place to share and explore other prompts, chains, and agents.
+
+- `Glossary <./glossary.html>`_: A glossary of all related terms, papers, methods, etc. Whether implemented in LangChain or not!
+
+- `Gallery <./gallery.html>`_: A collection of our favorite projects that use LangChain. Useful for finding inspiration or seeing how things were done in other applications.
+
+- `Deployments <./deployments.html>`_: A collection of instructions, code snippets, and template repositories for deploying LangChain apps.
+
+- `Discord <https://discord.gg/6adMQxSpJS>`_: Join us on our Discord to discuss all things LangChain!
+
+- `Tracing <./tracing.html>`_: A guide on using tracing in LangChain to visualize the execution of chains and agents.
+
+- `Production Support <https://forms.gle/57d8AmXBYp8PP8tZA>`_: As you move your LangChains into production, we'd love to offer more comprehensive support. Please fill out this form and we'll set up a dedicated support Slack channel.
+
+
+.. toctree::
+   :maxdepth: 1
+   :caption: Additional Resources
+   :name: resources
+   :hidden:
+
+   LangChainHub <https://github.com/hwchase17/langchain-hub>
+   ./glossary.md
+   ./gallery.rst
+   ./deployments.md
+   ./tracing.md
+   Discord <https://discord.gg/6adMQxSpJS>
+   Production Support <https://forms.gle/57d8AmXBYp8PP8tZA>

docs/make.bat

@@ -0,0 +1,35 @@
+@ECHO OFF
+
+pushd %~dp0
+
+REM Command file for Sphinx documentation
+
+if "%SPHINXBUILD%" == "" (
+	set SPHINXBUILD=sphinx-build
+)
+set SOURCEDIR=.
+set BUILDDIR=_build
+
+if "%1" == "" goto help
+
+%SPHINXBUILD% >NUL 2>NUL
+if errorlevel 9009 (
+	echo.
+	echo.The 'sphinx-build' command was not found. Make sure you have Sphinx
+	echo.installed, then set the SPHINXBUILD environment variable to point
+	echo.to the full path of the 'sphinx-build' executable. Alternatively you
+	echo.may add the Sphinx directory to PATH.
+	echo.
+	echo.If you don't have Sphinx installed, grab it from
+	echo.http://sphinx-doc.org/
+	exit /b 1
+)
+
+%SPHINXBUILD% -M %1 %SOURCEDIR% %BUILDDIR% %SPHINXOPTS% %O%
+goto end
+
+:help
+%SPHINXBUILD% -M help %SOURCEDIR% %BUILDDIR% %SPHINXOPTS% %O%
+
+:end
+popd

docs/modules/agents.rst

@@ -0,0 +1,30 @@
+Agents
+==========================
+
+Some applications will require not just a predetermined chain of calls to LLMs/other tools,
+but potentially an unknown chain that depends on the user's input.
+In these types of chains, there is a “agent” which has access to a suite of tools.
+Depending on the user input, the agent can then decide which, if any, of these tools to call.
+
+The following sections of documentation are provided:
+
+- `Getting Started <./agents/getting_started.html>`_: A notebook to help you get started working with agents as quickly as possible.
+
+- `Key Concepts <./agents/key_concepts.html>`_: A conceptual guide going over the various concepts related to agents.
+
+- `How-To Guides <./agents/how_to_guides.html>`_: A collection of how-to guides. These highlight how to integrate various types of tools, how to work with different types of agents, and how to customize agents.
+
+- `Reference <../reference/modules/agents.html>`_: API reference documentation for all Agent classes.
+
+
+
+.. toctree::
+   :maxdepth: 1
+   :caption: Agents
+   :name: Agents
+   :hidden:
+
+   ./agents/getting_started.ipynb
+   ./agents/key_concepts.md
+   ./agents/how_to_guides.rst
+   Reference<../reference/modules/agents.rst>

docs/modules/agents/agent_toolkits/csv.ipynb

@@ -0,0 +1,202 @@
+{
+ "cells": [
+  {
+   "cell_type": "markdown",
+   "id": "7094e328",
+   "metadata": {},
+   "source": [
+    "# CSV Agent\n",
+    "\n",
+    "This notebook shows how to use agents to interact with a csv. It is mostly optimized for question answering.\n",
+    "\n",
+    "**NOTE: this agent calls the Pandas DataFrame agent under the hood, which in turn calls the Python agent, which executes LLM generated Python code - this can be bad if the LLM generated Python code is harmful. Use cautiously.**\n",
+    "\n"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 1,
+   "id": "827982c7",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain.agents import create_csv_agent"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 2,
+   "id": "caae0bec",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain.llms import OpenAI"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 11,
+   "id": "16c4dc59",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "agent = create_csv_agent(OpenAI(temperature=0), 'titanic.csv', verbose=True)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 12,
+   "id": "46b9489d",
+   "metadata": {},
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "\n",
+      "\n",
+      "\u001b[1m> Entering new AgentExecutor chain...\u001b[0m\n",
+      "\u001b[32;1m\u001b[1;3mThought: I need to count the number of rows\n",
+      "Action: python_repl_ast\n",
+      "Action Input: len(df)\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3m891\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I now know the final answer\n",
+      "Final Answer: There are 891 rows in the dataframe.\u001b[0m\n",
+      "\n",
+      "\u001b[1m> Finished chain.\u001b[0m\n"
+     ]
+    },
+    {
+     "data": {
+      "text/plain": [
+       "'There are 891 rows in the dataframe.'"
+      ]
+     },
+     "execution_count": 12,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "agent.run(\"how many rows are there?\")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 6,
+   "id": "a96309be",
+   "metadata": {},
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "\n",
+      "\n",
+      "\u001b[1m> Entering new AgentExecutor chain...\u001b[0m\n",
+      "\u001b[32;1m\u001b[1;3mThought: I need to count the number of people with more than 3 siblings\n",
+      "Action: python_repl_ast\n",
+      "Action Input: df[df['SibSp'] > 3].shape[0]\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3m30\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I now know the final answer\n",
+      "Final Answer: 30 people have more than 3 siblings.\u001b[0m\n",
+      "\n",
+      "\u001b[1m> Finished chain.\u001b[0m\n"
+     ]
+    },
+    {
+     "data": {
+      "text/plain": [
+       "'30 people have more than 3 siblings.'"
+      ]
+     },
+     "execution_count": 6,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "agent.run(\"how many people have more than 3 sibligngs\")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 7,
+   "id": "964a09f7",
+   "metadata": {},
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "\n",
+      "\n",
+      "\u001b[1m> Entering new AgentExecutor chain...\u001b[0m\n",
+      "\u001b[32;1m\u001b[1;3mThought: I need to calculate the average age first\n",
+      "Action: python_repl_ast\n",
+      "Action Input: df['Age'].mean()\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3m29.69911764705882\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I can now calculate the square root\n",
+      "Action: python_repl_ast\n",
+      "Action Input: math.sqrt(df['Age'].mean())\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3mname 'math' is not defined\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I need to import the math library\n",
+      "Action: python_repl_ast\n",
+      "Action Input: import math\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3mNone\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I can now calculate the square root\n",
+      "Action: python_repl_ast\n",
+      "Action Input: math.sqrt(df['Age'].mean())\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3m5.449689683556195\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I now know the final answer\n",
+      "Final Answer: 5.449689683556195\u001b[0m\n",
+      "\n",
+      "\u001b[1m> Finished chain.\u001b[0m\n"
+     ]
+    },
+    {
+     "data": {
+      "text/plain": [
+       "'5.449689683556195'"
+      ]
+     },
+     "execution_count": 7,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "agent.run(\"whats the square root of the average age?\")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "551de2be",
+   "metadata": {},
+   "outputs": [],
+   "source": []
+  }
+ ],
+ "metadata": {
+  "kernelspec": {
+   "display_name": "Python 3 (ipykernel)",
+   "language": "python",
+   "name": "python3"
+  },
+  "language_info": {
+   "codemirror_mode": {
+    "name": "ipython",
+    "version": 3
+   },
+   "file_extension": ".py",
+   "mimetype": "text/x-python",
+   "name": "python",
+   "nbconvert_exporter": "python",
+   "pygments_lexer": "ipython3",
+   "version": "3.9.1"
+  }
+ },
+ "nbformat": 4,
+ "nbformat_minor": 5
+}

docs/modules/agents/agent_toolkits/json.ipynb

@@ -0,0 +1,190 @@
+{
+ "cells": [
+  {
+   "cell_type": "markdown",
+   "id": "85fb2c03-ab88-4c8c-97e3-a7f2954555ab",
+   "metadata": {},
+   "source": [
+    "# JSON Agent\n",
+    "\n",
+    "This notebook showcases an agent designed to interact with large JSON/dict objects. This is useful when you want to answer questions about a JSON blob that's too large to fit in the context window of an LLM. The agent is able to iteratively explore the blob to find what it needs to answer the user's question.\n",
+    "\n",
+    "In the below example, we are using the OpenAPI spec for the OpenAI API, which you can find [here](https://github.com/openai/openai-openapi/blob/master/openapi.yaml).\n",
+    "\n",
+    "We will use the JSON agent to answer some questions about the API spec."
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "893f90fd-f8f6-470a-a76d-1f200ba02e2f",
+   "metadata": {},
+   "source": [
+    "## Initialization"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 1,
+   "id": "ff988466-c389-4ec6-b6ac-14364a537fd5",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "import os\n",
+    "import yaml\n",
+    "\n",
+    "from langchain.agents import (\n",
+    "    create_json_agent,\n",
+    "    AgentExecutor\n",
+    ")\n",
+    "from langchain.agents.agent_toolkits import JsonToolkit\n",
+    "from langchain.chains import LLMChain\n",
+    "from langchain.llms.openai import OpenAI\n",
+    "from langchain.requests import RequestsWrapper\n",
+    "from langchain.tools.json.tool import JsonSpec"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 2,
+   "id": "9ecd1ba0-3937-4359-a41e-68605f0596a1",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "with open(\"openai_openapi.yml\") as f:\n",
+    "    data = yaml.load(f, Loader=yaml.FullLoader)\n",
+    "json_spec = JsonSpec(dict_=data, max_value_length=4000)\n",
+    "json_toolkit = JsonToolkit(spec=json_spec)\n",
+    "\n",
+    "json_agent_executor = create_json_agent(\n",
+    "    llm=OpenAI(temperature=0),\n",
+    "    toolkit=json_toolkit,\n",
+    "    verbose=True\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "05cfcb24-4389-4b8f-ad9e-466e3fca8db0",
+   "metadata": {},
+   "source": [
+    "## Example: getting the required POST parameters for a request"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 5,
+   "id": "faf13702-50f0-4d1b-b91f-48c750ccfd98",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "\n",
+      "\n",
+      "\u001b[1m> Entering new AgentExecutor chain...\u001b[0m\n",
+      "\u001b[32;1m\u001b[1;3mAction: json_spec_list_keys\n",
+      "Action Input: data\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3m['openapi', 'info', 'servers', 'tags', 'paths', 'components', 'x-oaiMeta']\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I should look at the paths key to see what endpoints exist\n",
+      "Action: json_spec_list_keys\n",
+      "Action Input: data[\"paths\"]\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3m['/engines', '/engines/{engine_id}', '/completions', '/edits', '/images/generations', '/images/edits', '/images/variations', '/embeddings', '/engines/{engine_id}/search', '/files', '/files/{file_id}', '/files/{file_id}/content', '/answers', '/classifications', '/fine-tunes', '/fine-tunes/{fine_tune_id}', '/fine-tunes/{fine_tune_id}/cancel', '/fine-tunes/{fine_tune_id}/events', '/models', '/models/{model}', '/moderations']\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I should look at the /completions endpoint to see what parameters are required\n",
+      "Action: json_spec_list_keys\n",
+      "Action Input: data[\"paths\"][\"/completions\"]\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3m['post']\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I should look at the post key to see what parameters are required\n",
+      "Action: json_spec_list_keys\n",
+      "Action Input: data[\"paths\"][\"/completions\"][\"post\"]\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3m['operationId', 'tags', 'summary', 'requestBody', 'responses', 'x-oaiMeta']\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I should look at the requestBody key to see what parameters are required\n",
+      "Action: json_spec_list_keys\n",
+      "Action Input: data[\"paths\"][\"/completions\"][\"post\"][\"requestBody\"]\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3m['required', 'content']\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I should look at the required key to see what parameters are required\n",
+      "Action: json_spec_get_value\n",
+      "Action Input: data[\"paths\"][\"/completions\"][\"post\"][\"requestBody\"][\"required\"]\u001b[0m\n",
+      "Observation: \u001b[33;1m\u001b[1;3mTrue\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I should look at the content key to see what parameters are required\n",
+      "Action: json_spec_list_keys\n",
+      "Action Input: data[\"paths\"][\"/completions\"][\"post\"][\"requestBody\"][\"content\"]\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3m['application/json']\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I should look at the application/json key to see what parameters are required\n",
+      "Action: json_spec_list_keys\n",
+      "Action Input: data[\"paths\"][\"/completions\"][\"post\"][\"requestBody\"][\"content\"][\"application/json\"]\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3m['schema']\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I should look at the schema key to see what parameters are required\n",
+      "Action: json_spec_list_keys\n",
+      "Action Input: data[\"paths\"][\"/completions\"][\"post\"][\"requestBody\"][\"content\"][\"application/json\"][\"schema\"]\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3m['$ref']\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I should look at the $ref key to see what parameters are required\n",
+      "Action: json_spec_get_value\n",
+      "Action Input: data[\"paths\"][\"/completions\"][\"post\"][\"requestBody\"][\"content\"][\"application/json\"][\"schema\"][\"$ref\"]\u001b[0m\n",
+      "Observation: \u001b[33;1m\u001b[1;3m#/components/schemas/CreateCompletionRequest\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I should look at the CreateCompletionRequest schema to see what parameters are required\n",
+      "Action: json_spec_list_keys\n",
+      "Action Input: data[\"components\"][\"schemas\"][\"CreateCompletionRequest\"]\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3m['type', 'properties', 'required']\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I should look at the required key to see what parameters are required\n",
+      "Action: json_spec_get_value\n",
+      "Action Input: data[\"components\"][\"schemas\"][\"CreateCompletionRequest\"][\"required\"]\u001b[0m\n",
+      "Observation: \u001b[33;1m\u001b[1;3m['model']\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I now know the final answer\n",
+      "Final Answer: The required parameters in the request body to the /completions endpoint are 'model'.\u001b[0m\n",
+      "\n",
+      "\u001b[1m> Finished chain.\u001b[0m\n"
+     ]
+    },
+    {
+     "data": {
+      "text/plain": [
+       "\"The required parameters in the request body to the /completions endpoint are 'model'.\""
+      ]
+     },
+     "execution_count": 5,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "json_agent_executor.run(\"What are the required parameters in the request body to the /completions endpoint?\")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "ba9c9d30",
+   "metadata": {},
+   "outputs": [],
+   "source": []
+  }
+ ],
+ "metadata": {
+  "kernelspec": {
+   "display_name": "Python 3 (ipykernel)",
+   "language": "python",
+   "name": "python3"
+  },
+  "language_info": {
+   "codemirror_mode": {
+    "name": "ipython",
+    "version": 3
+   },
+   "file_extension": ".py",
+   "mimetype": "text/x-python",
+   "name": "python",
+   "nbconvert_exporter": "python",
+   "pygments_lexer": "ipython3",
+   "version": "3.10.9"
+  }
+ },
+ "nbformat": 4,
+ "nbformat_minor": 5
+}