infra: run codespell on v0.1 prs (#21545)

Reverts langchain-ai/langchain#21458

.devcontainer/README.md

@@ -10,7 +10,7 @@ You can use the dev container configuration in this folder to build and run the
 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**.
+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).
   

.github/ISSUE_TEMPLATE/config.yml

@@ -4,6 +4,9 @@ contact_links:
   - name: 🤔 Question or Problem
     about: Ask a question or ask about a problem in GitHub Discussions.
     url: https://www.github.com/langchain-ai/langchain/discussions/categories/q-a
+  - name: Discord
+    url: https://discord.gg/6adMQxSpJS
+    about: General community discussions
   - name: Feature Request
     url: https://www.github.com/langchain-ai/langchain/discussions/categories/ideas
     about: Suggest a feature or an idea

.github/ISSUE_TEMPLATE/documentation.yml

@@ -26,13 +26,6 @@ body:
       [LangChain Github Discussions](https://github.com/langchain-ai/langchain/discussions),
       [LangChain Github Issues](https://github.com/langchain-ai/langchain/issues?q=is%3Aissue),
       [LangChain ChatBot](https://chat.langchain.com/)
-- type: input
-  id: url
-  attributes:
-    label: URL
-    description: URL to documentation
-  validations:
-    required: false
 - type: checkboxes
   id: checks
   attributes:
@@ -55,4 +48,4 @@ body:
     label: "Idea or request for content:"
     description: >
       Please describe as clearly as possible what topics you think are missing
-      from the current documentation.
+      from the current documentation.

.github/PULL_REQUEST_TEMPLATE.md

@@ -26,4 +26,4 @@ Additional guidelines:
 - Changes should be backwards compatible.
 - If you are adding something to community, do not re-import it in langchain.
 
-If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17.
+If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, hwchase17.

.github/actions/people/app/main.py

@@ -350,7 +350,11 @@ def get_graphql_pr_edges(*, settings: Settings, after: Union[str, None] = None):
         print("Querying PRs...")
     else:
         print(f"Querying PRs with cursor {after}...")
-    data = get_graphql_response(settings=settings, query=prs_query, after=after)
+    data = get_graphql_response(
+        settings=settings,
+        query=prs_query,
+        after=after
+    )
     graphql_response = PRsResponse.model_validate(data)
     return graphql_response.data.repository.pullRequests.edges
 
@@ -480,16 +484,10 @@ def get_contributors(settings: Settings):
             lines_changed = pr.additions + pr.deletions
             score = _logistic(files_changed, 20) + _logistic(lines_changed, 100)
             contributor_scores[pr.author.login] += score
-            three_months_ago = datetime.now(timezone.utc) - timedelta(days=3 * 30)
+            three_months_ago = (datetime.now(timezone.utc) - timedelta(days=3*30))
             if pr.createdAt > three_months_ago:
                 recent_contributor_scores[pr.author.login] += score
-    return (
-        contributors,
-        contributor_scores,
-        recent_contributor_scores,
-        reviewers,
-        authors,
-    )
+    return contributors, contributor_scores, recent_contributor_scores, reviewers, authors
 
 
 def get_top_users(
@@ -526,13 +524,9 @@ if __name__ == "__main__":
     # question_commentors, question_last_month_commentors, question_authors = get_experts(
     #     settings=settings
     # )
-    (
-        contributors,
-        contributor_scores,
-        recent_contributor_scores,
-        reviewers,
-        pr_authors,
-    ) = get_contributors(settings=settings)
+    contributors, contributor_scores, recent_contributor_scores, reviewers, pr_authors = get_contributors(
+        settings=settings
+    )
     # authors = {**question_authors, **pr_authors}
     authors = {**pr_authors}
     maintainers_logins = {
@@ -543,9 +537,7 @@ if __name__ == "__main__":
         "nfcampos",
         "efriis",
         "eyurtsev",
-        "rlancemartin",
-        "ccurme",
-        "vbarda",
+        "rlancemartin"
     }
     hidden_logins = {
         "dev2049",
@@ -553,7 +545,6 @@ if __name__ == "__main__":
         "obi1kenobi",
         "langchain-infra",
         "jacoblee93",
-        "isahers1",
         "dqbd",
         "bracesproul",
         "akira",
@@ -565,7 +556,7 @@ if __name__ == "__main__":
         maintainers.append(
             {
                 "login": login,
-                "count": contributors[login],  # + question_commentors[login],
+                "count": contributors[login], #+ question_commentors[login],
                 "avatarUrl": user.avatarUrl,
                 "twitterUsername": user.twitterUsername,
                 "url": user.url,
@@ -621,7 +612,9 @@ if __name__ == "__main__":
     new_people_content = yaml.dump(
         people, sort_keys=False, width=200, allow_unicode=True
     )
-    if people_old_content == new_people_content:
+    if (
+        people_old_content == new_people_content
+    ):
         logging.info("The LangChain People data hasn't changed, finishing.")
         sys.exit(0)
     people_path.write_text(new_people_content, encoding="utf-8")
@@ -634,7 +627,9 @@ if __name__ == "__main__":
     logging.info(f"Creating a new branch {branch_name}")
     subprocess.run(["git", "checkout", "-B", branch_name], check=True)
     logging.info("Adding updated file")
-    subprocess.run(["git", "add", str(people_path)], check=True)
+    subprocess.run(
+        ["git", "add", str(people_path)], check=True
+    )
     logging.info("Committing updated file")
     message = "👥 Update LangChain people data"
     result = subprocess.run(["git", "commit", "-m", message], check=True)
@@ -643,4 +638,4 @@ if __name__ == "__main__":
     logging.info("Creating PR")
     pr = repo.create_pull(title=message, body=message, base="master", head=branch_name)
     logging.info(f"Created PR: {pr.number}")
-    logging.info("Finished")
+    logging.info("Finished")

.github/scripts/check_diff.py

@@ -1,96 +1,16 @@
-import glob
 import json
-import os
-import re
 import sys
-import tomllib
-from collections import defaultdict
-from typing import Dict, List, Set
-
+import os
+from typing import Dict
 
 LANGCHAIN_DIRS = [
     "libs/core",
     "libs/text-splitters",
-    "libs/langchain",
     "libs/community",
+    "libs/langchain",
     "libs/experimental",
 ]
 
-
-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:
-    dependents = defaultdict(set)
-
-    for path in glob.glob("./libs/**/pyproject.toml", recursive=True):
-        if "template" in path:
-            continue
-        with open(path, "rb") as f:
-            pyproject = tomllib.load(f)["tool"]["poetry"]
-        pkg_dir = "libs" + "/".join(path.split("libs")[1].split("/")[:-1])
-        for dep in pyproject["dependencies"]:
-            if "langchain" in dep:
-                dependents[dep].add(pkg_dir)
-    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]]:
-    min_python = "3.8"
-    max_python = "3.12"
-
-    # custom logic for specific directories
-    if dir_ == "libs/partners/milvus":
-        # milvus poetry doesn't allow 3.12 because they
-        # declare deps in funny way
-        max_python = "3.11"
-
-    return [
-        {"working-directory": dir_, "python-version": min_python},
-        {"working-directory": dir_, "python-version": max_python},
-    ]
-
-
-def _get_configs_for_multi_dirs(
-    job: str, dirs_to_run: List[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"]:
-        dirs = add_dependents(
-            dirs_to_run["test"] | dirs_to_run["extended-test"], dependents
-        )
-    elif job == "extended-tests":
-        dirs = list(dirs_to_run["extended-test"])
-    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:]
 
@@ -101,11 +21,10 @@ if __name__ == "__main__":
     }
     docs_edited = False
 
-    if len(files) >= 300:
+    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)
+        raise ValueError("Max diff reached. Please manually run CI on changed libs.")
+
     for file in files:
         if any(
             file.startswith(dir_)
@@ -162,25 +81,14 @@ if __name__ == "__main__":
                 docs_edited = True
             dirs_to_run["lint"].add(".")
 
-    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",
-        ]
+    outputs = {
+        "dirs-to-lint": list(
+            dirs_to_run["lint"] | dirs_to_run["test"] | dirs_to_run["extended-test"]
+        ),
+        "dirs-to-test": list(dirs_to_run["test"] | dirs_to_run["extended-test"]),
+        "dirs-to-extended-test": list(dirs_to_run["extended-test"]),
+        "docs-edited": "true" if docs_edited else "",
     }
-    map_job_to_configs["test-doc-imports"] = (
-        [{"python-version": "3.12"}] if docs_edited else []
-    )
-
-    for key, value in map_job_to_configs.items():
+    for key, value in outputs.items():
         json_output = json.dumps(value)
-        print(f"{key}={json_output}")
+        print(f"{key}={json_output}")  # noqa: T201

.github/scripts/get_min_versions.py

@@ -74,4 +74,6 @@ if __name__ == "__main__":
     # Call the function to get the minimum versions
     min_versions = get_min_version_from_toml(toml_file)
 
-    print(" ".join([f"{lib}=={version}" for lib, version in min_versions.items()]))
+    print(
+        " ".join([f"{lib}=={version}" for lib, version in min_versions.items()])
+    )  # noqa: T201

.github/workflows/.codespell-exclude

@@ -1,7 +0,0 @@
-libs/community/langchain_community/llms/yuan2.py
-"NotIn": "not in",
-- `/checkin`: Check-in
-docs/docs/integrations/providers/trulens.mdx
-self.assertIn(
-from trulens_eval import Tru
-tru = Tru()

.github/workflows/_compile_integration_test.yml

@@ -7,10 +7,6 @@ on:
         required: true
         type: string
         description: "From which folder this pipeline executes"
-      python-version:
-        required: true
-        type: string
-        description: "Python version to use"
 
 env:
   POETRY_VERSION: "1.7.1"
@@ -28,15 +24,14 @@ jobs:
           - "3.9"
           - "3.10"
           - "3.11"
-          - "3.12"
-    name: "poetry run pytest -m compile tests/integration_tests #${{ inputs.python-version }}"
+    name: "poetry run pytest -m compile tests/integration_tests #${{ matrix.python-version }}"
     steps:
       - uses: actions/checkout@v4
 
-      - name: Set up Python ${{ inputs.python-version }} + Poetry ${{ env.POETRY_VERSION }}
+      - name: Set up Python ${{ matrix.python-version }} + Poetry ${{ env.POETRY_VERSION }}
         uses: "./.github/actions/poetry_setup"
         with:
-          python-version: ${{ inputs.python-version }}
+          python-version: ${{ matrix.python-version }}
           poetry-version: ${{ env.POETRY_VERSION }}
           working-directory: ${{ inputs.working-directory }}
           cache-key: compile-integration

.github/workflows/_dependencies.yml

@@ -11,10 +11,6 @@ on:
         required: false
         type: string
         description: "Relative path to the langchain library folder"
-      python-version:
-        required: true
-        type: string
-        description: "Python version to use"
 
 env:
   POETRY_VERSION: "1.7.1"
@@ -25,14 +21,21 @@ jobs:
       run:
         working-directory: ${{ inputs.working-directory }}
     runs-on: ubuntu-latest
-    name: dependency checks ${{ inputs.python-version }}
+    strategy:
+      matrix:
+        python-version:
+          - "3.8"
+          - "3.9"
+          - "3.10"
+          - "3.11"
+    name: dependency checks ${{ matrix.python-version }}
     steps:
       - uses: actions/checkout@v4
 
-      - name: Set up Python ${{ inputs.python-version }} + Poetry ${{ env.POETRY_VERSION }}
+      - name: Set up Python ${{ matrix.python-version }} + Poetry ${{ env.POETRY_VERSION }}
         uses: "./.github/actions/poetry_setup"
         with:
-          python-version: ${{ inputs.python-version }}
+          python-version: ${{ matrix.python-version }}
           poetry-version: ${{ env.POETRY_VERSION }}
           working-directory: ${{ inputs.working-directory }}
           cache-key: pydantic-cross-compat

.github/workflows/_integration_test.yml

@@ -6,28 +6,30 @@ on:
       working-directory:
         required: true
         type: string
-      python-version:
-        required: true
-        type: string
-        description: "Python version to use"
 
 env:
   POETRY_VERSION: "1.7.1"
 
 jobs:
   build:
+    environment: Scheduled testing
     defaults:
       run:
         working-directory: ${{ inputs.working-directory }}
     runs-on: ubuntu-latest
-    name: Python ${{ inputs.python-version }}
+    strategy:
+      matrix:
+        python-version:
+          - "3.8"
+          - "3.11"
+    name: Python ${{ matrix.python-version }}
     steps:
       - uses: actions/checkout@v4
 
-      - name: Set up Python ${{ inputs.python-version }} + Poetry ${{ env.POETRY_VERSION }}
+      - name: Set up Python ${{ matrix.python-version }} + Poetry ${{ env.POETRY_VERSION }}
         uses: "./.github/actions/poetry_setup"
         with:
-          python-version: ${{ inputs.python-version }}
+          python-version: ${{ matrix.python-version }}
           poetry-version: ${{ env.POETRY_VERSION }}
           working-directory: ${{ inputs.working-directory }}
           cache-key: core
@@ -51,15 +53,8 @@ jobs:
         shell: bash
         env:
           AI21_API_KEY: ${{ secrets.AI21_API_KEY }}
-          FIREWORKS_API_KEY: ${{ secrets.FIREWORKS_API_KEY }}
           GOOGLE_API_KEY: ${{ secrets.GOOGLE_API_KEY }}
           ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_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_LLM_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_LLM_DEPLOYMENT_NAME }}
-          AZURE_OPENAI_EMBEDDINGS_DEPLOYMENT_NAME: ${{ secrets.AZURE_OPENAI_EMBEDDINGS_DEPLOYMENT_NAME }}
           MISTRAL_API_KEY: ${{ secrets.MISTRAL_API_KEY }}
           TOGETHER_API_KEY: ${{ secrets.TOGETHER_API_KEY }}
           OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}

.github/workflows/_lint.yml

@@ -11,10 +11,6 @@ on:
         required: false
         type: string
         description: "Relative path to the langchain library folder"
-      python-version:
-        required: true
-        type: string
-        description: "Python version to use"
 
 env:
   POETRY_VERSION: "1.7.1"
@@ -25,15 +21,27 @@ env:
 
 jobs:
   build:
-    name: "make lint #${{ inputs.python-version }}"
+    name: "make lint #${{ matrix.python-version }}"
     runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        # Only lint on the min and max supported Python versions.
+        # It's extremely unlikely that there's a lint issue on any version in between
+        # that doesn't show up on the min or max versions.
+        #
+        # GitHub rate-limits how many jobs can be running at any one time.
+        # Starting new jobs is also relatively slow,
+        # so linting on fewer versions makes CI faster.
+        python-version:
+          - "3.8"
+          - "3.11"
     steps:
       - uses: actions/checkout@v4
 
-      - name: Set up Python ${{ inputs.python-version }} + Poetry ${{ env.POETRY_VERSION }}
+      - name: Set up Python ${{ matrix.python-version }} + Poetry ${{ env.POETRY_VERSION }}
         uses: "./.github/actions/poetry_setup"
         with:
-          python-version: ${{ inputs.python-version }}
+          python-version: ${{ matrix.python-version }}
           poetry-version: ${{ env.POETRY_VERSION }}
           working-directory: ${{ inputs.working-directory }}
           cache-key: lint-with-extras
@@ -78,7 +86,7 @@ jobs:
         with:
           path: |
             ${{ env.WORKDIR }}/.mypy_cache
-          key: mypy-lint-${{ runner.os }}-${{ runner.arch }}-py${{ inputs.python-version }}-${{ inputs.working-directory }}-${{ hashFiles(format('{0}/poetry.lock', inputs.working-directory)) }}
+          key: mypy-lint-${{ runner.os }}-${{ runner.arch }}-py${{ matrix.python-version }}-${{ inputs.working-directory }}-${{ hashFiles(format('{0}/poetry.lock', inputs.working-directory)) }}
 
 
       - name: Analysing the code with our lint
@@ -112,7 +120,7 @@ jobs:
         with:
           path: |
             ${{ env.WORKDIR }}/.mypy_cache_test
-          key: mypy-test-${{ runner.os }}-${{ runner.arch }}-py${{ inputs.python-version }}-${{ inputs.working-directory }}-${{ hashFiles(format('{0}/poetry.lock', inputs.working-directory)) }}
+          key: mypy-test-${{ runner.os }}-${{ runner.arch }}-py${{ matrix.python-version }}-${{ inputs.working-directory }}-${{ hashFiles(format('{0}/poetry.lock', inputs.working-directory)) }}
 
       - name: Analysing the code with our lint
         working-directory: ${{ inputs.working-directory }}

.github/workflows/_release.yml

@@ -72,69 +72,12 @@ jobs:
         run: |
           echo pkg-name="$(poetry version | cut -d ' ' -f 1)" >> $GITHUB_OUTPUT
           echo version="$(poetry version --short)" >> $GITHUB_OUTPUT
-  release-notes:
-    needs:
-      - build
-    runs-on: ubuntu-latest
-    outputs:
-      release-body: ${{ steps.generate-release-body.outputs.release-body }}
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          repository: langchain-ai/langchain
-          path: langchain
-          sparse-checkout: | # this only grabs files for relevant dir
-            ${{ inputs.working-directory }}
-          ref: master # this scopes to just master 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: |
-          REGEX="^$PKG_NAME==\\d+\\.\\d+\\.\\d+\$"
-          echo $REGEX
-          PREV_TAG=$(git tag --sort=-creatordate | grep -P $REGEX || true | head -1)
-          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, then we are releasing the first version
-          if [ -z "$PREV_TAG" ]; 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
     uses:
       ./.github/workflows/_test_release.yml
-    permissions: write-all
     with:
       working-directory: ${{ inputs.working-directory }}
       dangerous-nonmaster-release: ${{ inputs.dangerous-nonmaster-release }}
@@ -143,7 +86,6 @@ jobs:
   pre-release-checks:
     needs:
       - build
-      - release-notes
       - test-pypi-publish
     runs-on: ubuntu-latest
     steps:
@@ -202,7 +144,7 @@ jobs:
           poetry run python -c "import $IMPORT_NAME; print(dir($IMPORT_NAME))"
 
       - name: Import test dependencies
-        run: poetry install --with test
+        run: poetry install --with test,test_integration
         working-directory: ${{ inputs.working-directory }}
 
       # Overwrite the local version of the package with the test PyPI version.
@@ -235,7 +177,7 @@ jobs:
         env:
           MIN_VERSIONS: ${{ steps.min-version.outputs.min-versions }}
         run: |
-          poetry run pip install --force-reinstall $MIN_VERSIONS --editable .
+          poetry run pip install --force-reinstall $MIN_VERSIONS
           make tests
         working-directory: ${{ inputs.working-directory }}
 
@@ -245,10 +187,6 @@ jobs:
         with:
           credentials_json: '${{ secrets.GOOGLE_CREDENTIALS }}'
 
-      - name: Import integration test dependencies
-        run: poetry install --with test,test_integration
-        working-directory: ${{ inputs.working-directory }}
-
       - name: Run integration tests
         if: ${{ startsWith(inputs.working-directory, 'libs/partners/') }}
         env:
@@ -284,14 +222,12 @@ jobs:
           MONGODB_ATLAS_URI: ${{ secrets.MONGODB_ATLAS_URI }}
           VOYAGE_API_KEY: ${{ secrets.VOYAGE_API_KEY }}
           UPSTAGE_API_KEY: ${{ secrets.UPSTAGE_API_KEY }}
-          FIREWORKS_API_KEY: ${{ secrets.FIREWORKS_API_KEY }}
         run: make integration_tests
         working-directory: ${{ inputs.working-directory }}
 
   publish:
     needs:
       - build
-      - release-notes
       - test-pypi-publish
       - pre-release-checks
     runs-on: ubuntu-latest
@@ -333,7 +269,6 @@ jobs:
   mark-release:
     needs:
       - build
-      - release-notes
       - test-pypi-publish
       - pre-release-checks
       - publish
@@ -370,6 +305,5 @@ jobs:
           token: ${{ secrets.GITHUB_TOKEN }}
           generateReleaseNotes: false
           tag: ${{needs.build.outputs.pkg-name}}==${{ needs.build.outputs.version }}
-          body: ${{ needs.release-notes.outputs.release-body }}
+          body: "# Release ${{needs.build.outputs.pkg-name}}==${{ needs.build.outputs.version }}\n\nPackage-specific release note generation coming soon."
           commit: ${{ github.sha }}
-          makeLatest: ${{ needs.build.outputs.pkg-name == 'langchain-core'}}

.github/workflows/_test.yml

@@ -11,10 +11,6 @@ on:
         required: false
         type: string
         description: "Relative path to the langchain library folder"
-      python-version:
-        required: true
-        type: string
-        description: "Python version to use"
 
 env:
   POETRY_VERSION: "1.7.1"
@@ -25,14 +21,21 @@ jobs:
       run:
         working-directory: ${{ inputs.working-directory }}
     runs-on: ubuntu-latest
-    name: "make test #${{ inputs.python-version }}"
+    strategy:
+      matrix:
+        python-version:
+          - "3.8"
+          - "3.9"
+          - "3.10"
+          - "3.11"
+    name: "make test #${{ matrix.python-version }}"
     steps:
       - uses: actions/checkout@v4
 
-      - name: Set up Python ${{ inputs.python-version }} + Poetry ${{ env.POETRY_VERSION }}
+      - name: Set up Python ${{ matrix.python-version }} + Poetry ${{ env.POETRY_VERSION }}
         uses: "./.github/actions/poetry_setup"
         with:
-          python-version: ${{ inputs.python-version }}
+          python-version: ${{ matrix.python-version }}
           poetry-version: ${{ env.POETRY_VERSION }}
           working-directory: ${{ inputs.working-directory }}
           cache-key: core

.github/workflows/_test_doc_imports.yml

@@ -2,11 +2,6 @@ name: test_doc_imports
 
 on:
   workflow_call:
-    inputs:
-      python-version:
-        required: true
-        type: string
-        description: "Python version to use"
 
 env:
   POETRY_VERSION: "1.7.1"
@@ -17,15 +12,15 @@ jobs:
     strategy:
       matrix:
         python-version:
-          - "3.12"
-    name: "check doc imports #${{ inputs.python-version }}"
+          - "3.11"
+    name: "check doc imports #${{ matrix.python-version }}"
     steps:
       - uses: actions/checkout@v4
 
-      - name: Set up Python ${{ inputs.python-version }} + Poetry ${{ env.POETRY_VERSION }}
+      - name: Set up Python ${{ matrix.python-version }} + Poetry ${{ env.POETRY_VERSION }}
         uses: "./.github/actions/poetry_setup"
         with:
-          python-version: ${{ inputs.python-version }}
+          python-version: ${{ matrix.python-version }}
           poetry-version: ${{ env.POETRY_VERSION }}
           cache-key: core
 

.github/workflows/check-broken-links.yml

@@ -7,7 +7,6 @@ on:
 
 jobs:
   check-links:
-    if: github.repository_owner == 'langchain-ai'
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4

.github/workflows/check_diffs.yml

@@ -26,112 +26,104 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-python@v5
         with:
-          python-version: '3.11'
+          python-version: '3.10'
       - id: files
         uses: Ana06/get-changed-files@v2.2.0
       - id: set-matrix
         run: |
           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-doc-imports: ${{ steps.set-matrix.outputs.test-doc-imports }}
+      dirs-to-lint: ${{ steps.set-matrix.outputs.dirs-to-lint }}
+      dirs-to-test: ${{ steps.set-matrix.outputs.dirs-to-test }}
+      dirs-to-extended-test: ${{ steps.set-matrix.outputs.dirs-to-extended-test }}
+      docs-edited: ${{ steps.set-matrix.outputs.docs-edited }}
   lint:
-    name: cd ${{ matrix.job-configs.working-directory }}
+    name: cd ${{ matrix.working-directory }}
     needs: [ build ]
-    if: ${{ needs.build.outputs.lint != '[]' }}
+    if: ${{ needs.build.outputs.dirs-to-lint != '[]' }}
     strategy:
       matrix:
-        job-configs: ${{ fromJson(needs.build.outputs.lint) }}
+        working-directory: ${{ fromJson(needs.build.outputs.dirs-to-lint) }}
     uses: ./.github/workflows/_lint.yml
     with:
-      working-directory: ${{ matrix.job-configs.working-directory }}
-      python-version: ${{ matrix.job-configs.python-version }}
+      working-directory: ${{ matrix.working-directory }}
     secrets: inherit
 
   test:
-    name: cd ${{ matrix.job-configs.working-directory }}
+    name: cd ${{ matrix.working-directory }}
     needs: [ build ]
-    if: ${{ needs.build.outputs.test != '[]' }}
+    if: ${{ needs.build.outputs.dirs-to-test != '[]' }}
     strategy:
       matrix:
-        job-configs: ${{ fromJson(needs.build.outputs.test) }}
+        working-directory: ${{ fromJson(needs.build.outputs.dirs-to-test) }}
     uses: ./.github/workflows/_test.yml
     with:
-      working-directory: ${{ matrix.job-configs.working-directory }}
-      python-version: ${{ matrix.job-configs.python-version }}
+      working-directory: ${{ matrix.working-directory }}
     secrets: inherit
 
   test-doc-imports:
     needs: [ build ]
-    if: ${{ needs.build.outputs.test-doc-imports != '[]' }}
-    strategy:
-      matrix:
-        job-configs: ${{ fromJson(needs.build.outputs.test-doc-imports) }}
+    if: ${{ needs.build.outputs.dirs-to-test != '[]' || needs.build.outputs.docs-edited }}
     uses: ./.github/workflows/_test_doc_imports.yml
     secrets: inherit
-    with:
-      python-version: ${{ matrix.job-configs.python-version }}
 
   compile-integration-tests:
-    name: cd ${{ matrix.job-configs.working-directory }}
+    name: cd ${{ matrix.working-directory }}
     needs: [ build ]
-    if: ${{ needs.build.outputs.compile-integration-tests != '[]' }}
+    if: ${{ needs.build.outputs.dirs-to-test != '[]' }}
     strategy:
       matrix:
-        job-configs: ${{ fromJson(needs.build.outputs.compile-integration-tests) }}
+        working-directory: ${{ fromJson(needs.build.outputs.dirs-to-test) }}
     uses: ./.github/workflows/_compile_integration_test.yml
     with:
-      working-directory: ${{ matrix.job-configs.working-directory }}
-      python-version: ${{ matrix.job-configs.python-version }}
+      working-directory: ${{ matrix.working-directory }}
     secrets: inherit
 
   dependencies:
-    name: cd ${{ matrix.job-configs.working-directory }}
+    name: cd ${{ matrix.working-directory }}
     needs: [ build ]
-    if: ${{ needs.build.outputs.dependencies != '[]' }}
+    if: ${{ needs.build.outputs.dirs-to-test != '[]' }}
     strategy:
       matrix:
-        job-configs: ${{ fromJson(needs.build.outputs.dependencies) }}
+        working-directory: ${{ fromJson(needs.build.outputs.dirs-to-test) }}
     uses: ./.github/workflows/_dependencies.yml
     with:
-      working-directory: ${{ matrix.job-configs.working-directory }}
-      python-version: ${{ matrix.job-configs.python-version }}
+      working-directory: ${{ matrix.working-directory }}
     secrets: inherit
 
   extended-tests:
-    name: "cd ${{ matrix.job-configs.working-directory }} / make extended_tests #${{ matrix.job-configs.python-version }}"
+    name: "cd ${{ matrix.working-directory }} / make extended_tests #${{ matrix.python-version }}"
     needs: [ build ]
-    if: ${{ needs.build.outputs.extended-tests != '[]' }}
+    if: ${{ needs.build.outputs.dirs-to-extended-test != '[]' }}
     strategy:
       matrix:
         # note different variable for extended test dirs
-        job-configs: ${{ fromJson(needs.build.outputs.extended-tests) }}
+        working-directory: ${{ fromJson(needs.build.outputs.dirs-to-extended-test) }}
+        python-version:
+          - "3.8"
+          - "3.9"
+          - "3.10"
+          - "3.11"
     runs-on: ubuntu-latest
     defaults:
       run:
-        working-directory: ${{ matrix.job-configs.working-directory }}
+        working-directory: ${{ matrix.working-directory }}
     steps:
       - uses: actions/checkout@v4
 
-      - name: Set up Python ${{ matrix.job-configs.python-version }} + Poetry ${{ env.POETRY_VERSION }}
+      - name: Set up Python ${{ matrix.python-version }} + Poetry ${{ env.POETRY_VERSION }}
         uses: "./.github/actions/poetry_setup"
         with:
-          python-version: ${{ matrix.job-configs.python-version }}
+          python-version: ${{ matrix.python-version }}
           poetry-version: ${{ env.POETRY_VERSION }}
-          working-directory: ${{ matrix.job-configs.working-directory }}
+          working-directory: ${{ matrix.working-directory }}
           cache-key: extended
 
       - name: Install dependencies
         shell: bash
         run: |
           echo "Running extended tests, installing dependencies with poetry..."
-          poetry install --with test
-          poetry run pip install uv
-          poetry run uv pip install -r extended_testing_deps.txt
+          poetry install -E extended_testing --with test
 
       - name: Run extended tests
         run: make extended_tests

.github/workflows/check_new_docs.yml

@@ -1,36 +0,0 @@
----
-name: Integration docs lint
-
-on:
-  push:
-    branches: [master]
-  pull_request:
-
-# 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
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-python@v5
-        with:
-          python-version: '3.10'
-      - id: files
-        uses: Ana06/get-changed-files@v2.2.0
-        with:
-          filter: |
-            *.ipynb
-            *.md
-            *.mdx
-      - name: Check new docs
-        run: |
-          python docs/scripts/check_templates.py ${{ steps.files.outputs.added }}

.github/workflows/codespell.yml

@@ -29,9 +29,9 @@ jobs:
           python .github/workflows/extract_ignored_words_list.py
         id: extract_ignore_words
 
-#      - name: Codespell
-#        uses: codespell-project/actions-codespell@v2
-#        with:
-#          skip: guide_imports.json,*.ambr,./cookbook/data/imdb_top_1000.csv,*.lock
-#          ignore_words_list: ${{ steps.extract_ignore_words.outputs.ignore_words_list }}
-#          exclude_file: ./.github/workflows/codespell-exclude
+      - name: Codespell
+        uses: codespell-project/actions-codespell@v2
+        with:
+          skip: guide_imports.json,*.ambr,./cookbook/data/imdb_top_1000.csv,*.lock
+          ignore_words_list: ${{ steps.extract_ignore_words.outputs.ignore_words_list }}
+          exclude_file: libs/community/langchain_community/llms/yuan2.py

.github/workflows/extract_ignored_words_list.py

@@ -7,4 +7,4 @@ ignore_words_list = (
     pyproject_toml.get("tool", {}).get("codespell", {}).get("ignore-words-list")
 )
 
-print(f"::set-output name=ignore_words_list::{ignore_words_list}")
+print(f"::set-output name=ignore_words_list::{ignore_words_list}")  # noqa: T201

.github/workflows/people.yml

@@ -16,7 +16,6 @@ jobs:
   langchain-people:
     if: github.repository_owner == 'langchain-ai'
     runs-on: ubuntu-latest
-    permissions: write-all
     steps:
       - name: Dump GitHub context
         env:

.github/workflows/scheduled_test.yml

@@ -10,11 +10,8 @@ env:
 
 jobs:
   build:
-    if: github.repository_owner == 'langchain-ai'
-    name: Python ${{ matrix.python-version }} - ${{ matrix.working-directory }}
     runs-on: ubuntu-latest
     strategy:
-      fail-fast: false
       matrix:
         python-version:
           - "3.8"
@@ -27,38 +24,16 @@ jobs:
           - "libs/partners/groq"
           - "libs/partners/mistralai"
           - "libs/partners/together"
-          - "libs/partners/google-vertexai"
-          - "libs/partners/google-genai"
-          - "libs/partners/aws"
-
+    name: Python ${{ matrix.python-version }} - ${{ matrix.working-directory }}
     steps:
       - uses: actions/checkout@v4
-        with:
-          path: langchain
-      - uses: actions/checkout@v4
-        with:
-          repository: langchain-ai/langchain-google
-          path: langchain-google
-      - uses: actions/checkout@v4
-        with:
-          repository: langchain-ai/langchain-aws
-          path: langchain-aws
-
-      - name: Move libs
-        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 }}
-        uses: "./langchain/.github/actions/poetry_setup"
+        uses: "./.github/actions/poetry_setup"
         with:
           python-version: ${{ matrix.python-version }}
           poetry-version: ${{ env.POETRY_VERSION }}
-          working-directory: langchain/${{ matrix.working-directory }}
+          working-directory: ${{ matrix.working-directory }}
           cache-key: scheduled
 
       - name: 'Authenticate to Google Cloud'
@@ -67,20 +42,16 @@ jobs:
         with:
           credentials_json: '${{ secrets.GOOGLE_CREDENTIALS }}'
 
-      - name: Configure AWS Credentials
-        uses: aws-actions/configure-aws-credentials@v4
-        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
+        working-directory: ${{ matrix.working-directory }}
+        shell: bash
         run: |
           echo "Running scheduled tests, installing dependencies with poetry..."
-          cd langchain/${{ matrix.working-directory }}
           poetry install --with=test_integration,test
 
       - name: Run integration tests
+        working-directory: ${{ matrix.working-directory }}
+        shell: bash
         env:
           OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
           ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
@@ -95,24 +66,12 @@ jobs:
           GROQ_API_KEY: ${{ secrets.GROQ_API_KEY }}
           MISTRAL_API_KEY: ${{ secrets.MISTRAL_API_KEY }}
           TOGETHER_API_KEY: ${{ secrets.TOGETHER_API_KEY }}
-          COHERE_API_KEY: ${{ secrets.COHERE_API_KEY }}
-          NVIDIA_API_KEY: ${{ secrets.NVIDIA_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 }}
         run: |
-          cd langchain/${{ matrix.working-directory }}
-          make integration_tests
-
-      - name: Remove external libraries
-        run: | 
-          rm -rf \
-            langchain/libs/partners/google-genai \
-            langchain/libs/partners/google-vertexai \
-            langchain/libs/partners/aws
+          make integration_test
 
       - name: Ensure the tests did not create any additional files
-        working-directory: langchain
+        working-directory: ${{ matrix.working-directory }}
+        shell: bash
         run: |
           set -eu
 

.gitignore

@@ -133,7 +133,6 @@ env.bak/
 
 # mypy
 .mypy_cache/
-.mypy_cache_test/
 .dmypy.json
 dmypy.json
 
@@ -179,4 +178,3 @@ _dist
 docs/docs/templates
 
 prof
-virtualenv/

Makefile

@@ -3,7 +3,7 @@
 ## help: Show this help info.
 help: Makefile
 	@printf "\n\033[1mUsage: make <TARGETS> ...\033[0m\n\n\033[1mTargets:\033[0m\n\n"
-	@sed -n 's/^## //p' $< | awk -F':' '{printf "\033[36m%-30s\033[0m %s\n", $$1, $$2}' | sort | sed -e 's/^/  /'
+	@sed -n 's/^##//p' $< | awk -F':' '{printf "\033[36m%-30s\033[0m %s\n", $$1, $$2}' | sort | sed -e 's/^/ /'
 
 ## all: Default target, shows help.
 all: help
@@ -17,7 +17,7 @@ clean: docs_clean api_docs_clean
 
 ## docs_build: Build the documentation.
 docs_build:
-	cd docs && make build
+	cd docs && make build-local
 
 ## docs_clean: Clean the documentation build artifacts.
 docs_clean:
@@ -32,19 +32,10 @@ api_docs_build:
 	poetry run python docs/api_reference/create_api_rst.py
 	cd docs/api_reference && poetry run make html
 
-API_PKG ?= text-splitters
-
-api_docs_quick_preview:
-	poetry run pip install "pydantic<2"
-	poetry run python docs/api_reference/create_api_rst.py $(API_PKG)
-	cd docs/api_reference && poetry run make html
-	open docs/api_reference/_build/html/$(shell echo $(API_PKG) | sed 's/-/_/g')_api_reference.html
-
 ## api_docs_clean: Clean the API Reference documentation build artifacts.
 api_docs_clean:
 	find ./docs/api_reference -name '*_api_reference.rst' -delete
-	git clean -fdX ./docs/api_reference
-	
+	cd docs/api_reference && poetry run make clean
 
 ## api_docs_linkcheck: Run linkchecker on the API Reference documentation.
 api_docs_linkcheck:

README.md

@@ -2,16 +2,17 @@
 
 ⚡ Build context-aware reasoning applications ⚡
 
-[![Release Notes](https://img.shields.io/github/release/langchain-ai/langchain?style=flat-square)](https://github.com/langchain-ai/langchain/releases)
+[![Release Notes](https://img.shields.io/github/release/langchain-ai/langchain)](https://github.com/langchain-ai/langchain/releases)
 [![CI](https://github.com/langchain-ai/langchain/actions/workflows/check_diffs.yml/badge.svg)](https://github.com/langchain-ai/langchain/actions/workflows/check_diffs.yml)
-[![PyPI - License](https://img.shields.io/pypi/l/langchain-core?style=flat-square)](https://opensource.org/licenses/MIT)
-[![PyPI - Downloads](https://img.shields.io/pypi/dm/langchain-core?style=flat-square)](https://pypistats.org/packages/langchain-core)
-[![GitHub star chart](https://img.shields.io/github/stars/langchain-ai/langchain?style=flat-square)](https://star-history.com/#langchain-ai/langchain)
-[![Dependency Status](https://img.shields.io/librariesio/github/langchain-ai/langchain?style=flat-square)](https://libraries.io/github/langchain-ai/langchain)
-[![Open Issues](https://img.shields.io/github/issues-raw/langchain-ai/langchain?style=flat-square)](https://github.com/langchain-ai/langchain/issues)
-[![Open in Dev Containers](https://img.shields.io/static/v1?label=Dev%20Containers&message=Open&color=blue&logo=visualstudiocode&style=flat-square)](https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/langchain-ai/langchain)
-[![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/langchain-ai/langchain)
+[![Downloads](https://static.pepy.tech/badge/langchain/month)](https://pepy.tech/project/langchain)
+[![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)
+[![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)
+[![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/langchain-ai/langchain)
+[![GitHub star chart](https://img.shields.io/github/stars/langchain-ai/langchain?style=social)](https://star-history.com/#langchain-ai/langchain)
+[![Dependency Status](https://img.shields.io/librariesio/github/langchain-ai/langchain)](https://libraries.io/github/langchain-ai/langchain)
+[![Open Issues](https://img.shields.io/github/issues-raw/langchain-ai/langchain)](https://github.com/langchain-ai/langchain/issues)
 
 Looking for the JS/TS library? Check out [LangChain.js](https://github.com/langchain-ai/langchainjs).
 
@@ -37,44 +38,43 @@ conda install langchain -c conda-forge
 
 For these applications, LangChain simplifies the entire application lifecycle:
 
-- **Open-source libraries**:  Build your applications using LangChain's open-source [building blocks](https://python.langchain.com/v0.2/docs/concepts#langchain-expression-language-lcel), [components](https://python.langchain.com/v0.2/docs/concepts), and [third-party integrations](https://python.langchain.com/v0.2/docs/integrations/platforms/).
-Use [LangGraph](/docs/concepts/#langgraph) to build stateful agents with first-class streaming and human-in-the-loop support.
-- **Productionization**: Inspect, monitor, and evaluate your apps with [LangSmith](https://docs.smith.langchain.com/) so that you can constantly optimize and deploy with confidence.
-- **Deployment**: Turn your LangGraph applications into production-ready APIs and Assistants with [LangGraph Cloud](https://langchain-ai.github.io/langgraph/cloud/).
+- **Open-source libraries**: Build your applications using LangChain's [modular building blocks](https://python.langchain.com/docs/expression_language/) and [components](https://python.langchain.com/docs/modules/). Integrate with hundreds of [third-party providers](https://python.langchain.com/docs/integrations/platforms/).
+- **Productionization**: Inspect, monitor, and evaluate your apps with [LangSmith](https://python.langchain.com/docs/langsmith/) so that you can constantly optimize and deploy with confidence.
+- **Deployment**: Turn any chain into a REST API with [LangServe](https://python.langchain.com/docs/langserve).
 
 ### Open-source libraries
 - **`langchain-core`**: Base abstractions and LangChain Expression Language.
 - **`langchain-community`**: Third party integrations.
   - Some integrations have been further split into **partner packages** that only rely on **`langchain-core`**. Examples include **`langchain_openai`** and **`langchain_anthropic`**.
 - **`langchain`**: Chains, agents, and retrieval strategies that make up an application's cognitive architecture.
-- **[`LangGraph`](https://langchain-ai.github.io/langgraph/)**: A library for building robust and stateful multi-actor applications with LLMs by modeling steps as edges and nodes in a graph. Integrates smoothly with LangChain, but can be used without it.
+- **[`LangGraph`](https://python.langchain.com/docs/langgraph)**: A library for building robust and stateful multi-actor applications with LLMs by modeling steps as edges and nodes in a graph.
 
 ### Productionization:
-- **[LangSmith](https://docs.smith.langchain.com/)**: A developer platform that lets you debug, test, evaluate, and monitor chains built on any LLM framework and seamlessly integrates with LangChain.
+- **[LangSmith](https://python.langchain.com/docs/langsmith)**: A developer platform that lets you debug, test, evaluate, and monitor chains built on any LLM framework and seamlessly integrates with LangChain.
 
 ### Deployment:
-- **[LangGraph Cloud](https://langchain-ai.github.io/langgraph/cloud/)**: Turn your LangGraph applications into production-ready APIs and Assistants.
+- **[LangServe](https://python.langchain.com/docs/langserve)**: A library for deploying LangChain chains as REST APIs.
 
-![Diagram outlining the hierarchical organization of the LangChain framework, displaying the interconnected parts across multiple layers.](docs/static/svg/langchain_stack_062024.svg "LangChain Architecture Overview")
+![Diagram outlining the hierarchical organization of the LangChain framework, displaying the interconnected parts across multiple layers.](docs/static/svg/langchain_stack.svg "LangChain Architecture Overview")
 
 ## 🧱 What can you build with LangChain?
 
 **❓ Question answering with RAG**
 
-- [Documentation](https://python.langchain.com/v0.2/docs/tutorials/rag/)
+- [Documentation](https://python.langchain.com/docs/use_cases/question_answering/)
 - End-to-end Example: [Chat LangChain](https://chat.langchain.com) and [repo](https://github.com/langchain-ai/chat-langchain)
 
 **🧱 Extracting structured output**
 
-- [Documentation](https://python.langchain.com/v0.2/docs/tutorials/extraction/)
+- [Documentation](https://python.langchain.com/docs/use_cases/extraction/)
 - End-to-end Example: [SQL Llama2 Template](https://github.com/langchain-ai/langchain-extract/)
 
 **🤖 Chatbots**
 
-- [Documentation](https://python.langchain.com/v0.2/docs/tutorials/chatbot/)
+- [Documentation](https://python.langchain.com/docs/use_cases/chatbots)
 - End-to-end Example: [Web LangChain (web researcher chatbot)](https://weblangchain.vercel.app) and [repo](https://github.com/langchain-ai/weblangchain)
 
-And much more! Head to the [Tutorials](https://python.langchain.com/v0.2/docs/tutorials/) section of the docs for more.
+And much more! Head to the [Use cases](https://python.langchain.com/docs/use_cases/) section of the docs for more.
 
 ## 🚀 How does LangChain help?
 The main value props of the LangChain libraries are:
@@ -87,49 +87,49 @@ Off-the-shelf chains make it easy to get started. Components make it easy to cus
 
 LCEL is the foundation of many of LangChain's components, and is a declarative way to compose chains. LCEL was designed from day 1 to support putting prototypes in production, with no code changes, from the simplest “prompt + LLM” chain to the most complex chains.
 
-- **[Overview](https://python.langchain.com/v0.2/docs/concepts/#langchain-expression-language-lcel)**: LCEL and its benefits
-- **[Interface](https://python.langchain.com/v0.2/docs/concepts/#runnable-interface)**: The standard Runnable interface for LCEL objects
-- **[Primitives](https://python.langchain.com/v0.2/docs/how_to/#langchain-expression-language-lcel)**: More on the primitives LCEL includes
-- **[Cheatsheet](https://python.langchain.com/v0.2/docs/how_to/lcel_cheatsheet/)**: Quick overview of the most common usage patterns
+- **[Overview](https://python.langchain.com/docs/expression_language/)**: LCEL and its benefits
+- **[Interface](https://python.langchain.com/docs/expression_language/interface)**: The standard interface for LCEL objects
+- **[Primitives](https://python.langchain.com/docs/expression_language/primitives)**: More on the primitives LCEL includes
 
 ## Components
 
 Components fall into the following **modules**:
 
-**📃 Model I/O**
+**📃 Model I/O:**
 
-This includes [prompt management](https://python.langchain.com/v0.2/docs/concepts/#prompt-templates), [prompt optimization](https://python.langchain.com/v0.2/docs/concepts/#example-selectors), a generic interface for [chat models](https://python.langchain.com/v0.2/docs/concepts/#chat-models) and [LLMs](https://python.langchain.com/v0.2/docs/concepts/#llms), and common utilities for working with [model outputs](https://python.langchain.com/v0.2/docs/concepts/#output-parsers).
+This includes [prompt management](https://python.langchain.com/docs/modules/model_io/prompts/), [prompt optimization](https://python.langchain.com/docs/modules/model_io/prompts/example_selectors/), a generic interface for [chat models](https://python.langchain.com/docs/modules/model_io/chat/) and [LLMs](https://python.langchain.com/docs/modules/model_io/llms/), and common utilities for working with [model outputs](https://python.langchain.com/docs/modules/model_io/output_parsers/).
 
-**📚 Retrieval**
+**📚 Retrieval:**
 
-Retrieval Augmented Generation involves [loading data](https://python.langchain.com/v0.2/docs/concepts/#document-loaders) from a variety of sources, [preparing it](https://python.langchain.com/v0.2/docs/concepts/#text-splitters), then [searching over (a.k.a. retrieving from)](https://python.langchain.com/v0.2/docs/concepts/#retrievers) it for use in the generation step.
+Retrieval Augmented Generation involves [loading data](https://python.langchain.com/docs/modules/data_connection/document_loaders/) from a variety of sources, [preparing it](https://python.langchain.com/docs/modules/data_connection/document_loaders/), [then retrieving it](https://python.langchain.com/docs/modules/data_connection/retrievers/) for use in the generation step.
 
-**🤖 Agents**
+**🤖 Agents:**
 
-Agents allow an LLM autonomy over how a task is accomplished. Agents make decisions about which Actions to take, then take that Action, observe the result, and repeat until the task is complete. LangChain provides a [standard interface for agents](https://python.langchain.com/v0.2/docs/concepts/#agents), along with [LangGraph](https://github.com/langchain-ai/langgraph) for building custom agents.
+Agents allow an LLM autonomy over how a task is accomplished. Agents make decisions about which Actions to take, then take that Action, observe the result, and repeat until the task is complete done. LangChain provides a [standard interface for agents](https://python.langchain.com/docs/modules/agents/), a [selection of agents](https://python.langchain.com/docs/modules/agents/agent_types/) to choose from, and examples of end-to-end agents.
 
 ## 📖 Documentation
 
 Please see [here](https://python.langchain.com) for full documentation, which includes:
 
-- [Introduction](https://python.langchain.com/v0.2/docs/introduction/): Overview of the framework and the structure of the docs.
-- [Tutorials](https://python.langchain.com/docs/use_cases/): If you're looking to build something specific or are more of a hands-on learner, check out our tutorials. This is the best place to get started.
-- [How-to guides](https://python.langchain.com/v0.2/docs/how_to/): Answers to “How do I….?” type questions. These guides are goal-oriented and concrete; they're meant to help you complete a specific task.
-- [Conceptual guide](https://python.langchain.com/v0.2/docs/concepts/): Conceptual explanations of the key parts of the framework.
-- [API Reference](https://api.python.langchain.com): Thorough documentation of every class and method.
+- [Getting started](https://python.langchain.com/docs/get_started/introduction): installation, setting up the environment, simple examples
+- [Use case](https://python.langchain.com/docs/use_cases/) walkthroughs and best practice [guides](https://python.langchain.com/docs/guides/)
+- Overviews of the [interfaces](https://python.langchain.com/docs/expression_language/), [components](https://python.langchain.com/docs/modules/), and [integrations](https://python.langchain.com/docs/integrations/providers)
+
+You can also check out the full [API Reference docs](https://api.python.langchain.com).
 
 ## 🌐 Ecosystem
 
-- [🦜🛠️ LangSmith](https://docs.smith.langchain.com/): Trace and evaluate your language model applications and intelligent agents to help you move from prototype to production.
-- [🦜🕸️ LangGraph](https://langchain-ai.github.io/langgraph/): Create stateful, multi-actor applications with LLMs. Integrates smoothly with LangChain, but can be used without it.
-- [🦜🏓 LangServe](https://python.langchain.com/docs/langserve): Deploy LangChain runnables and chains as REST APIs.
+- [🦜🛠️ LangSmith](https://python.langchain.com/docs/langsmith/): Tracing and evaluating your language model applications and intelligent agents to help you move from prototype to production.
+- [🦜🕸️ LangGraph](https://python.langchain.com/docs/langgraph): Creating stateful, multi-actor applications with LLMs, built on top of (and intended to be used with) LangChain primitives.
+- [🦜🏓 LangServe](https://python.langchain.com/docs/langserve): Deploying LangChain runnables and chains as REST APIs.
+  - [LangChain Templates](https://python.langchain.com/docs/templates/): Example applications hosted with LangServe.
 
 
 ## 💁 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 infrastructure, or better documentation.
 
-For detailed information on how to contribute, see [here](https://python.langchain.com/v0.2/docs/contributing/).
+For detailed information on how to contribute, see [here](https://python.langchain.com/docs/contributing/).
 
 ## 🌟 Contributors
 

cookbook/autogpt/marathon_times.ipynb

@@ -46,7 +46,7 @@
     "from langchain_experimental.autonomous_agents import AutoGPT\n",
     "from langchain_openai import ChatOpenAI\n",
     "\n",
-    "# Needed since jupyter runs an async eventloop\n",
+    "# Needed synce jupyter runs an async eventloop\n",
     "nest_asyncio.apply()"
    ]
   },

cookbook/nomic_multimodal_rag.ipynb

@@ -1,497 +0,0 @@
-{
- "cells": [
-  {
-   "attachments": {},
-   "cell_type": "markdown",
-   "id": "9fc3897d-176f-4729-8fd1-cfb4add53abd",
-   "metadata": {},
-   "source": [
-    "## Nomic multi-modal RAG\n",
-    "\n",
-    "Many documents contain a mixture of content types, including text and images. \n",
-    "\n",
-    "Yet, information captured in images is lost in most RAG applications.\n",
-    "\n",
-    "With the emergence of multimodal LLMs, like [GPT-4V](https://openai.com/research/gpt-4v-system-card), it is worth considering how to utilize images in RAG:\n",
-    "\n",
-    "In this demo we\n",
-    "\n",
-    "* Use multimodal embeddings from Nomic Embed [Vision](https://huggingface.co/nomic-ai/nomic-embed-vision-v1.5) and [Text](https://huggingface.co/nomic-ai/nomic-embed-text-v1.5) to embed images and text\n",
-    "* Retrieve both using similarity search\n",
-    "* Pass raw images and text chunks to a multimodal LLM for answer synthesis \n",
-    "\n",
-    "## Signup\n",
-    "\n",
-    "Get your API token, then run:\n",
-    "```\n",
-    "! nomic login\n",
-    "```\n",
-    "\n",
-    "Then run with your generated API token \n",
-    "```\n",
-    "! nomic login < token > \n",
-    "```\n",
-    "\n",
-    "## Packages\n",
-    "\n",
-    "For `unstructured`, you will also need `poppler` ([installation instructions](https://pdf2image.readthedocs.io/en/latest/installation.html)) and `tesseract` ([installation instructions](https://tesseract-ocr.github.io/tessdoc/Installation.html)) in your system."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "54926b9b-75c2-4cd4-8f14-b3882a0d370b",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "! nomic login token"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "febbc459-ebba-4c1a-a52b-fed7731593f8",
-   "metadata": {
-    "scrolled": true
-   },
-   "outputs": [],
-   "source": [
-    "! pip install -U langchain-nomic langchain_community tiktoken langchain-openai chromadb langchain # (newest versions required for multi-modal)"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "acbdc603-39e2-4a5f-836c-2bbaecd46b0b",
-   "metadata": {
-    "scrolled": true
-   },
-   "outputs": [],
-   "source": [
-    "# lock to 0.10.19 due to a persistent bug in more recent versions\n",
-    "! pip install \"unstructured[all-docs]==0.10.19\" pillow pydantic lxml pillow matplotlib tiktoken"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "1e94b3fb-8e3e-4736-be0a-ad881626c7bd",
-   "metadata": {},
-   "source": [
-    "## Data Loading\n",
-    "\n",
-    "### Partition PDF text and images\n",
-    "  \n",
-    "Let's look at an example pdfs containing interesting images.\n",
-    "\n",
-    "1/ Art from the J Paul Getty museum:\n",
-    "\n",
-    " * Here is a [zip file](https://drive.google.com/file/d/18kRKbq2dqAhhJ3DfZRnYcTBEUfYxe1YR/view?usp=sharing) with the PDF and the already extracted images. \n",
-    "* https://www.getty.edu/publications/resources/virtuallibrary/0892360224.pdf\n",
-    "\n",
-    "2/ Famous photographs from library of congress:\n",
-    "\n",
-    "* https://www.loc.gov/lcm/pdf/LCM_2020_1112.pdf\n",
-    "* We'll use this as an example below\n",
-    "\n",
-    "We can use `partition_pdf` below from [Unstructured](https://unstructured-io.github.io/unstructured/introduction.html#key-concepts) to extract text and images.\n",
-    "\n",
-    "To supply this to extract the images:\n",
-    "```\n",
-    "extract_images_in_pdf=True\n",
-    "```\n",
-    "\n",
-    "\n",
-    "\n",
-    "If using this zip file, then you can simply process the text only with:\n",
-    "```\n",
-    "extract_images_in_pdf=False\n",
-    "```"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "9646b524-71a7-4b2a-bdc8-0b81f77e968f",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "# Folder with pdf and extracted images\n",
-    "from pathlib import Path\n",
-    "\n",
-    "# replace with actual path to images\n",
-    "path = Path(\"../art\")"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "77f096ab-a933-41d0-8f4e-1efc83998fc3",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "path.resolve()"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "bc4839c0-8773-4a07-ba59-5364501269b2",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "# Extract images, tables, and chunk text\n",
-    "from unstructured.partition.pdf import partition_pdf\n",
-    "\n",
-    "raw_pdf_elements = partition_pdf(\n",
-    "    filename=str(path.resolve()) + \"/getty.pdf\",\n",
-    "    extract_images_in_pdf=False,\n",
-    "    infer_table_structure=True,\n",
-    "    chunking_strategy=\"by_title\",\n",
-    "    max_characters=4000,\n",
-    "    new_after_n_chars=3800,\n",
-    "    combine_text_under_n_chars=2000,\n",
-    "    image_output_dir_path=path,\n",
-    ")"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "969545ad",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "# Categorize text elements by type\n",
-    "tables = []\n",
-    "texts = []\n",
-    "for element in raw_pdf_elements:\n",
-    "    if \"unstructured.documents.elements.Table\" in str(type(element)):\n",
-    "        tables.append(str(element))\n",
-    "    elif \"unstructured.documents.elements.CompositeElement\" in str(type(element)):\n",
-    "        texts.append(str(element))"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "5d8e6349-1547-4cbf-9c6f-491d8610ec10",
-   "metadata": {},
-   "source": [
-    "## Multi-modal embeddings with our document\n",
-    "\n",
-    "We will use [nomic-embed-vision-v1.5](https://huggingface.co/nomic-ai/nomic-embed-vision-v1.5) embeddings. This model is aligned \n",
-    "to [nomic-embed-text-v1.5](https://huggingface.co/nomic-ai/nomic-embed-text-v1.5) allowing for multimodal semantic search and Multimodal RAG!"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "4bc15842-cb95-4f84-9eb5-656b0282a800",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "import os\n",
-    "import uuid\n",
-    "\n",
-    "import chromadb\n",
-    "import numpy as np\n",
-    "from langchain_community.vectorstores import Chroma\n",
-    "from langchain_nomic import NomicEmbeddings\n",
-    "from PIL import Image as _PILImage\n",
-    "\n",
-    "# Create chroma\n",
-    "text_vectorstore = Chroma(\n",
-    "    collection_name=\"mm_rag_clip_photos_text\",\n",
-    "    embedding_function=NomicEmbeddings(\n",
-    "        vision_model=\"nomic-embed-vision-v1.5\", model=\"nomic-embed-text-v1.5\"\n",
-    "    ),\n",
-    ")\n",
-    "image_vectorstore = Chroma(\n",
-    "    collection_name=\"mm_rag_clip_photos_image\",\n",
-    "    embedding_function=NomicEmbeddings(\n",
-    "        vision_model=\"nomic-embed-vision-v1.5\", model=\"nomic-embed-text-v1.5\"\n",
-    "    ),\n",
-    ")\n",
-    "\n",
-    "# Get image URIs with .jpg extension only\n",
-    "image_uris = sorted(\n",
-    "    [\n",
-    "        os.path.join(path, image_name)\n",
-    "        for image_name in os.listdir(path)\n",
-    "        if image_name.endswith(\".jpg\")\n",
-    "    ]\n",
-    ")\n",
-    "\n",
-    "# Add images\n",
-    "image_vectorstore.add_images(uris=image_uris)\n",
-    "\n",
-    "# Add documents\n",
-    "text_vectorstore.add_texts(texts=texts)\n",
-    "\n",
-    "# Make retriever\n",
-    "image_retriever = image_vectorstore.as_retriever()\n",
-    "text_retriever = text_vectorstore.as_retriever()"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "02a186d0-27e0-4820-8092-63b5349dd25d",
-   "metadata": {},
-   "source": [
-    "## RAG\n",
-    "\n",
-    "`vectorstore.add_images` will store / retrieve images as base64 encoded strings.\n",
-    "\n",
-    "These can be passed to [GPT-4V](https://platform.openai.com/docs/guides/vision)."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "344f56a8-0dc3-433e-851c-3f7600c7a72b",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "import base64\n",
-    "import io\n",
-    "from io import BytesIO\n",
-    "\n",
-    "import numpy as np\n",
-    "from PIL import Image\n",
-    "\n",
-    "\n",
-    "def resize_base64_image(base64_string, size=(128, 128)):\n",
-    "    \"\"\"\n",
-    "    Resize an image encoded as a Base64 string.\n",
-    "\n",
-    "    Args:\n",
-    "    base64_string (str): Base64 string of the original image.\n",
-    "    size (tuple): Desired size of the image as (width, height).\n",
-    "\n",
-    "    Returns:\n",
-    "    str: Base64 string of the resized image.\n",
-    "    \"\"\"\n",
-    "    # Decode the Base64 string\n",
-    "    img_data = base64.b64decode(base64_string)\n",
-    "    img = Image.open(io.BytesIO(img_data))\n",
-    "\n",
-    "    # Resize the image\n",
-    "    resized_img = img.resize(size, Image.LANCZOS)\n",
-    "\n",
-    "    # Save the resized image to a bytes buffer\n",
-    "    buffered = io.BytesIO()\n",
-    "    resized_img.save(buffered, format=img.format)\n",
-    "\n",
-    "    # Encode the resized image to Base64\n",
-    "    return base64.b64encode(buffered.getvalue()).decode(\"utf-8\")\n",
-    "\n",
-    "\n",
-    "def is_base64(s):\n",
-    "    \"\"\"Check if a string is Base64 encoded\"\"\"\n",
-    "    try:\n",
-    "        return base64.b64encode(base64.b64decode(s)) == s.encode()\n",
-    "    except Exception:\n",
-    "        return False\n",
-    "\n",
-    "\n",
-    "def split_image_text_types(docs):\n",
-    "    \"\"\"Split numpy array images and texts\"\"\"\n",
-    "    images = []\n",
-    "    text = []\n",
-    "    for doc in docs:\n",
-    "        doc = doc.page_content  # Extract Document contents\n",
-    "        if is_base64(doc):\n",
-    "            # Resize image to avoid OAI server error\n",
-    "            images.append(\n",
-    "                resize_base64_image(doc, size=(250, 250))\n",
-    "            )  # base64 encoded str\n",
-    "        else:\n",
-    "            text.append(doc)\n",
-    "    return {\"images\": images, \"texts\": text}"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "23a2c1d8-fea6-4152-b184-3172dd46c735",
-   "metadata": {},
-   "source": [
-    "Currently, we format the inputs using a `RunnableLambda` while we add image support to `ChatPromptTemplates`.\n",
-    "\n",
-    "Our runnable follows the classic RAG flow - \n",
-    "\n",
-    "* We first compute the context (both \"texts\" and \"images\" in this case) and the question (just a RunnablePassthrough here) \n",
-    "* Then we pass this into our prompt template, which is a custom function that formats the message for the gpt-4-vision-preview model. \n",
-    "* And finally we parse the output as a string."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "5d8919dc-c238-4746-86ba-45d940a7d260",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "import os\n",
-    "\n",
-    "os.environ[\"OPENAI_API_KEY\"] = \"\""
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "4c93fab3-74c4-4f1d-958a-0bc4cdd0797e",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "from operator import itemgetter\n",
-    "\n",
-    "from langchain_core.messages import HumanMessage, SystemMessage\n",
-    "from langchain_core.output_parsers import StrOutputParser\n",
-    "from langchain_core.runnables import RunnableLambda, RunnablePassthrough\n",
-    "from langchain_openai import ChatOpenAI\n",
-    "\n",
-    "\n",
-    "def prompt_func(data_dict):\n",
-    "    # Joining the context texts into a single string\n",
-    "    formatted_texts = \"\\n\".join(data_dict[\"text_context\"][\"texts\"])\n",
-    "    messages = []\n",
-    "\n",
-    "    # Adding image(s) to the messages if present\n",
-    "    if data_dict[\"image_context\"][\"images\"]:\n",
-    "        image_message = {\n",
-    "            \"type\": \"image_url\",\n",
-    "            \"image_url\": {\n",
-    "                \"url\": f\"data:image/jpeg;base64,{data_dict['image_context']['images'][0]}\"\n",
-    "            },\n",
-    "        }\n",
-    "        messages.append(image_message)\n",
-    "\n",
-    "    # Adding the text message for analysis\n",
-    "    text_message = {\n",
-    "        \"type\": \"text\",\n",
-    "        \"text\": (\n",
-    "            \"As an expert art critic and historian, your task is to analyze and interpret images, \"\n",
-    "            \"considering their historical and cultural significance. Alongside the images, you will be \"\n",
-    "            \"provided with related text to offer context. Both will be retrieved from a vectorstore based \"\n",
-    "            \"on user-input keywords. Please use your extensive knowledge and analytical skills to provide a \"\n",
-    "            \"comprehensive summary that includes:\\n\"\n",
-    "            \"- A detailed description of the visual elements in the image.\\n\"\n",
-    "            \"- The historical and cultural context of the image.\\n\"\n",
-    "            \"- An interpretation of the image's symbolism and meaning.\\n\"\n",
-    "            \"- Connections between the image and the related text.\\n\\n\"\n",
-    "            f\"User-provided keywords: {data_dict['question']}\\n\\n\"\n",
-    "            \"Text and / or tables:\\n\"\n",
-    "            f\"{formatted_texts}\"\n",
-    "        ),\n",
-    "    }\n",
-    "    messages.append(text_message)\n",
-    "\n",
-    "    return [HumanMessage(content=messages)]\n",
-    "\n",
-    "\n",
-    "model = ChatOpenAI(temperature=0, model=\"gpt-4-vision-preview\", max_tokens=1024)\n",
-    "\n",
-    "# RAG pipeline\n",
-    "chain = (\n",
-    "    {\n",
-    "        \"text_context\": text_retriever | RunnableLambda(split_image_text_types),\n",
-    "        \"image_context\": image_retriever | RunnableLambda(split_image_text_types),\n",
-    "        \"question\": RunnablePassthrough(),\n",
-    "    }\n",
-    "    | RunnableLambda(prompt_func)\n",
-    "    | model\n",
-    "    | StrOutputParser()\n",
-    ")"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "1566096d-97c2-4ddc-ba4a-6ef88c525e4e",
-   "metadata": {},
-   "source": [
-    "## Test retrieval and run RAG"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "90121e56-674b-473b-871d-6e4753fd0c45",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "from IPython.display import HTML, display\n",
-    "\n",
-    "\n",
-    "def plt_img_base64(img_base64):\n",
-    "    # Create an HTML img tag with the base64 string as the source\n",
-    "    image_html = f'<img src=\"data:image/jpeg;base64,{img_base64}\" />'\n",
-    "\n",
-    "    # Display the image by rendering the HTML\n",
-    "    display(HTML(image_html))\n",
-    "\n",
-    "\n",
-    "docs = text_retriever.invoke(\"Women with children\", k=5)\n",
-    "for doc in docs:\n",
-    "    if is_base64(doc.page_content):\n",
-    "        plt_img_base64(doc.page_content)\n",
-    "    else:\n",
-    "        print(doc.page_content)"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "44eaa532-f035-4c04-b578-02339d42554c",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "docs = image_retriever.invoke(\"Women with children\", k=5)\n",
-    "for doc in docs:\n",
-    "    if is_base64(doc.page_content):\n",
-    "        plt_img_base64(doc.page_content)\n",
-    "    else:\n",
-    "        print(doc.page_content)"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "69fb15fd-76fc-49b4-806d-c4db2990027d",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "chain.invoke(\"Women with children\")"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "227f08b8-e732-4089-b65c-6eb6f9e48f15",
-   "metadata": {},
-   "source": [
-    "We can see the images retrieved in the LangSmith trace:\n",
-    "\n",
-    "LangSmith [trace](https://smith.langchain.com/public/69c558a5-49dc-4c60-a49b-3adbb70f74c5/r/e872c2c8-528c-468f-aefd-8b5cd730a673)."
-   ]
-  }
- ],
- "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.11.9"
-  }
- },
- "nbformat": 4,
- "nbformat_minor": 5
-}

cookbook/oracleai_demo.ipynb

@@ -6,24 +6,23 @@
    "source": [
     "# Oracle AI Vector Search with Document Processing\n",
     "Oracle AI Vector Search is designed for Artificial Intelligence (AI) workloads that allows you to query data based on semantics, rather than keywords.\n",
-    "One of the biggest benefits of Oracle AI Vector Search is that semantic search on unstructured data can be combined with relational search on business data in one single system.\n",
-    "This is not only powerful but also significantly more effective because you don't need to add a specialized vector database, eliminating the pain of data fragmentation between multiple systems.\n",
+    "One of the biggest benefit of Oracle AI Vector Search is that semantic search on unstructured data can be combined with relational search on business data in one single system. This is not only powerful but also significantly more effective because you don't need to add a specialized vector database, eliminating the pain of data fragmentation between multiple systems.\n",
     "\n",
-    "In addition, your vectors can benefit from all of Oracle Database’s most powerful features, like the following:\n",
+    "In addition, because Oracle has been building database technologies for so long, your vectors can benefit from all of Oracle Database's most powerful features, like the following:\n",
     "\n",
-    " * [Partitioning Support](https://www.oracle.com/database/technologies/partitioning.html)\n",
-    " * [Real Application Clusters scalability](https://www.oracle.com/database/real-application-clusters/)\n",
-    " * [Exadata smart scans](https://www.oracle.com/database/technologies/exadata/software/smartscan/)\n",
-    " * [Shard processing across geographically distributed databases](https://www.oracle.com/database/distributed-database/)\n",
-    " * [Transactions](https://docs.oracle.com/en/database/oracle/oracle-database/23/cncpt/transactions.html)\n",
-    " * [Parallel SQL](https://docs.oracle.com/en/database/oracle/oracle-database/21/vldbg/parallel-exec-intro.html#GUID-D28717E4-0F77-44F5-BB4E-234C31D4E4BA)\n",
-    " * [Disaster recovery](https://www.oracle.com/database/data-guard/)\n",
-    " * [Security](https://www.oracle.com/security/database-security/)\n",
-    " * [Oracle Machine Learning](https://www.oracle.com/artificial-intelligence/database-machine-learning/)\n",
-    " * [Oracle Graph Database](https://www.oracle.com/database/integrated-graph-database/)\n",
-    " * [Oracle Spatial and Graph](https://www.oracle.com/database/spatial/)\n",
-    " * [Oracle Blockchain](https://docs.oracle.com/en/database/oracle/oracle-database/23/arpls/dbms_blockchain_table.html#GUID-B469E277-978E-4378-A8C1-26D3FF96C9A6)\n",
-    " * [JSON](https://docs.oracle.com/en/database/oracle/oracle-database/23/adjsn/json-in-oracle-database.html)\n",
+    " * Partitioning Support\n",
+    " * Real Application Clusters scalability\n",
+    " * Exadata smart scans\n",
+    " * Shard processing across geographically distributed databases\n",
+    " * Transactions\n",
+    " * Parallel SQL\n",
+    " * Disaster recovery\n",
+    " * Security\n",
+    " * Oracle Machine Learning\n",
+    " * Oracle Graph Database\n",
+    " * Oracle Spatial and Graph\n",
+    " * Oracle Blockchain\n",
+    " * JSON\n",
     "\n",
     "This guide demonstrates how Oracle AI Vector Search can be used with Langchain to serve an end-to-end RAG pipeline. This guide goes through examples of:\n",
     "\n",
@@ -34,13 +33,6 @@
     " * Storing and Indexing them in a Vector Store and querying them for queries in OracleVS"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "metadata": {},
-   "source": [
-    "If you are just starting with Oracle Database, consider exploring the [free Oracle 23 AI](https://www.oracle.com/database/free/#resources) which provides a great introduction to setting up your database environment. While working with the database, it is often advisable to avoid using the system user by default; instead, you can create your own user for enhanced security and customization. For detailed steps on user creation, refer to our [end-to-end guide](https://github.com/langchain-ai/langchain/blob/master/cookbook/oracleai_demo.ipynb) which also shows how to set up a user in Oracle. Additionally, understanding user privileges is crucial for managing database security effectively. You can learn more about this topic in the official [Oracle guide](https://docs.oracle.com/en/database/oracle/oracle-database/19/admqs/administering-user-accounts-and-security.html#GUID-36B21D72-1BBB-46C9-A0C9-F0D2A8591B8D) on administering user accounts and security."
-   ]
-  },
   {
    "cell_type": "markdown",
    "metadata": {},
@@ -86,7 +78,8 @@
     "\n",
     "import oracledb\n",
     "\n",
-    "# Update with your username, password, hostname, and service_name\n",
+    "# please update with your username, password, hostname and service_name\n",
+    "# please make sure this user has sufficient privileges to perform all below\n",
     "username = \"\"\n",
     "password = \"\"\n",
     "dsn = \"\"\n",
@@ -96,45 +89,40 @@
     "    print(\"Connection successful!\")\n",
     "\n",
     "    cursor = conn.cursor()\n",
-    "    try:\n",
-    "        cursor.execute(\n",
-    "            \"\"\"\n",
-    "            begin\n",
-    "                -- Drop user\n",
-    "                begin\n",
-    "                    execute immediate 'drop user testuser cascade';\n",
-    "                exception\n",
-    "                    when others then\n",
-    "                        dbms_output.put_line('Error dropping user: ' || SQLERRM);\n",
-    "                end;\n",
-    "                \n",
-    "                -- Create user and grant privileges\n",
-    "                execute immediate 'create user testuser identified by testuser';\n",
-    "                execute immediate 'grant connect, unlimited tablespace, create credential, create procedure, create any index to testuser';\n",
-    "                execute immediate 'create or replace directory DEMO_PY_DIR as ''/scratch/hroy/view_storage/hroy_devstorage/demo/orachain''';\n",
-    "                execute immediate 'grant read, write on directory DEMO_PY_DIR to public';\n",
-    "                execute immediate 'grant create mining model to testuser';\n",
-    "                \n",
-    "                -- Network access\n",
-    "                begin\n",
-    "                    DBMS_NETWORK_ACL_ADMIN.APPEND_HOST_ACE(\n",
-    "                        host => '*',\n",
-    "                        ace => xs$ace_type(privilege_list => xs$name_list('connect'),\n",
-    "                                           principal_name => 'testuser',\n",
-    "                                           principal_type => xs_acl.ptype_db)\n",
-    "                    );\n",
-    "                end;\n",
-    "            end;\n",
-    "            \"\"\"\n",
-    "        )\n",
-    "        print(\"User setup done!\")\n",
-    "    except Exception as e:\n",
-    "        print(f\"User setup failed with error: {e}\")\n",
-    "    finally:\n",
-    "        cursor.close()\n",
+    "    cursor.execute(\n",
+    "        \"\"\"\n",
+    "    begin\n",
+    "        -- drop user\n",
+    "        begin\n",
+    "            execute immediate 'drop user testuser cascade';\n",
+    "        exception\n",
+    "            when others then\n",
+    "                dbms_output.put_line('Error setting up user.');\n",
+    "        end;\n",
+    "        execute immediate 'create user testuser identified by testuser';\n",
+    "        execute immediate 'grant connect, unlimited tablespace, create credential, create procedure, create any index to testuser';\n",
+    "        execute immediate 'create or replace directory DEMO_PY_DIR as ''/scratch/hroy/view_storage/hroy_devstorage/demo/orachain''';\n",
+    "        execute immediate 'grant read, write on directory DEMO_PY_DIR to public';\n",
+    "        execute immediate 'grant create mining model to testuser';\n",
+    "\n",
+    "        -- network access\n",
+    "        begin\n",
+    "            DBMS_NETWORK_ACL_ADMIN.APPEND_HOST_ACE(\n",
+    "                host => '*',\n",
+    "                ace => xs$ace_type(privilege_list => xs$name_list('connect'),\n",
+    "                                principal_name => 'testuser',\n",
+    "                                principal_type => xs_acl.ptype_db));\n",
+    "        end;\n",
+    "    end;\n",
+    "    \"\"\"\n",
+    "    )\n",
+    "    print(\"User setup done!\")\n",
+    "    cursor.close()\n",
     "    conn.close()\n",
     "except Exception as e:\n",
-    "    print(f\"Connection failed with error: {e}\")\n",
+    "    print(\"User setup failed!\")\n",
+    "    cursor.close()\n",
+    "    conn.close()\n",
     "    sys.exit(1)"
    ]
   },
@@ -143,13 +131,13 @@
    "metadata": {},
    "source": [
     "## Process Documents using Oracle AI\n",
-    "Consider the following scenario: users possess documents stored either in an Oracle Database or a file system and intend to utilize this data with Oracle AI Vector Search powered by Langchain.\n",
+    "Let's think about a scenario that the users have some documents in Oracle Database or in a file system. They want to use the data for Oracle AI Vector Search using Langchain.\n",
     "\n",
-    "To prepare the documents for analysis, a comprehensive preprocessing workflow is necessary. Initially, the documents must be retrieved, summarized (if required), and chunked as needed. Subsequent steps involve generating embeddings for these chunks and integrating them into the Oracle AI Vector Store. Users can then conduct semantic searches on this data.\n",
+    "For that, the users need to do some document preprocessing. The first step would be to read the documents, generate their summary(if needed) and then chunk/split them if needed. After that, they need to generate the embeddings for those chunks and store into Oracle AI Vector Store. Finally, the users will perform some semantic queries on those data. \n",
     "\n",
-    "The Oracle AI Vector Search Langchain library encompasses a suite of document processing tools that facilitate document loading, chunking, summary generation, and embedding creation.\n",
+    "Oracle AI Vector Search Langchain library provides a range of document processing functionalities including document loading, splitting, generating summary and embeddings.\n",
     "\n",
-    "In the sections that follow, we will detail the utilization of Oracle AI Langchain APIs to effectively implement each of these processes."
+    "In the following sections, we will go through how to use Oracle AI Langchain APIs to achieve each of these functionalities individually. "
    ]
   },
   {
@@ -157,7 +145,7 @@
    "metadata": {},
    "source": [
     "### Connect to Demo User\n",
-    "The following sample code will show how to connect to Oracle Database. By default, python-oracledb runs in a ‘Thin’ mode which connects directly to Oracle Database. This mode does not need Oracle Client libraries. However, some additional functionality is available when python-oracledb uses them. Python-oracledb is said to be in ‘Thick’ mode when Oracle Client libraries are used. Both modes have comprehensive functionality supporting the Python Database API v2.0 Specification. See the following [guide](https://python-oracledb.readthedocs.io/en/latest/user_guide/appendix_a.html#featuresummary) that talks about features supported in each mode. You might want to switch to thick-mode if you are unable to use thin-mode."
+    "The following sample code will show how to connect to Oracle Database. "
    ]
   },
   {
@@ -254,7 +242,9 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "With the inclusion of a demo user and a populated sample table, the remaining configuration involves setting up embedding and summary functionalities. Users are presented with multiple provider options, including local database solutions and third-party services such as Ocigenai, Hugging Face, and OpenAI. Should users opt for a third-party provider, they are required to establish credentials containing the necessary authentication details. Conversely, if selecting a database as the provider for embeddings, it is necessary to upload an ONNX model to the Oracle Database. No additional setup is required for summary functionalities when using the database option."
+    "\n",
+    "\n",
+    "Now that we have a demo user and a demo table with some data, we just need to do one more setup. For embedding and summary, we have a few provider options that the users can choose from such as database, 3rd party providers like ocigenai, huggingface, openai, etc. If the users choose to use 3rd party provider, they need to create a credential with corresponding authentication information. On the other hand, if the users choose to use 'database' as provider, they need to load an onnx model to Oracle Database for embeddings; however, for summary, they don't need to do anything."
    ]
   },
   {
@@ -263,13 +253,13 @@
    "source": [
     "### Load ONNX Model\n",
     "\n",
-    "Oracle accommodates a variety of embedding providers, enabling users to choose between proprietary database solutions and third-party services such as OCIGENAI and HuggingFace. This selection dictates the methodology for generating and managing embeddings.\n",
+    "To generate embeddings, Oracle provides a few provider options for users to choose from. The users can choose 'database' provider or some 3rd party providers like OCIGENAI, HuggingFace, etc.\n",
     "\n",
-    "***Important*** : Should users opt for the database option, they must upload an ONNX model into the Oracle Database. Conversely, if a third-party provider is selected for embedding generation, uploading an ONNX model to Oracle Database is not required.\n",
+    "***Note*** If the users choose database option, they need to load an ONNX model to Oracle Database. The users do not need to load an ONNX model to Oracle Database if they choose to use 3rd party provider to generate embeddings.\n",
     "\n",
-    "A significant advantage of utilizing an ONNX model directly within Oracle is the enhanced security and performance it offers by eliminating the need to transmit data to external parties. Additionally, this method avoids the latency typically associated with network or REST API calls.\n",
+    "One of the core benefits of using an ONNX model is that the users do not need to transfer their data to 3rd party to generate embeddings. And also, since it does not involve any network or REST API calls, it may provide better performance.\n",
     "\n",
-    "Below is the example code to upload an ONNX model into Oracle Database:"
+    "Here is the sample code to load an ONNX model to Oracle Database:"
    ]
   },
   {
@@ -308,11 +298,11 @@
    "source": [
     "### Create Credential\n",
     "\n",
-    "When selecting third-party providers for generating embeddings, users are required to establish credentials to securely access the provider's endpoints.\n",
+    "On the other hand, if the users choose to use 3rd party provider to generate embeddings and summary, they need to create credential to access 3rd party provider's end points.\n",
     "\n",
-    "***Important:*** No credentials are necessary when opting for the 'database' provider to generate embeddings. However, should users decide to utilize a third-party provider, they must create credentials specific to the chosen provider.\n",
+    "***Note:*** The users do not need to create any credential if they choose to use 'database' provider to generate embeddings and summary. Should the users choose to 3rd party provider, they need to create credential for the 3rd party provider they want to use. \n",
     "\n",
-    "Below is an illustrative example:"
+    "Here is a sample example:"
    ]
   },
   {
@@ -362,11 +352,11 @@
    "metadata": {},
    "source": [
     "### Load Documents\n",
-    "Users have the flexibility to load documents from either the Oracle Database, a file system, or both, by appropriately configuring the loader parameters. For comprehensive details on these parameters, please consult the [Oracle AI Vector Search Guide](https://docs.oracle.com/en/database/oracle/oracle-database/23/arpls/dbms_vector_chain1.html#GUID-73397E89-92FB-48ED-94BB-1AD960C4EA1F).\n",
+    "The users can load the documents from Oracle Database or a file system or both. They just need to set the loader parameters accordingly. Please refer to the Oracle AI Vector Search Guide book for complete information about these parameters.\n",
     "\n",
-    "A significant advantage of utilizing OracleDocLoader is its capability to process over 150 distinct file formats, eliminating the need for multiple loaders for different document types. For a complete list of the supported formats, please refer to the [Oracle Text Supported Document Formats](https://docs.oracle.com/en/database/oracle/oracle-database/23/ccref/oracle-text-supported-document-formats.html).\n",
+    "The main benefit of using OracleDocLoader is that it can handle 150+ different file formats. You don't need to use different types of loader for different file formats. Here is the list formats that we support: [Oracle Text Supported Document Formats](https://docs.oracle.com/en/database/oracle/oracle-database/23/ccref/oracle-text-supported-document-formats.html)\n",
     "\n",
-    "Below is a sample code snippet that demonstrates how to use OracleDocLoader"
+    "The following sample code will show how to do that:"
    ]
   },
   {
@@ -409,7 +399,7 @@
    "metadata": {},
    "source": [
     "### Generate Summary\n",
-    "Now that the user loaded the documents, they may want to generate a summary for each document. The Oracle AI Vector Search Langchain library offers a suite of APIs designed for document summarization. It supports multiple summarization providers such as Database, OCIGENAI, HuggingFace, among others, allowing users to select the provider that best meets their needs. To utilize these capabilities, users must configure the summary parameters as specified. For detailed information on these parameters, please consult the [Oracle AI Vector Search Guide book](https://docs.oracle.com/en/database/oracle/oracle-database/23/arpls/dbms_vector_chain1.html#GUID-EC9DDB58-6A15-4B36-BA66-ECBA20D2CE57)."
+    "Now that the user loaded the documents, they may want to generate a summary for each document. The Oracle AI Vector Search Langchain library provides an API to do that. There are a few summary generation provider options including Database, OCIGENAI, HuggingFace and so on. The users can choose their preferred provider to generate a summary. Like before, they just need to set the summary parameters accordingly. Please refer to the Oracle AI Vector Search Guide book for complete information about these parameters."
    ]
   },
   {
@@ -480,9 +470,9 @@
    "metadata": {},
    "source": [
     "### Split Documents\n",
-    "The documents may vary in size, ranging from small to very large. Users often prefer to chunk their documents into smaller sections to facilitate the generation of embeddings. A wide array of customization options is available for this splitting process. For comprehensive details regarding these parameters, please consult the [Oracle AI Vector Search Guide](https://docs.oracle.com/en/database/oracle/oracle-database/23/arpls/dbms_vector_chain1.html#GUID-4E145629-7098-4C7C-804F-FC85D1F24240).\n",
+    "The documents can be in different sizes: small, medium, large, or very large. The users like to split/chunk their documents into smaller pieces to generate embeddings. There are lots of different splitting customizations the users can do. Please refer to the Oracle AI Vector Search Guide book for complete information about these parameters.\n",
     "\n",
-    "Below is a sample code illustrating how to implement this:"
+    "The following sample code will show how to do that:"
    ]
   },
   {
@@ -523,14 +513,14 @@
    "metadata": {},
    "source": [
     "### Generate Embeddings\n",
-    "Now that the documents are chunked as per requirements, the users may want to generate embeddings for these chunks. Oracle AI Vector Search provides multiple methods for generating embeddings, utilizing either locally hosted ONNX models or third-party APIs. For comprehensive instructions on configuring these alternatives, please refer to the [Oracle AI Vector Search Guide](https://docs.oracle.com/en/database/oracle/oracle-database/23/arpls/dbms_vector_chain1.html#GUID-C6439E94-4E86-4ECD-954E-4B73D53579DE)."
+    "Now that the documents are chunked as per requirements, the users may want to generate embeddings for these chunks. Oracle AI Vector Search provides a number of ways to generate embeddings. The users can load an ONNX embedding model to Oracle Database and use it to generate embeddings or use some 3rd party API's end points to generate embeddings. Please refer to the Oracle AI Vector Search Guide book for complete information about these parameters."
    ]
   },
   {
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "***Note:*** Users may need to configure a proxy to utilize third-party embedding generation providers, excluding the 'database' provider that utilizes an ONNX model."
+    "***Note:*** The users may need to set proxy if they want to use some 3rd party embedding generation providers other than 'database' provider (aka using ONNX model)."
    ]
   },
   {
@@ -762,18 +752,20 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "The example provided illustrates the creation of a vector store using the DOT_PRODUCT distance strategy. Users have the flexibility to employ various distance strategies with the Oracle AI Vector Store, as detailed in our [comprehensive guide](https://python.langchain.com/v0.1/docs/integrations/vectorstores/oracle/)."
+    "The above example creates a vector store with DOT_PRODUCT distance strategy. \n",
+    "\n",
+    "However, the users can create Oracle AI Vector Store provides different distance strategies. Please see the [comprehensive guide](/docs/integrations/vectorstores/oracle) for more information."
    ]
   },
   {
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "With embeddings now stored in vector stores, it is advisable to establish an index to enhance semantic search performance during query execution.\n",
+    "Now that we have embeddings stored in vector stores, let's create an index on them to get better semantic search performance during query time.\n",
     "\n",
-    "***Note*** Should you encounter an \"insufficient memory\" error, it is recommended to increase the  ***vector_memory_size*** in your database configuration\n",
+    "***Note*** If you are getting some insufficient memory error, please increase ***vector_memory_size*** in your database.\n",
     "\n",
-    "Below is a sample code snippet for creating an index:"
+    "Here is the sample code to create an index:"
    ]
   },
   {
@@ -793,9 +785,9 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "This example demonstrates the creation of a default HNSW index on embeddings within the 'oravs' table. Users may adjust various parameters according to their specific needs. For detailed information on these parameters, please consult the [Oracle AI Vector Search Guide book](https://docs.oracle.com/en/database/oracle/oracle-database/23/vecse/manage-different-categories-vector-indexes.html).\n",
+    "The above example creates a default HNSW index on the embeddings stored in 'oravs' table. The users can set different parameters as per their requirements. Please refer to the Oracle AI Vector Search Guide book for complete information about these parameters.\n",
     "\n",
-    "Additionally, various types of vector indices can be created to meet diverse requirements. More details can be found in our [comprehensive guide](https://python.langchain.com/v0.1/docs/integrations/vectorstores/oracle/).\n"
+    "Also, there are different types of vector indices that the users can create. Please see the [comprehensive guide](/docs/integrations/vectorstores/oracle) for more information.\n"
    ]
   },
   {
@@ -805,9 +797,9 @@
     "## Perform Semantic Search\n",
     "All set!\n",
     "\n",
-    "We have successfully processed the documents and stored them in the vector store, followed by the creation of an index to enhance query performance. We are now prepared to proceed with semantic searches.\n",
+    "We have processed the documents, stored them to vector store, and then created index to get better query performance. Now let's do some semantic searches.\n",
     "\n",
-    "Below is the sample code for this process:"
+    "Here is the sample code for this:"
    ]
   },
   {

cookbook/rag_upstage_layout_analysis_groundedness_check.ipynb

@@ -36,9 +36,7 @@
     "\n",
     "docs = loader.load()\n",
     "\n",
-    "vectorstore = DocArrayInMemorySearch.from_documents(\n",
-    "    docs, embedding=UpstageEmbeddings(model=\"solar-embedding-1-large\")\n",
-    ")\n",
+    "vectorstore = DocArrayInMemorySearch.from_documents(docs, embedding=UpstageEmbeddings())\n",
     "retriever = vectorstore.as_retriever()\n",
     "\n",
     "template = \"\"\"Answer the question based only on the following context:\n",

cookbook/rag_with_quantized_embeddings.ipynb

@@ -39,10 +39,12 @@
     "from langchain_community.document_loaders.recursive_url_loader import (\n",
     "    RecursiveUrlLoader,\n",
     ")\n",
+    "\n",
+    "# noqa\n",
     "from langchain_community.vectorstores import Chroma\n",
     "\n",
     "# For our example, we'll load docs from the web\n",
-    "from langchain_text_splitters import RecursiveCharacterTextSplitter\n",
+    "from langchain_text_splitters import RecursiveCharacterTextSplitter  # noqa\n",
     "\n",
     "DOCSTORE_DIR = \".\"\n",
     "DOCSTORE_ID_KEY = \"doc_id\""

cookbook/sql_db_qa.mdx

@@ -647,7 +647,7 @@ Sometimes you may not have the luxury of using OpenAI or other service-hosted la
 import logging
 import torch
 from transformers import AutoTokenizer, GPT2TokenizerFast, pipeline, AutoModelForSeq2SeqLM, AutoModelForCausalLM
-from langchain_huggingface import HuggingFacePipeline
+from langchain_community.llms import HuggingFacePipeline
 
 # Note: This model requires a large GPU, e.g. an 80GB A100. See documentation for other ways to run private non-OpenAI models.
 model_id = "google/flan-ul2"
@@ -992,7 +992,7 @@ Now that you have some examples (with manually corrected output SQL), you can do
 ```python
 from langchain.prompts import FewShotPromptTemplate, PromptTemplate
 from langchain.chains.sql_database.prompt import _sqlite_prompt, PROMPT_SUFFIX
-from langchain_huggingface import HuggingFaceEmbeddings
+from langchain_community.embeddings.huggingface import HuggingFaceEmbeddings
 from langchain.prompts.example_selector.semantic_similarity import SemanticSimilarityExampleSelector
 from langchain_community.vectorstores import Chroma
 

docs/Makefile

@@ -13,7 +13,7 @@ OUTPUT_NEW_DOCS_DIR = $(OUTPUT_NEW_DIR)/docs
 
 PYTHON = .venv/bin/python
 
-PARTNER_DEPS_LIST := $(shell find ../libs/partners -mindepth 1 -maxdepth 1 -type d -exec test -e "{}/pyproject.toml" \; -print | grep -vE "airbyte|ibm" | tr '\n' ' ')
+PARTNER_DEPS_LIST := $(shell ls -1 ../libs/partners | grep -vE "airbyte|ibm" | xargs -I {} echo "../libs/partners/{}" | tr '\n' ' ')
 
 PORT ?= 3001
 
@@ -35,16 +35,21 @@ generate-files:
 	mkdir -p $(INTERMEDIATE_DIR)
 	cp -r $(SOURCE_DIR)/* $(INTERMEDIATE_DIR)
 	mkdir -p $(INTERMEDIATE_DIR)/templates
+	cp ../templates/docs/INDEX.md $(INTERMEDIATE_DIR)/templates/index.md
+	cp ../cookbook/README.md $(INTERMEDIATE_DIR)/cookbook.mdx
 
 	$(PYTHON) scripts/model_feat_table.py $(INTERMEDIATE_DIR)
 
-	$(PYTHON) scripts/document_loader_feat_table.py $(INTERMEDIATE_DIR)
-
 	$(PYTHON) scripts/copy_templates.py $(INTERMEDIATE_DIR)
 
 	wget -q https://raw.githubusercontent.com/langchain-ai/langserve/main/README.md -O $(INTERMEDIATE_DIR)/langserve.md
 	$(PYTHON) scripts/resolve_local_links.py $(INTERMEDIATE_DIR)/langserve.md https://github.com/langchain-ai/langserve/tree/main/
 
+	wget -q https://raw.githubusercontent.com/langchain-ai/langgraph/main/README.md -O $(INTERMEDIATE_DIR)/langgraph.md
+	$(PYTHON) scripts/resolve_local_links.py $(INTERMEDIATE_DIR)/langgraph.md https://github.com/langchain-ai/langgraph/tree/main/
+
+	$(PYTHON) scripts/generate_api_reference_links.py --docs_dir $(INTERMEDIATE_DIR)
+
 copy-infra:
 	mkdir -p $(OUTPUT_NEW_DIR)
 	cp -r src $(OUTPUT_NEW_DIR)
@@ -61,22 +66,19 @@ render:
 	$(PYTHON) scripts/notebook_convert.py $(INTERMEDIATE_DIR) $(OUTPUT_NEW_DOCS_DIR)
 
 md-sync:
-	rsync -avm --include="*/" --include="*.mdx" --include="*.md" --include="*.png" --include="*/_category_.yml" --exclude="*" $(INTERMEDIATE_DIR)/ $(OUTPUT_NEW_DOCS_DIR)
-
-generate-references:
-	$(PYTHON) scripts/generate_api_reference_links.py --docs_dir $(OUTPUT_NEW_DOCS_DIR)
+	rsync -avm --include="*/" --include="*.mdx" --include="*.md" --include="*.png" --exclude="*" $(INTERMEDIATE_DIR)/ $(OUTPUT_NEW_DOCS_DIR)
 
 build: install-py-deps generate-files copy-infra render md-sync
 
-vercel-build: install-vercel-deps build generate-references
+vercel-build: install-vercel-deps build
 	rm -rf docs
 	mv $(OUTPUT_NEW_DOCS_DIR) docs
 	rm -rf build
 	yarn run docusaurus build
-	mv build v0.2
+	mv build v0.1
 	mkdir build
-	mv v0.2 build
-	mv build/v0.2/404.html build
+	mv v0.1 build
+	mv build/v0.1/404.html build
 
 start:
 	cd $(OUTPUT_NEW_DIR) && yarn && yarn start --port=$(PORT)

docs/api_reference/_static/css/custom.css

@@ -12,8 +12,7 @@ pre {
   }
 }
 
-#my-component-root *,
-#headlessui-portal-root * {
+#my-component-root *, #headlessui-portal-root * {
   z-index: 10000;
 }
 

docs/api_reference/create_api_rst.py

@@ -10,21 +10,12 @@ from pathlib import Path
 from typing import Dict, List, Literal, Optional, Sequence, TypedDict, Union
 
 import toml
-import typing_extensions
-from langchain_core.runnables import Runnable, RunnableSerializable
 from pydantic import BaseModel
 
 ROOT_DIR = Path(__file__).parents[2].absolute()
 HERE = Path(__file__).parent
 
-ClassKind = Literal[
-    "TypedDict",
-    "Regular",
-    "Pydantic",
-    "enum",
-    "RunnablePydantic",
-    "RunnableNonPydantic",
-]
+ClassKind = Literal["TypedDict", "Regular", "Pydantic", "enum"]
 
 
 class ClassInfo(TypedDict):
@@ -78,36 +69,8 @@ def _load_module_members(module_path: str, namespace: str) -> ModuleMembers:
             continue
 
         if inspect.isclass(type_):
-            # The clasification of the class is used to select a template
-            # for the object when rendering the documentation.
-            # See `templates` directory for defined templates.
-            # This is a hacky solution to distinguish between different
-            # kinds of thing that we want to render.
-            if type(type_) is typing_extensions._TypedDictMeta:  # type: ignore
+            if type(type_) == typing._TypedDictMeta:  # type: ignore
                 kind: ClassKind = "TypedDict"
-            elif type(type_) is typing._TypedDictMeta:  # type: ignore
-                kind: ClassKind = "TypedDict"
-            elif (
-                issubclass(type_, Runnable)
-                and issubclass(type_, BaseModel)
-                and type_ is not Runnable
-            ):
-                # RunnableSerializable subclasses from Pydantic which
-                # for which we use autodoc_pydantic for rendering.
-                # We need to distinguish these from regular Pydantic
-                # classes so we can hide inherited Runnable methods
-                # and provide a link to the Runnable interface from
-                # the template.
-                kind = "RunnablePydantic"
-            elif (
-                issubclass(type_, Runnable)
-                and not issubclass(type_, BaseModel)
-                and type_ is not Runnable
-            ):
-                # These are not pydantic classes but are Runnable.
-                # We'll hide all the inherited methods from Runnable
-                # but use a regular class template to render.
-                kind = "RunnableNonPydantic"
             elif issubclass(type_, Enum):
                 kind = "enum"
             elif issubclass(type_, BaseModel):
@@ -165,11 +128,11 @@ def _load_package_modules(
     of the modules/packages are part of the package vs. 3rd party or built-in.
 
     Parameters:
-        package_directory (Union[str, Path]): Path to the package directory.
-        submodule (Optional[str]): Optional name of submodule to load.
+        package_directory: Path to the package directory.
+        submodule: Optional name of submodule to load.
 
     Returns:
-        Dict[str, ModuleMembers]: A dictionary where keys are module names and values are ModuleMembers objects.
+        list: A list of loaded module objects.
     """
     package_path = (
         Path(package_directory)
@@ -224,7 +187,7 @@ def _load_package_modules(
             modules_by_namespace[top_namespace] = _module_members
 
         except ImportError as e:
-            print(f"Error: Unable to import module '{namespace}' with error: {e}")
+            print(f"Error: Unable to import module '{namespace}' with error: {e}")  # noqa: T201
 
     return modules_by_namespace
 
@@ -288,10 +251,6 @@ Classes
                     template = "enum.rst"
                 elif class_["kind"] == "Pydantic":
                     template = "pydantic.rst"
-                elif class_["kind"] == "RunnablePydantic":
-                    template = "runnable_pydantic.rst"
-                elif class_["kind"] == "RunnableNonPydantic":
-                    template = "runnable_non_pydantic.rst"
                 else:
                     template = "class.rst"
 
@@ -400,14 +359,9 @@ def main(dirs: Optional[list] = None) -> None:
         dirs = [
             dir_
             for dir_ in os.listdir(ROOT_DIR / "libs")
-            if dir_ not in ("cli", "partners", "standard-tests")
-        ]
-        dirs += [
-            dir_
-            for dir_ in os.listdir(ROOT_DIR / "libs" / "partners")
-            if os.path.isdir(ROOT_DIR / "libs" / "partners" / dir_)
-            and "pyproject.toml" in os.listdir(ROOT_DIR / "libs" / "partners" / dir_)
+            if dir_ not in ("cli", "partners")
         ]
+        dirs += os.listdir(ROOT_DIR / "libs" / "partners")
     for dir_ in dirs:
         # Skip any hidden directories
         # Some of these could be present by mistake in the code base

docs/api_reference/templates/class.rst

@@ -33,4 +33,4 @@
    {% endblock %}
 
 
-.. example_links:: {{ objname }}
+.. example_links:: {{ objname }}

docs/api_reference/templates/pydantic.rst

@@ -15,8 +15,6 @@
     :member-order: groupwise
     :show-inheritance: True
     :special-members: __call__
-    :exclude-members: construct, copy, dict, from_orm, parse_file, parse_obj, parse_raw, schema, schema_json, update_forward_refs, validate, json, is_lc_serializable, to_json, to_json_not_implemented, lc_secrets, lc_attributes, lc_id, get_lc_namespace
-
 
     {% block attributes %}
     {% endblock %}

docs/api_reference/templates/runnable_non_pydantic.rst

@@ -1,40 +0,0 @@
-:mod:`{{module}}`.{{objname}}
-{{ underline }}==============
-
-.. NOTE:: {{objname}} implements the standard :py:class:`Runnable Interface <langchain_core.runnables.base.Runnable>`. 🏃
-
-    The :py:class:`Runnable Interface <langchain_core.runnables.base.Runnable>` has additional methods that are available on runnables, such as :py:meth:`with_types <langchain_core.runnables.base.Runnable.with_types>`, :py:meth:`with_retry <langchain_core.runnables.base.Runnable.with_retry>`, :py:meth:`assign <langchain_core.runnables.base.Runnable.assign>`, :py:meth:`bind <langchain_core.runnables.base.Runnable.bind>`, :py:meth:`get_graph <langchain_core.runnables.base.Runnable.get_graph>`, and more.
-
-.. currentmodule:: {{ module }}
-
-.. autoclass:: {{ objname }}
-
-   {% block attributes %}
-   {% if attributes %}
-   .. rubric:: {{ _('Attributes') }}
-
-   .. autosummary::
-   {% for item in attributes %}
-      ~{{ name }}.{{ item }}
-   {%- endfor %}
-   {% endif %}
-   {% endblock %}
-
-   {% block methods %}
-   {% if methods %}
-   .. rubric:: {{ _('Methods') }}
-
-   .. autosummary::
-   {% for item in methods %}
-      ~{{ name }}.{{ item }}
-   {%- endfor %}
-
-   {% for item in methods %}
-   .. automethod:: {{ name }}.{{ item }}
-   {%- endfor %}
-
-   {% endif %}
-   {% endblock %}
-
-
-.. example_links:: {{ objname }}

docs/api_reference/templates/runnable_pydantic.rst

@@ -1,24 +0,0 @@
-:mod:`{{module}}`.{{objname}}
-{{ underline }}==============
-
-.. NOTE:: {{objname}} implements the standard :py:class:`Runnable Interface <langchain_core.runnables.base.Runnable>`. 🏃
-
-    The :py:class:`Runnable Interface <langchain_core.runnables.base.Runnable>` has additional methods that are available on runnables, such as :py:meth:`with_types <langchain_core.runnables.base.Runnable.with_types>`, :py:meth:`with_retry <langchain_core.runnables.base.Runnable.with_retry>`, :py:meth:`assign <langchain_core.runnables.base.Runnable.assign>`, :py:meth:`bind <langchain_core.runnables.base.Runnable.bind>`, :py:meth:`get_graph <langchain_core.runnables.base.Runnable.get_graph>`, and more.
-
-.. currentmodule:: {{ module }}
-
-.. autopydantic_model:: {{ objname }}
-    :model-show-json: False
-    :model-show-config-summary: False
-    :model-show-validator-members: False
-    :model-show-field-summary: False
-    :field-signature-prefix: param
-    :members:
-    :undoc-members:
-    :inherited-members:
-    :member-order: groupwise
-    :show-inheritance: True
-    :special-members: __call__
-    :exclude-members: construct, copy, dict, from_orm, parse_file, parse_obj, parse_raw, schema, schema_json, update_forward_refs, validate, json, is_lc_serializable, to_json_not_implemented, lc_secrets, lc_attributes, lc_id, get_lc_namespace, astream_log, transform, atransform, get_output_schema, get_prompts, config_schema, map, pick, pipe, with_listeners, with_alisteners, with_config, with_fallbacks, with_types, with_retry, InputType, OutputType, config_specs, output_schema, get_input_schema, get_graph, get_name, input_schema, name, bind, assign
-
-.. example_links:: {{ objname }}

docs/api_reference/themes/scikit-learn-modern/layout.html

@@ -2,129 +2,132 @@
 {%- set url_root = pathto('', 1) %}
 {%- if url_root == '#' %}{% set url_root = '' %}{% endif %}
 {%- if not embedded and docstitle %}
-    {%- set titlesuffix = " — "|safe + docstitle|e %}
+  {%- set titlesuffix = " — "|safe + docstitle|e %}
 {%- else %}
-    {%- set titlesuffix = "" %}
+  {%- set titlesuffix = "" %}
 {%- endif %}
 {%- set lang_attr = 'en' %}
 
 <!DOCTYPE html>
 <!--[if IE 8]><html class="no-js lt-ie9" lang="{{ lang_attr }}" > <![endif]-->
-<!--[if gt IE 8]><!-->
-<html class="no-js" lang="{{ lang_attr }}"> <!--<![endif]-->
+<!--[if gt IE 8]><!--> <html class="no-js" lang="{{ lang_attr }}" > <!--<![endif]-->
 <head>
-    <meta charset="utf-8">
-    {{ metatags }}
-    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <meta charset="utf-8">
+  {{ metatags }}
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
-    {% block htmltitle %}
-        <title>{{ title|striptags|e }}{{ titlesuffix }}</title>
-    {% endblock %}
-    <link rel="canonical"
-          href="https://api.python.langchain.com/en/latest/{{ pagename }}.html"/>
+  {% block htmltitle %}
+  <title>{{ title|striptags|e }}{{ titlesuffix }}</title>
+  {% endblock %}
+  <link rel="canonical" href="https://api.python.langchain.com/en/latest/{{pagename}}.html" />
 
-    {% if favicon_url %}
-        <link rel="shortcut icon" href="{{ favicon_url|e }}"/>
-    {% endif %}
+  {% if favicon_url %}
+  <link rel="shortcut icon" href="{{ favicon_url|e }}"/>
+  {% endif %}
 
-    <link rel="stylesheet"
-          href="{{ pathto('_static/css/vendor/bootstrap.min.css', 1) }}"
-          type="text/css"/>
-    {%- for css in css_files %}
-        {%- if css|attr("rel") %}
-            <link rel="{{ css.rel }}" href="{{ pathto(css.filename, 1) }}"
-                  type="text/css"{% if css.title is not none %}
-                  title="{{ css.title }}"{% endif %} />
-        {%- else %}
-            <link rel="stylesheet" href="{{ pathto(css, 1) }}" type="text/css"/>
-        {%- endif %}
-    {%- endfor %}
-    <link rel="stylesheet" href="{{ pathto('_static/' + style, 1) }}" type="text/css"/>
-    <script id="documentation_options" data-url_root="{{ pathto('', 1) }}"
-            src="{{ pathto('_static/documentation_options.js', 1) }}"></script>
-    <script src="{{ pathto('_static/jquery.js', 1) }}"></script>
-    {%- block extrahead %} {% endblock %}
+  <link rel="stylesheet" href="{{ pathto('_static/css/vendor/bootstrap.min.css', 1) }}" type="text/css" />
+  {%- for css in css_files %}
+    {%- if css|attr("rel") %}
+  <link rel="{{ css.rel }}" href="{{ pathto(css.filename, 1) }}" type="text/css"{% if css.title is not none %} title="{{ css.title }}"{% endif %} />
+    {%- else %}
+  <link rel="stylesheet" href="{{ pathto(css, 1) }}" type="text/css" />
+    {%- endif %}
+  {%- endfor %}
+  <link rel="stylesheet" href="{{ pathto('_static/' + style, 1) }}" type="text/css" />
+<script id="documentation_options" data-url_root="{{ pathto('', 1) }}" src="{{ pathto('_static/documentation_options.js', 1) }}"></script>
+<script src="{{ pathto('_static/jquery.js', 1) }}"></script>
+{%- block extrahead %} {% endblock %}
 </head>
 <body>
 {% include "nav.html" %}
 {%- block content %}
-    <div class="d-flex" id="sk-doc-wrapper">
-        <input type="checkbox" name="sk-toggle-checkbox" id="sk-toggle-checkbox">
-        <label id="sk-sidemenu-toggle" class="sk-btn-toggle-toc btn sk-btn-primary"
-               for="sk-toggle-checkbox">Toggle Menu</label>
-        <div id="sk-sidebar-wrapper" class="border-right">
-            <div class="sk-sidebar-toc-wrapper">
-                {%- if meta and meta['parenttoc']|tobool %}
-                    <div class="sk-sidebar-toc">
-                        {% set nav = get_nav_object(maxdepth=3, collapse=True, numbered=True) %}
-                        <ul>
-                            {% for main_nav_item in nav %}
-                                {% if main_nav_item.active %}
-                                    <li>
-                                        <a href="{{ main_nav_item.url }}"
-                                           class="sk-toc-active">{{ main_nav_item.title }}</a>
-                                    </li>
-                                    <ul>
-                                        {% for nav_item in main_nav_item.children %}
-                                            <li>
-                                                <a href="{{ nav_item.url }}"
-                                                   class="{% if nav_item.active %}sk-toc-active{% endif %}">{{ nav_item.title }}</a>
-                                                {% if nav_item.children %}
-                                                    <ul>
-                                                        {% for inner_child in nav_item.children %}
-                                                            <li class="sk-toctree-l3">
-                                                                <a href="{{ inner_child.url }}">{{ inner_child.title }}</a>
-                                                            </li>
-                                                        {% endfor %}
-                                                    </ul>
-                                                {% endif %}
-                                            </li>
-                                        {% endfor %}
-                                    </ul>
-                                {% endif %}
-                            {% endfor %}
-                        </ul>
-                    </div>
-                {%- elif meta and meta['globalsidebartoc']|tobool %}
-                    <div class="sk-sidebar-toc sk-sidebar-global-toc">
-                        {{ toctree(maxdepth=2, titles_only=True) }}
-                    </div>
-                {%- else %}
-                    <div class="sk-sidebar-toc">
-                        {{ toc }}
-                    </div>
-                {%- endif %}
-            </div>
+<div class="d-flex" id="sk-doc-wrapper">
+    <input type="checkbox" name="sk-toggle-checkbox" id="sk-toggle-checkbox">
+    <label id="sk-sidemenu-toggle" class="sk-btn-toggle-toc btn sk-btn-primary" for="sk-toggle-checkbox">Toggle Menu</label>
+    <div id="sk-sidebar-wrapper" class="border-right">
+      <div class="sk-sidebar-toc-wrapper">
+        <div class="btn-group w-100 mb-2" role="group" aria-label="rellinks">
+          {%- if prev %}
+            <a href="{{ prev.link|e }}" role="button" class="btn sk-btn-rellink py-1" sk-rellink-tooltip="{{ prev.title|striptags }}">Prev</a>
+          {%- else %}
+            <a href="#" role="button" class="btn sk-btn-rellink py-1 disabled"">Prev</a>
+          {%- endif %}
+          {%- if parents -%}
+            <a href="{{ parents[-1].link|e }}" role="button" class="btn sk-btn-rellink py-1" sk-rellink-tooltip="{{ parents[-1].title|striptags }}">Up</a>
+          {%- else %}
+            <a href="#" role="button" class="btn sk-btn-rellink disabled py-1">Up</a>
+          {%- endif %}
+          {%- if next %}
+            <a href="{{ next.link|e }}" role="button" class="btn sk-btn-rellink py-1" sk-rellink-tooltip="{{ next.title|striptags }}">Next</a>
+          {%- else %}
+            <a href="#" role="button" class="btn sk-btn-rellink py-1 disabled"">Next</a>
+          {%- endif %}
         </div>
-        <div id="sk-page-content-wrapper">
-            <div class="sk-page-content container-fluid body px-md-3" role="main">
-                {% block body %}{% endblock %}
+            {%- if meta and meta['parenttoc']|tobool %}
+            <div class="sk-sidebar-toc">
+            {% set nav = get_nav_object(maxdepth=3, collapse=True, numbered=True) %}
+              <ul>
+              {% for main_nav_item in nav %}
+              {% if main_nav_item.active %}
+              <li>
+                <a href="{{ main_nav_item.url }}" class="sk-toc-active">{{ main_nav_item.title }}</a>
+              </li>
+              <ul>
+              {% for nav_item in main_nav_item.children %}
+                <li>
+                  <a href="{{ nav_item.url }}" class="{% if nav_item.active %}sk-toc-active{% endif %}">{{ nav_item.title }}</a>
+                  {% if nav_item.children %}
+                  <ul>
+                    {% for inner_child in nav_item.children %}
+                      <li class="sk-toctree-l3">
+                        <a href="{{ inner_child.url }}">{{ inner_child.title }}</a>
+                      </li>
+                    {% endfor %}
+                  </ul>
+                  {% endif %}
+                </li>
+              {% endfor %}
+              </ul>
+              {% endif %}
+              {% endfor %}
+              </ul>
             </div>
-            <div class="container">
-                <footer class="sk-content-footer">
-                    {%- if pagename != 'index' %}
-                        {%- if show_copyright %}
-                            {%- if hasdoc('copyright') %}
-                                {% trans path=pathto('copyright'), copyright=copyright|e %}
-                                    &copy; {{ copyright }}.{% endtrans %}
-                            {%- else %}
-                                {% trans copyright=copyright|e %}&copy; {{ copyright }}
-                                    .{% endtrans %}
-                            {%- endif %}
-                        {%- endif %}
-                        {%- if last_updated %}
-                            {% trans last_updated=last_updated|e %}Last updated
-                                on {{ last_updated }}.{% endtrans %}
-                        {%- endif %}
-                        {%- if show_source and has_source and sourcename %}
-                            <a href="{{ pathto('_sources/' + sourcename, true)|e }}"
-                               rel="nofollow">{{ _('Show this page source') }}</a>
-                        {%- endif %}
-                    {%- endif %}
-                </footer>
+            {%- elif meta and meta['globalsidebartoc']|tobool %}
+            <div class="sk-sidebar-toc sk-sidebar-global-toc">
+              {{ toctree(maxdepth=2, titles_only=True) }}
             </div>
-        </div>
+            {%- else %}
+            <div class="sk-sidebar-toc">
+              {{ toc }}
+            </div>
+            {%- endif %}
+      </div>
     </div>
+    <div id="sk-page-content-wrapper">
+      <div class="sk-page-content container-fluid body px-md-3" role="main">
+        {% block body %}{% endblock %}
+      </div>
+    <div class="container">
+      <footer class="sk-content-footer">
+        {%- if pagename != 'index' %}
+        {%- if show_copyright %}
+          {%- if hasdoc('copyright') %}
+            {% trans path=pathto('copyright'), copyright=copyright|e %}&copy; {{ copyright }}.{% endtrans %}
+          {%- else %}
+            {% trans copyright=copyright|e %}&copy; {{ copyright }}.{% endtrans %}
+          {%- endif %}
+        {%- endif %}
+        {%- if last_updated %}
+          {% trans last_updated=last_updated|e %}Last updated on {{ last_updated }}.{% endtrans %}
+        {%- endif %}
+        {%- if show_source and has_source and sourcename %}
+          <a href="{{ pathto('_sources/' + sourcename, true)|e }}" rel="nofollow">{{ _('Show this page source') }}</a>
+        {%- endif %}
+        {%- endif %}
+      </footer>
+    </div>
+  </div>
+</div>
 {%- endblock %}
 <script src="{{ pathto('_static/js/vendor/bootstrap.min.js', 1) }}"></script>
 {% include "javascript.html" %}

docs/api_reference/themes/scikit-learn-modern/static/css/theme.css

@@ -1398,20 +1398,3 @@ table.sk-sponsor-table td {
 .highlight .vi { color: #bb60d5 } /* Name.Variable.Instance */
 .highlight .vm { color: #bb60d5 } /* Name.Variable.Magic */
 .highlight .il { color: #208050 } /* Literal.Number.Integer.Long */
-
-/** Custom styles overriding certain values */
-
-div.sk-sidebar-toc-wrapper {
-  width: unset;
-  overflow-x: auto;
-}
-
-div.sk-sidebar-toc-wrapper > [aria-label="rellinks"] {
-  position: sticky;
-  left: 0;
-}
-
-.navbar-nav .dropdown-menu {
-  max-height: 80vh;
-  overflow-y: auto;
-}

docs/docs/additional_resources/arxiv_references.mdx

@@ -1,912 +0,0 @@
-# arXiv
-            
-LangChain implements the latest research in the field of Natural Language Processing.
-This page contains `arXiv` papers referenced in the LangChain Documentation, API Reference,
- Templates, and Cookbooks.
-
-From the opposite direction, scientists use LangChain in research and reference LangChain in the research papers. 
-Here you find [such papers](https://arxiv.org/search/?query=langchain&searchtype=all&source=header).
-
-## Summary
-
-| arXiv id / Title | Authors | Published date 🔻 | LangChain Documentation|
-|------------------|---------|-------------------|------------------------|
-| `2402.03620v1` [Self-Discover: Large Language Models Self-Compose Reasoning Structures](http://arxiv.org/abs/2402.03620v1) | Pei Zhou, Jay Pujara, Xiang Ren,  et al. | 2024-02-06 | `Cookbook:` [self-discover](https://github.com/langchain-ai/langchain/blob/master/cookbook/self-discover.ipynb)
-| `2401.18059v1` [RAPTOR: Recursive Abstractive Processing for Tree-Organized Retrieval](http://arxiv.org/abs/2401.18059v1) | Parth Sarthi, Salman Abdullah, Aditi Tuli,  et al. | 2024-01-31 | `Cookbook:` [RAPTOR](https://github.com/langchain-ai/langchain/blob/master/cookbook/RAPTOR.ipynb)
-| `2401.15884v2` [Corrective Retrieval Augmented Generation](http://arxiv.org/abs/2401.15884v2) | Shi-Qi Yan, Jia-Chen Gu, Yun Zhu,  et al. | 2024-01-29 | `Cookbook:` [langgraph_crag](https://github.com/langchain-ai/langchain/blob/master/cookbook/langgraph_crag.ipynb)
-| `2401.04088v1` [Mixtral of Experts](http://arxiv.org/abs/2401.04088v1) | Albert Q. Jiang, Alexandre Sablayrolles, Antoine Roux,  et al. | 2024-01-08 | `Cookbook:` [together_ai](https://github.com/langchain-ai/langchain/blob/master/cookbook/together_ai.ipynb)
-| `2312.06648v2` [Dense X Retrieval: What Retrieval Granularity Should We Use?](http://arxiv.org/abs/2312.06648v2) | Tong Chen, Hongwei Wang, Sihao Chen,  et al. | 2023-12-11 | `Template:` [propositional-retrieval](https://python.langchain.com/docs/templates/propositional-retrieval)
-| `2311.09210v1` [Chain-of-Note: Enhancing Robustness in Retrieval-Augmented Language Models](http://arxiv.org/abs/2311.09210v1) | Wenhao Yu, Hongming Zhang, Xiaoman Pan,  et al. | 2023-11-15 | `Template:` [chain-of-note-wiki](https://python.langchain.com/docs/templates/chain-of-note-wiki)
-| `2310.11511v1` [Self-RAG: Learning to Retrieve, Generate, and Critique through Self-Reflection](http://arxiv.org/abs/2310.11511v1) | Akari Asai, Zeqiu Wu, Yizhong Wang,  et al. | 2023-10-17 | `Cookbook:` [langgraph_self_rag](https://github.com/langchain-ai/langchain/blob/master/cookbook/langgraph_self_rag.ipynb)
-| `2310.06117v2` [Take a Step Back: Evoking Reasoning via Abstraction in Large Language Models](http://arxiv.org/abs/2310.06117v2) | Huaixiu Steven Zheng, Swaroop Mishra, Xinyun Chen,  et al. | 2023-10-09 | `Template:` [stepback-qa-prompting](https://python.langchain.com/docs/templates/stepback-qa-prompting), `Cookbook:` [stepback-qa](https://github.com/langchain-ai/langchain/blob/master/cookbook/stepback-qa.ipynb)
-| `2307.09288v2` [Llama 2: Open Foundation and Fine-Tuned Chat Models](http://arxiv.org/abs/2307.09288v2) | Hugo Touvron, Louis Martin, Kevin Stone,  et al. | 2023-07-18 | `Cookbook:` [Semi_Structured_RAG](https://github.com/langchain-ai/langchain/blob/master/cookbook/Semi_Structured_RAG.ipynb)
-| `2305.14283v3` [Query Rewriting for Retrieval-Augmented Large Language Models](http://arxiv.org/abs/2305.14283v3) | Xinbei Ma, Yeyun Gong, Pengcheng He,  et al. | 2023-05-23 | `Template:` [rewrite-retrieve-read](https://python.langchain.com/docs/templates/rewrite-retrieve-read), `Cookbook:` [rewrite](https://github.com/langchain-ai/langchain/blob/master/cookbook/rewrite.ipynb)
-| `2305.08291v1` [Large Language Model Guided Tree-of-Thought](http://arxiv.org/abs/2305.08291v1) | Jieyi Long | 2023-05-15 | `API:` [langchain_experimental.tot](https://api.python.langchain.com/en/latest/experimental_api_reference.html#module-langchain_experimental.tot), `Cookbook:` [tree_of_thought](https://github.com/langchain-ai/langchain/blob/master/cookbook/tree_of_thought.ipynb)
-| `2305.04091v3` [Plan-and-Solve Prompting: Improving Zero-Shot Chain-of-Thought Reasoning by Large Language Models](http://arxiv.org/abs/2305.04091v3) | Lei Wang, Wanyu Xu, Yihuai Lan,  et al. | 2023-05-06 | `Cookbook:` [plan_and_execute_agent](https://github.com/langchain-ai/langchain/blob/master/cookbook/plan_and_execute_agent.ipynb)
-| `2304.08485v2` [Visual Instruction Tuning](http://arxiv.org/abs/2304.08485v2) | Haotian Liu, Chunyuan Li, Qingyang Wu,  et al. | 2023-04-17 | `Cookbook:` [Semi_structured_and_multi_modal_RAG](https://github.com/langchain-ai/langchain/blob/master/cookbook/Semi_structured_and_multi_modal_RAG.ipynb), [Semi_structured_multi_modal_RAG_LLaMA2](https://github.com/langchain-ai/langchain/blob/master/cookbook/Semi_structured_multi_modal_RAG_LLaMA2.ipynb)
-| `2304.03442v2` [Generative Agents: Interactive Simulacra of Human Behavior](http://arxiv.org/abs/2304.03442v2) | Joon Sung Park, Joseph C. O'Brien, Carrie J. Cai,  et al. | 2023-04-07 | `Cookbook:` [multiagent_bidding](https://github.com/langchain-ai/langchain/blob/master/cookbook/multiagent_bidding.ipynb), [generative_agents_interactive_simulacra_of_human_behavior](https://github.com/langchain-ai/langchain/blob/master/cookbook/generative_agents_interactive_simulacra_of_human_behavior.ipynb)
-| `2303.17760v2` [CAMEL: Communicative Agents for "Mind" Exploration of Large Language Model Society](http://arxiv.org/abs/2303.17760v2) | Guohao Li, Hasan Abed Al Kader Hammoud, Hani Itani,  et al. | 2023-03-31 | `Cookbook:` [camel_role_playing](https://github.com/langchain-ai/langchain/blob/master/cookbook/camel_role_playing.ipynb)
-| `2303.17580v4` [HuggingGPT: Solving AI Tasks with ChatGPT and its Friends in Hugging Face](http://arxiv.org/abs/2303.17580v4) | Yongliang Shen, Kaitao Song, Xu Tan,  et al. | 2023-03-30 | `API:` [langchain_experimental.autonomous_agents](https://api.python.langchain.com/en/latest/experimental_api_reference.html#module-langchain_experimental.autonomous_agents), `Cookbook:` [hugginggpt](https://github.com/langchain-ai/langchain/blob/master/cookbook/hugginggpt.ipynb)
-| `2303.08774v6` [GPT-4 Technical Report](http://arxiv.org/abs/2303.08774v6) | OpenAI, Josh Achiam, Steven Adler,  et al. | 2023-03-15 | `Docs:` [docs/integrations/vectorstores/mongodb_atlas](https://python.langchain.com/docs/integrations/vectorstores/mongodb_atlas)
-| `2301.10226v4` [A Watermark for Large Language Models](http://arxiv.org/abs/2301.10226v4) | John Kirchenbauer, Jonas Geiping, Yuxin Wen,  et al. | 2023-01-24 | `API:` [langchain_community...HuggingFaceEndpoint](https://api.python.langchain.com/en/latest/llms/langchain_community.llms.huggingface_endpoint.HuggingFaceEndpoint.html#langchain_community.llms.huggingface_endpoint.HuggingFaceEndpoint), [langchain_huggingface...HuggingFaceEndpoint](https://api.python.langchain.com/en/latest/llms/langchain_huggingface.llms.huggingface_endpoint.HuggingFaceEndpoint.html#langchain_huggingface.llms.huggingface_endpoint.HuggingFaceEndpoint), [langchain_community...OCIModelDeploymentTGI](https://api.python.langchain.com/en/latest/llms/langchain_community.llms.oci_data_science_model_deployment_endpoint.OCIModelDeploymentTGI.html#langchain_community.llms.oci_data_science_model_deployment_endpoint.OCIModelDeploymentTGI), [langchain_community...HuggingFaceTextGenInference](https://api.python.langchain.com/en/latest/llms/langchain_community.llms.huggingface_text_gen_inference.HuggingFaceTextGenInference.html#langchain_community.llms.huggingface_text_gen_inference.HuggingFaceTextGenInference)
-| `2212.10496v1` [Precise Zero-Shot Dense Retrieval without Relevance Labels](http://arxiv.org/abs/2212.10496v1) | Luyu Gao, Xueguang Ma, Jimmy Lin,  et al. | 2022-12-20 | `API:` [langchain...HypotheticalDocumentEmbedder](https://api.python.langchain.com/en/latest/chains/langchain.chains.hyde.base.HypotheticalDocumentEmbedder.html#langchain.chains.hyde.base.HypotheticalDocumentEmbedder), `Template:` [hyde](https://python.langchain.com/docs/templates/hyde), `Cookbook:` [hypothetical_document_embeddings](https://github.com/langchain-ai/langchain/blob/master/cookbook/hypothetical_document_embeddings.ipynb)
-| `2212.07425v3` [Robust and Explainable Identification of Logical Fallacies in Natural Language Arguments](http://arxiv.org/abs/2212.07425v3) | Zhivar Sourati, Vishnu Priya Prasanna Venkatesh, Darshan Deshpande,  et al. | 2022-12-12 | `API:` [langchain_experimental.fallacy_removal](https://api.python.langchain.com/en/latest/experimental_api_reference.html#module-langchain_experimental.fallacy_removal)
-| `2211.13892v2` [Complementary Explanations for Effective In-Context Learning](http://arxiv.org/abs/2211.13892v2) | Xi Ye, Srinivasan Iyer, Asli Celikyilmaz,  et al. | 2022-11-25 | `API:` [langchain_core...MaxMarginalRelevanceExampleSelector](https://api.python.langchain.com/en/latest/example_selectors/langchain_core.example_selectors.semantic_similarity.MaxMarginalRelevanceExampleSelector.html#langchain_core.example_selectors.semantic_similarity.MaxMarginalRelevanceExampleSelector)
-| `2211.10435v2` [PAL: Program-aided Language Models](http://arxiv.org/abs/2211.10435v2) | Luyu Gao, Aman Madaan, Shuyan Zhou,  et al. | 2022-11-18 | `API:` [langchain_experimental...PALChain](https://api.python.langchain.com/en/latest/pal_chain/langchain_experimental.pal_chain.base.PALChain.html#langchain_experimental.pal_chain.base.PALChain), [langchain_experimental.pal_chain](https://api.python.langchain.com/en/latest/experimental_api_reference.html#module-langchain_experimental.pal_chain), `Cookbook:` [program_aided_language_model](https://github.com/langchain-ai/langchain/blob/master/cookbook/program_aided_language_model.ipynb)
-| `2210.03629v3` [ReAct: Synergizing Reasoning and Acting in Language Models](http://arxiv.org/abs/2210.03629v3) | Shunyu Yao, Jeffrey Zhao, Dian Yu,  et al. | 2022-10-06 | `Docs:` [docs/integrations/providers/cohere](https://python.langchain.com/docs/integrations/providers/cohere), [docs/integrations/chat/huggingface](https://python.langchain.com/docs/integrations/chat/huggingface), [docs/integrations/tools/ionic_shopping](https://python.langchain.com/docs/integrations/tools/ionic_shopping), `API:` [langchain...create_react_agent](https://api.python.langchain.com/en/latest/agents/langchain.agents.react.agent.create_react_agent.html#langchain.agents.react.agent.create_react_agent), [langchain...TrajectoryEvalChain](https://api.python.langchain.com/en/latest/evaluation/langchain.evaluation.agents.trajectory_eval_chain.TrajectoryEvalChain.html#langchain.evaluation.agents.trajectory_eval_chain.TrajectoryEvalChain)
-| `2209.10785v2` [Deep Lake: a Lakehouse for Deep Learning](http://arxiv.org/abs/2209.10785v2) | Sasun Hambardzumyan, Abhinav Tuli, Levon Ghukasyan,  et al. | 2022-09-22 | `Docs:` [docs/integrations/providers/activeloop_deeplake](https://python.langchain.com/docs/integrations/providers/activeloop_deeplake)
-| `2205.12654v1` [Bitext Mining Using Distilled Sentence Representations for Low-Resource Languages](http://arxiv.org/abs/2205.12654v1) | Kevin Heffernan, Onur Çelebi, Holger Schwenk | 2022-05-25 | `API:` [langchain_community...LaserEmbeddings](https://api.python.langchain.com/en/latest/embeddings/langchain_community.embeddings.laser.LaserEmbeddings.html#langchain_community.embeddings.laser.LaserEmbeddings)
-| `2204.00498v1` [Evaluating the Text-to-SQL Capabilities of Large Language Models](http://arxiv.org/abs/2204.00498v1) | Nitarshan Rajkumar, Raymond Li, Dzmitry Bahdanau | 2022-03-15 | `API:` [langchain_community...SparkSQL](https://api.python.langchain.com/en/latest/utilities/langchain_community.utilities.spark_sql.SparkSQL.html#langchain_community.utilities.spark_sql.SparkSQL), [langchain_community...SQLDatabase](https://api.python.langchain.com/en/latest/utilities/langchain_community.utilities.sql_database.SQLDatabase.html#langchain_community.utilities.sql_database.SQLDatabase)
-| `2202.00666v5` [Locally Typical Sampling](http://arxiv.org/abs/2202.00666v5) | Clara Meister, Tiago Pimentel, Gian Wiher,  et al. | 2022-02-01 | `API:` [langchain_community...HuggingFaceEndpoint](https://api.python.langchain.com/en/latest/llms/langchain_community.llms.huggingface_endpoint.HuggingFaceEndpoint.html#langchain_community.llms.huggingface_endpoint.HuggingFaceEndpoint), [langchain_huggingface...HuggingFaceEndpoint](https://api.python.langchain.com/en/latest/llms/langchain_huggingface.llms.huggingface_endpoint.HuggingFaceEndpoint.html#langchain_huggingface.llms.huggingface_endpoint.HuggingFaceEndpoint), [langchain_community...HuggingFaceTextGenInference](https://api.python.langchain.com/en/latest/llms/langchain_community.llms.huggingface_text_gen_inference.HuggingFaceTextGenInference.html#langchain_community.llms.huggingface_text_gen_inference.HuggingFaceTextGenInference)
-| `2103.00020v1` [Learning Transferable Visual Models From Natural Language Supervision](http://arxiv.org/abs/2103.00020v1) | Alec Radford, Jong Wook Kim, Chris Hallacy,  et al. | 2021-02-26 | `API:` [langchain_experimental.open_clip](https://api.python.langchain.com/en/latest/experimental_api_reference.html#module-langchain_experimental.open_clip)
-| `1909.05858v2` [CTRL: A Conditional Transformer Language Model for Controllable Generation](http://arxiv.org/abs/1909.05858v2) | Nitish Shirish Keskar, Bryan McCann, Lav R. Varshney,  et al. | 2019-09-11 | `API:` [langchain_community...HuggingFaceEndpoint](https://api.python.langchain.com/en/latest/llms/langchain_community.llms.huggingface_endpoint.HuggingFaceEndpoint.html#langchain_community.llms.huggingface_endpoint.HuggingFaceEndpoint), [langchain_huggingface...HuggingFaceEndpoint](https://api.python.langchain.com/en/latest/llms/langchain_huggingface.llms.huggingface_endpoint.HuggingFaceEndpoint.html#langchain_huggingface.llms.huggingface_endpoint.HuggingFaceEndpoint), [langchain_community...HuggingFaceTextGenInference](https://api.python.langchain.com/en/latest/llms/langchain_community.llms.huggingface_text_gen_inference.HuggingFaceTextGenInference.html#langchain_community.llms.huggingface_text_gen_inference.HuggingFaceTextGenInference)
-| `1908.10084v1` [Sentence-BERT: Sentence Embeddings using Siamese BERT-Networks](http://arxiv.org/abs/1908.10084v1) | Nils Reimers, Iryna Gurevych | 2019-08-27 | `Docs:` [docs/integrations/text_embedding/sentence_transformers](https://python.langchain.com/docs/integrations/text_embedding/sentence_transformers)
-
-## Self-Discover: Large Language Models Self-Compose Reasoning Structures
-
-- **arXiv id:** 2402.03620v1
-- **Title:** Self-Discover: Large Language Models Self-Compose Reasoning Structures
-- **Authors:** Pei Zhou, Jay Pujara, Xiang Ren,  et al.
-- **Published Date:** 2024-02-06
-- **URL:** http://arxiv.org/abs/2402.03620v1
-- **LangChain:**
-
-   - **Cookbook:** [self-discover](https://github.com/langchain-ai/langchain/blob/master/cookbook/self-discover.ipynb)
-
-**Abstract:** We introduce SELF-DISCOVER, a general framework for LLMs to self-discover the
-task-intrinsic reasoning structures to tackle complex reasoning problems that
-are challenging for typical prompting methods. Core to the framework is a
-self-discovery process where LLMs select multiple atomic reasoning modules such
-as critical thinking and step-by-step thinking, and compose them into an
-explicit reasoning structure for LLMs to follow during decoding. SELF-DISCOVER
-substantially improves GPT-4 and PaLM 2's performance on challenging reasoning
-benchmarks such as BigBench-Hard, grounded agent reasoning, and MATH, by as
-much as 32% compared to Chain of Thought (CoT). Furthermore, SELF-DISCOVER
-outperforms inference-intensive methods such as CoT-Self-Consistency by more
-than 20%, while requiring 10-40x fewer inference compute. Finally, we show that
-the self-discovered reasoning structures are universally applicable across
-model families: from PaLM 2-L to GPT-4, and from GPT-4 to Llama2, and share
-commonalities with human reasoning patterns.
-                
-## RAPTOR: Recursive Abstractive Processing for Tree-Organized Retrieval
-
-- **arXiv id:** 2401.18059v1
-- **Title:** RAPTOR: Recursive Abstractive Processing for Tree-Organized Retrieval
-- **Authors:** Parth Sarthi, Salman Abdullah, Aditi Tuli,  et al.
-- **Published Date:** 2024-01-31
-- **URL:** http://arxiv.org/abs/2401.18059v1
-- **LangChain:**
-
-   - **Cookbook:** [RAPTOR](https://github.com/langchain-ai/langchain/blob/master/cookbook/RAPTOR.ipynb)
-
-**Abstract:** Retrieval-augmented language models can better adapt to changes in world
-state and incorporate long-tail knowledge. However, most existing methods
-retrieve only short contiguous chunks from a retrieval corpus, limiting
-holistic understanding of the overall document context. We introduce the novel
-approach of recursively embedding, clustering, and summarizing chunks of text,
-constructing a tree with differing levels of summarization from the bottom up.
-At inference time, our RAPTOR model retrieves from this tree, integrating
-information across lengthy documents at different levels of abstraction.
-Controlled experiments show that retrieval with recursive summaries offers
-significant improvements over traditional retrieval-augmented LMs on several
-tasks. On question-answering tasks that involve complex, multi-step reasoning,
-we show state-of-the-art results; for example, by coupling RAPTOR retrieval
-with the use of GPT-4, we can improve the best performance on the QuALITY
-benchmark by 20% in absolute accuracy.
-                
-## Corrective Retrieval Augmented Generation
-
-- **arXiv id:** 2401.15884v2
-- **Title:** Corrective Retrieval Augmented Generation
-- **Authors:** Shi-Qi Yan, Jia-Chen Gu, Yun Zhu,  et al.
-- **Published Date:** 2024-01-29
-- **URL:** http://arxiv.org/abs/2401.15884v2
-- **LangChain:**
-
-   - **Cookbook:** [langgraph_crag](https://github.com/langchain-ai/langchain/blob/master/cookbook/langgraph_crag.ipynb)
-
-**Abstract:** Large language models (LLMs) inevitably exhibit hallucinations since the
-accuracy of generated texts cannot be secured solely by the parametric
-knowledge they encapsulate. Although retrieval-augmented generation (RAG) is a
-practicable complement to LLMs, it relies heavily on the relevance of retrieved
-documents, raising concerns about how the model behaves if retrieval goes
-wrong. To this end, we propose the Corrective Retrieval Augmented Generation
-(CRAG) to improve the robustness of generation. Specifically, a lightweight
-retrieval evaluator is designed to assess the overall quality of retrieved
-documents for a query, returning a confidence degree based on which different
-knowledge retrieval actions can be triggered. Since retrieval from static and
-limited corpora can only return sub-optimal documents, large-scale web searches
-are utilized as an extension for augmenting the retrieval results. Besides, a
-decompose-then-recompose algorithm is designed for retrieved documents to
-selectively focus on key information and filter out irrelevant information in
-them. CRAG is plug-and-play and can be seamlessly coupled with various
-RAG-based approaches. Experiments on four datasets covering short- and
-long-form generation tasks show that CRAG can significantly improve the
-performance of RAG-based approaches.
-                
-## Mixtral of Experts
-
-- **arXiv id:** 2401.04088v1
-- **Title:** Mixtral of Experts
-- **Authors:** Albert Q. Jiang, Alexandre Sablayrolles, Antoine Roux,  et al.
-- **Published Date:** 2024-01-08
-- **URL:** http://arxiv.org/abs/2401.04088v1
-- **LangChain:**
-
-   - **Cookbook:** [together_ai](https://github.com/langchain-ai/langchain/blob/master/cookbook/together_ai.ipynb)
-
-**Abstract:** We introduce Mixtral 8x7B, a Sparse Mixture of Experts (SMoE) language model.
-Mixtral has the same architecture as Mistral 7B, with the difference that each
-layer is composed of 8 feedforward blocks (i.e. experts). For every token, at
-each layer, a router network selects two experts to process the current state
-and combine their outputs. Even though each token only sees two experts, the
-selected experts can be different at each timestep. As a result, each token has
-access to 47B parameters, but only uses 13B active parameters during inference.
-Mixtral was trained with a context size of 32k tokens and it outperforms or
-matches Llama 2 70B and GPT-3.5 across all evaluated benchmarks. In particular,
-Mixtral vastly outperforms Llama 2 70B on mathematics, code generation, and
-multilingual benchmarks. We also provide a model fine-tuned to follow
-instructions, Mixtral 8x7B - Instruct, that surpasses GPT-3.5 Turbo,
-Claude-2.1, Gemini Pro, and Llama 2 70B - chat model on human benchmarks. Both
-the base and instruct models are released under the Apache 2.0 license.
-                
-## Dense X Retrieval: What Retrieval Granularity Should We Use?
-
-- **arXiv id:** 2312.06648v2
-- **Title:** Dense X Retrieval: What Retrieval Granularity Should We Use?
-- **Authors:** Tong Chen, Hongwei Wang, Sihao Chen,  et al.
-- **Published Date:** 2023-12-11
-- **URL:** http://arxiv.org/abs/2312.06648v2
-- **LangChain:**
-
-   - **Template:** [propositional-retrieval](https://python.langchain.com/docs/templates/propositional-retrieval)
-
-**Abstract:** Dense retrieval has become a prominent method to obtain relevant context or
-world knowledge in open-domain NLP tasks. When we use a learned dense retriever
-on a retrieval corpus at inference time, an often-overlooked design choice is
-the retrieval unit in which the corpus is indexed, e.g. document, passage, or
-sentence. We discover that the retrieval unit choice significantly impacts the
-performance of both retrieval and downstream tasks. Distinct from the typical
-approach of using passages or sentences, we introduce a novel retrieval unit,
-proposition, for dense retrieval. Propositions are defined as atomic
-expressions within text, each encapsulating a distinct factoid and presented in
-a concise, self-contained natural language format. We conduct an empirical
-comparison of different retrieval granularity. Our results reveal that
-proposition-based retrieval significantly outperforms traditional passage or
-sentence-based methods in dense retrieval. Moreover, retrieval by proposition
-also enhances the performance of downstream QA tasks, since the retrieved texts
-are more condensed with question-relevant information, reducing the need for
-lengthy input tokens and minimizing the inclusion of extraneous, irrelevant
-information.
-                
-## Chain-of-Note: Enhancing Robustness in Retrieval-Augmented Language Models
-
-- **arXiv id:** 2311.09210v1
-- **Title:** Chain-of-Note: Enhancing Robustness in Retrieval-Augmented Language Models
-- **Authors:** Wenhao Yu, Hongming Zhang, Xiaoman Pan,  et al.
-- **Published Date:** 2023-11-15
-- **URL:** http://arxiv.org/abs/2311.09210v1
-- **LangChain:**
-
-   - **Template:** [chain-of-note-wiki](https://python.langchain.com/docs/templates/chain-of-note-wiki)
-
-**Abstract:** Retrieval-augmented language models (RALMs) represent a substantial
-advancement in the capabilities of large language models, notably in reducing
-factual hallucination by leveraging external knowledge sources. However, the
-reliability of the retrieved information is not always guaranteed. The
-retrieval of irrelevant data can lead to misguided responses, and potentially
-causing the model to overlook its inherent knowledge, even when it possesses
-adequate information to address the query. Moreover, standard RALMs often
-struggle to assess whether they possess adequate knowledge, both intrinsic and
-retrieved, to provide an accurate answer. In situations where knowledge is
-lacking, these systems should ideally respond with "unknown" when the answer is
-unattainable. In response to these challenges, we introduces Chain-of-Noting
-(CoN), a novel approach aimed at improving the robustness of RALMs in facing
-noisy, irrelevant documents and in handling unknown scenarios. The core idea of
-CoN is to generate sequential reading notes for retrieved documents, enabling a
-thorough evaluation of their relevance to the given question and integrating
-this information to formulate the final answer. We employed ChatGPT to create
-training data for CoN, which was subsequently trained on an LLaMa-2 7B model.
-Our experiments across four open-domain QA benchmarks show that RALMs equipped
-with CoN significantly outperform standard RALMs. Notably, CoN achieves an
-average improvement of +7.9 in EM score given entirely noisy retrieved
-documents and +10.5 in rejection rates for real-time questions that fall
-outside the pre-training knowledge scope.
-                
-## Self-RAG: Learning to Retrieve, Generate, and Critique through Self-Reflection
-
-- **arXiv id:** 2310.11511v1
-- **Title:** Self-RAG: Learning to Retrieve, Generate, and Critique through Self-Reflection
-- **Authors:** Akari Asai, Zeqiu Wu, Yizhong Wang,  et al.
-- **Published Date:** 2023-10-17
-- **URL:** http://arxiv.org/abs/2310.11511v1
-- **LangChain:**
-
-   - **Cookbook:** [langgraph_self_rag](https://github.com/langchain-ai/langchain/blob/master/cookbook/langgraph_self_rag.ipynb)
-
-**Abstract:** Despite their remarkable capabilities, large language models (LLMs) often
-produce responses containing factual inaccuracies due to their sole reliance on
-the parametric knowledge they encapsulate. Retrieval-Augmented Generation
-(RAG), an ad hoc approach that augments LMs with retrieval of relevant
-knowledge, decreases such issues. However, indiscriminately retrieving and
-incorporating a fixed number of retrieved passages, regardless of whether
-retrieval is necessary, or passages are relevant, diminishes LM versatility or
-can lead to unhelpful response generation. We introduce a new framework called
-Self-Reflective Retrieval-Augmented Generation (Self-RAG) that enhances an LM's
-quality and factuality through retrieval and self-reflection. Our framework
-trains a single arbitrary LM that adaptively retrieves passages on-demand, and
-generates and reflects on retrieved passages and its own generations using
-special tokens, called reflection tokens. Generating reflection tokens makes
-the LM controllable during the inference phase, enabling it to tailor its
-behavior to diverse task requirements. Experiments show that Self-RAG (7B and
-13B parameters) significantly outperforms state-of-the-art LLMs and
-retrieval-augmented models on a diverse set of tasks. Specifically, Self-RAG
-outperforms ChatGPT and retrieval-augmented Llama2-chat on Open-domain QA,
-reasoning and fact verification tasks, and it shows significant gains in
-improving factuality and citation accuracy for long-form generations relative
-to these models.
-                
-## Take a Step Back: Evoking Reasoning via Abstraction in Large Language Models
-
-- **arXiv id:** 2310.06117v2
-- **Title:** Take a Step Back: Evoking Reasoning via Abstraction in Large Language Models
-- **Authors:** Huaixiu Steven Zheng, Swaroop Mishra, Xinyun Chen,  et al.
-- **Published Date:** 2023-10-09
-- **URL:** http://arxiv.org/abs/2310.06117v2
-- **LangChain:**
-
-   - **Template:** [stepback-qa-prompting](https://python.langchain.com/docs/templates/stepback-qa-prompting)
-   - **Cookbook:** [stepback-qa](https://github.com/langchain-ai/langchain/blob/master/cookbook/stepback-qa.ipynb)
-
-**Abstract:** We present Step-Back Prompting, a simple prompting technique that enables
-LLMs to do abstractions to derive high-level concepts and first principles from
-instances containing specific details. Using the concepts and principles to
-guide reasoning, LLMs significantly improve their abilities in following a
-correct reasoning path towards the solution. We conduct experiments of
-Step-Back Prompting with PaLM-2L, GPT-4 and Llama2-70B models, and observe
-substantial performance gains on various challenging reasoning-intensive tasks
-including STEM, Knowledge QA, and Multi-Hop Reasoning. For instance, Step-Back
-Prompting improves PaLM-2L performance on MMLU (Physics and Chemistry) by 7%
-and 11% respectively, TimeQA by 27%, and MuSiQue by 7%.
-                
-## Llama 2: Open Foundation and Fine-Tuned Chat Models
-
-- **arXiv id:** 2307.09288v2
-- **Title:** Llama 2: Open Foundation and Fine-Tuned Chat Models
-- **Authors:** Hugo Touvron, Louis Martin, Kevin Stone,  et al.
-- **Published Date:** 2023-07-18
-- **URL:** http://arxiv.org/abs/2307.09288v2
-- **LangChain:**
-
-   - **Cookbook:** [Semi_Structured_RAG](https://github.com/langchain-ai/langchain/blob/master/cookbook/Semi_Structured_RAG.ipynb)
-
-**Abstract:** In this work, we develop and release Llama 2, a collection of pretrained and
-fine-tuned large language models (LLMs) ranging in scale from 7 billion to 70
-billion parameters. Our fine-tuned LLMs, called Llama 2-Chat, are optimized for
-dialogue use cases. Our models outperform open-source chat models on most
-benchmarks we tested, and based on our human evaluations for helpfulness and
-safety, may be a suitable substitute for closed-source models. We provide a
-detailed description of our approach to fine-tuning and safety improvements of
-Llama 2-Chat in order to enable the community to build on our work and
-contribute to the responsible development of LLMs.
-                
-## Query Rewriting for Retrieval-Augmented Large Language Models
-
-- **arXiv id:** 2305.14283v3
-- **Title:** Query Rewriting for Retrieval-Augmented Large Language Models
-- **Authors:** Xinbei Ma, Yeyun Gong, Pengcheng He,  et al.
-- **Published Date:** 2023-05-23
-- **URL:** http://arxiv.org/abs/2305.14283v3
-- **LangChain:**
-
-   - **Template:** [rewrite-retrieve-read](https://python.langchain.com/docs/templates/rewrite-retrieve-read)
-   - **Cookbook:** [rewrite](https://github.com/langchain-ai/langchain/blob/master/cookbook/rewrite.ipynb)
-
-**Abstract:** Large Language Models (LLMs) play powerful, black-box readers in the
-retrieve-then-read pipeline, making remarkable progress in knowledge-intensive
-tasks. This work introduces a new framework, Rewrite-Retrieve-Read instead of
-the previous retrieve-then-read for the retrieval-augmented LLMs from the
-perspective of the query rewriting. Unlike prior studies focusing on adapting
-either the retriever or the reader, our approach pays attention to the
-adaptation of the search query itself, for there is inevitably a gap between
-the input text and the needed knowledge in retrieval. We first prompt an LLM to
-generate the query, then use a web search engine to retrieve contexts.
-Furthermore, to better align the query to the frozen modules, we propose a
-trainable scheme for our pipeline. A small language model is adopted as a
-trainable rewriter to cater to the black-box LLM reader. The rewriter is
-trained using the feedback of the LLM reader by reinforcement learning.
-Evaluation is conducted on downstream tasks, open-domain QA and multiple-choice
-QA. Experiments results show consistent performance improvement, indicating
-that our framework is proven effective and scalable, and brings a new framework
-for retrieval-augmented LLM.
-                
-## Large Language Model Guided Tree-of-Thought
-
-- **arXiv id:** 2305.08291v1
-- **Title:** Large Language Model Guided Tree-of-Thought
-- **Authors:** Jieyi Long
-- **Published Date:** 2023-05-15
-- **URL:** http://arxiv.org/abs/2305.08291v1
-- **LangChain:**
-
-   - **API Reference:** [langchain_experimental.tot](https://api.python.langchain.com/en/latest/experimental_api_reference.html#module-langchain_experimental.tot)
-   - **Cookbook:** [tree_of_thought](https://github.com/langchain-ai/langchain/blob/master/cookbook/tree_of_thought.ipynb)
-
-**Abstract:** In this paper, we introduce the Tree-of-Thought (ToT) framework, a novel
-approach aimed at improving the problem-solving capabilities of auto-regressive
-large language models (LLMs). The ToT technique is inspired by the human mind's
-approach for solving complex reasoning tasks through trial and error. In this
-process, the human mind explores the solution space through a tree-like thought
-process, allowing for backtracking when necessary. To implement ToT as a
-software system, we augment an LLM with additional modules including a prompter
-agent, a checker module, a memory module, and a ToT controller. In order to
-solve a given problem, these modules engage in a multi-round conversation with
-the LLM. The memory module records the conversation and state history of the
-problem solving process, which allows the system to backtrack to the previous
-steps of the thought-process and explore other directions from there. To verify
-the effectiveness of the proposed technique, we implemented a ToT-based solver
-for the Sudoku Puzzle. Experimental results show that the ToT framework can
-significantly increase the success rate of Sudoku puzzle solving. Our
-implementation of the ToT-based Sudoku solver is available on GitHub:
-\url{https://github.com/jieyilong/tree-of-thought-puzzle-solver}.
-                
-## Plan-and-Solve Prompting: Improving Zero-Shot Chain-of-Thought Reasoning by Large Language Models
-
-- **arXiv id:** 2305.04091v3
-- **Title:** Plan-and-Solve Prompting: Improving Zero-Shot Chain-of-Thought Reasoning by Large Language Models
-- **Authors:** Lei Wang, Wanyu Xu, Yihuai Lan,  et al.
-- **Published Date:** 2023-05-06
-- **URL:** http://arxiv.org/abs/2305.04091v3
-- **LangChain:**
-
-   - **Cookbook:** [plan_and_execute_agent](https://github.com/langchain-ai/langchain/blob/master/cookbook/plan_and_execute_agent.ipynb)
-
-**Abstract:** Large language models (LLMs) have recently been shown to deliver impressive
-performance in various NLP tasks. To tackle multi-step reasoning tasks,
-few-shot chain-of-thought (CoT) prompting includes a few manually crafted
-step-by-step reasoning demonstrations which enable LLMs to explicitly generate
-reasoning steps and improve their reasoning task accuracy. To eliminate the
-manual effort, Zero-shot-CoT concatenates the target problem statement with
-"Let's think step by step" as an input prompt to LLMs. Despite the success of
-Zero-shot-CoT, it still suffers from three pitfalls: calculation errors,
-missing-step errors, and semantic misunderstanding errors. To address the
-missing-step errors, we propose Plan-and-Solve (PS) Prompting. It consists of
-two components: first, devising a plan to divide the entire task into smaller
-subtasks, and then carrying out the subtasks according to the plan. To address
-the calculation errors and improve the quality of generated reasoning steps, we
-extend PS prompting with more detailed instructions and derive PS+ prompting.
-We evaluate our proposed prompting strategy on ten datasets across three
-reasoning problems. The experimental results over GPT-3 show that our proposed
-zero-shot prompting consistently outperforms Zero-shot-CoT across all datasets
-by a large margin, is comparable to or exceeds Zero-shot-Program-of-Thought
-Prompting, and has comparable performance with 8-shot CoT prompting on the math
-reasoning problem. The code can be found at
-https://github.com/AGI-Edgerunners/Plan-and-Solve-Prompting.
-                
-## Visual Instruction Tuning
-
-- **arXiv id:** 2304.08485v2
-- **Title:** Visual Instruction Tuning
-- **Authors:** Haotian Liu, Chunyuan Li, Qingyang Wu,  et al.
-- **Published Date:** 2023-04-17
-- **URL:** http://arxiv.org/abs/2304.08485v2
-- **LangChain:**
-
-   - **Cookbook:** [Semi_structured_and_multi_modal_RAG](https://github.com/langchain-ai/langchain/blob/master/cookbook/Semi_structured_and_multi_modal_RAG.ipynb), [Semi_structured_multi_modal_RAG_LLaMA2](https://github.com/langchain-ai/langchain/blob/master/cookbook/Semi_structured_multi_modal_RAG_LLaMA2.ipynb)
-
-**Abstract:** Instruction tuning large language models (LLMs) using machine-generated
-instruction-following data has improved zero-shot capabilities on new tasks,
-but the idea is less explored in the multimodal field. In this paper, we
-present the first attempt to use language-only GPT-4 to generate multimodal
-language-image instruction-following data. By instruction tuning on such
-generated data, we introduce LLaVA: Large Language and Vision Assistant, an
-end-to-end trained large multimodal model that connects a vision encoder and
-LLM for general-purpose visual and language understanding.Our early experiments
-show that LLaVA demonstrates impressive multimodel chat abilities, sometimes
-exhibiting the behaviors of multimodal GPT-4 on unseen images/instructions, and
-yields a 85.1% relative score compared with GPT-4 on a synthetic multimodal
-instruction-following dataset. When fine-tuned on Science QA, the synergy of
-LLaVA and GPT-4 achieves a new state-of-the-art accuracy of 92.53%. We make
-GPT-4 generated visual instruction tuning data, our model and code base
-publicly available.
-                
-## Generative Agents: Interactive Simulacra of Human Behavior
-
-- **arXiv id:** 2304.03442v2
-- **Title:** Generative Agents: Interactive Simulacra of Human Behavior
-- **Authors:** Joon Sung Park, Joseph C. O'Brien, Carrie J. Cai,  et al.
-- **Published Date:** 2023-04-07
-- **URL:** http://arxiv.org/abs/2304.03442v2
-- **LangChain:**
-
-   - **Cookbook:** [multiagent_bidding](https://github.com/langchain-ai/langchain/blob/master/cookbook/multiagent_bidding.ipynb), [generative_agents_interactive_simulacra_of_human_behavior](https://github.com/langchain-ai/langchain/blob/master/cookbook/generative_agents_interactive_simulacra_of_human_behavior.ipynb)
-
-**Abstract:** Believable proxies of human behavior can empower interactive applications
-ranging from immersive environments to rehearsal spaces for interpersonal
-communication to prototyping tools. In this paper, we introduce generative
-agents--computational software agents that simulate believable human behavior.
-Generative agents wake up, cook breakfast, and head to work; artists paint,
-while authors write; they form opinions, notice each other, and initiate
-conversations; they remember and reflect on days past as they plan the next
-day. To enable generative agents, we describe an architecture that extends a
-large language model to store a complete record of the agent's experiences
-using natural language, synthesize those memories over time into higher-level
-reflections, and retrieve them dynamically to plan behavior. We instantiate
-generative agents to populate an interactive sandbox environment inspired by
-The Sims, where end users can interact with a small town of twenty five agents
-using natural language. In an evaluation, these generative agents produce
-believable individual and emergent social behaviors: for example, starting with
-only a single user-specified notion that one agent wants to throw a Valentine's
-Day party, the agents autonomously spread invitations to the party over the
-next two days, make new acquaintances, ask each other out on dates to the
-party, and coordinate to show up for the party together at the right time. We
-demonstrate through ablation that the components of our agent
-architecture--observation, planning, and reflection--each contribute critically
-to the believability of agent behavior. By fusing large language models with
-computational, interactive agents, this work introduces architectural and
-interaction patterns for enabling believable simulations of human behavior.
-                
-## CAMEL: Communicative Agents for "Mind" Exploration of Large Language Model Society
-
-- **arXiv id:** 2303.17760v2
-- **Title:** CAMEL: Communicative Agents for "Mind" Exploration of Large Language Model Society
-- **Authors:** Guohao Li, Hasan Abed Al Kader Hammoud, Hani Itani,  et al.
-- **Published Date:** 2023-03-31
-- **URL:** http://arxiv.org/abs/2303.17760v2
-- **LangChain:**
-
-   - **Cookbook:** [camel_role_playing](https://github.com/langchain-ai/langchain/blob/master/cookbook/camel_role_playing.ipynb)
-
-**Abstract:** The rapid advancement of chat-based language models has led to remarkable
-progress in complex task-solving. However, their success heavily relies on
-human input to guide the conversation, which can be challenging and
-time-consuming. This paper explores the potential of building scalable
-techniques to facilitate autonomous cooperation among communicative agents, and
-provides insight into their "cognitive" processes. To address the challenges of
-achieving autonomous cooperation, we propose a novel communicative agent
-framework named role-playing. Our approach involves using inception prompting
-to guide chat agents toward task completion while maintaining consistency with
-human intentions. We showcase how role-playing can be used to generate
-conversational data for studying the behaviors and capabilities of a society of
-agents, providing a valuable resource for investigating conversational language
-models. In particular, we conduct comprehensive studies on
-instruction-following cooperation in multi-agent settings. Our contributions
-include introducing a novel communicative agent framework, offering a scalable
-approach for studying the cooperative behaviors and capabilities of multi-agent
-systems, and open-sourcing our library to support research on communicative
-agents and beyond: https://github.com/camel-ai/camel.
-                
-## HuggingGPT: Solving AI Tasks with ChatGPT and its Friends in Hugging Face
-
-- **arXiv id:** 2303.17580v4
-- **Title:** HuggingGPT: Solving AI Tasks with ChatGPT and its Friends in Hugging Face
-- **Authors:** Yongliang Shen, Kaitao Song, Xu Tan,  et al.
-- **Published Date:** 2023-03-30
-- **URL:** http://arxiv.org/abs/2303.17580v4
-- **LangChain:**
-
-   - **API Reference:** [langchain_experimental.autonomous_agents](https://api.python.langchain.com/en/latest/experimental_api_reference.html#module-langchain_experimental.autonomous_agents)
-   - **Cookbook:** [hugginggpt](https://github.com/langchain-ai/langchain/blob/master/cookbook/hugginggpt.ipynb)
-
-**Abstract:** Solving complicated AI tasks with different domains and modalities is a key
-step toward artificial general intelligence. While there are numerous AI models
-available for various domains and modalities, they cannot handle complicated AI
-tasks autonomously. Considering large language models (LLMs) have exhibited
-exceptional abilities in language understanding, generation, interaction, and
-reasoning, we advocate that LLMs could act as a controller to manage existing
-AI models to solve complicated AI tasks, with language serving as a generic
-interface to empower this. Based on this philosophy, we present HuggingGPT, an
-LLM-powered agent that leverages LLMs (e.g., ChatGPT) to connect various AI
-models in machine learning communities (e.g., Hugging Face) to solve AI tasks.
-Specifically, we use ChatGPT to conduct task planning when receiving a user
-request, select models according to their function descriptions available in
-Hugging Face, execute each subtask with the selected AI model, and summarize
-the response according to the execution results. By leveraging the strong
-language capability of ChatGPT and abundant AI models in Hugging Face,
-HuggingGPT can tackle a wide range of sophisticated AI tasks spanning different
-modalities and domains and achieve impressive results in language, vision,
-speech, and other challenging tasks, which paves a new way towards the
-realization of artificial general intelligence.
-                
-## GPT-4 Technical Report
-
-- **arXiv id:** 2303.08774v6
-- **Title:** GPT-4 Technical Report
-- **Authors:** OpenAI, Josh Achiam, Steven Adler,  et al.
-- **Published Date:** 2023-03-15
-- **URL:** http://arxiv.org/abs/2303.08774v6
-- **LangChain:**
-
-   - **Documentation:** [docs/integrations/vectorstores/mongodb_atlas](https://python.langchain.com/docs/integrations/vectorstores/mongodb_atlas)
-
-**Abstract:** We report the development of GPT-4, a large-scale, multimodal model which can
-accept image and text inputs and produce text outputs. While less capable than
-humans in many real-world scenarios, GPT-4 exhibits human-level performance on
-various professional and academic benchmarks, including passing a simulated bar
-exam with a score around the top 10% of test takers. GPT-4 is a
-Transformer-based model pre-trained to predict the next token in a document.
-The post-training alignment process results in improved performance on measures
-of factuality and adherence to desired behavior. A core component of this
-project was developing infrastructure and optimization methods that behave
-predictably across a wide range of scales. This allowed us to accurately
-predict some aspects of GPT-4's performance based on models trained with no
-more than 1/1,000th the compute of GPT-4.
-                
-## A Watermark for Large Language Models
-
-- **arXiv id:** 2301.10226v4
-- **Title:** A Watermark for Large Language Models
-- **Authors:** John Kirchenbauer, Jonas Geiping, Yuxin Wen,  et al.
-- **Published Date:** 2023-01-24
-- **URL:** http://arxiv.org/abs/2301.10226v4
-- **LangChain:**
-
-   - **API Reference:** [langchain_community...HuggingFaceEndpoint](https://api.python.langchain.com/en/latest/llms/langchain_community.llms.huggingface_endpoint.HuggingFaceEndpoint.html#langchain_community.llms.huggingface_endpoint.HuggingFaceEndpoint), [langchain_huggingface...HuggingFaceEndpoint](https://api.python.langchain.com/en/latest/llms/langchain_huggingface.llms.huggingface_endpoint.HuggingFaceEndpoint.html#langchain_huggingface.llms.huggingface_endpoint.HuggingFaceEndpoint), [langchain_community...OCIModelDeploymentTGI](https://api.python.langchain.com/en/latest/llms/langchain_community.llms.oci_data_science_model_deployment_endpoint.OCIModelDeploymentTGI.html#langchain_community.llms.oci_data_science_model_deployment_endpoint.OCIModelDeploymentTGI), [langchain_community...HuggingFaceTextGenInference](https://api.python.langchain.com/en/latest/llms/langchain_community.llms.huggingface_text_gen_inference.HuggingFaceTextGenInference.html#langchain_community.llms.huggingface_text_gen_inference.HuggingFaceTextGenInference)
-
-**Abstract:** Potential harms of large language models can be mitigated by watermarking
-model output, i.e., embedding signals into generated text that are invisible to
-humans but algorithmically detectable from a short span of tokens. We propose a
-watermarking framework for proprietary language models. The watermark can be
-embedded with negligible impact on text quality, and can be detected using an
-efficient open-source algorithm without access to the language model API or
-parameters. The watermark works by selecting a randomized set of "green" tokens
-before a word is generated, and then softly promoting use of green tokens
-during sampling. We propose a statistical test for detecting the watermark with
-interpretable p-values, and derive an information-theoretic framework for
-analyzing the sensitivity of the watermark. We test the watermark using a
-multi-billion parameter model from the Open Pretrained Transformer (OPT)
-family, and discuss robustness and security.
-                
-## Precise Zero-Shot Dense Retrieval without Relevance Labels
-
-- **arXiv id:** 2212.10496v1
-- **Title:** Precise Zero-Shot Dense Retrieval without Relevance Labels
-- **Authors:** Luyu Gao, Xueguang Ma, Jimmy Lin,  et al.
-- **Published Date:** 2022-12-20
-- **URL:** http://arxiv.org/abs/2212.10496v1
-- **LangChain:**
-
-   - **API Reference:** [langchain...HypotheticalDocumentEmbedder](https://api.python.langchain.com/en/latest/chains/langchain.chains.hyde.base.HypotheticalDocumentEmbedder.html#langchain.chains.hyde.base.HypotheticalDocumentEmbedder)
-   - **Template:** [hyde](https://python.langchain.com/docs/templates/hyde)
-   - **Cookbook:** [hypothetical_document_embeddings](https://github.com/langchain-ai/langchain/blob/master/cookbook/hypothetical_document_embeddings.ipynb)
-
-**Abstract:** While dense retrieval has been shown effective and efficient across tasks and
-languages, it remains difficult to create effective fully zero-shot dense
-retrieval systems when no relevance label is available. In this paper, we
-recognize the difficulty of zero-shot learning and encoding relevance. Instead,
-we propose to pivot through Hypothetical Document Embeddings~(HyDE). Given a
-query, HyDE first zero-shot instructs an instruction-following language model
-(e.g. InstructGPT) to generate a hypothetical document. The document captures
-relevance patterns but is unreal and may contain false details. Then, an
-unsupervised contrastively learned encoder~(e.g. Contriever) encodes the
-document into an embedding vector. This vector identifies a neighborhood in the
-corpus embedding space, where similar real documents are retrieved based on
-vector similarity. This second step ground the generated document to the actual
-corpus, with the encoder's dense bottleneck filtering out the incorrect
-details. Our experiments show that HyDE significantly outperforms the
-state-of-the-art unsupervised dense retriever Contriever and shows strong
-performance comparable to fine-tuned retrievers, across various tasks (e.g. web
-search, QA, fact verification) and languages~(e.g. sw, ko, ja).
-                
-## Robust and Explainable Identification of Logical Fallacies in Natural Language Arguments
-
-- **arXiv id:** 2212.07425v3
-- **Title:** Robust and Explainable Identification of Logical Fallacies in Natural Language Arguments
-- **Authors:** Zhivar Sourati, Vishnu Priya Prasanna Venkatesh, Darshan Deshpande,  et al.
-- **Published Date:** 2022-12-12
-- **URL:** http://arxiv.org/abs/2212.07425v3
-- **LangChain:**
-
-   - **API Reference:** [langchain_experimental.fallacy_removal](https://api.python.langchain.com/en/latest/experimental_api_reference.html#module-langchain_experimental.fallacy_removal)
-
-**Abstract:** The spread of misinformation, propaganda, and flawed argumentation has been
-amplified in the Internet era. Given the volume of data and the subtlety of
-identifying violations of argumentation norms, supporting information analytics
-tasks, like content moderation, with trustworthy methods that can identify
-logical fallacies is essential. In this paper, we formalize prior theoretical
-work on logical fallacies into a comprehensive three-stage evaluation framework
-of detection, coarse-grained, and fine-grained classification. We adapt
-existing evaluation datasets for each stage of the evaluation. We employ three
-families of robust and explainable methods based on prototype reasoning,
-instance-based reasoning, and knowledge injection. The methods combine language
-models with background knowledge and explainable mechanisms. Moreover, we
-address data sparsity with strategies for data augmentation and curriculum
-learning. Our three-stage framework natively consolidates prior datasets and
-methods from existing tasks, like propaganda detection, serving as an
-overarching evaluation testbed. We extensively evaluate these methods on our
-datasets, focusing on their robustness and explainability. Our results provide
-insight into the strengths and weaknesses of the methods on different
-components and fallacy classes, indicating that fallacy identification is a
-challenging task that may require specialized forms of reasoning to capture
-various classes. We share our open-source code and data on GitHub to support
-further work on logical fallacy identification.
-                
-## Complementary Explanations for Effective In-Context Learning
-
-- **arXiv id:** 2211.13892v2
-- **Title:** Complementary Explanations for Effective In-Context Learning
-- **Authors:** Xi Ye, Srinivasan Iyer, Asli Celikyilmaz,  et al.
-- **Published Date:** 2022-11-25
-- **URL:** http://arxiv.org/abs/2211.13892v2
-- **LangChain:**
-
-   - **API Reference:** [langchain_core...MaxMarginalRelevanceExampleSelector](https://api.python.langchain.com/en/latest/example_selectors/langchain_core.example_selectors.semantic_similarity.MaxMarginalRelevanceExampleSelector.html#langchain_core.example_selectors.semantic_similarity.MaxMarginalRelevanceExampleSelector)
-
-**Abstract:** Large language models (LLMs) have exhibited remarkable capabilities in
-learning from explanations in prompts, but there has been limited understanding
-of exactly how these explanations function or why they are effective. This work
-aims to better understand the mechanisms by which explanations are used for
-in-context learning. We first study the impact of two different factors on the
-performance of prompts with explanations: the computation trace (the way the
-solution is decomposed) and the natural language used to express the prompt. By
-perturbing explanations on three controlled tasks, we show that both factors
-contribute to the effectiveness of explanations. We further study how to form
-maximally effective sets of explanations for solving a given test query. We
-find that LLMs can benefit from the complementarity of the explanation set:
-diverse reasoning skills shown by different exemplars can lead to better
-performance. Therefore, we propose a maximal marginal relevance-based exemplar
-selection approach for constructing exemplar sets that are both relevant as
-well as complementary, which successfully improves the in-context learning
-performance across three real-world tasks on multiple LLMs.
-                
-## PAL: Program-aided Language Models
-
-- **arXiv id:** 2211.10435v2
-- **Title:** PAL: Program-aided Language Models
-- **Authors:** Luyu Gao, Aman Madaan, Shuyan Zhou,  et al.
-- **Published Date:** 2022-11-18
-- **URL:** http://arxiv.org/abs/2211.10435v2
-- **LangChain:**
-
-   - **API Reference:** [langchain_experimental...PALChain](https://api.python.langchain.com/en/latest/pal_chain/langchain_experimental.pal_chain.base.PALChain.html#langchain_experimental.pal_chain.base.PALChain), [langchain_experimental.pal_chain](https://api.python.langchain.com/en/latest/experimental_api_reference.html#module-langchain_experimental.pal_chain)
-   - **Cookbook:** [program_aided_language_model](https://github.com/langchain-ai/langchain/blob/master/cookbook/program_aided_language_model.ipynb)
-
-**Abstract:** Large language models (LLMs) have recently demonstrated an impressive ability
-to perform arithmetic and symbolic reasoning tasks, when provided with a few
-examples at test time ("few-shot prompting"). Much of this success can be
-attributed to prompting methods such as "chain-of-thought'', which employ LLMs
-for both understanding the problem description by decomposing it into steps, as
-well as solving each step of the problem. While LLMs seem to be adept at this
-sort of step-by-step decomposition, LLMs often make logical and arithmetic
-mistakes in the solution part, even when the problem is decomposed correctly.
-In this paper, we present Program-Aided Language models (PAL): a novel approach
-that uses the LLM to read natural language problems and generate programs as
-the intermediate reasoning steps, but offloads the solution step to a runtime
-such as a Python interpreter. With PAL, decomposing the natural language
-problem into runnable steps remains the only learning task for the LLM, while
-solving is delegated to the interpreter. We demonstrate this synergy between a
-neural LLM and a symbolic interpreter across 13 mathematical, symbolic, and
-algorithmic reasoning tasks from BIG-Bench Hard and other benchmarks. In all
-these natural language reasoning tasks, generating code using an LLM and
-reasoning using a Python interpreter leads to more accurate results than much
-larger models. For example, PAL using Codex achieves state-of-the-art few-shot
-accuracy on the GSM8K benchmark of math word problems, surpassing PaLM-540B
-which uses chain-of-thought by absolute 15% top-1. Our code and data are
-publicly available at http://reasonwithpal.com/ .
-                
-## ReAct: Synergizing Reasoning and Acting in Language Models
-
-- **arXiv id:** 2210.03629v3
-- **Title:** ReAct: Synergizing Reasoning and Acting in Language Models
-- **Authors:** Shunyu Yao, Jeffrey Zhao, Dian Yu,  et al.
-- **Published Date:** 2022-10-06
-- **URL:** http://arxiv.org/abs/2210.03629v3
-- **LangChain:**
-
-   - **Documentation:** [docs/integrations/providers/cohere](https://python.langchain.com/docs/integrations/providers/cohere), [docs/integrations/chat/huggingface](https://python.langchain.com/docs/integrations/chat/huggingface), [docs/integrations/tools/ionic_shopping](https://python.langchain.com/docs/integrations/tools/ionic_shopping)
-   - **API Reference:** [langchain...create_react_agent](https://api.python.langchain.com/en/latest/agents/langchain.agents.react.agent.create_react_agent.html#langchain.agents.react.agent.create_react_agent), [langchain...TrajectoryEvalChain](https://api.python.langchain.com/en/latest/evaluation/langchain.evaluation.agents.trajectory_eval_chain.TrajectoryEvalChain.html#langchain.evaluation.agents.trajectory_eval_chain.TrajectoryEvalChain)
-
-**Abstract:** While large language models (LLMs) have demonstrated impressive capabilities
-across tasks in language understanding and interactive decision making, their
-abilities for reasoning (e.g. chain-of-thought prompting) and acting (e.g.
-action plan generation) have primarily been studied as separate topics. In this
-paper, we explore the use of LLMs to generate both reasoning traces and
-task-specific actions in an interleaved manner, allowing for greater synergy
-between the two: reasoning traces help the model induce, track, and update
-action plans as well as handle exceptions, while actions allow it to interface
-with external sources, such as knowledge bases or environments, to gather
-additional information. We apply our approach, named ReAct, to a diverse set of
-language and decision making tasks and demonstrate its effectiveness over
-state-of-the-art baselines, as well as improved human interpretability and
-trustworthiness over methods without reasoning or acting components.
-Concretely, on question answering (HotpotQA) and fact verification (Fever),
-ReAct overcomes issues of hallucination and error propagation prevalent in
-chain-of-thought reasoning by interacting with a simple Wikipedia API, and
-generates human-like task-solving trajectories that are more interpretable than
-baselines without reasoning traces. On two interactive decision making
-benchmarks (ALFWorld and WebShop), ReAct outperforms imitation and
-reinforcement learning methods by an absolute success rate of 34% and 10%
-respectively, while being prompted with only one or two in-context examples.
-Project site with code: https://react-lm.github.io
-                
-## Deep Lake: a Lakehouse for Deep Learning
-
-- **arXiv id:** 2209.10785v2
-- **Title:** Deep Lake: a Lakehouse for Deep Learning
-- **Authors:** Sasun Hambardzumyan, Abhinav Tuli, Levon Ghukasyan,  et al.
-- **Published Date:** 2022-09-22
-- **URL:** http://arxiv.org/abs/2209.10785v2
-- **LangChain:**
-
-   - **Documentation:** [docs/integrations/providers/activeloop_deeplake](https://python.langchain.com/docs/integrations/providers/activeloop_deeplake)
-
-**Abstract:** Traditional data lakes provide critical data infrastructure for analytical
-workloads by enabling time travel, running SQL queries, ingesting data with
-ACID transactions, and visualizing petabyte-scale datasets on cloud storage.
-They allow organizations to break down data silos, unlock data-driven
-decision-making, improve operational efficiency, and reduce costs. However, as
-deep learning usage increases, traditional data lakes are not well-designed for
-applications such as natural language processing (NLP), audio processing,
-computer vision, and applications involving non-tabular datasets. This paper
-presents Deep Lake, an open-source lakehouse for deep learning applications
-developed at Activeloop. Deep Lake maintains the benefits of a vanilla data
-lake with one key difference: it stores complex data, such as images, videos,
-annotations, as well as tabular data, in the form of tensors and rapidly
-streams the data over the network to (a) Tensor Query Language, (b) in-browser
-visualization engine, or (c) deep learning frameworks without sacrificing GPU
-utilization. Datasets stored in Deep Lake can be accessed from PyTorch,
-TensorFlow, JAX, and integrate with numerous MLOps tools.
-                
-## Bitext Mining Using Distilled Sentence Representations for Low-Resource Languages
-
-- **arXiv id:** 2205.12654v1
-- **Title:** Bitext Mining Using Distilled Sentence Representations for Low-Resource Languages
-- **Authors:** Kevin Heffernan, Onur Çelebi, Holger Schwenk
-- **Published Date:** 2022-05-25
-- **URL:** http://arxiv.org/abs/2205.12654v1
-- **LangChain:**
-
-   - **API Reference:** [langchain_community...LaserEmbeddings](https://api.python.langchain.com/en/latest/embeddings/langchain_community.embeddings.laser.LaserEmbeddings.html#langchain_community.embeddings.laser.LaserEmbeddings)
-
-**Abstract:** Scaling multilingual representation learning beyond the hundred most frequent
-languages is challenging, in particular to cover the long tail of low-resource
-languages. A promising approach has been to train one-for-all multilingual
-models capable of cross-lingual transfer, but these models often suffer from
-insufficient capacity and interference between unrelated languages. Instead, we
-move away from this approach and focus on training multiple language (family)
-specific representations, but most prominently enable all languages to still be
-encoded in the same representational space. To achieve this, we focus on
-teacher-student training, allowing all encoders to be mutually compatible for
-bitext mining, and enabling fast learning of new languages. We introduce a new
-teacher-student training scheme which combines supervised and self-supervised
-training, allowing encoders to take advantage of monolingual training data,
-which is valuable in the low-resource setting.
-  Our approach significantly outperforms the original LASER encoder. We study
-very low-resource languages and handle 50 African languages, many of which are
-not covered by any other model. For these languages, we train sentence
-encoders, mine bitexts, and validate the bitexts by training NMT systems.
-                
-## Evaluating the Text-to-SQL Capabilities of Large Language Models
-
-- **arXiv id:** 2204.00498v1
-- **Title:** Evaluating the Text-to-SQL Capabilities of Large Language Models
-- **Authors:** Nitarshan Rajkumar, Raymond Li, Dzmitry Bahdanau
-- **Published Date:** 2022-03-15
-- **URL:** http://arxiv.org/abs/2204.00498v1
-- **LangChain:**
-
-   - **API Reference:** [langchain_community...SparkSQL](https://api.python.langchain.com/en/latest/utilities/langchain_community.utilities.spark_sql.SparkSQL.html#langchain_community.utilities.spark_sql.SparkSQL), [langchain_community...SQLDatabase](https://api.python.langchain.com/en/latest/utilities/langchain_community.utilities.sql_database.SQLDatabase.html#langchain_community.utilities.sql_database.SQLDatabase)
-
-**Abstract:** We perform an empirical evaluation of Text-to-SQL capabilities of the Codex
-language model. We find that, without any finetuning, Codex is a strong
-baseline on the Spider benchmark; we also analyze the failure modes of Codex in
-this setting. Furthermore, we demonstrate on the GeoQuery and Scholar
-benchmarks that a small number of in-domain examples provided in the prompt
-enables Codex to perform better than state-of-the-art models finetuned on such
-few-shot examples.
-                
-## Locally Typical Sampling
-
-- **arXiv id:** 2202.00666v5
-- **Title:** Locally Typical Sampling
-- **Authors:** Clara Meister, Tiago Pimentel, Gian Wiher,  et al.
-- **Published Date:** 2022-02-01
-- **URL:** http://arxiv.org/abs/2202.00666v5
-- **LangChain:**
-
-   - **API Reference:** [langchain_community...HuggingFaceEndpoint](https://api.python.langchain.com/en/latest/llms/langchain_community.llms.huggingface_endpoint.HuggingFaceEndpoint.html#langchain_community.llms.huggingface_endpoint.HuggingFaceEndpoint), [langchain_huggingface...HuggingFaceEndpoint](https://api.python.langchain.com/en/latest/llms/langchain_huggingface.llms.huggingface_endpoint.HuggingFaceEndpoint.html#langchain_huggingface.llms.huggingface_endpoint.HuggingFaceEndpoint), [langchain_community...HuggingFaceTextGenInference](https://api.python.langchain.com/en/latest/llms/langchain_community.llms.huggingface_text_gen_inference.HuggingFaceTextGenInference.html#langchain_community.llms.huggingface_text_gen_inference.HuggingFaceTextGenInference)
-
-**Abstract:** Today's probabilistic language generators fall short when it comes to
-producing coherent and fluent text despite the fact that the underlying models
-perform well under standard metrics, e.g., perplexity. This discrepancy has
-puzzled the language generation community for the last few years. In this work,
-we posit that the abstraction of natural language generation as a discrete
-stochastic process--which allows for an information-theoretic analysis--can
-provide new insights into the behavior of probabilistic language generators,
-e.g., why high-probability texts can be dull or repetitive. Humans use language
-as a means of communicating information, aiming to do so in a simultaneously
-efficient and error-minimizing manner; in fact, psycholinguistics research
-suggests humans choose each word in a string with this subconscious goal in
-mind. We formally define the set of strings that meet this criterion: those for
-which each word has an information content close to the expected information
-content, i.e., the conditional entropy of our model. We then propose a simple
-and efficient procedure for enforcing this criterion when generating from
-probabilistic models, which we call locally typical sampling. Automatic and
-human evaluations show that, in comparison to nucleus and top-k sampling,
-locally typical sampling offers competitive performance (in both abstractive
-summarization and story generation) in terms of quality while consistently
-reducing degenerate repetitions.
-                
-## Learning Transferable Visual Models From Natural Language Supervision
-
-- **arXiv id:** 2103.00020v1
-- **Title:** Learning Transferable Visual Models From Natural Language Supervision
-- **Authors:** Alec Radford, Jong Wook Kim, Chris Hallacy,  et al.
-- **Published Date:** 2021-02-26
-- **URL:** http://arxiv.org/abs/2103.00020v1
-- **LangChain:**
-
-   - **API Reference:** [langchain_experimental.open_clip](https://api.python.langchain.com/en/latest/experimental_api_reference.html#module-langchain_experimental.open_clip)
-
-**Abstract:** State-of-the-art computer vision systems are trained to predict a fixed set
-of predetermined object categories. This restricted form of supervision limits
-their generality and usability since additional labeled data is needed to
-specify any other visual concept. Learning directly from raw text about images
-is a promising alternative which leverages a much broader source of
-supervision. We demonstrate that the simple pre-training task of predicting
-which caption goes with which image is an efficient and scalable way to learn
-SOTA image representations from scratch on a dataset of 400 million (image,
-text) pairs collected from the internet. After pre-training, natural language
-is used to reference learned visual concepts (or describe new ones) enabling
-zero-shot transfer of the model to downstream tasks. We study the performance
-of this approach by benchmarking on over 30 different existing computer vision
-datasets, spanning tasks such as OCR, action recognition in videos,
-geo-localization, and many types of fine-grained object classification. The
-model transfers non-trivially to most tasks and is often competitive with a
-fully supervised baseline without the need for any dataset specific training.
-For instance, we match the accuracy of the original ResNet-50 on ImageNet
-zero-shot without needing to use any of the 1.28 million training examples it
-was trained on. We release our code and pre-trained model weights at
-https://github.com/OpenAI/CLIP.
-                
-## CTRL: A Conditional Transformer Language Model for Controllable Generation
-
-- **arXiv id:** 1909.05858v2
-- **Title:** CTRL: A Conditional Transformer Language Model for Controllable Generation
-- **Authors:** Nitish Shirish Keskar, Bryan McCann, Lav R. Varshney,  et al.
-- **Published Date:** 2019-09-11
-- **URL:** http://arxiv.org/abs/1909.05858v2
-- **LangChain:**
-
-   - **API Reference:** [langchain_community...HuggingFaceEndpoint](https://api.python.langchain.com/en/latest/llms/langchain_community.llms.huggingface_endpoint.HuggingFaceEndpoint.html#langchain_community.llms.huggingface_endpoint.HuggingFaceEndpoint), [langchain_huggingface...HuggingFaceEndpoint](https://api.python.langchain.com/en/latest/llms/langchain_huggingface.llms.huggingface_endpoint.HuggingFaceEndpoint.html#langchain_huggingface.llms.huggingface_endpoint.HuggingFaceEndpoint), [langchain_community...HuggingFaceTextGenInference](https://api.python.langchain.com/en/latest/llms/langchain_community.llms.huggingface_text_gen_inference.HuggingFaceTextGenInference.html#langchain_community.llms.huggingface_text_gen_inference.HuggingFaceTextGenInference)
-
-**Abstract:** Large-scale language models show promising text generation capabilities, but
-users cannot easily control particular aspects of the generated text. We
-release CTRL, a 1.63 billion-parameter conditional transformer language model,
-trained to condition on control codes that govern style, content, and
-task-specific behavior. Control codes were derived from structure that
-naturally co-occurs with raw text, preserving the advantages of unsupervised
-learning while providing more explicit control over text generation. These
-codes also allow CTRL to predict which parts of the training data are most
-likely given a sequence. This provides a potential method for analyzing large
-amounts of data via model-based source attribution. We have released multiple
-full-sized, pretrained versions of CTRL at https://github.com/salesforce/ctrl.
-                
-## Sentence-BERT: Sentence Embeddings using Siamese BERT-Networks
-
-- **arXiv id:** 1908.10084v1
-- **Title:** Sentence-BERT: Sentence Embeddings using Siamese BERT-Networks
-- **Authors:** Nils Reimers, Iryna Gurevych
-- **Published Date:** 2019-08-27
-- **URL:** http://arxiv.org/abs/1908.10084v1
-- **LangChain:**
-
-   - **Documentation:** [docs/integrations/text_embedding/sentence_transformers](https://python.langchain.com/docs/integrations/text_embedding/sentence_transformers)
-
-**Abstract:** BERT (Devlin et al., 2018) and RoBERTa (Liu et al., 2019) has set a new
-state-of-the-art performance on sentence-pair regression tasks like semantic
-textual similarity (STS). However, it requires that both sentences are fed into
-the network, which causes a massive computational overhead: Finding the most
-similar pair in a collection of 10,000 sentences requires about 50 million
-inference computations (~65 hours) with BERT. The construction of BERT makes it
-unsuitable for semantic similarity search as well as for unsupervised tasks
-like clustering.
-  In this publication, we present Sentence-BERT (SBERT), a modification of the
-pretrained BERT network that use siamese and triplet network structures to
-derive semantically meaningful sentence embeddings that can be compared using
-cosine-similarity. This reduces the effort for finding the most similar pair
-from 65 hours with BERT / RoBERTa to about 5 seconds with SBERT, while
-maintaining the accuracy from BERT.
-  We evaluate SBERT and SRoBERTa on common STS tasks and transfer learning
-tasks, where it outperforms other state-of-the-art sentence embeddings methods.
-                

docs/docs/additional_resources/tutorials.mdx

@@ -1,17 +1,25 @@
-# 3rd Party Tutorials
+# Tutorials
+
+## Books and Handbooks
+
+- [Generative AI with LangChain](https://www.amazon.com/Generative-AI-LangChain-language-ChatGPT/dp/1835083463/ref=sr_1_1?crid=1GMOMH0G7GLR&keywords=generative+ai+with+langchain&qid=1703247181&sprefix=%2Caps%2C298&sr=8-1) by [Ben Auffrath](https://www.amazon.com/stores/Ben-Auffarth/author/B08JQKSZ7D?ref=ap_rdr&store_ref=ap_rdr&isDramIntegrated=true&shoppingPortalEnabled=true), ©️ 2023 Packt Publishing
+- [LangChain AI Handbook](https://www.pinecone.io/learn/langchain/) By **James Briggs** and **Francisco Ingham**
+- [LangChain Cheatsheet](https://pub.towardsai.net/langchain-cheatsheet-all-secrets-on-a-single-page-8be26b721cde) by **Ivan Reznikov**
+
 
 ##  Tutorials
 
 ### [LangChain v 0.1 by LangChain.ai](https://www.youtube.com/playlist?list=PLfaIDFEXuae0gBSJ9T0w7cu7iJZbH3T31)
 ### [Build with Langchain - Advanced by LangChain.ai](https://www.youtube.com/playlist?list=PLfaIDFEXuae06tclDATrMYY0idsTdLg9v)
 ### [LangGraph by LangChain.ai](https://www.youtube.com/playlist?list=PLfaIDFEXuae16n2TWUkKq5PgJ0w6Pkwtg)
+
 ### [by Greg Kamradt](https://www.youtube.com/playlist?list=PLqZXAkvF1bPNQER9mLmDbntNfSpzdDIU5)
 ### [by Sam Witteveen](https://www.youtube.com/playlist?list=PL8motc6AQftk1Bs42EW45kwYbyJ4jOdiZ)
 ### [by James Briggs](https://www.youtube.com/playlist?list=PLIUOU7oqGTLieV9uTIFMm6_4PXg-hlN6F)
 ### [by Prompt Engineering](https://www.youtube.com/playlist?list=PLVEEucA9MYhOu89CX8H3MBZqayTbcCTMr)
 ### [by Mayo Oshin](https://www.youtube.com/@chatwithdata/search?query=langchain)
 ### [by 1 little Coder](https://www.youtube.com/playlist?list=PLpdmBGJ6ELUK-v0MK-t4wZmVEbxM5xk6L)
-### [by BobLin (Chinese language)](https://www.youtube.com/playlist?list=PLbd7ntv6PxC3QMFQvtWfk55p-Op_syO1C)
+
 
 ## Courses
 
@@ -25,7 +33,6 @@
 ### Online courses
 
 - [Udemy](https://www.udemy.com/courses/search/?q=langchain)
-- [DataCamp](https://www.datacamp.com/courses/developing-llm-applications-with-langchain)
 - [Pluralsight](https://www.pluralsight.com/search?q=langchain)
 - [Coursera](https://www.coursera.org/search?query=langchain)
 - [Maven](https://maven.com/courses?query=langchain)
@@ -41,11 +48,8 @@
 - [by Rabbitmetrics](https://youtu.be/aywZrzNaKjs)
 - [by Ivan Reznikov](https://medium.com/@ivanreznikov/langchain-101-course-updated-668f7b41d6cb)
 
-## Books and Handbooks
-
-- [Generative AI with LangChain](https://www.amazon.com/Generative-AI-LangChain-language-ChatGPT/dp/1835083463/ref=sr_1_1?crid=1GMOMH0G7GLR&keywords=generative+ai+with+langchain&qid=1703247181&sprefix=%2Caps%2C298&sr=8-1) by [Ben Auffrath](https://www.amazon.com/stores/Ben-Auffarth/author/B08JQKSZ7D?ref=ap_rdr&store_ref=ap_rdr&isDramIntegrated=true&shoppingPortalEnabled=true), ©️ 2023 Packt Publishing
-- [LangChain AI Handbook](https://www.pinecone.io/learn/langchain/) By **James Briggs** and **Francisco Ingham**
-- [LangChain Cheatsheet](https://pub.towardsai.net/langchain-cheatsheet-all-secrets-on-a-single-page-8be26b721cde) by **Ivan Reznikov**
-- [Dive into Langchain (Chinese language)](https://langchain.boblin.app/)
+## [Documentation: Use cases](/docs/use_cases)
 
 ---------------------
+
+

docs/docs/additional_resources/youtube.mdx

@@ -1,63 +1,137 @@
 # YouTube videos
 
-[Updated 2024-05-16]
+⛓ icon marks a new addition [last update 2023-09-21]
 
 ### [Official LangChain YouTube channel](https://www.youtube.com/@LangChain)
 
-### [Tutorials on YouTube](/docs/additional_resources/tutorials/#tutorials)
+### Introduction to LangChain with Harrison Chase, creator of LangChain
+- [Building the Future with LLMs, `LangChain`, & `Pinecone`](https://youtu.be/nMniwlGyX-c) by [Pinecone](https://www.youtube.com/@pinecone-io)
+- [LangChain and Weaviate with Harrison Chase and Bob van Luijt - Weaviate Podcast #36](https://youtu.be/lhby7Ql7hbk) by [Weaviate • Vector Database](https://www.youtube.com/@Weaviate)
+- [LangChain Demo + Q&A with Harrison Chase](https://youtu.be/zaYTXQFR0_s?t=788) by [Full Stack Deep Learning](https://www.youtube.com/@The_Full_Stack)
+- [LangChain Agents: Build Personal Assistants For Your Data (Q&A with Harrison Chase and Mayo Oshin)](https://youtu.be/gVkF8cwfBLI) by [Chat with data](https://www.youtube.com/@chatwithdata)
 
 ## Videos (sorted by views)
 
-Only videos with 40K+ views:
+- [Using `ChatGPT` with YOUR OWN Data. This is magical. (LangChain OpenAI API)](https://youtu.be/9AXP7tCI9PI) by [TechLead](https://www.youtube.com/@TechLead)
+- [First look - `ChatGPT` + `WolframAlpha` (`GPT-3.5` and Wolfram|Alpha via LangChain by James Weaver)](https://youtu.be/wYGbY811oMo) by [Dr Alan D. Thompson](https://www.youtube.com/@DrAlanDThompson) 
+- [LangChain explained - The hottest new Python framework](https://youtu.be/RoR4XJw8wIc) by [AssemblyAI](https://www.youtube.com/@AssemblyAI)
+- [Chatbot with INFINITE MEMORY using `OpenAI` & `Pinecone` - `GPT-3`, `Embeddings`, `ADA`, `Vector DB`, `Semantic`](https://youtu.be/2xNzB7xq8nk) by [David Shapiro ~ AI](https://www.youtube.com/@DaveShap)
+- [LangChain for LLMs is... basically just an Ansible playbook](https://youtu.be/X51N9C-OhlE) by [David Shapiro ~ AI](https://www.youtube.com/@DaveShap)
+- [Build your own LLM Apps with LangChain & `GPT-Index`](https://youtu.be/-75p09zFUJY) by [1littlecoder](https://www.youtube.com/@1littlecoder)
+- [`BabyAGI` - New System of Autonomous AI Agents with LangChain](https://youtu.be/lg3kJvf1kXo) by [1littlecoder](https://www.youtube.com/@1littlecoder)
+- [Run `BabyAGI` with Langchain Agents (with Python Code)](https://youtu.be/WosPGHPObx8) by [1littlecoder](https://www.youtube.com/@1littlecoder)
+- [How to Use Langchain With `Zapier` | Write and Send Email with GPT-3 | OpenAI API Tutorial](https://youtu.be/p9v2-xEa9A0) by [StarMorph AI](https://www.youtube.com/@starmorph)
+- [Use Your Locally Stored Files To Get Response From GPT - `OpenAI` | Langchain | Python](https://youtu.be/NC1Ni9KS-rk) by [Shweta Lodha](https://www.youtube.com/@shweta-lodha)
+- [`Langchain JS` | How to Use GPT-3, GPT-4 to Reference your own Data | `OpenAI Embeddings` Intro](https://youtu.be/veV2I-NEjaM) by [StarMorph AI](https://www.youtube.com/@starmorph)
+- [The easiest way to work with large language models | Learn LangChain in 10min](https://youtu.be/kmbS6FDQh7c) by [Sophia Yang](https://www.youtube.com/@SophiaYangDS)
+- [4 Autonomous AI Agents: “Westworld” simulation `BabyAGI`, `AutoGPT`, `Camel`, `LangChain`](https://youtu.be/yWbnH6inT_U) by [Sophia Yang](https://www.youtube.com/@SophiaYangDS)
+- [AI CAN SEARCH THE INTERNET? Langchain Agents + OpenAI ChatGPT](https://youtu.be/J-GL0htqda8) by [tylerwhatsgood](https://www.youtube.com/@tylerwhatsgood)
+- [Query Your Data with GPT-4 | Embeddings, Vector Databases | Langchain JS Knowledgebase](https://youtu.be/jRnUPUTkZmU) by [StarMorph AI](https://www.youtube.com/@starmorph)
+- [`Weaviate` + LangChain for LLM apps presented by Erika Cardenas](https://youtu.be/7AGj4Td5Lgw) by [`Weaviate` • Vector Database](https://www.youtube.com/@Weaviate)
+- [Langchain Overview — How to Use Langchain & `ChatGPT`](https://youtu.be/oYVYIq0lOtI) by [Python In Office](https://www.youtube.com/@pythoninoffice6568)
+- [Langchain Overview - How to Use Langchain & `ChatGPT`](https://youtu.be/oYVYIq0lOtI) by [Python In Office](https://www.youtube.com/@pythoninoffice6568)
+- [LangChain Tutorials](https://www.youtube.com/watch?v=FuqdVNB_8c0&list=PL9V0lbeJ69brU-ojMpU1Y7Ic58Tap0Cw6) by [Edrick](https://www.youtube.com/@edrickdch):
+  - [LangChain, Chroma DB, OpenAI Beginner Guide | ChatGPT with your PDF](https://youtu.be/FuqdVNB_8c0)
+  - [LangChain 101: The Complete Beginner's Guide](https://youtu.be/P3MAbZ2eMUI)
+- [Custom langchain Agent & Tools with memory. Turn any `Python function` into langchain tool with Gpt 3](https://youtu.be/NIG8lXk0ULg) by [echohive](https://www.youtube.com/@echohive)
+- [Building AI LLM Apps with LangChain (and more?) - LIVE STREAM](https://www.youtube.com/live/M-2Cj_2fzWI?feature=share) by [Nicholas Renotte](https://www.youtube.com/@NicholasRenotte)
+- [`ChatGPT` with any `YouTube` video using langchain and `chromadb`](https://youtu.be/TQZfB2bzVwU) by [echohive](https://www.youtube.com/@echohive)
+- [How to Talk to a `PDF` using LangChain and `ChatGPT`](https://youtu.be/v2i1YDtrIwk) by [Automata Learning Lab](https://www.youtube.com/@automatalearninglab)
+- [Langchain Document Loaders Part 1: Unstructured Files](https://youtu.be/O5C0wfsen98) by [Merk](https://www.youtube.com/@heymichaeldaigler) 
+- [LangChain - Prompt Templates (what all the best prompt engineers use)](https://youtu.be/1aRu8b0XNOQ) by [Nick Daigler](https://www.youtube.com/@nickdaigler)
+- [LangChain. Crear aplicaciones Python impulsadas por GPT](https://youtu.be/DkW_rDndts8) by [Jesús Conde](https://www.youtube.com/@0utKast)
+- [Easiest Way to Use GPT In Your Products | LangChain Basics Tutorial](https://youtu.be/fLy0VenZyGc) by [Rachel Woods](https://www.youtube.com/@therachelwoods)
+- [`BabyAGI` + `GPT-4` Langchain Agent with Internet Access](https://youtu.be/wx1z_hs5P6E) by [tylerwhatsgood](https://www.youtube.com/@tylerwhatsgood)
+- [Learning LLM Agents. How does it actually work? LangChain, AutoGPT & OpenAI](https://youtu.be/mb_YAABSplk) by [Arnoldas Kemeklis](https://www.youtube.com/@processusAI)
+- [Get Started with LangChain in `Node.js`](https://youtu.be/Wxx1KUWJFv4) by [Developers Digest](https://www.youtube.com/@DevelopersDigest)
+- [LangChain + `OpenAI` tutorial: Building a Q&A system w/ own text data](https://youtu.be/DYOU_Z0hAwo) by [Samuel Chan](https://www.youtube.com/@SamuelChan)
+- [Langchain + `Zapier` Agent](https://youtu.be/yribLAb-pxA) by [Merk](https://www.youtube.com/@heymichaeldaigler)
+- [Connecting the Internet with `ChatGPT` (LLMs) using Langchain And Answers Your Questions](https://youtu.be/9Y0TBC63yZg) by [Kamalraj M M](https://www.youtube.com/@insightbuilder)
+- [Build More Powerful LLM Applications for Business’s with LangChain (Beginners Guide)](https://youtu.be/sp3-WLKEcBg) by[ No Code Blackbox](https://www.youtube.com/@nocodeblackbox)
+- [LangFlow LLM Agent Demo for 🦜🔗LangChain](https://youtu.be/zJxDHaWt-6o) by [Cobus Greyling](https://www.youtube.com/@CobusGreylingZA)
+- [Chatbot Factory: Streamline Python Chatbot Creation with LLMs and Langchain](https://youtu.be/eYer3uzrcuM) by [Finxter](https://www.youtube.com/@CobusGreylingZA)
+- [LangChain Tutorial - ChatGPT mit eigenen Daten](https://youtu.be/0XDLyY90E2c) by [Coding Crashkurse](https://www.youtube.com/@codingcrashkurse6429)
+- [Chat with a `CSV` | LangChain Agents Tutorial (Beginners)](https://youtu.be/tjeti5vXWOU) by [GoDataProf](https://www.youtube.com/@godataprof)
+- [Introdução ao Langchain - #Cortes - Live DataHackers](https://youtu.be/fw8y5VRei5Y) by [Prof. João Gabriel Lima](https://www.youtube.com/@profjoaogabriellima)
+- [LangChain: Level up `ChatGPT` !? | LangChain Tutorial Part 1](https://youtu.be/vxUGx8aZpDE) by [Code Affinity](https://www.youtube.com/@codeaffinitydev)
+- [KI schreibt krasses Youtube Skript 😲😳 | LangChain Tutorial Deutsch](https://youtu.be/QpTiXyK1jus) by [SimpleKI](https://www.youtube.com/@simpleki)
+- [Chat with Audio: Langchain, `Chroma DB`, OpenAI, and `Assembly AI`](https://youtu.be/Kjy7cx1r75g) by [AI Anytime](https://www.youtube.com/@AIAnytime)
+- [QA over documents with Auto vector index selection with Langchain router chains](https://youtu.be/9G05qybShv8) by [echohive](https://www.youtube.com/@echohive)
+- [Build your own custom LLM application with `Bubble.io` & Langchain (No Code & Beginner friendly)](https://youtu.be/O7NhQGu1m6c) by [No Code Blackbox](https://www.youtube.com/@nocodeblackbox)
+- [Simple App to Question Your Docs: Leveraging `Streamlit`, `Hugging Face Spaces`, LangChain, and `Claude`!](https://youtu.be/X4YbNECRr7o) by [Chris Alexiuk](https://www.youtube.com/@chrisalexiuk)
+- [LANGCHAIN AI- `ConstitutionalChainAI` + Databutton AI ASSISTANT Web App](https://youtu.be/5zIU6_rdJCU) by [Avra](https://www.youtube.com/@Avra_b)
+- [LANGCHAIN AI AUTONOMOUS AGENT WEB APP - 👶 `BABY AGI` 🤖 with EMAIL AUTOMATION using `DATABUTTON`](https://youtu.be/cvAwOGfeHgw) by [Avra](https://www.youtube.com/@Avra_b)
+- [The Future of Data Analysis: Using A.I. Models in Data Analysis (LangChain)](https://youtu.be/v_LIcVyg5dk) by [Absent Data](https://www.youtube.com/@absentdata)
+- [Memory in LangChain | Deep dive (python)](https://youtu.be/70lqvTFh_Yg) by [Eden Marco](https://www.youtube.com/@EdenMarco)
+- [9 LangChain UseCases | Beginner's Guide | 2023](https://youtu.be/zS8_qosHNMw) by [Data Science Basics](https://www.youtube.com/@datasciencebasics)
+- [Use Large Language Models in Jupyter Notebook | LangChain | Agents & Indexes](https://youtu.be/JSe11L1a_QQ) by [Abhinaw Tiwari](https://www.youtube.com/@AbhinawTiwariAT)
+- [How to Talk to Your Langchain Agent | `11 Labs` + `Whisper`](https://youtu.be/N4k459Zw2PU) by [VRSEN](https://www.youtube.com/@vrsen)
+- [LangChain Deep Dive: 5 FUN AI App Ideas To Build Quickly and Easily](https://youtu.be/mPYEPzLkeks) by [James NoCode](https://www.youtube.com/@jamesnocode)
+- [LangChain 101: Models](https://youtu.be/T6c_XsyaNSQ) by [Mckay Wrigley](https://www.youtube.com/@realmckaywrigley)
+- [LangChain with JavaScript Tutorial #1 | Setup & Using LLMs](https://youtu.be/W3AoeMrg27o) by [Leon van Zyl](https://www.youtube.com/@leonvanzyl)
+- [LangChain Overview & Tutorial for Beginners: Build Powerful AI Apps Quickly & Easily (ZERO CODE)](https://youtu.be/iI84yym473Q) by [James NoCode](https://www.youtube.com/@jamesnocode)
+- [LangChain In Action: Real-World Use Case With Step-by-Step Tutorial](https://youtu.be/UO699Szp82M) by [Rabbitmetrics](https://www.youtube.com/@rabbitmetrics)
+- [Summarizing and Querying Multiple Papers with LangChain](https://youtu.be/p_MQRWH5Y6k) by [Automata Learning Lab](https://www.youtube.com/@automatalearninglab)
+- [Using Langchain (and `Replit`) through `Tana`, ask `Google`/`Wikipedia`/`Wolfram Alpha` to fill out a table](https://youtu.be/Webau9lEzoI) by [Stian Håklev](https://www.youtube.com/@StianHaklev)
+- [Langchain PDF App (GUI) | Create a ChatGPT For Your `PDF` in Python](https://youtu.be/wUAUdEw5oxM) by [Alejandro AO - Software & Ai](https://www.youtube.com/@alejandro_ao)
+- [Auto-GPT with LangChain 🔥 | Create Your Own Personal AI Assistant](https://youtu.be/imDfPmMKEjM) by [Data Science Basics](https://www.youtube.com/@datasciencebasics)
+- [Create Your OWN Slack AI Assistant with Python & LangChain](https://youtu.be/3jFXRNn2Bu8) by [Dave Ebbelaar](https://www.youtube.com/@daveebbelaar)
+- [How to Create LOCAL Chatbots with GPT4All and LangChain [Full Guide]](https://youtu.be/4p1Fojur8Zw) by [Liam Ottley](https://www.youtube.com/@LiamOttley)
+- [Build a `Multilingual PDF` Search App with LangChain, `Cohere` and `Bubble`](https://youtu.be/hOrtuumOrv8) by [Menlo Park Lab](https://www.youtube.com/@menloparklab)
+- [Building a LangChain Agent (code-free!) Using `Bubble` and `Flowise`](https://youtu.be/jDJIIVWTZDE) by [Menlo Park Lab](https://www.youtube.com/@menloparklab)
+- [Build a LangChain-based Semantic PDF Search App with No-Code Tools Bubble and Flowise](https://youtu.be/s33v5cIeqA4) by [Menlo Park Lab](https://www.youtube.com/@menloparklab)
+- [LangChain Memory Tutorial | Building a ChatGPT Clone in Python](https://youtu.be/Cwq91cj2Pnc) by [Alejandro AO - Software & Ai](https://www.youtube.com/@alejandro_ao)
+- [ChatGPT For Your DATA | Chat with Multiple Documents Using LangChain](https://youtu.be/TeDgIDqQmzs) by [Data Science Basics](https://www.youtube.com/@datasciencebasics)
+- [`Llama Index`: Chat with Documentation using URL Loader](https://youtu.be/XJRoDEctAwA) by [Merk](https://www.youtube.com/@heymichaeldaigler)
+- [Using OpenAI, LangChain, and `Gradio` to Build Custom GenAI Applications](https://youtu.be/1MsmqMg3yUc) by [David Hundley](https://www.youtube.com/@dkhundley)
+- [LangChain, Chroma DB, OpenAI Beginner Guide | ChatGPT with your PDF](https://youtu.be/FuqdVNB_8c0)
+- [Build AI chatbot with custom knowledge base using OpenAI API and GPT Index](https://youtu.be/vDZAZuaXf48) by [Irina Nik](https://www.youtube.com/@irina_nik)
+- [Build Your Own Auto-GPT Apps with LangChain (Python Tutorial)](https://youtu.be/NYSWn1ipbgg) by [Dave Ebbelaar](https://www.youtube.com/@daveebbelaar)
+- [Chat with Multiple `PDFs` | LangChain App Tutorial in Python (Free LLMs and Embeddings)](https://youtu.be/dXxQ0LR-3Hg) by [Alejandro AO - Software & Ai](https://www.youtube.com/@alejandro_ao)
+- [Chat with a `CSV` | `LangChain Agents` Tutorial (Beginners)](https://youtu.be/tjeti5vXWOU) by [Alejandro AO - Software & Ai](https://www.youtube.com/@alejandro_ao)
+- [Create Your Own ChatGPT with `PDF` Data in 5 Minutes (LangChain Tutorial)](https://youtu.be/au2WVVGUvc8) by [Liam Ottley](https://www.youtube.com/@LiamOttley)
+- [Build a Custom Chatbot with OpenAI: `GPT-Index` & LangChain | Step-by-Step Tutorial](https://youtu.be/FIDv6nc4CgU) by [Fabrikod](https://www.youtube.com/@fabrikod)
+- [`Flowise` is an open-source no-code UI visual tool to build 🦜🔗LangChain applications](https://youtu.be/CovAPtQPU0k) by [Cobus Greyling](https://www.youtube.com/@CobusGreylingZA)
+- [LangChain & GPT 4 For Data Analysis: The `Pandas` Dataframe Agent](https://youtu.be/rFQ5Kmkd4jc) by [Rabbitmetrics](https://www.youtube.com/@rabbitmetrics)
+- [`GirlfriendGPT` - AI girlfriend with LangChain](https://youtu.be/LiN3D1QZGQw) by [Girlfriend GPT](https://www.youtube.com/@girlfriendGPT)
+- [How to build with Langchain 10x easier | ⛓️ LangFlow & `Flowise`](https://youtu.be/Ya1oGL7ZTvU) by [AI Jason](https://www.youtube.com/@AIJasonZ)
+- [Getting Started With LangChain In 20 Minutes- Build Celebrity Search Application](https://youtu.be/_FpT1cwcSLg) by [Krish Naik](https://www.youtube.com/@krishnaik06)
+- ⛓ [Vector Embeddings Tutorial – Code Your Own AI Assistant with `GPT-4 API` + LangChain + NLP](https://youtu.be/yfHHvmaMkcA?si=5uJhxoh2tvdnOXok) by [FreeCodeCamp.org](https://www.youtube.com/@freecodecamp)
+- ⛓ [Fully LOCAL `Llama 2` Q&A with LangChain](https://youtu.be/wgYctKFnQ74?si=UX1F3W-B3MqF4-K-) by [1littlecoder](https://www.youtube.com/@1littlecoder)
+- ⛓ [Fully LOCAL `Llama 2` Langchain on CPU](https://youtu.be/yhECvKMu8kM?si=IvjxwlA1c09VwHZ4) by [1littlecoder](https://www.youtube.com/@1littlecoder)
+- ⛓ [Build LangChain Audio Apps with Python in 5 Minutes](https://youtu.be/7w7ysaDz2W4?si=BvdMiyHhormr2-vr) by [AssemblyAI](https://www.youtube.com/@AssemblyAI)
+- ⛓ [`Voiceflow` & `Flowise`: Want to Beat Competition? New Tutorial with Real AI Chatbot](https://youtu.be/EZKkmeFwag0?si=-4dETYDHEstiK_bb) by [AI SIMP](https://www.youtube.com/@aisimp)
+- ⛓ [THIS Is How You Build Production-Ready AI Apps (`LangSmith` Tutorial)](https://youtu.be/tFXm5ijih98?si=lfiqpyaivxHFyI94) by [Dave Ebbelaar](https://www.youtube.com/@daveebbelaar)
+- ⛓ [Build POWERFUL LLM Bots EASILY with Your Own Data - `Embedchain` - Langchain 2.0? (Tutorial)](https://youtu.be/jE24Y_GasE8?si=0yEDZt3BK5Q-LIuF) by [WorldofAI](https://www.youtube.com/@intheworldofai)
+- ⛓ [`Code Llama` powered Gradio App for Coding: Runs on CPU](https://youtu.be/AJOhV6Ryy5o?si=ouuQT6IghYlc1NEJ) by [AI Anytime](https://www.youtube.com/@AIAnytime)
+- ⛓ [LangChain Complete Course in One Video | Develop LangChain (AI) Based Solutions for Your Business](https://youtu.be/j9mQd-MyIg8?si=_wlNT3nP2LpDKztZ) by [UBprogrammer](https://www.youtube.com/@UBprogrammer)
+- ⛓ [How to Run `LLaMA` Locally on CPU or GPU | Python & Langchain & CTransformers Guide](https://youtu.be/SvjWDX2NqiM?si=DxFml8XeGhiLTzLV) by [Code With Prince](https://www.youtube.com/@CodeWithPrince)
+- ⛓ [PyData Heidelberg #11 - TimeSeries Forecasting & LLM Langchain](https://www.youtube.com/live/Glbwb5Hxu18?si=PIEY8Raq_C9PCHuW) by [PyData](https://www.youtube.com/@PyDataTV)
+- ⛓ [Prompt Engineering in Web Development | Using LangChain and Templates with OpenAI](https://youtu.be/pK6WzlTOlYw?si=fkcDQsBG2h-DM8uQ) by [Akamai Developer
+](https://www.youtube.com/@AkamaiDeveloper)
+- ⛓ [Retrieval-Augmented Generation (RAG) using LangChain and `Pinecone` - The RAG Special Episode](https://youtu.be/J_tCD_J6w3s?si=60Mnr5VD9UED9bGG) by [Generative AI and Data Science On AWS](https://www.youtube.com/@GenerativeAIOnAWS)
+- ⛓ [`LLAMA2 70b-chat` Multiple Documents Chatbot with Langchain & Streamlit |All OPEN SOURCE|Replicate API](https://youtu.be/vhghB81vViM?si=dszzJnArMeac7lyc) by [DataInsightEdge](https://www.youtube.com/@DataInsightEdge01)
+- ⛓ [Chatting with 44K Fashion Products: LangChain Opportunities and Pitfalls](https://youtu.be/Zudgske0F_s?si=8HSshHoEhh0PemJA) by [Rabbitmetrics](https://www.youtube.com/@rabbitmetrics)
+- ⛓ [Structured Data Extraction from `ChatGPT` with LangChain](https://youtu.be/q1lYg8JISpQ?si=0HctzOHYZvq62sve) by [MG](https://www.youtube.com/@MG_cafe)
+- ⛓ [Chat with Multiple PDFs using `Llama 2`, `Pinecone` and LangChain (Free LLMs and Embeddings)](https://youtu.be/TcJ_tVSGS4g?si=FZYnMDJyoFfL3Z2i) by [Muhammad Moin](https://www.youtube.com/@muhammadmoinfaisal)
+- ⛓ [Integrate Audio into `LangChain.js` apps in 5 Minutes](https://youtu.be/hNpUSaYZIzs?si=Gb9h7W9A8lzfvFKi) by [AssemblyAI](https://www.youtube.com/@AssemblyAI)
+- ⛓ [`ChatGPT` for your data with Local LLM](https://youtu.be/bWrjpwhHEMU?si=uM6ZZ18z9og4M90u) by [Jacob Jedryszek](https://www.youtube.com/@jj09)
+- ⛓ [Training `Chatgpt` with your personal data using langchain step by step in detail](https://youtu.be/j3xOMde2v9Y?si=179HsiMU-hEPuSs4) by [NextGen Machines](https://www.youtube.com/@MayankGupta-kb5yc)
+- ⛓ [Use ANY language in `LangSmith` with REST](https://youtu.be/7BL0GEdMmgY?si=iXfOEdBLqXF6hqRM) by [Nerding I/O](https://www.youtube.com/@nerding_io)
+- ⛓ [How to Leverage the Full Potential of LLMs for Your Business with Langchain - Leon Ruddat](https://youtu.be/vZmoEa7oWMg?si=ZhMmydq7RtkZd56Q) by [PyData](https://www.youtube.com/@PyDataTV)
+- ⛓ [`ChatCSV` App: Chat with CSV files using LangChain and `Llama 2`](https://youtu.be/PvsMg6jFs8E?si=Qzg5u5gijxj933Ya) by [Muhammad Moin](https://www.youtube.com/@muhammadmoinfaisal)
+- ⛓ [Build Chat PDF app in Python with LangChain, OpenAI, Streamlit | Full project | Learn Coding](https://www.youtube.com/watch?v=WYzFzZg4YZI) by [Jutsupoint](https://www.youtube.com/@JutsuPoint)
+- ⛓ [Build Eminem Bot App with LangChain, Streamlit, OpenAI | Full Python Project | Tutorial | AI ChatBot](https://www.youtube.com/watch?v=a2shHB4MRZ4) by [Jutsupoint](https://www.youtube.com/@JutsuPoint)
+
+
+### [Prompt Engineering and LangChain](https://www.youtube.com/watch?v=muXbPpG_ys4&list=PLEJK-H61Xlwzm5FYLDdKt_6yibO33zoMW) by [Venelin Valkov](https://www.youtube.com/@venelin_valkov)
+- [Getting Started with LangChain: Load Custom Data, Run OpenAI Models, Embeddings and `ChatGPT`](https://www.youtube.com/watch?v=muXbPpG_ys4)
+- [Loaders, Indexes & Vectorstores in LangChain: Question Answering on `PDF` files with `ChatGPT`](https://www.youtube.com/watch?v=FQnvfR8Dmr0)
+- [LangChain Models: `ChatGPT`, `Flan Alpaca`, `OpenAI Embeddings`, Prompt Templates & Streaming](https://www.youtube.com/watch?v=zy6LiK5F5-s)
+- [LangChain Chains: Use `ChatGPT` to Build Conversational Agents, Summaries and Q&A on Text With LLMs](https://www.youtube.com/watch?v=h1tJZQPcimM)
+- [Analyze Custom CSV Data with `GPT-4` using Langchain](https://www.youtube.com/watch?v=Ew3sGdX8at4)
+- [Build ChatGPT Chatbots with LangChain Memory: Understanding and Implementing Memory in Conversations](https://youtu.be/CyuUlf54wTs)
 
-- [Using `ChatGPT` with YOUR OWN Data. This is magical. (LangChain `OpenAI API`)](https://youtu.be/9AXP7tCI9PI)
-- [Chat with Multiple `PDFs` | LangChain App Tutorial in Python (Free LLMs and Embeddings)](https://youtu.be/dXxQ0LR-3Hg?si=pjXKhsHRzn10vOqX)
-- [`Hugging Face` + Langchain in 5 mins | Access 200k+ FREE AI models for your AI apps](https://youtu.be/_j7JEDWuqLE?si=psimQscN3qo2dOa9)
-- [LangChain Crash Course For Beginners | LangChain Tutorial](https://youtu.be/nAmC7SoVLd8?si=qJdvyG5-rnjqfdj1)
-- [Vector Embeddings Tutorial – Code Your Own AI Assistant with GPT-4 API + LangChain + NLP](https://youtu.be/yfHHvmaMkcA?si=UBP3yw50cLm3a2nj)
-- [Development with Large Language Models Tutorial – `OpenAI`, Langchain, Agents, `Chroma`](https://youtu.be/xZDB1naRUlk?si=v8J1q6oFHRyTkf7Y)
-- [Langchain: `PDF` Chat App (GUI) | ChatGPT for Your PDF FILES | Step-by-Step Tutorial](https://youtu.be/RIWbalZ7sTo?si=LbKsCcuyv0BtnrTY)
-- [Vector Search `RAG` Tutorial – Combine Your Data with LLMs with Advanced Search](https://youtu.be/JEBDfGqrAUA?si=pD7oxpfwWeJCxfBt)
-- [LangChain Crash Course for Beginners](https://youtu.be/lG7Uxts9SXs?si=Yte4S5afN7KNCw0F)
-- [Learn `RAG` From Scratch – Python AI Tutorial from a LangChain Engineer](https://youtu.be/sVcwVQRHIc8?si=_LN4g0vOgSdtlB3S)
-- [`Llama 2` in LangChain — FIRST Open Source Conversational Agent!](https://youtu.be/6iHVJyX2e50?si=rtq1maPrzWKHbwVV)
-- [LangChain Tutorial for Beginners | Generative AI Series](https://youtu.be/cQUUkZnyoD0?si=KYz-bvcocdqGh9f_)
-- [Chatbots with `RAG`: LangChain Full Walkthrough](https://youtu.be/LhnCsygAvzY?si=yS7T98VLfcWdkDek)
-- [LangChain Explained In 15 Minutes - A MUST Learn For Python Programmers](https://youtu.be/mrjq3lFz23s?si=wkQGcSKUJjuiiEPf)
-- [LLM Project | End to End LLM Project Using Langchain, `OpenAI` in Finance Domain](https://youtu.be/MoqgmWV1fm8?si=oVl-5kJVgd3a07Y_)
-- [What is LangChain?](https://youtu.be/1bUy-1hGZpI?si=NZ0D51VM5y-DhjGe)
-- [`RAG` + Langchain Python Project: Easy AI/Chat For Your Doc](https://youtu.be/tcqEUSNCn8I?si=RLcWPBVLIErRqdmU)
-- [Getting Started With LangChain In 20 Minutes- Build Celebrity Search Application](https://youtu.be/_FpT1cwcSLg?si=X9qVazlXYucN_JBP)
-- [LangChain GEN AI Tutorial – 6 End-to-End Projects using OpenAI, Google `Gemini Pro`, `LLAMA2`](https://youtu.be/x0AnCE9SE4A?si=_92gJYm7kb-V2bi0)
-- [Complete Langchain GEN AI Crash Course With 6 End To End LLM Projects With OPENAI, `LLAMA2`, `Gemini Pro`](https://youtu.be/aWKrL4z5H6w?si=NVLi7Yiq0ccE7xXE)
-- [AI Leader Reveals The Future of AI AGENTS (LangChain CEO)](https://youtu.be/9ZhbA0FHZYc?si=1r4P6kRvKVvEhRgE)
-- [Learn How To Query Pdf using Langchain Open AI in 5 min](https://youtu.be/5Ghv-F1wF_0?si=ZZRjrWfeiFOVrcvu)
-- [Reliable, fully local RAG agents with `LLaMA3`](https://youtu.be/-ROS6gfYIts?si=75CXA8W_BbnkIxcV)
-- [Learn `LangChain.js` - Build LLM apps with JavaScript and `OpenAI`](https://youtu.be/HSZ_uaif57o?si=Icj-RAhwMT-vHaYA)
-- [LLM Project | End to End LLM Project Using LangChain, Google Palm In Ed-Tech Industry](https://youtu.be/AjQPRomyd-k?si=eC3NT6kn02Lhpz-_)
-- [Chatbot Answering from Your Own Knowledge Base: Langchain, `ChatGPT`, `Pinecone`, and `Streamlit`: | Code](https://youtu.be/nAKhxQ3hcMA?si=9Zd_Nd_jiYhtml5w)
-- [LangChain is AMAZING | Quick Python Tutorial](https://youtu.be/I4mFqyqFkxg?si=aJ66qh558OfNAczD)
-- [`GirlfriendGPT` - AI girlfriend with LangChain](https://youtu.be/LiN3D1QZGQw?si=kZR-lnJwixeVrjmh)
-- [Using NEW `MPT-7B` in `Hugging Face` and LangChain](https://youtu.be/DXpk9K7DgMo?si=99JDpV_ueimwJhMi)
-- [LangChain - COMPLETE TUTORIAL - Basics to advanced concept!](https://youtu.be/a89vqgK-Qcs?si=0aVO2EOqsw7GE5e3)
-- [LangChain Agents: Simply Explained!](https://youtu.be/Xi9Ui-9qcPw?si=DCuG7nGx8dxcfhkx)
-- [Chat With Multiple `PDF` Documents With Langchain And Google `Gemini Pro`](https://youtu.be/uus5eLz6smA?si=YUwvHtaZsGeIl0WD)
-- [LLM Project | End to end LLM project Using Langchain, `Google Palm` in Retail Industry](https://youtu.be/4wtrl4hnPT8?si=_eOKPpdLfWu5UXMQ)
-- [Tutorial | Chat with any Website using Python and Langchain](https://youtu.be/bupx08ZgSFg?si=KRrjYZFnuLsstGwW)
-- [Prompt Engineering And LLM's With LangChain In One Shot-Generative AI](https://youtu.be/t2bSApmPzU4?si=87vPQQtYEWTyu2Kx)
-- [Build a Custom Chatbot with `OpenAI`: `GPT-Index` & LangChain | Step-by-Step Tutorial](https://youtu.be/FIDv6nc4CgU?si=gR1u3DUG9lvzBIKK)
-- [Search Your `PDF` App using Langchain, `ChromaDB`, and Open Source LLM: No OpenAI API (Runs on CPU)](https://youtu.be/rIV1EseKwU4?si=UxZEoXSiPai8fXgl)
-- [Building a `RAG` application from scratch using Python, LangChain, and the `OpenAI API`](https://youtu.be/BrsocJb-fAo?si=hvkh9iTGzJ-LnsX-)
-- [Function Calling via `ChatGPT API` - First Look With LangChain](https://youtu.be/0-zlUy7VUjg?si=Vc6LFseckEc6qvuk)
-- [Private GPT, free deployment! Langchain-Chachat helps you easily play with major mainstream AI models! | Zero Degree Commentary](https://youtu.be/3LLUyaHP-3I?si=AZumEeFXsvqaLl0f)
-- [Create a ChatGPT clone using `Streamlit` and LangChain](https://youtu.be/IaTiyQ2oYUQ?si=WbgsYmqPDnMidSUK)
-- [What's next for AI agents ft. LangChain's Harrison Chase](https://youtu.be/pBBe1pk8hf4?si=H4vdBF9nmkNZxiHt)
-- [`LangFlow`: Build Chatbots without Writing Code - LangChain](https://youtu.be/KJ-ux3hre4s?si=TJuDu4bAlva1myNL)
-- [Building a LangChain Custom Medical Agent with Memory](https://youtu.be/6UFtRwWnHws?si=wymYad26VgigRkHy)
-- [`Ollama` meets LangChain](https://youtu.be/k_1pOF1mj8k?si=RlBiCrmaR3s7SnMK)
-- [End To End LLM Langchain Project using `Pinecone` Vector Database](https://youtu.be/erUfLIi9OFM?si=aHpuHXdIEmAfS4eF)
-- [`LLaMA2` with LangChain - Basics | LangChain TUTORIAL](https://youtu.be/cIRzwSXB4Rc?si=FUs0OLVJpzKhut0h)
-- [Understanding `ReACT` with LangChain](https://youtu.be/Eug2clsLtFs?si=imgj534ggxlypS0d)
 
 ---------------------
-[Updated 2024-05-16]
+⛓ icon marks a new addition [last update 2024-02-04]

docs/docs/changelog/core.mdx

@@ -1,10 +1,27 @@
 # langchain-core
 
-## 0.1.x
+## 0.1.7 (Jan 5, 2024)
+
+#### Deleted
+
+No deletions.
 
 #### Deprecated
 
 - `BaseChatModel` methods `__call__`, `call_as_llm`, `predict`, `predict_messages`. Will be removed in 0.2.0. Use `BaseChatModel.invoke` instead.
 - `BaseChatModel` methods `apredict`, `apredict_messages`. Will be removed in 0.2.0. Use `BaseChatModel.ainvoke` instead.
 - `BaseLLM` methods `__call__, `predict`, `predict_messages`. Will be removed in 0.2.0. Use `BaseLLM.invoke` instead.
-- `BaseLLM` methods `apredict`, `apredict_messages`. Will be removed in 0.2.0. Use `BaseLLM.ainvoke` instead.
+- `BaseLLM` methods `apredict`, `apredict_messages`. Will be removed in 0.2.0. Use `BaseLLM.ainvoke` instead.
+
+#### Fixed
+
+- Restrict recursive URL scraping: [#15559](https://github.com/langchain-ai/langchain/pull/15559)
+
+#### Added
+
+No additions.
+
+#### Beta
+
+- Marked `langchain_core.load.load` and `langchain_core.load.loads` as beta.
+- Marked `langchain_core.beta.runnables.context.ContextGet` and `langchain_core.beta.runnables.context.ContextSet` as beta.

docs/docs/changelog/langchain.mdx

@@ -1,73 +1,16 @@
 # langchain
 
-## 0.2.0
-
-### Deleted
-
-As of release 0.2.0, `langchain` is required to be integration-agnostic. This means that code in `langchain`  should not by default instantiate any specific chat models, llms, embedding models, vectorstores etc; instead, the user will be required to specify those explicitly.
-
-The following functions and classes require an explicit LLM to be passed as an argument:
-
-- `langchain.agents.agent_toolkits.vectorstore.toolkit.VectorStoreToolkit`
-- `langchain.agents.agent_toolkits.vectorstore.toolkit.VectorStoreRouterToolkit`
-- `langchain.chains.openai_functions.get_openapi_chain`
-- `langchain.chains.router.MultiRetrievalQAChain.from_retrievers`
-- `langchain.indexes.VectorStoreIndexWrapper.query`
-- `langchain.indexes.VectorStoreIndexWrapper.query_with_sources`
-- `langchain.indexes.VectorStoreIndexWrapper.aquery_with_sources`
-- `langchain.chains.flare.FlareChain`
-
-The following classes now require passing an explicit Embedding model as an argument:
-
-- `langchain.indexes.VectostoreIndexCreator`
-
-The following code has been removed:
-
-- `langchain.natbot.NatBotChain.from_default` removed in favor of the `from_llm` class method.
-
-### Deprecated
-
-We have two main types of deprecations:
-
-1. Code that was moved from `langchain` into another package (e.g, `langchain-community`)
-
-If you try to import it from `langchain`, the import will keep on working, but will raise a deprecation warning. The warning will provide a replacement import statement.
-
-```python
-python -c "from langchain.document_loaders.markdown import UnstructuredMarkdownLoader"
-
-```
-
-```python
-LangChainDeprecationWarning: Importing UnstructuredMarkdownLoader from langchain.document_loaders is deprecated. Please replace deprecated imports:
-
->> from langchain.document_loaders import UnstructuredMarkdownLoader
-
-with new imports of:
-
->> from langchain_community.document_loaders import UnstructuredMarkdownLoader
-```
-
-We will continue supporting the imports in `langchain` until release 0.4 as long as the relevant package where the code lives is installed. (e.g., as long as `langchain_community` is installed.)
-
-However, we advise for users to not rely on these imports and instead migrate to the new imports. To help with this process, we’re releasing a migration script via the LangChain CLI. See further instructions in migration guide.
-
-1. Code that has better alternatives available and will eventually be removed, so there’s only a single way to do things. (e.g., `predict_messages` method in ChatModels has been deprecated in favor of `invoke`).
-
-Many of these were marked for removal in 0.2. We have bumped the removal to 0.3.
-
-
 ## 0.1.0 (Jan 5, 2024)
 
-### Deleted
+#### Deleted
 
 No deletions.
 
-### Deprecated
+#### Deprecated
 
 Deprecated classes and methods will be removed in 0.2.0
 
-| Deprecated                      | Alternative                       | Reason                                         |
+| Deprecated                | Alternative                       | Reason                                         |
 |---------------------------------|-----------------------------------|------------------------------------------------|
 | ChatVectorDBChain               | ConversationalRetrievalChain      | More general to all retrievers                 |
 | create_ernie_fn_chain           | create_ernie_fn_runnable          | Use LCEL under the hood                        |

docs/docs/contributing/code.mdx

@@ -1,9 +1,36 @@
-# Setup
+---
+sidebar_position: 1
+---
+# Contribute Code
 
-This guide walks through how to run the repository locally and check in your first code.
+To contribute to this project, please follow the ["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 a maintainer.
+
+Please follow the checked-in pull request template when opening pull requests. Note related issues and tag relevant
+maintainers.
+
+Pull requests cannot land without passing the formatting, linting, and testing checks first. See [Testing](#testing) and
+[Formatting and Linting](#formatting-and-linting) for how to run these checks locally.
+
+It's essential that we maintain great documentation and testing. If you:
+- Fix a bug
+  - Add a relevant unit or integration test when possible. These live in `tests/unit_tests` and `tests/integration_tests`.
+- Make an improvement
+  - Update any affected example notebooks and documentation. These live in `docs`.
+  - Update unit and integration tests when relevant.
+- Add a feature
+  - Add a demo notebook in `docs/docs/`.
+  - Add unit and integration tests.
+
+We are a small, progress-oriented team. If there's something you'd like to add or change, opening a pull request is the
+best way to get our attention.
+
+## 🚀 Quick Start
+
+This quick start guide explains how to run the repository locally.
 For a [development container](https://containers.dev/), see the [.devcontainer folder](https://github.com/langchain-ai/langchain/tree/master/.devcontainer).
 
-## Dependency Management: Poetry and other env/dependency managers
+### Dependency Management: Poetry and other env/dependency managers
 
 This project utilizes [Poetry](https://python-poetry.org/) v1.7.1+ as a dependency manager.
 
@@ -14,7 +41,7 @@ Install Poetry: **[documentation on how to install it](https://python-poetry.org
 ❗Note: If you use `Conda` or `Pyenv` as your environment/package manager, after installing Poetry,
 tell Poetry to use the virtualenv python environment (`poetry config virtualenvs.prefer-active-python true`)
 
-## Different packages
+### Different packages
 
 This repository contains multiple packages:
 - `langchain-core`: Base interfaces for key abstractions as well as logic for combining them in chains (LangChain Expression Language).
@@ -32,7 +59,7 @@ For this quickstart, start with langchain-community:
 cd libs/community
 ```
 
-## Local Development Dependencies
+### Local Development Dependencies
 
 Install langchain-community development requirements (for running langchain, running examples, linting, formatting, tests, and coverage):
 
@@ -52,9 +79,9 @@ If you are still seeing this bug on v1.6.1+, you may also try disabling "modern
 (`poetry config installer.modern-installation false`) and re-installing requirements.
 See [this `debugpy` issue](https://github.com/microsoft/debugpy/issues/1246) for more details.
 
-## Testing
+### Testing
 
-**Note:** In `langchain`, `langchain-community`, and `langchain-experimental`, some test dependencies are optional. See the following section about optional dependencies.
+_In `langchain`, `langchain-community`, and `langchain-experimental`, some test dependencies are optional; see section about optional dependencies_.
 
 Unit tests cover modular logic that does not require calls to outside APIs.
 If you add new logic, please add a unit test.
@@ -91,11 +118,11 @@ poetry install --with test
 make test
 ```
 
-## Formatting and Linting
+### Formatting and Linting
 
 Run these locally before submitting a PR; the CI system will check also.
 
-### Code Formatting
+#### Code Formatting
 
 Formatting for this project is done via [ruff](https://docs.astral.sh/ruff/rules/).
 
@@ -147,7 +174,7 @@ This can be very helpful when you've made changes to only certain parts of the p
 
 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.
 
-### Spellcheck
+#### Spellcheck
 
 Spellchecking for this project is done via [codespell](https://github.com/codespell-project/codespell).
 Note that `codespell` finds common typos, so it could have false-positive (correctly spelled but rarely used) and false-negatives (not finding misspelled) words.
@@ -179,7 +206,9 @@ ignore-words-list = 'momento,collison,ned,foor,reworkd,parth,whats,aapply,mysogy
 
 `langchain-core` and partner packages **do not use** optional dependencies in this way.
 
-You'll notice that `pyproject.toml` and `poetry.lock` are **not** touched when you add optional dependencies below.
+You only need to add a new dependency if a **unit test** relies on the package.
+If your package is only required for **integration tests**, then you can skip these
+steps and leave all pyproject.toml and poetry.lock files alone.
 
 If you're adding a new dependency to Langchain, assume that it will be an optional dependency, and
 that most users won't have it installed.
@@ -187,12 +216,20 @@ that most users won't have it installed.
 Users who do not have the dependency installed should be able to **import** your code without
 any side effects (no warnings, no errors, no exceptions).
 
-To introduce the dependency to a library, please do the following:
+To introduce the dependency to the pyproject.toml file correctly, please do the following:
 
-1. Open extended_testing_deps.txt and add the dependency
-2. Add a unit test that the very least attempts to import the new code. Ideally, the unit
+1. Add the dependency to the main group as an optional dependency
+  ```bash
+  poetry add --optional [package_name]
+  ```
+2. Open pyproject.toml and add the dependency to the `extended_testing` extra
+3. Relock the poetry file to update the extra.
+  ```bash
+  poetry lock --no-update
+  ```
+4. Add a unit test that the very least attempts to import the new code. Ideally, the unit
 test makes use of lightweight fixtures to test the logic of the code.
-3. Please use the `@pytest.mark.requires(package_name)` decorator for any unit tests that require the dependency.
+5. Please use the `@pytest.mark.requires(package_name)` decorator for any tests that require the dependency.
 
 ## Adding a Jupyter Notebook
 

docs/docs/contributing/code/guidelines.mdx

@@ -1,35 +0,0 @@
-# General guidelines
-
-Here are some things to keep in mind for all types of contributions:
-
-- Follow the ["fork and pull request"](https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project) workflow.
-- Fill out the checked-in pull request template when opening pull requests. Note related issues and tag relevant maintainers.
-- Ensure your PR passes formatting, linting, and testing checks before requesting a review.
-  - If you would like comments or feedback on your current progress, please open an issue or discussion and tag a maintainer.
-  - See the sections on [Testing](/docs/contributing/code/setup#testing) and [Formatting and Linting](/docs/contributing/code/setup#formatting-and-linting) for how to run these checks locally.
-- Backwards compatibility is key. Your changes must not be breaking, except in case of critical bug and security fixes.
-- Look for duplicate PRs or issues that have already been opened before opening a new one.
-- Keep scope as isolated as possible. As a general rule, your changes should not affect more than one package at a time.
-
-## Bugfixes
-
-We encourage and appreciate bugfixes. We ask that you:
-
-- Explain the bug in enough detail for maintainers to be able to reproduce it.
-  - If an accompanying issue exists, link to it. Prefix with `Fixes` so that the issue will close automatically when the PR is merged.
-- Avoid breaking changes if possible.
-- Include unit tests that fail without the bugfix.
-
-If you come across a bug and don't know how to fix it, we ask that you open an issue for it describing in detail the environment in which you encountered the bug.
-
-## New features
-
-We aim to keep the bar high for new features. We generally don't accept new core abstractions, changes to infra, changes to dependencies,
-or new agents/chains from outside contributors without an existing GitHub discussion or issue that demonstrates an acute need for them.
-
-- New features must come with docs, unit tests, and (if appropriate) integration tests.
-- New integrations must come with docs, unit tests, and (if appropriate) integration tests.
-  - See [this page](/docs/contributing/integrations) for more details on contributing new integrations.
-- New functionality should not inherit from or use deprecated methods or classes.
-- We will reject features that are likely to lead to security vulnerabilities or reports.
-- Do not add any hard dependencies. Integrations may add optional dependencies.

docs/docs/contributing/code/index.mdx

@@ -1,6 +0,0 @@
-# Contribute Code
-
-If you would like to add a new feature or update an existing one, please read the resources below before getting started:
-
-- [General guidelines](/docs/contributing/code/guidelines/)
-- [Setup](/docs/contributing/code/setup/)

docs/docs/contributing/documentation/_category_.yml

@@ -0,0 +1,2 @@
+label: 'Documentation'
+position: 3

docs/docs/contributing/documentation/index.mdx

@@ -1,7 +0,0 @@
-# Contribute Documentation
-
-Documentation is a vital part of LangChain. We welcome both new documentation for new features and 
-community improvements to our current documentation. Please read the resources below before getting started:
-
-- [Documentation style guide](/docs/contributing/documentation/style_guide/)
-- [Setup](/docs/contributing/documentation/setup/)

docs/docs/contributing/documentation/style_guide.mdx

@@ -1,8 +1,10 @@
 ---
-sidebar_class_name: "hidden"
+sidebar_label: "Style guide"
 ---
 
-# Documentation Style Guide
+# LangChain Documentation Style Guide
+
+## Introduction
 
 As LangChain continues to grow, the surface area of documentation required to cover it continues to grow too.
 This page provides guidelines for anyone writing documentation for LangChain, as well as some of our philosophies around
@@ -10,137 +12,116 @@ organization and structure.
 
 ## Philosophy
 
-LangChain's documentation follows the [Diataxis framework](https://diataxis.fr).
-Under this framework, all documentation falls under one of four categories: [Tutorials](/docs/contributing/documentation/style_guide/#tutorials),
-[How-to guides](/docs/contributing/documentation/style_guide/#how-to-guides),
-[References](/docs/contributing/documentation/style_guide/#references), and [Explanations](/docs/contributing/documentation/style_guide/#conceptual-guide).
+LangChain's documentation aspires to follow the [Diataxis framework](https://diataxis.fr).
+Under this framework, all documentation falls under one of four categories:
 
-### Tutorials
-
-Tutorials are lessons that take the reader through a practical activity. Their purpose is to help the user
-gain understanding of concepts and how they interact by showing one way to achieve some goal in a hands-on way. They should **avoid** giving
-multiple permutations of ways to achieve that goal in-depth. Instead, it should guide a new user through a recommended path to accomplishing the tutorial's goal. While the end result of a tutorial does not necessarily need to
-be completely production-ready, it should be useful and practically satisfy the the goal that you clearly stated in the tutorial's introduction. Information on how to address additional scenarios
-belongs in how-to guides.
-
-To quote the Diataxis website:
-
-> A tutorial serves the user’s *acquisition* of skills and knowledge - their study. Its purpose is not to help the user get something done, but to help them learn.
-
-In LangChain, these are often higher level guides that show off end-to-end use cases.
-
-Some examples include:
-
-- [Build a Simple LLM Application with LCEL](/docs/tutorials/llm_chain/)
-- [Build a Retrieval Augmented Generation (RAG) App](/docs/tutorials/rag/)
-  
-Here are some high-level tips on writing a good tutorial:
-
-- Focus on guiding the user to get something done, but keep in mind the end-goal is more to impart principles than to create a perfect production system.
-- Be specific, not abstract and follow one path.
-  - No need to go deeply into alternative approaches, but it’s ok to reference them, ideally with a link to an appropriate how-to guide.
-- Get "a point on the board" as soon as possible - something the user can run that outputs something.
-  - You can iterate and expand afterwards.
-  - Try to frequently checkpoint at given steps where the user can run code and see progress.
-- Focus on results, not technical explanation.
-  - Crosslink heavily to appropriate conceptual/reference pages.
-- The first time you mention a LangChain concept, use its full name (e.g. "LangChain Expression Language (LCEL)"), and link to its conceptual/other documentation page.
-  - It's also helpful to add a prerequisite callout that links to any pages with necessary background information.
-- End with a recap/next steps section summarizing what the tutorial covered and future reading, such as related how-to guides.
-  
-### How-to guides
-
-A how-to guide, as the name implies, demonstrates how to do something discrete and specific.
-It should assume that the user is already familiar with underlying concepts, and is trying to solve an immediate problem, but
-should still give some background or list the scenarios where the information contained within can be relevant.
-They can and should discuss alternatives if one approach may be better than another in certain cases.
-
-To quote the Diataxis website:
-
-> A how-to guide serves the work of the already-competent user, whom you can assume to know what they want to do, and to be able to follow your instructions correctly.
-
-Some examples include:
-
-- [How to: return structured data from a model](/docs/how_to/structured_output/)
-- [How to: write a custom chat model](/docs/how_to/custom_chat_model/)
-
-Here are some high-level tips on writing a good how-to guide:
-
-- Clearly explain what you are guiding the user through at the start.
-- Assume higher intent than a tutorial and show what the user needs to do to get that task done.
-- Assume familiarity of concepts, but explain why suggested actions are helpful.
-  - Crosslink heavily to conceptual/reference pages.
-- Discuss alternatives and responses to real-world tradeoffs that may arise when solving a problem.
-- Use lots of example code.
-  - Prefer full code blocks that the reader can copy and run.
-- End with a recap/next steps section summarizing what the tutorial covered and future reading, such as other related how-to guides.
-
-### Conceptual guide
-
-LangChain's conceptual guide falls under the **Explanation** quadrant of Diataxis. They should cover LangChain terms and concepts
-in a more abstract way than how-to guides or tutorials, and should be geared towards curious users interested in
-gaining a deeper understanding of the framework. Try to avoid excessively large code examples - the goal here is to
-impart perspective to the user rather than to finish a practical project. These guides should cover **why** things work they way they do.
-
-This guide on documentation style is meant to fall under this category.
-
-To quote the Diataxis website:
-
-> The perspective of explanation is higher and wider than that of the other types. It does not take the user’s eye-level view, as in a how-to guide, or a close-up view of the machinery, like reference material. Its scope in each case is a topic - “an area of knowledge”, that somehow has to be bounded in a reasonable, meaningful way.
-
-Some examples include:
-
-- [Retrieval conceptual docs](/docs/concepts/#retrieval)
-- [Chat model conceptual docs](/docs/concepts/#chat-models)
-
-Here are some high-level tips on writing a good conceptual guide:
-
-- Explain design decisions. Why does concept X exist and why was it designed this way?
-- Use analogies and reference other concepts and alternatives
-- Avoid blending in too much reference content
-- You can and should reference content covered in other guides, but make sure to link to them
-
-### References
-
-References contain detailed, low-level information that describes exactly what functionality exists and how to use it.
-In LangChain, this is mainly our API reference pages, which are populated from docstrings within code.
-References pages are generally not read end-to-end, but are consulted as necessary when a user needs to know
-how to use something specific.
-
-To quote the Diataxis website:
-
-> The only purpose of a reference guide is to describe, as succinctly as possible, and in an orderly way. Whereas the content of tutorials and how-to guides are led by needs of the user, reference material is led by the product it describes.
-
-Many of the reference pages in LangChain are automatically generated from code,
-but here are some high-level tips on writing a good docstring:
-
-- Be concise
-- Discuss special cases and deviations from a user's expectations
-- Go into detail on required inputs and outputs
-- Light details on when one might use the feature are fine, but in-depth details belong in other sections.
+- **Tutorials**: Lessons that take the reader by the hand through a series of conceptual steps to complete a project.
+  - An example of this is our [LCEL streaming guide](/docs/expression_language/streaming).
+  - Our guides on [custom components](/docs/modules/model_io/chat/custom_chat_model) is another one.
+- **How-to guides**: Guides that take the reader through the steps required to solve a real-world problem.
+  - The clearest examples of this are our [Use case](/docs/use_cases/) quickstart pages.
+- **Reference**: Technical descriptions of the machinery and how to operate it.
+  - Our [Runnable interface](/docs/expression_language/interface) page is an example of this.
+  - The [API reference pages](https://api.python.langchain.com/) are another.
+- **Explanation**: Explanations that clarify and illuminate a particular topic.
+  - The [LCEL primitives pages](/docs/expression_language/primitives/sequence) are an example of this.
 
 Each category serves a distinct purpose and requires a specific approach to writing and structuring the content.
 
-## General guidelines
+## Taxonomy
+
+Keeping the above in mind, we have sorted LangChain's docs into categories. It is helpful to think in these terms
+when contributing new documentation:
+
+### Getting started
+
+The [getting started section](/docs/get_started/introduction) includes a high-level introduction to LangChain, a quickstart that
+tours LangChain's various features, and logistical instructions around installation and project setup.
+
+It contains elements of **How-to guides** and **Explanations**.
+
+### Use cases
+
+[Use cases](/docs/use_cases/) are guides that are meant to show how to use LangChain to accomplish a specific task (RAG, information extraction, etc.).
+The quickstarts should be good entrypoints for first-time LangChain developers who prefer to learn by getting something practical prototyped,
+then taking the pieces apart retrospectively. These should mirror what LangChain is good at.
+
+The quickstart pages here should fit the **How-to guide** category, with the other pages intended to be **Explanations** of more
+in-depth concepts and strategies that accompany the main happy paths.
+
+:::note
+The below sections are listed roughly in order of increasing level of abstraction.
+:::
+
+### Expression Language
+
+[LangChain Expression Language (LCEL)](/docs/expression_language/) is the fundamental way that most LangChain components fit together, and this section is designed to teach
+developers how to use it to build with LangChain's primitives effectively.
+
+This section should contains **Tutorials** that teach how to stream and use LCEL primitives for more abstract tasks, **Explanations** of specific behaviors,
+and some **References** for how to use different methods in the Runnable interface.
+
+### Components
+
+The [components section](/docs/modules) covers concepts one level of abstraction higher than LCEL.
+Abstract base classes like `BaseChatModel` and `BaseRetriever` should be covered here, as well as core implementations of these base classes,
+such as `ChatPromptTemplate` and `RecursiveCharacterTextSplitter`. Customization guides belong here too.
+
+This section should contain mostly conceptual **Tutorials**, **References**, and **Explanations** of the components they cover.
+
+:::note
+As a general rule of thumb, everything covered in the `Expression Language` and `Components` sections (with the exception of the `Composition` section of components) should
+cover only components that exist in `langchain_core`.
+:::
+
+### Integrations
+
+The [integrations](/docs/integrations/platforms/) are specific implementations of components. These often involve third-party APIs and services.
+If this is the case, as a general rule, these are maintained by the third-party partner.
+
+This section should contain mostly **Explanations** and **References**, though the actual content here is more flexible than other sections and more at the
+discretion of the third-party provider.
+
+:::note
+Concepts covered in `Integrations` should generally exist in `langchain_community` or specific partner packages.
+:::
+
+### Guides and Ecosystem
+
+The [Guides](/docs/guides) and [Ecosystem](/docs/langsmith/) sections should contain guides that address higher-level problems than the sections above.
+This includes, but is not limited to, considerations around productionization and development workflows.
+
+These should contain mostly **How-to guides**, **Explanations**, and **Tutorials**.
+
+### API references
+
+LangChain's API references. Should act as **References** (as the name implies) with some **Explanation**-focused content as well. 
+
+## Sample developer journey
+
+We have set up our docs to assist a new developer to LangChain. Let's walk through the intended path:
+
+- The developer lands on https://python.langchain.com, and reads through the introduction and the diagram.
+- If they are just curious, they may be drawn to the [Quickstart](/docs/get_started/quickstart) to get a high-level tour of what LangChain contains.
+- If they have a specific task in mind that they want to accomplish, they will be drawn to the Use-Case section. The use-case should provide a good, concrete hook that shows the value LangChain can provide them and be a good entrypoint to the framework.
+- They can then move to learn more about the fundamentals of LangChain through the Expression Language sections.
+- Next, they can learn about LangChain's various components and integrations.
+- Finally, they can get additional knowledge through the Guides.
+
+This is only an ideal of course - sections will inevitably reference lower or higher-level concepts that are documented in other sections.
+
+## Guidelines
 
 Here are some other guidelines you should think about when writing and organizing documentation.
 
-We generally do not merge new tutorials from outside contributors without an actue need.
-We welcome updates as well as new integration docs, how-tos, and references.
-
-### Avoid duplication
-
-Multiple pages that cover the same material in depth are difficult to maintain and cause confusion. There should
-be only one (very rarely two), canonical pages for a given concept or feature. Instead, you should link to other guides.
-
-### Link to other sections
+### Linking to other sections
 
 Because sections of the docs do not exist in a vacuum, it is important to link to other sections as often as possible
 to allow a developer to learn more about an unfamiliar topic inline.
 
 This includes linking to the API references as well as conceptual sections!
 
-### Be concise
+### Conciseness
 
 In general, take a less-is-more approach. If a section with a good explanation of a concept already exists, you should link to it rather than
 re-explain it, unless the concept you are documenting presents some new wrinkle.
@@ -149,10 +130,9 @@ Be concise, including in code samples.
 
 ### General style
 
-- Use active voice and present tense whenever possible
-- Use examples and code snippets to illustrate concepts and usage
-- Use appropriate header levels (`#`, `##`, `###`, etc.) to organize the content hierarchically
-- Use fewer cells with more code to make copy/paste easier
-- Use bullet points and numbered lists to break down information into easily digestible chunks
-- Use tables (especially for **Reference** sections) and diagrams often to present information visually
-- Include the table of contents for longer documentation pages to help readers navigate the content, but hide it for shorter pages
+- Use active voice and present tense whenever possible.
+- Use examples and code snippets to illustrate concepts and usage.
+- Use appropriate header levels (`#`, `##`, `###`, etc.) to organize the content hierarchically.
+- Use bullet points and numbered lists to break down information into easily digestible chunks.
+- Use tables (especially for **Reference** sections) and diagrams often to present information visually.
+- Include the table of contents for longer documentation pages to help readers navigate the content, but hide it for shorter pages.

docs/docs/contributing/documentation/technical_logistics.mdx

@@ -1,8 +1,4 @@
----
-sidebar_class_name: "hidden"
----
-
-# Setup
+# Technical logistics
 
 LangChain documentation consists of two components:
 
@@ -16,6 +12,8 @@ used to generate the externally facing [API Reference](https://api.python.langch
 The content for the API reference is autogenerated by scanning the docstrings in the codebase. For this reason we ask that
 developers document their code well.
 
+The main documentation is built using [Quarto](https://quarto.org) and [Docusaurus 2](https://docusaurus.io/).
+
 The `API Reference` is largely autogenerated by [sphinx](https://www.sphinx-doc.org/en/master/)
 from the code and is hosted by [Read the Docs](https://readthedocs.org/).
 
@@ -31,7 +29,7 @@ The content for the main documentation is located in the `/docs` directory of th
 
 The documentation is written using a combination of ipython notebooks (`.ipynb` files)
 and markdown (`.mdx` files). The notebooks are converted to markdown
-and then built using [Docusaurus 2](https://docusaurus.io/).
+using [Quarto](https://quarto.org) and then built using [Docusaurus 2](https://docusaurus.io/).
 
 Feel free to make contributions to the main documentation! 🥰
 
@@ -50,6 +48,10 @@ locally to ensure that it looks good and is free of errors.
 If you're unable to build it locally that's okay as well, as you will be able to
 see a preview of the documentation on the pull request page.
 
+### Install dependencies
+
+- [Quarto](https://quarto.org) - package that converts Jupyter notebooks (`.ipynb` files) into mdx files for serving in Docusaurus. [Download link](https://quarto.org/docs/download/).
+
 From the **monorepo root**, run the following command to install the dependencies:
 
 ```bash
@@ -76,18 +78,6 @@ make docs_build
 make api_docs_build
 ```
 
-:::tip
-
-The `make api_docs_build` command takes a long time. If you're making cosmetic changes to the API docs and want to see how they look, use:
-
-```bash
-make api_docs_quick_preview
-```
-
-which will just build a small subset of the API reference.
-
-:::
-
 Finally, run the link checker to ensure all links are valid:
 
 ```bash

docs/docs/contributing/index.mdx

@@ -12,8 +12,8 @@ As an open-source project in a rapidly developing field, we are extremely open t
 
 There are many ways to contribute to LangChain. Here are some common ways people contribute:
 
-- [**Documentation**](/docs/contributing/documentation/): Help improve our docs, including this one!
-- [**Code**](/docs/contributing/code/): Help us write code, fix bugs, or improve our infrastructure.
+- [**Documentation**](/docs/contributing/documentation/style_guide): Help improve our docs, including this one!
+- [**Code**](./code.mdx): Help us write code, fix bugs, or improve our infrastructure.
 - [**Integrations**](integrations.mdx): Help us integrate with your favorite vendors and tools.
 - [**Discussions**](https://github.com/langchain-ai/langchain/discussions): Help answer usage questions and discuss issues with users.
 
@@ -48,7 +48,7 @@ In a similar vein, we do enforce certain linting, formatting, and documentation
 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.
 
-### 🌟 Recognition
+# 🌟 Recognition
 
 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 through another means.
+If you have a Twitter account you would like us to mention, please let us know in the PR or through another means.

docs/docs/contributing/integrations.mdx

@@ -1,7 +1,6 @@
 ---
 sidebar_position: 5
 ---
-
 # Contribute Integrations
 
 To begin, make sure you have all the dependencies outlined in guide on [Contributing Code](/docs/contributing/code/).
@@ -11,7 +10,7 @@ There are a few different places you can contribute integrations for LangChain:
 - **Community**: For lighter-weight integrations that are primarily maintained by LangChain and the Open Source Community.
 - **Partner Packages**: For independent packages that are co-maintained by LangChain and a partner.
 
-For the most part, **new integrations should be added to the Community package**. Partner packages require more maintenance as separate packages, so please confirm with the LangChain team before creating a new partner package.
+For the most part, new integrations should be added to the Community package. Partner packages require more maintenance as separate packages, so please confirm with the LangChain team before creating a new partner package.
 
 In the following sections, we'll walk through how to contribute to each of these packages from a fake company, `Parrot Link AI`.
 
@@ -60,10 +59,6 @@ And add documentation to:
 
 ## Partner package in LangChain repo
 
-:::caution
-Before starting a **partner** package, please confirm your intent with the LangChain team. Partner packages require more maintenance as separate packages, so we will close PRs that add new partner packages without prior discussion. See the above section for how to add a community integration.
-:::
-
 Partner packages can be hosted in the `LangChain` monorepo or in an external repo.
 
 Partner package in the `LangChain` repo is placed in `libs/partners/{partner}` 

docs/docs/contributing/repo_structure.mdx

@@ -6,8 +6,7 @@ sidebar_position: 0.5
 If you plan on contributing to LangChain code or documentation, it can be useful
 to understand the high level structure of the repository.
 
-LangChain is organized as a [monorepo](https://en.wikipedia.org/wiki/Monorepo) that contains multiple packages.
-You can check out our [installation guide](/docs/how_to/installation/) for more on how they fit together.
+LangChain is organized as a [monorep](https://en.wikipedia.org/wiki/Monorepo) that contains multiple packages.
 
 Here's the structure visualized as a tree:
 
@@ -16,22 +15,12 @@ Here's the structure visualized as a tree:
 ├── cookbook # Tutorials and examples
 ├── docs # Contains content for the documentation here: https://python.langchain.com/
 ├── libs
-│   ├── langchain
-│   │   ├── langchain
+│   ├── langchain # Main package
 │   │   ├── tests/unit_tests # Unit tests (present in each package not shown for brevity)
 │   │   ├── tests/integration_tests # Integration tests (present in each package not shown for brevity)
-│   ├── community # Third-party integrations
-│   │   ├── langchain-community
-│   ├── core # Base interfaces for key abstractions
-│   │   ├── langchain-core
-│   ├── experimental # Experimental components and chains
-│   │   ├── langchain-experimental
-|   ├── cli # Command line interface
-│   │   ├── langchain-cli
-│   ├── text-splitters
-│   │   ├── langchain-text-splitters
-│   ├── standard-tests
-│   │   ├── langchain-standard-tests
+│   ├── langchain-community # Third-party integrations
+│   ├── langchain-core # Base interfaces for key abstractions
+│   ├── langchain-experimental # Experimental components and chains
 │   ├── partners
 │       ├── langchain-partner-1
 │       ├── langchain-partner-2
@@ -52,7 +41,7 @@ There are other files in the root directory level, but their presence should be
 The `/docs` directory contains the content for the documentation that is shown
 at https://python.langchain.com/ and the associated API Reference https://api.python.langchain.com/en/latest/langchain_api_reference.html.
 
-See the [documentation](/docs/contributing/documentation/) guidelines to learn how to contribute to the documentation.
+See the [documentation](/docs/contributing/documentation/style_guide) guidelines to learn how to contribute to the documentation.
 
 ## Code
 
@@ -60,6 +49,6 @@ The `/libs` directory contains the code for the LangChain packages.
 
 To learn more about how to contribute code see the following guidelines:
 
-- [Code](/docs/contributing/code/): Learn how to develop in the LangChain codebase.
-- [Integrations](./integrations.mdx): Learn how to contribute to third-party integrations to `langchain-community` or to start a new partner package.
-- [Testing](./testing.mdx): Guidelines to learn how to write tests for the packages.
+- [Code](./code.mdx) Learn how to develop in the LangChain codebase.
+- [Integrations](./integrations.mdx) to learn how to contribute to third-party integrations to langchain-community or to start a new partner package.
+- [Testing](./testing.mdx) guidelines to learn how to write tests for the packages.

docs/docs/contributing/testing.mdx

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 6
+sidebar_position: 2
 ---
 
 # Testing

docs/docs/expression_language/cookbook/code_writing.ipynb

@@ -0,0 +1,139 @@
+{
+ "cells": [
+  {
+   "cell_type": "raw",
+   "id": "1e997ab7",
+   "metadata": {},
+   "source": [
+    "---\n",
+    "sidebar_class_name: hidden\n",
+    "---"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "f09fd305",
+   "metadata": {},
+   "source": [
+    "# Code writing\n",
+    "\n",
+    "Example of how to use LCEL to write Python code."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "0653c7c7",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "%pip install --upgrade --quiet  langchain-core langchain-experimental langchain-openai"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 1,
+   "id": "bd7c259a",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain_core.output_parsers import StrOutputParser\n",
+    "from langchain_core.prompts import (\n",
+    "    ChatPromptTemplate,\n",
+    ")\n",
+    "from langchain_experimental.utilities import PythonREPL\n",
+    "from langchain_openai import ChatOpenAI"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 12,
+   "id": "73795d2d",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "template = \"\"\"Write some python code to solve the user's problem. \n",
+    "\n",
+    "Return only python code in Markdown format, e.g.:\n",
+    "\n",
+    "```python\n",
+    "....\n",
+    "```\"\"\"\n",
+    "prompt = ChatPromptTemplate.from_messages([(\"system\", template), (\"human\", \"{input}\")])\n",
+    "\n",
+    "model = ChatOpenAI()"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 13,
+   "id": "42859e8a",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "def _sanitize_output(text: str):\n",
+    "    _, after = text.split(\"```python\")\n",
+    "    return after.split(\"```\")[0]"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 14,
+   "id": "5ded1a86",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "chain = prompt | model | StrOutputParser() | _sanitize_output | PythonREPL().run"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 15,
+   "id": "208c2b75",
+   "metadata": {},
+   "outputs": [
+    {
+     "name": "stderr",
+     "output_type": "stream",
+     "text": [
+      "Python REPL can execute arbitrary code. Use with caution.\n"
+     ]
+    },
+    {
+     "data": {
+      "text/plain": [
+       "'4\\n'"
+      ]
+     },
+     "execution_count": 15,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "chain.invoke({\"input\": \"whats 2 plus 2\"})"
+   ]
+  }
+ ],
+ "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.1"
+  }
+ },
+ "nbformat": 4,
+ "nbformat_minor": 5
+}

docs/docs/expression_language/cookbook/multiple_chains.ipynb

@@ -0,0 +1,267 @@
+{
+ "cells": [
+  {
+   "cell_type": "raw",
+   "id": "877102d1-02ea-4fa3-8ec7-a08e242b95b3",
+   "metadata": {},
+   "source": [
+    "---\n",
+    "sidebar_position: 2\n",
+    "title: Multiple chains\n",
+    "---"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "0f2bf8d3",
+   "metadata": {},
+   "source": [
+    "Runnables can easily be used to string together multiple Chains"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "id": "0f316b5c",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "%pip install --upgrade --quiet  langchain langchain-openai"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 4,
+   "id": "d65d4e9e",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "'El país donde se encuentra la ciudad de Honolulu, donde nació Barack Obama, el 44º Presidente de los Estados Unidos, es Estados Unidos. Honolulu se encuentra en la isla de Oahu, en el estado de Hawái.'"
+      ]
+     },
+     "execution_count": 4,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "from operator import itemgetter\n",
+    "\n",
+    "from langchain_core.output_parsers import StrOutputParser\n",
+    "from langchain_core.prompts import ChatPromptTemplate\n",
+    "from langchain_openai import ChatOpenAI\n",
+    "\n",
+    "prompt1 = ChatPromptTemplate.from_template(\"what is the city {person} is from?\")\n",
+    "prompt2 = ChatPromptTemplate.from_template(\n",
+    "    \"what country is the city {city} in? respond in {language}\"\n",
+    ")\n",
+    "\n",
+    "model = ChatOpenAI()\n",
+    "\n",
+    "chain1 = prompt1 | model | StrOutputParser()\n",
+    "\n",
+    "chain2 = (\n",
+    "    {\"city\": chain1, \"language\": itemgetter(\"language\")}\n",
+    "    | prompt2\n",
+    "    | model\n",
+    "    | StrOutputParser()\n",
+    ")\n",
+    "\n",
+    "chain2.invoke({\"person\": \"obama\", \"language\": \"spanish\"})"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 8,
+   "id": "878f8176",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain_core.runnables import RunnablePassthrough\n",
+    "\n",
+    "prompt1 = ChatPromptTemplate.from_template(\n",
+    "    \"generate a {attribute} color. Return the name of the color and nothing else:\"\n",
+    ")\n",
+    "prompt2 = ChatPromptTemplate.from_template(\n",
+    "    \"what is a fruit of color: {color}. Return the name of the fruit and nothing else:\"\n",
+    ")\n",
+    "prompt3 = ChatPromptTemplate.from_template(\n",
+    "    \"what is a country with a flag that has the color: {color}. Return the name of the country and nothing else:\"\n",
+    ")\n",
+    "prompt4 = ChatPromptTemplate.from_template(\n",
+    "    \"What is the color of {fruit} and the flag of {country}?\"\n",
+    ")\n",
+    "\n",
+    "model_parser = model | StrOutputParser()\n",
+    "\n",
+    "color_generator = (\n",
+    "    {\"attribute\": RunnablePassthrough()} | prompt1 | {\"color\": model_parser}\n",
+    ")\n",
+    "color_to_fruit = prompt2 | model_parser\n",
+    "color_to_country = prompt3 | model_parser\n",
+    "question_generator = (\n",
+    "    color_generator | {\"fruit\": color_to_fruit, \"country\": color_to_country} | prompt4\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 9,
+   "id": "d621a870",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "ChatPromptValue(messages=[HumanMessage(content='What is the color of strawberry and the flag of China?', additional_kwargs={}, example=False)])"
+      ]
+     },
+     "execution_count": 9,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "question_generator.invoke(\"warm\")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 10,
+   "id": "b4a9812b-bead-4fd9-ae27-0b8be57e5dc1",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "AIMessage(content='The color of an apple is typically red or green. The flag of China is predominantly red with a large yellow star in the upper left corner and four smaller yellow stars surrounding it.', additional_kwargs={}, example=False)"
+      ]
+     },
+     "execution_count": 10,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "prompt = question_generator.invoke(\"warm\")\n",
+    "model.invoke(prompt)"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "6d75a313-f1c8-4e94-9a17-24e0bf4a2bdc",
+   "metadata": {},
+   "source": [
+    "### Branching and Merging\n",
+    "\n",
+    "You may want the output of one component to be processed by 2 or more other components. [RunnableParallels](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.base.RunnableParallel.html#langchain_core.runnables.base.RunnableParallel) let you split or fork the chain so multiple components can process the input in parallel. Later, other components can join or merge the results to synthesize a final response. This type of chain creates a computation graph that looks like the following:\n",
+    "\n",
+    "```text\n",
+    "     Input\n",
+    "      / \\\n",
+    "     /   \\\n",
+    " Branch1 Branch2\n",
+    "     \\   /\n",
+    "      \\ /\n",
+    "      Combine\n",
+    "```"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 11,
+   "id": "247fa0bd-4596-4063-8cb3-1d7fc119d982",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "planner = (\n",
+    "    ChatPromptTemplate.from_template(\"Generate an argument about: {input}\")\n",
+    "    | ChatOpenAI()\n",
+    "    | StrOutputParser()\n",
+    "    | {\"base_response\": RunnablePassthrough()}\n",
+    ")\n",
+    "\n",
+    "arguments_for = (\n",
+    "    ChatPromptTemplate.from_template(\n",
+    "        \"List the pros or positive aspects of {base_response}\"\n",
+    "    )\n",
+    "    | ChatOpenAI()\n",
+    "    | StrOutputParser()\n",
+    ")\n",
+    "arguments_against = (\n",
+    "    ChatPromptTemplate.from_template(\n",
+    "        \"List the cons or negative aspects of {base_response}\"\n",
+    "    )\n",
+    "    | ChatOpenAI()\n",
+    "    | StrOutputParser()\n",
+    ")\n",
+    "\n",
+    "final_responder = (\n",
+    "    ChatPromptTemplate.from_messages(\n",
+    "        [\n",
+    "            (\"ai\", \"{original_response}\"),\n",
+    "            (\"human\", \"Pros:\\n{results_1}\\n\\nCons:\\n{results_2}\"),\n",
+    "            (\"system\", \"Generate a final response given the critique\"),\n",
+    "        ]\n",
+    "    )\n",
+    "    | ChatOpenAI()\n",
+    "    | StrOutputParser()\n",
+    ")\n",
+    "\n",
+    "chain = (\n",
+    "    planner\n",
+    "    | {\n",
+    "        \"results_1\": arguments_for,\n",
+    "        \"results_2\": arguments_against,\n",
+    "        \"original_response\": itemgetter(\"base_response\"),\n",
+    "    }\n",
+    "    | final_responder\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 12,
+   "id": "2564f310-0674-4bb1-9c4e-d7848ca73511",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "'While Scrum has its potential cons and challenges, many organizations have successfully embraced and implemented this project management framework to great effect. The cons mentioned above can be mitigated or overcome with proper training, support, and a commitment to continuous improvement. It is also important to note that not all cons may be applicable to every organization or project.\\n\\nFor example, while Scrum may be complex initially, with proper training and guidance, teams can quickly grasp the concepts and practices. The lack of predictability can be mitigated by implementing techniques such as velocity tracking and release planning. The limited documentation can be addressed by maintaining a balance between lightweight documentation and clear communication among team members. The dependency on team collaboration can be improved through effective communication channels and regular team-building activities.\\n\\nScrum can be scaled and adapted to larger projects by using frameworks like Scrum of Scrums or LeSS (Large Scale Scrum). Concerns about speed versus quality can be addressed by incorporating quality assurance practices, such as continuous integration and automated testing, into the Scrum process. Scope creep can be managed by having a well-defined and prioritized product backlog, and a strong product owner can be developed through training and mentorship.\\n\\nResistance to change can be overcome by providing proper education and communication to stakeholders and involving them in the decision-making process. Ultimately, the cons of Scrum can be seen as opportunities for growth and improvement, and with the right mindset and support, they can be effectively managed.\\n\\nIn conclusion, while Scrum may have its challenges and potential cons, the benefits and advantages it offers in terms of collaboration, flexibility, adaptability, transparency, and customer satisfaction make it a widely adopted and successful project management framework. With proper implementation and continuous improvement, organizations can leverage Scrum to drive innovation, efficiency, and project success.'"
+      ]
+     },
+     "execution_count": 12,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "chain.invoke({\"input\": \"scrum\"})"
+   ]
+  }
+ ],
+ "metadata": {
+  "kernelspec": {
+   "display_name": "poetry-venv",
+   "language": "python",
+   "name": "poetry-venv"
+  },
+  "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/docs/expression_language/cookbook/prompt_llm_parser.ipynb

@@ -0,0 +1,436 @@
+{
+ "cells": [
+  {
+   "cell_type": "raw",
+   "id": "abf7263d-3a62-4016-b5d5-b157f92f2070",
+   "metadata": {},
+   "source": [
+    "---\n",
+    "sidebar_position: 0\n",
+    "title: Prompt + LLM\n",
+    "---\n"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "9a434f2b-9405-468c-9dfd-254d456b57a6",
+   "metadata": {},
+   "source": [
+    "The most common and valuable composition is taking:\n",
+    "\n",
+    "``PromptTemplate`` / ``ChatPromptTemplate`` -> ``LLM`` / ``ChatModel`` -> ``OutputParser``\n",
+    "\n",
+    "Almost any other chains you build will use this building block."
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "93aa2c87",
+   "metadata": {},
+   "source": [
+    "## PromptTemplate + LLM\n",
+    "\n",
+    "The simplest composition is just combining a prompt and model to create a chain that takes user input, adds it to a prompt, passes it to a model, and returns the raw model output.\n",
+    "\n",
+    "Note, you can mix and match PromptTemplate/ChatPromptTemplates and LLMs/ChatModels as you like here."
+   ]
+  },
+  {
+   "cell_type": "raw",
+   "id": "ef79a54b",
+   "metadata": {},
+   "source": [
+    "%pip install --upgrade --quiet  langchain langchain-openai"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 1,
+   "id": "466b65b3",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain_core.prompts import ChatPromptTemplate\n",
+    "from langchain_openai import ChatOpenAI\n",
+    "\n",
+    "prompt = ChatPromptTemplate.from_template(\"tell me a joke about {foo}\")\n",
+    "model = ChatOpenAI()\n",
+    "chain = prompt | model"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 2,
+   "id": "e3d0a6cd",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "AIMessage(content=\"Why don't bears wear shoes?\\n\\nBecause they have bear feet!\", additional_kwargs={}, example=False)"
+      ]
+     },
+     "execution_count": 2,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "chain.invoke({\"foo\": \"bears\"})"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "7eb9ef50",
+   "metadata": {},
+   "source": [
+    "Often times we want to attach kwargs that'll be passed to each model call. Here are a few examples of that:"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "0b1d8f88",
+   "metadata": {},
+   "source": [
+    "### Attaching Stop Sequences"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 3,
+   "id": "562a06bf",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "chain = prompt | model.bind(stop=[\"\\n\"])"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 4,
+   "id": "43f5d04c",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "AIMessage(content='Why did the bear never wear shoes?', additional_kwargs={}, example=False)"
+      ]
+     },
+     "execution_count": 4,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "chain.invoke({\"foo\": \"bears\"})"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "f3eaf88a",
+   "metadata": {},
+   "source": [
+    "### Attaching Function Call information"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 5,
+   "id": "f94b71b2",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "functions = [\n",
+    "    {\n",
+    "        \"name\": \"joke\",\n",
+    "        \"description\": \"A joke\",\n",
+    "        \"parameters\": {\n",
+    "            \"type\": \"object\",\n",
+    "            \"properties\": {\n",
+    "                \"setup\": {\"type\": \"string\", \"description\": \"The setup for the joke\"},\n",
+    "                \"punchline\": {\n",
+    "                    \"type\": \"string\",\n",
+    "                    \"description\": \"The punchline for the joke\",\n",
+    "                },\n",
+    "            },\n",
+    "            \"required\": [\"setup\", \"punchline\"],\n",
+    "        },\n",
+    "    }\n",
+    "]\n",
+    "chain = prompt | model.bind(function_call={\"name\": \"joke\"}, functions=functions)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 6,
+   "id": "decf7710",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "AIMessage(content='', additional_kwargs={'function_call': {'name': 'joke', 'arguments': '{\\n  \"setup\": \"Why don\\'t bears wear shoes?\",\\n  \"punchline\": \"Because they have bear feet!\"\\n}'}}, example=False)"
+      ]
+     },
+     "execution_count": 6,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "chain.invoke({\"foo\": \"bears\"}, config={})"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "9098c5ed",
+   "metadata": {},
+   "source": [
+    "## PromptTemplate + LLM + OutputParser\n",
+    "\n",
+    "We can also add in an output parser to easily transform the raw LLM/ChatModel output into a more workable format"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 7,
+   "id": "cc194c78",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain_core.output_parsers import StrOutputParser\n",
+    "\n",
+    "chain = prompt | model | StrOutputParser()"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "77acf448",
+   "metadata": {},
+   "source": [
+    "Notice that this now returns a string - a much more workable format for downstream tasks"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 8,
+   "id": "e3d69a18",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "\"Why don't bears wear shoes?\\n\\nBecause they have bear feet!\""
+      ]
+     },
+     "execution_count": 8,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "chain.invoke({\"foo\": \"bears\"})"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "c01864e5",
+   "metadata": {},
+   "source": [
+    "### Functions Output Parser\n",
+    "\n",
+    "When you specify the function to return, you may just want to parse that directly"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 9,
+   "id": "ad0dd88e",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain.output_parsers.openai_functions import JsonOutputFunctionsParser\n",
+    "\n",
+    "chain = (\n",
+    "    prompt\n",
+    "    | model.bind(function_call={\"name\": \"joke\"}, functions=functions)\n",
+    "    | JsonOutputFunctionsParser()\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 10,
+   "id": "1e7aa8eb",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "{'setup': \"Why don't bears like fast food?\",\n",
+       " 'punchline': \"Because they can't catch it!\"}"
+      ]
+     },
+     "execution_count": 10,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "chain.invoke({\"foo\": \"bears\"})"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 11,
+   "id": "d4aa1a01",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain.output_parsers.openai_functions import JsonKeyOutputFunctionsParser\n",
+    "\n",
+    "chain = (\n",
+    "    prompt\n",
+    "    | model.bind(function_call={\"name\": \"joke\"}, functions=functions)\n",
+    "    | JsonKeyOutputFunctionsParser(key_name=\"setup\")\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 12,
+   "id": "8b6df9ba",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "\"Why don't bears wear shoes?\""
+      ]
+     },
+     "execution_count": 12,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "chain.invoke({\"foo\": \"bears\"})"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "023fbccb-ef7d-489e-a9ba-f98e17283d51",
+   "metadata": {},
+   "source": [
+    "## Simplifying input\n",
+    "\n",
+    "To make invocation even simpler, we can add a `RunnableParallel` to take care of creating the prompt input dict for us:"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 13,
+   "id": "9601c0f0-71f9-4bd4-a672-7bd04084b018",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain_core.runnables import RunnableParallel, RunnablePassthrough\n",
+    "\n",
+    "map_ = RunnableParallel(foo=RunnablePassthrough())\n",
+    "chain = (\n",
+    "    map_\n",
+    "    | prompt\n",
+    "    | model.bind(function_call={\"name\": \"joke\"}, functions=functions)\n",
+    "    | JsonKeyOutputFunctionsParser(key_name=\"setup\")\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 14,
+   "id": "7ec4f154-fda5-4847-9220-41aa902fdc33",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "\"Why don't bears wear shoes?\""
+      ]
+     },
+     "execution_count": 14,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "chain.invoke(\"bears\")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "def00bfe-0f83-4805-8c8f-8a53f99fa8ea",
+   "metadata": {},
+   "source": [
+    "Since we're composing our map with another Runnable, we can even use some syntactic sugar and just use a dict:"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 21,
+   "id": "7bf3846a-02ee-41a3-ba1b-a708827d4f3a",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "chain = (\n",
+    "    {\"foo\": RunnablePassthrough()}\n",
+    "    | prompt\n",
+    "    | model.bind(function_call={\"name\": \"joke\"}, functions=functions)\n",
+    "    | JsonKeyOutputFunctionsParser(key_name=\"setup\")\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 22,
+   "id": "e566d6a1-538d-4cb5-a210-a63e082e4c74",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "\"Why don't bears like fast food?\""
+      ]
+     },
+     "execution_count": 22,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "chain.invoke(\"bears\")"
+   ]
+  }
+ ],
+ "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/docs/expression_language/get_started.ipynb

@@ -0,0 +1,537 @@
+{
+ "cells": [
+  {
+   "cell_type": "raw",
+   "id": "366a0e68-fd67-4fe5-a292-5c33733339ea",
+   "metadata": {},
+   "source": [
+    "---\n",
+    "sidebar_position: 0\n",
+    "title: Get started\n",
+    "keywords: [chain.invoke]\n",
+    "---"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "befa7fd1",
+   "metadata": {},
+   "source": [
+    "LCEL makes it easy to build complex chains from basic components, and supports out of the box functionality such as streaming, parallelism, and logging."
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "9a9acd2e",
+   "metadata": {},
+   "source": [
+    "## Basic example: prompt + model + output parser\n",
+    "\n",
+    "The most basic and common use case is chaining a prompt template and a model together. To see how this works, let's create a chain that takes a topic and generates a joke:"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "278b0027",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "%pip install --upgrade --quiet  langchain-core langchain-community langchain-openai"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "c3d54f72",
+   "metadata": {},
+   "source": [
+    "```{=mdx}\n",
+    "import ChatModelTabs from \"@theme/ChatModelTabs\";\n",
+    "\n",
+    "<ChatModelTabs openaiParams={`model=\"gpt-4\"`} />\n",
+    "```"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "f9eed8e8",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "# | output: false\n",
+    "# | echo: false\n",
+    "\n",
+    "from langchain_openai import ChatOpenAI\n",
+    "\n",
+    "model = ChatOpenAI(model=\"gpt-4\")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 1,
+   "id": "466b65b3",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "\"Why don't ice creams ever get invited to parties?\\n\\nBecause they always drip when things heat up!\""
+      ]
+     },
+     "execution_count": 1,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "from langchain_core.output_parsers import StrOutputParser\n",
+    "from langchain_core.prompts import ChatPromptTemplate\n",
+    "\n",
+    "prompt = ChatPromptTemplate.from_template(\"tell me a short joke about {topic}\")\n",
+    "output_parser = StrOutputParser()\n",
+    "\n",
+    "chain = prompt | model | output_parser\n",
+    "\n",
+    "chain.invoke({\"topic\": \"ice cream\"})"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "81c502c5-85ee-4f36-aaf4-d6e350b7792f",
+   "metadata": {},
+   "source": [
+    "Notice this line of the code, where we piece together these different components into a single chain using LCEL:\n",
+    "\n",
+    "```\n",
+    "chain = prompt | model | output_parser\n",
+    "```\n",
+    "\n",
+    "The `|` symbol is similar to a [unix pipe operator](https://en.wikipedia.org/wiki/Pipeline_(Unix)), which chains together the different components, feeding the output from one component as input into the next component. \n",
+    "\n",
+    "In this chain the user input is passed to the prompt template, then the prompt template output is passed to the model, then the model output is passed to the output parser. Let's take a look at each component individually to really understand what's going on."
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "aa1b77fa",
+   "metadata": {},
+   "source": [
+    "### 1. Prompt\n",
+    "\n",
+    "`prompt` is a `BasePromptTemplate`, which means it takes in a dictionary of template variables and produces a `PromptValue`. A `PromptValue` is a wrapper around a completed prompt that can be passed to either an `LLM` (which takes a string as input) or `ChatModel` (which takes a sequence of messages as input). It can work with either language model type because it defines logic both for producing `BaseMessage`s and for producing a string."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 2,
+   "id": "b8656990",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "ChatPromptValue(messages=[HumanMessage(content='tell me a short joke about ice cream')])"
+      ]
+     },
+     "execution_count": 2,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "prompt_value = prompt.invoke({\"topic\": \"ice cream\"})\n",
+    "prompt_value"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 3,
+   "id": "e6034488",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "[HumanMessage(content='tell me a short joke about ice cream')]"
+      ]
+     },
+     "execution_count": 3,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "prompt_value.to_messages()"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 4,
+   "id": "60565463",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "'Human: tell me a short joke about ice cream'"
+      ]
+     },
+     "execution_count": 4,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "prompt_value.to_string()"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "577f0f76",
+   "metadata": {},
+   "source": [
+    "### 2. Model\n",
+    "\n",
+    "The `PromptValue` is then passed to `model`. In this case our `model` is a `ChatModel`, meaning it will output a `BaseMessage`."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 5,
+   "id": "33cf5f72",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "AIMessage(content=\"Why don't ice creams ever get invited to parties?\\n\\nBecause they always bring a melt down!\")"
+      ]
+     },
+     "execution_count": 5,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "message = model.invoke(prompt_value)\n",
+    "message"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "327e7db8",
+   "metadata": {},
+   "source": [
+    "If our `model` was an `LLM`, it would output a string."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 6,
+   "id": "8feb05da",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "'\\n\\nRobot: Why did the ice cream truck break down? Because it had a meltdown!'"
+      ]
+     },
+     "execution_count": 6,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "from langchain_openai import OpenAI\n",
+    "\n",
+    "llm = OpenAI(model=\"gpt-3.5-turbo-instruct\")\n",
+    "llm.invoke(prompt_value)"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "91847478",
+   "metadata": {},
+   "source": [
+    "### 3. Output parser\n",
+    "\n",
+    "And lastly we pass our `model` output to the `output_parser`, which is a `BaseOutputParser` meaning it takes either a string or a \n",
+    "`BaseMessage` as input. The specific `StrOutputParser` simply converts any input into a string."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 13,
+   "id": "533e59a8",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "\"Why did the ice cream go to therapy? \\n\\nBecause it had too many toppings and couldn't find its cone-fidence!\""
+      ]
+     },
+     "execution_count": 13,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "output_parser.invoke(message)"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "9851e842",
+   "metadata": {},
+   "source": [
+    "### 4. Entire Pipeline\n",
+    "\n",
+    "To follow the steps along:\n",
+    "\n",
+    "1. We pass in user input on the desired topic as `{\"topic\": \"ice cream\"}`\n",
+    "2. The `prompt` component takes the user input, which is then used to construct a PromptValue after using the `topic` to construct the prompt. \n",
+    "3. The `model` component takes the generated prompt, and passes into the OpenAI LLM model for evaluation. The generated output from the model is a `ChatMessage` object. \n",
+    "4. Finally, the `output_parser` component takes in a `ChatMessage`, and transforms this into a Python string, which is returned from the invoke method. \n"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "c4873109",
+   "metadata": {},
+   "source": [
+    "```mermaid\n",
+    "graph LR\n",
+    "    A(Input: topic=ice cream) --> |Dict| B(PromptTemplate)\n",
+    "    B -->|PromptValue| C(ChatModel)    \n",
+    "    C -->|ChatMessage| D(StrOutputParser)\n",
+    "    D --> |String| F(Result)\n",
+    "```\n"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "fe63534d",
+   "metadata": {},
+   "source": [
+    ":::info\n",
+    "\n",
+    "Note that if you’re curious about the output of any components, you can always test out a smaller version of the chain such as `prompt` or `prompt | model` to see the intermediate results:\n",
+    "\n",
+    ":::"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "11089b6f-23f8-474f-97ec-8cae8d0ca6d4",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "input = {\"topic\": \"ice cream\"}\n",
+    "\n",
+    "prompt.invoke(input)\n",
+    "# > ChatPromptValue(messages=[HumanMessage(content='tell me a short joke about ice cream')])\n",
+    "\n",
+    "(prompt | model).invoke(input)\n",
+    "# > AIMessage(content=\"Why did the ice cream go to therapy?\\nBecause it had too many toppings and couldn't cone-trol itself!\")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "cc7d3b9d-e400-4c9b-9188-f29dac73e6bb",
+   "metadata": {},
+   "source": [
+    "## RAG Search Example\n",
+    "\n",
+    "For our next example, we want to run a retrieval-augmented generation chain to add some context when responding to questions."
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "b8fe8eb4",
+   "metadata": {},
+   "source": [
+    "```{=mdx}\n",
+    "<ChatModelTabs />\n",
+    "```"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "662426e8-4316-41dc-8312-9b58edc7e0c9",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "# Requires:\n",
+    "# pip install langchain docarray tiktoken\n",
+    "\n",
+    "from langchain_community.vectorstores import DocArrayInMemorySearch\n",
+    "from langchain_core.output_parsers import StrOutputParser\n",
+    "from langchain_core.prompts import ChatPromptTemplate\n",
+    "from langchain_core.runnables import RunnableParallel, RunnablePassthrough\n",
+    "from langchain_openai import OpenAIEmbeddings\n",
+    "\n",
+    "vectorstore = DocArrayInMemorySearch.from_texts(\n",
+    "    [\"harrison worked at kensho\", \"bears like to eat honey\"],\n",
+    "    embedding=OpenAIEmbeddings(),\n",
+    ")\n",
+    "retriever = vectorstore.as_retriever()\n",
+    "\n",
+    "template = \"\"\"Answer the question based only on the following context:\n",
+    "{context}\n",
+    "\n",
+    "Question: {question}\n",
+    "\"\"\"\n",
+    "prompt = ChatPromptTemplate.from_template(template)\n",
+    "output_parser = StrOutputParser()\n",
+    "\n",
+    "setup_and_retrieval = RunnableParallel(\n",
+    "    {\"context\": retriever, \"question\": RunnablePassthrough()}\n",
+    ")\n",
+    "chain = setup_and_retrieval | prompt | model | output_parser\n",
+    "\n",
+    "chain.invoke(\"where did harrison work?\")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "f0999140-6001-423b-970b-adf1dfdb4dec",
+   "metadata": {},
+   "source": [
+    "In this case, the composed chain is: "
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "5b88e9bb-f04a-4a56-87ec-19a0e6350763",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "chain = setup_and_retrieval | prompt | model | output_parser"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "6e929e15-40a5-4569-8969-384f636cab87",
+   "metadata": {},
+   "source": [
+    "To explain this, we first can see that the prompt template above takes in `context` and `question` as values to be substituted in the prompt. Before building the prompt template, we want to retrieve relevant documents to the search and include them as part of the context. \n",
+    "\n",
+    "As a preliminary step, we’ve setup the retriever using an in memory store, which can retrieve documents based on a query. This is a runnable component as well that can be chained together with other components, but you can also try to run it separately:"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "a7319ef6-613b-4638-ad7d-4a2183702c1d",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "retriever.invoke(\"where did harrison work?\")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "e6833844-f1c4-444c-a3d2-31b3c6b31d46",
+   "metadata": {},
+   "source": [
+    "We then use the `RunnableParallel` to prepare the expected inputs into the prompt by using the entries for the retrieved documents as well as the original user question, using the retriever for document search, and `RunnablePassthrough` to pass the user’s question:"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "dcbca26b-d6b9-4c24-806c-1ec8fdaab4ed",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "setup_and_retrieval = RunnableParallel(\n",
+    "    {\"context\": retriever, \"question\": RunnablePassthrough()}\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "68c721c1-048b-4a64-9d78-df54fe465992",
+   "metadata": {},
+   "source": [
+    "To review, the complete chain is:"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "1d5115a7-7b8e-458b-b936-26cc87ee81c4",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "setup_and_retrieval = RunnableParallel(\n",
+    "    {\"context\": retriever, \"question\": RunnablePassthrough()}\n",
+    ")\n",
+    "chain = setup_and_retrieval | prompt | model | output_parser"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "5c6f5f74-b387-48a0-bedd-1fae202cd10a",
+   "metadata": {},
+   "source": [
+    "With the flow being:\n",
+    "\n",
+    "1. The first steps create a `RunnableParallel` object with two entries.  The first entry, `context` will include the document results fetched by the retriever. The second entry, `question` will contain the user’s original question. To pass on the question, we use `RunnablePassthrough` to copy this entry. \n",
+    "2. Feed the dictionary from the step above to the `prompt` component. It then takes the user input which is `question` as well as the retrieved document which is `context` to construct a prompt and output a PromptValue. \n",
+    "3. The `model` component takes the generated prompt, and passes into the OpenAI LLM model for evaluation. The generated output from the model is a `ChatMessage` object. \n",
+    "4. Finally, the `output_parser` component takes in a `ChatMessage`, and transforms this into a Python string, which is returned from the invoke method.\n",
+    "\n",
+    "```mermaid\n",
+    "graph LR\n",
+    "    A(Question) --> B(RunnableParallel)\n",
+    "    B -->|Question| C(Retriever)\n",
+    "    B -->|Question| D(RunnablePassThrough)\n",
+    "    C -->|context=retrieved docs| E(PromptTemplate)\n",
+    "    D -->|question=Question| E\n",
+    "    E -->|PromptValue| F(ChatModel)    \n",
+    "    F -->|ChatMessage| G(StrOutputParser)\n",
+    "    G --> |String| H(Result)\n",
+    "```\n",
+    "\n"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "8c2438df-164e-4bbe-b5f4-461695e45b0f",
+   "metadata": {},
+   "source": [
+    "## Next steps\n",
+    "\n",
+    "We recommend reading our [Advantages of LCEL](/docs/expression_language/why) section next to see a side-by-side comparison of the code needed to produce common functionality with and without LCEL."
+   ]
+  }
+ ],
+ "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.11.0"
+  }
+ },
+ "nbformat": 4,
+ "nbformat_minor": 5
+}

docs/docs/expression_language/how_to/decorator.ipynb

@@ -0,0 +1,136 @@
+{
+ "cells": [
+  {
+   "cell_type": "markdown",
+   "id": "b45110ef",
+   "metadata": {},
+   "source": [
+    "# Create a runnable with the @chain decorator\n",
+    "\n",
+    "You can also turn an arbitrary function into a chain by adding a `@chain` decorator. This is functionally equivalent to wrapping in a [`RunnableLambda`](/docs/expression_language/primitives/functions).\n",
+    "\n",
+    "This will have the benefit of improved observability by tracing your chain correctly. Any calls to runnables inside this function will be traced as nested children.\n",
+    "\n",
+    "It will also allow you to use this as any other runnable, compose it in chain, etc.\n",
+    "\n",
+    "Let's take a look at this in action!"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "23b2b564",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "%pip install --upgrade --quiet  langchain langchain-openai"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 16,
+   "id": "d9370420",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain_core.output_parsers import StrOutputParser\n",
+    "from langchain_core.prompts import ChatPromptTemplate\n",
+    "from langchain_core.runnables import chain\n",
+    "from langchain_openai import ChatOpenAI"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 17,
+   "id": "b7f74f7e",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "prompt1 = ChatPromptTemplate.from_template(\"Tell me a joke about {topic}\")\n",
+    "prompt2 = ChatPromptTemplate.from_template(\"What is the subject of this joke: {joke}\")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 18,
+   "id": "2b0365c4",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "@chain\n",
+    "def custom_chain(text):\n",
+    "    prompt_val1 = prompt1.invoke({\"topic\": text})\n",
+    "    output1 = ChatOpenAI().invoke(prompt_val1)\n",
+    "    parsed_output1 = StrOutputParser().invoke(output1)\n",
+    "    chain2 = prompt2 | ChatOpenAI() | StrOutputParser()\n",
+    "    return chain2.invoke({\"joke\": parsed_output1})"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "904d6872",
+   "metadata": {},
+   "source": [
+    "`custom_chain` is now a runnable, meaning you will need to use `invoke`"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 21,
+   "id": "6448bdd3",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "'The subject of this joke is bears.'"
+      ]
+     },
+     "execution_count": 21,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "custom_chain.invoke(\"bears\")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "aa767ea9",
+   "metadata": {},
+   "source": [
+    "If you check out your LangSmith traces, you should see a `custom_chain` trace in there, with the calls to OpenAI nested underneath"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "f1245bdc",
+   "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.1"
+  }
+ },
+ "nbformat": 4,
+ "nbformat_minor": 5
+}

docs/docs/expression_language/how_to/inspect.ipynb

@@ -5,21 +5,11 @@
    "id": "8c5eb99a",
    "metadata": {},
    "source": [
-    "# How to inspect runnables\n",
+    "# Inspect your runnables\n",
     "\n",
-    ":::info Prerequisites\n",
+    "Once you create a runnable with LCEL, you may often want to inspect it to get a better sense for what is going on. This notebook covers some methods for doing so.\n",
     "\n",
-    "This guide assumes familiarity with the following concepts:\n",
-    "- [LangChain Expression Language (LCEL)](/docs/concepts/#langchain-expression-language)\n",
-    "- [Chaining runnables](/docs/how_to/sequence/)\n",
-    "\n",
-    ":::\n",
-    "\n",
-    "Once you create a runnable with [LangChain Expression Language](/docs/concepts/#langchain-expression-language), you may often want to inspect it to get a better sense for what is going on. This notebook covers some methods for doing so.\n",
-    "\n",
-    "This guide shows some ways you can programmatically introspect the internal steps of chains. If you are instead interested in debugging issues in your chain, see [this section](/docs/how_to/debugging) instead.\n",
-    "\n",
-    "First, let's create an example chain. We will create one that does retrieval:"
+    "First, let's create an example LCEL. We will create one that does retrieval"
    ]
   },
   {
@@ -29,7 +19,21 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "%pip install -qU langchain langchain-openai faiss-cpu tiktoken"
+    "%pip install --upgrade --quiet  langchain langchain-openai faiss-cpu tiktoken"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 1,
+   "id": "a88f4b24",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain_community.vectorstores import FAISS\n",
+    "from langchain_core.output_parsers import StrOutputParser\n",
+    "from langchain_core.prompts import ChatPromptTemplate\n",
+    "from langchain_core.runnables import RunnablePassthrough\n",
+    "from langchain_openai import ChatOpenAI, OpenAIEmbeddings"
    ]
   },
   {
@@ -39,12 +43,6 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "from langchain_community.vectorstores import FAISS\n",
-    "from langchain_core.output_parsers import StrOutputParser\n",
-    "from langchain_core.prompts import ChatPromptTemplate\n",
-    "from langchain_core.runnables import RunnablePassthrough\n",
-    "from langchain_openai import ChatOpenAI, OpenAIEmbeddings\n",
-    "\n",
     "vectorstore = FAISS.from_texts(\n",
     "    [\"harrison worked at kensho\"], embedding=OpenAIEmbeddings()\n",
     ")\n",
@@ -57,8 +55,16 @@
     "\"\"\"\n",
     "prompt = ChatPromptTemplate.from_template(template)\n",
     "\n",
-    "model = ChatOpenAI()\n",
-    "\n",
+    "model = ChatOpenAI()"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 3,
+   "id": "70e3fe93",
+   "metadata": {},
+   "outputs": [],
+   "source": [
     "chain = (\n",
     "    {\"context\": retriever, \"question\": RunnablePassthrough()}\n",
     "    | prompt\n",
@@ -74,7 +80,7 @@
    "source": [
     "## Get a graph\n",
     "\n",
-    "You can use the `get_graph()` method to get a graph representation of the runnable:"
+    "You can get a graph of the runnable"
    ]
   },
   {
@@ -94,7 +100,7 @@
    "source": [
     "## Print a graph\n",
     "\n",
-    "While that is not super legible, you can use the `print_ascii()` method to show that graph in a way that's easier to understand:"
+    "While that is not super legible, you can print it to get a display that's easier to understand"
    ]
   },
   {
@@ -160,7 +166,7 @@
    "source": [
     "## Get the prompts\n",
     "\n",
-    "You may want to see just the prompts that are used in a chain with the `get_prompts()` method:"
+    "An important part of every chain is the prompts that are used. You can get the prompts present in the chain:"
    ]
   },
   {
@@ -184,18 +190,6 @@
     "chain.get_prompts()"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "id": "c5a74bd5",
-   "metadata": {},
-   "source": [
-    "## Next steps\n",
-    "\n",
-    "You've now learned how to introspect your composed LCEL chains.\n",
-    "\n",
-    "Next, check out the other how-to guides on runnables in this section, or the related how-to guide on [debugging your chains](/docs/how_to/debugging)."
-   ]
-  },
   {
    "cell_type": "code",
    "execution_count": null,
@@ -221,7 +215,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.9.1"
+   "version": "3.10.1"
   }
  },
  "nbformat": 4,

docs/docs/expression_language/how_to/message_history.ipynb

@@ -0,0 +1,592 @@
+{
+ "cells": [
+  {
+   "cell_type": "markdown",
+   "id": "6a4becbd-238e-4c1d-a02d-08e61fbc3763",
+   "metadata": {},
+   "source": [
+    "# Add message history (memory)\n",
+    "\n",
+    "The `RunnableWithMessageHistory` lets us add message history to certain types of chains. It wraps another Runnable and manages the chat message history for it.\n",
+    "\n",
+    "Specifically, it can be used for any Runnable that takes as input one of\n",
+    "\n",
+    "* a sequence of `BaseMessage`\n",
+    "* a dict with a key that takes a sequence of `BaseMessage`\n",
+    "* a dict with a key that takes the latest message(s) as a string or sequence of `BaseMessage`, and a separate key that takes historical messages\n",
+    "\n",
+    "And returns as output one of\n",
+    "\n",
+    "* a string that can be treated as the contents of an `AIMessage`\n",
+    "* a sequence of `BaseMessage`\n",
+    "* a dict with a key that contains a sequence of `BaseMessage`\n",
+    "\n",
+    "Let's take a look at some examples to see how it works. First we construct a runnable (which here accepts a dict as input and returns a message as output):"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 1,
+   "id": "2ed413b4-33a1-48ee-89b0-2d4917ec101a",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain_core.prompts import ChatPromptTemplate, MessagesPlaceholder\n",
+    "from langchain_openai.chat_models import ChatOpenAI\n",
+    "\n",
+    "model = ChatOpenAI()\n",
+    "prompt = ChatPromptTemplate.from_messages(\n",
+    "    [\n",
+    "        (\n",
+    "            \"system\",\n",
+    "            \"You're an assistant who's good at {ability}. Respond in 20 words or fewer\",\n",
+    "        ),\n",
+    "        MessagesPlaceholder(variable_name=\"history\"),\n",
+    "        (\"human\", \"{input}\"),\n",
+    "    ]\n",
+    ")\n",
+    "runnable = prompt | model"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "9fd175e1-c7b8-4929-a57e-3331865fe7aa",
+   "metadata": {},
+   "source": [
+    "To manage the message history, we will need:\n",
+    "1. This runnable;\n",
+    "2. A callable that returns an instance of `BaseChatMessageHistory`.\n",
+    "\n",
+    "Check out the [memory integrations](https://integrations.langchain.com/memory) page for implementations of chat message histories using Redis and other providers. Here we demonstrate using an in-memory `ChatMessageHistory` as well as more persistent storage using `RedisChatMessageHistory`."
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "3d83adad-9672-496d-9f25-5747e7b8c8bb",
+   "metadata": {},
+   "source": [
+    "## In-memory\n",
+    "\n",
+    "Below we show a simple example in which the chat history lives in memory, in this case via a global Python dict.\n",
+    "\n",
+    "We construct a callable `get_session_history` that references this dict to return an instance of `ChatMessageHistory`. The arguments to the callable can be specified by passing a configuration to the `RunnableWithMessageHistory` at runtime. By default, the configuration parameter is expected to be a single string `session_id`. This can be adjusted via the `history_factory_config` kwarg.\n",
+    "\n",
+    "Using the single-parameter default:"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 2,
+   "id": "54348d02-d8ee-440c-bbf9-41bc0fbbc46c",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain_community.chat_message_histories import ChatMessageHistory\n",
+    "from langchain_core.chat_history import BaseChatMessageHistory\n",
+    "from langchain_core.runnables.history import RunnableWithMessageHistory\n",
+    "\n",
+    "store = {}\n",
+    "\n",
+    "\n",
+    "def get_session_history(session_id: str) -> BaseChatMessageHistory:\n",
+    "    if session_id not in store:\n",
+    "        store[session_id] = ChatMessageHistory()\n",
+    "    return store[session_id]\n",
+    "\n",
+    "\n",
+    "with_message_history = RunnableWithMessageHistory(\n",
+    "    runnable,\n",
+    "    get_session_history,\n",
+    "    input_messages_key=\"input\",\n",
+    "    history_messages_key=\"history\",\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "01acb505-3fd3-4ab4-9f04-5ea07e81542e",
+   "metadata": {},
+   "source": [
+    "Note that we've specified `input_messages_key` (the key to be treated as the latest input message) and `history_messages_key` (the key to add historical messages to).\n",
+    "\n",
+    "When invoking this new runnable, we specify the corresponding chat history via a configuration parameter:"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 3,
+   "id": "01384412-f08e-4634-9edb-3f46f475b582",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "AIMessage(content='Cosine is a trigonometric function that calculates the ratio of the adjacent side to the hypotenuse of a right triangle.')"
+      ]
+     },
+     "execution_count": 3,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "with_message_history.invoke(\n",
+    "    {\"ability\": \"math\", \"input\": \"What does cosine mean?\"},\n",
+    "    config={\"configurable\": {\"session_id\": \"abc123\"}},\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 4,
+   "id": "954688a2-9a3f-47ee-a9e8-fa0c83e69477",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "AIMessage(content='Cosine is a mathematical function used to calculate the length of a side in a right triangle.')"
+      ]
+     },
+     "execution_count": 4,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "# Remembers\n",
+    "with_message_history.invoke(\n",
+    "    {\"ability\": \"math\", \"input\": \"What?\"},\n",
+    "    config={\"configurable\": {\"session_id\": \"abc123\"}},\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 5,
+   "id": "39350d7c-2641-4744-bc2a-fd6a57c4ea90",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "AIMessage(content='I can help with math problems. What do you need assistance with?')"
+      ]
+     },
+     "execution_count": 5,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "# New session_id --> does not remember.\n",
+    "with_message_history.invoke(\n",
+    "    {\"ability\": \"math\", \"input\": \"What?\"},\n",
+    "    config={\"configurable\": {\"session_id\": \"def234\"}},\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "d29497be-3366-408d-bbb9-d4a8bf4ef37c",
+   "metadata": {},
+   "source": [
+    "The configuration parameters by which we track message histories can be customized by passing in a list of ``ConfigurableFieldSpec`` objects to the ``history_factory_config`` parameter. Below, we use two parameters: a `user_id` and `conversation_id`."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 6,
+   "id": "1c89daee-deff-4fdf-86a3-178f7d8ef536",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain_core.runnables import ConfigurableFieldSpec\n",
+    "\n",
+    "store = {}\n",
+    "\n",
+    "\n",
+    "def get_session_history(user_id: str, conversation_id: str) -> BaseChatMessageHistory:\n",
+    "    if (user_id, conversation_id) not in store:\n",
+    "        store[(user_id, conversation_id)] = ChatMessageHistory()\n",
+    "    return store[(user_id, conversation_id)]\n",
+    "\n",
+    "\n",
+    "with_message_history = RunnableWithMessageHistory(\n",
+    "    runnable,\n",
+    "    get_session_history,\n",
+    "    input_messages_key=\"input\",\n",
+    "    history_messages_key=\"history\",\n",
+    "    history_factory_config=[\n",
+    "        ConfigurableFieldSpec(\n",
+    "            id=\"user_id\",\n",
+    "            annotation=str,\n",
+    "            name=\"User ID\",\n",
+    "            description=\"Unique identifier for the user.\",\n",
+    "            default=\"\",\n",
+    "            is_shared=True,\n",
+    "        ),\n",
+    "        ConfigurableFieldSpec(\n",
+    "            id=\"conversation_id\",\n",
+    "            annotation=str,\n",
+    "            name=\"Conversation ID\",\n",
+    "            description=\"Unique identifier for the conversation.\",\n",
+    "            default=\"\",\n",
+    "            is_shared=True,\n",
+    "        ),\n",
+    "    ],\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "65c5622e-09b8-4f2f-8c8a-2dab0fd040fa",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "with_message_history.invoke(\n",
+    "    {\"ability\": \"math\", \"input\": \"Hello\"},\n",
+    "    config={\"configurable\": {\"user_id\": \"123\", \"conversation_id\": \"1\"}},\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "18f1a459-3f88-4ee6-8542-76a907070dd6",
+   "metadata": {},
+   "source": [
+    "### Examples with runnables of different signatures\n",
+    "\n",
+    "The above runnable takes a dict as input and returns a BaseMessage. Below we show some alternatives."
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "48eae1bf-b59d-4a61-8e62-b6dbf667e866",
+   "metadata": {},
+   "source": [
+    "#### Messages input, dict output"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 7,
+   "id": "17733d4f-3a32-4055-9d44-5d58b9446a26",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "{'output_message': AIMessage(content=\"Simone de Beauvoir believed in the existence of free will. She argued that individuals have the ability to make choices and determine their own actions, even in the face of social and cultural constraints. She rejected the idea that individuals are purely products of their environment or predetermined by biology or destiny. Instead, she emphasized the importance of personal responsibility and the need for individuals to actively engage in creating their own lives and defining their own existence. De Beauvoir believed that freedom and agency come from recognizing one's own freedom and actively exercising it in the pursuit of personal and collective liberation.\")}"
+      ]
+     },
+     "execution_count": 7,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "from langchain_core.messages import HumanMessage\n",
+    "from langchain_core.runnables import RunnableParallel\n",
+    "\n",
+    "chain = RunnableParallel({\"output_message\": ChatOpenAI()})\n",
+    "\n",
+    "\n",
+    "def get_session_history(session_id: str) -> BaseChatMessageHistory:\n",
+    "    if session_id not in store:\n",
+    "        store[session_id] = ChatMessageHistory()\n",
+    "    return store[session_id]\n",
+    "\n",
+    "\n",
+    "with_message_history = RunnableWithMessageHistory(\n",
+    "    chain,\n",
+    "    get_session_history,\n",
+    "    output_messages_key=\"output_message\",\n",
+    ")\n",
+    "\n",
+    "with_message_history.invoke(\n",
+    "    [HumanMessage(content=\"What did Simone de Beauvoir believe about free will\")],\n",
+    "    config={\"configurable\": {\"session_id\": \"baz\"}},\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 8,
+   "id": "efb57ef5-91f9-426b-84b9-b77f071a9dd7",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "{'output_message': AIMessage(content='Simone de Beauvoir\\'s views on free will were closely aligned with those of her contemporary and partner Jean-Paul Sartre. Both de Beauvoir and Sartre were existentialist philosophers who emphasized the importance of individual freedom and the rejection of determinism. They believed that human beings have the capacity to transcend their circumstances and create their own meaning and values.\\n\\nSartre, in his famous work \"Being and Nothingness,\" argued that human beings are condemned to be free, meaning that we are burdened with the responsibility of making choices and defining ourselves in a world that lacks inherent meaning. Like de Beauvoir, Sartre believed that individuals have the ability to exercise their freedom and make choices in the face of external and internal constraints.\\n\\nWhile there may be some nuanced differences in their philosophical writings, overall, de Beauvoir and Sartre shared a similar belief in the existence of free will and the importance of individual agency in shaping one\\'s own life.')}"
+      ]
+     },
+     "execution_count": 8,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "with_message_history.invoke(\n",
+    "    [HumanMessage(content=\"How did this compare to Sartre\")],\n",
+    "    config={\"configurable\": {\"session_id\": \"baz\"}},\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "a39eac5f-a9d8-4729-be06-5e7faf0c424d",
+   "metadata": {},
+   "source": [
+    "#### Messages input, messages output"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "e45bcd95-e31f-4a9a-967a-78f96e8da881",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "RunnableWithMessageHistory(\n",
+    "    ChatOpenAI(),\n",
+    "    get_session_history,\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "04daa921-a2d1-40f9-8cd1-ae4e9a4163a7",
+   "metadata": {},
+   "source": [
+    "#### Dict with single key for all messages input, messages output"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "27157f15-9fb0-4167-9870-f4d7f234b3cb",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from operator import itemgetter\n",
+    "\n",
+    "RunnableWithMessageHistory(\n",
+    "    itemgetter(\"input_messages\") | ChatOpenAI(),\n",
+    "    get_session_history,\n",
+    "    input_messages_key=\"input_messages\",\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "418ca7af-9ed9-478c-8bca-cba0de2ca61e",
+   "metadata": {},
+   "source": [
+    "## Persistent storage"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "76799a13-d99a-4c4f-91f2-db699e40b8df",
+   "metadata": {},
+   "source": [
+    "In many cases it is preferable to persist conversation histories. `RunnableWithMessageHistory` is agnostic as to how the `get_session_history` callable retrieves its chat message histories. See [here](https://github.com/langchain-ai/langserve/blob/main/examples/chat_with_persistence_and_user/server.py) for an example using a local filesystem. Below we demonstrate how one could use Redis. Check out the [memory integrations](https://integrations.langchain.com/memory) page for implementations of chat message histories using other providers."
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "6bca45e5-35d9-4603-9ca9-6ac0ce0e35cd",
+   "metadata": {},
+   "source": [
+    "### Setup\n",
+    "\n",
+    "We'll need to install Redis if it's not installed already:"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "477d04b3-c2b6-4ba5-962f-492c0d625cd5",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "%pip install --upgrade --quiet redis"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "6a0ec9e0-7b1c-4c6f-b570-e61d520b47c6",
+   "metadata": {},
+   "source": [
+    "Start a local Redis Stack server if we don't have an existing Redis deployment to connect to:\n",
+    "```bash\n",
+    "docker run -d -p 6379:6379 -p 8001:8001 redis/redis-stack:latest\n",
+    "```"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 9,
+   "id": "cd6a250e-17fe-4368-a39d-1fe6b2cbde68",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "REDIS_URL = \"redis://localhost:6379/0\""
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "36f43b87-655c-4f64-aa7b-bd8c1955d8e5",
+   "metadata": {},
+   "source": [
+    "### [LangSmith](/docs/langsmith)\n",
+    "\n",
+    "LangSmith is especially useful for something like message history injection, where it can be hard to otherwise understand what the inputs are to various parts of the chain.\n",
+    "\n",
+    "Note that LangSmith is not needed, but it is helpful.\n",
+    "If you do want to use LangSmith, after you sign up at the link above, make sure to uncoment the below and set your environment variables to start logging traces:"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 2,
+   "id": "2afc1556-8da1-4499-ba11-983b66c58b18",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "# os.environ[\"LANGCHAIN_TRACING_V2\"] = \"true\"\n",
+    "# os.environ[\"LANGCHAIN_API_KEY\"] = getpass.getpass()"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "f9d81796-ce61-484c-89e2-6c567d5e54ef",
+   "metadata": {},
+   "source": [
+    "Updating the message history implementation just requires us to define a new callable, this time returning an instance of `RedisChatMessageHistory`:"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 10,
+   "id": "ca7c64d8-e138-4ef8-9734-f82076c47d80",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain_community.chat_message_histories import RedisChatMessageHistory\n",
+    "\n",
+    "\n",
+    "def get_message_history(session_id: str) -> RedisChatMessageHistory:\n",
+    "    return RedisChatMessageHistory(session_id, url=REDIS_URL)\n",
+    "\n",
+    "\n",
+    "with_message_history = RunnableWithMessageHistory(\n",
+    "    runnable,\n",
+    "    get_message_history,\n",
+    "    input_messages_key=\"input\",\n",
+    "    history_messages_key=\"history\",\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "37eefdec-9901-4650-b64c-d3c097ed5f4d",
+   "metadata": {},
+   "source": [
+    "We can invoke as before:"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 11,
+   "id": "a85bcc22-ca4c-4ad5-9440-f94be7318f3e",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "AIMessage(content='Cosine is a trigonometric function that represents the ratio of the adjacent side to the hypotenuse in a right triangle.')"
+      ]
+     },
+     "execution_count": 11,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "with_message_history.invoke(\n",
+    "    {\"ability\": \"math\", \"input\": \"What does cosine mean?\"},\n",
+    "    config={\"configurable\": {\"session_id\": \"foobar\"}},\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 12,
+   "id": "ab29abd3-751f-41ce-a1b0-53f6b565e79d",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "AIMessage(content='The inverse of cosine is the arccosine function, denoted as acos or cos^-1, which gives the angle corresponding to a given cosine value.')"
+      ]
+     },
+     "execution_count": 12,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "with_message_history.invoke(\n",
+    "    {\"ability\": \"math\", \"input\": \"What's its inverse\"},\n",
+    "    config={\"configurable\": {\"session_id\": \"foobar\"}},\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "da3d1feb-b4bb-4624-961c-7db2e1180df7",
+   "metadata": {},
+   "source": [
+    ":::{.callout-tip}\n",
+    "\n",
+    "[Langsmith trace](https://smith.langchain.com/public/bd73e122-6ec1-48b2-82df-e6483dc9cb63/r)\n",
+    "\n",
+    ":::"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "61d5115e-64a1-4ad5-b676-8afd4ef6093e",
+   "metadata": {},
+   "source": [
+    "Looking at the Langsmith trace for the second call, we can see that when constructing the prompt, a \"history\" variable has been injected which is a list of two messages (our first input and first output)."
+   ]
+  }
+ ],
+ "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.13"
+  }
+ },
+ "nbformat": 4,
+ "nbformat_minor": 5
+}

docs/docs/expression_language/how_to/routing.ipynb

@@ -7,6 +7,7 @@
    "source": [
     "---\n",
     "sidebar_position: 3\n",
+    "title: \"Route logic based on input\"\n",
     "keywords: [RunnableBranch, LCEL]\n",
     "---"
    ]
@@ -16,25 +17,16 @@
    "id": "4b47436a",
    "metadata": {},
    "source": [
-    "# How to route between sub-chains\n",
+    "# Dynamically route logic based on input\n",
     "\n",
-    ":::info Prerequisites\n",
+    "This notebook covers how to do routing in the LangChain Expression Language.\n",
     "\n",
-    "This guide assumes familiarity with the following concepts:\n",
-    "- [LangChain Expression Language (LCEL)](/docs/concepts/#langchain-expression-language)\n",
-    "- [Chaining runnables](/docs/how_to/sequence/)\n",
-    "- [Configuring chain parameters at runtime](/docs/how_to/configure)\n",
-    "- [Prompt templates](/docs/concepts/#prompt-templates)\n",
-    "- [Chat Messages](/docs/concepts/#message-types)\n",
-    "\n",
-    ":::\n",
-    "\n",
-    "Routing allows you to create non-deterministic chains where the output of a previous step defines the next step. Routing can help provide structure and consistency around interactions with models by allowing you to define states and use information related to those states as context to model calls.\n",
+    "Routing allows you to create non-deterministic chains where the output of a previous step defines the next step. Routing helps provide structure and consistency around interactions with LLMs.\n",
     "\n",
     "There are two ways to perform routing:\n",
     "\n",
-    "1. Conditionally return runnables from a [`RunnableLambda`](/docs/how_to/functions) (recommended)\n",
-    "2. Using a `RunnableBranch` (legacy)\n",
+    "1. Conditionally return runnables from a [`RunnableLambda`](/docs/expression_language/primitives/functions) (recommended)\n",
+    "2. Using a `RunnableBranch`.\n",
     "\n",
     "We'll illustrate both methods using a two step sequence where the first step classifies an input question as being about `LangChain`, `Anthropic`, or `Other`, then routes to a corresponding prompt chain."
    ]
@@ -323,7 +315,7 @@
    "id": "fa0f589d",
    "metadata": {},
    "source": [
-    "## Routing by semantic similarity\n",
+    "# Routing by semantic similarity\n",
     "\n",
     "One especially useful technique is to use embeddings to route a query to the most relevant prompt. Here's an example."
    ]
@@ -335,7 +327,7 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "from langchain_community.utils.math import cosine_similarity\n",
+    "from langchain.utils.math import cosine_similarity\n",
     "from langchain_core.output_parsers import StrOutputParser\n",
     "from langchain_core.prompts import PromptTemplate\n",
     "from langchain_core.runnables import RunnableLambda, RunnablePassthrough\n",
@@ -371,7 +363,7 @@
     "chain = (\n",
     "    {\"query\": RunnablePassthrough()}\n",
     "    | RunnableLambda(prompt_router)\n",
-    "    | ChatAnthropic(model=\"claude-3-haiku-20240307\")\n",
+    "    | ChatAnthropic(model_name=\"claude-3-haiku-20240307\")\n",
     "    | StrOutputParser()\n",
     ")"
    ]
@@ -438,18 +430,6 @@
     "print(chain.invoke(\"What's a path integral\"))"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "id": "ff40bcb3",
-   "metadata": {},
-   "source": [
-    "## Next steps\n",
-    "\n",
-    "You've now learned how to add routing to your composed LCEL chains.\n",
-    "\n",
-    "Next, check out the other how-to guides on runnables in this section."
-   ]
-  },
   {
    "cell_type": "markdown",
    "id": "927b7498",
@@ -473,7 +453,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.9.1"
+   "version": "3.10.5"
   }
  },
  "nbformat": 4,

docs/docs/expression_language/index.mdx

@@ -0,0 +1,33 @@
+---
+sidebar_class_name: hidden
+---
+
+# LangChain Expression Language (LCEL)
+
+LangChain Expression Language, or LCEL, is a declarative way to easily compose chains together.
+LCEL was designed from day 1 to **support putting prototypes in production, with no code changes**, from the simplest “prompt + LLM” chain to the most complex chains (we’ve seen folks successfully run LCEL chains with 100s of steps in production). To highlight a few of the reasons you might want to use LCEL:
+
+[**First-class streaming support**](/docs/expression_language/streaming)
+When you build your chains with LCEL you get the best possible time-to-first-token (time elapsed until the first chunk of output comes out). For some chains this means eg. we stream tokens straight from an LLM to a streaming output parser, and you get back parsed, incremental chunks of output at the same rate as the LLM provider outputs the raw tokens.
+
+[**Async support**](/docs/expression_language/interface)
+Any chain built with LCEL can be called both with the synchronous API (eg. in your Jupyter notebook while prototyping) as well as with the asynchronous API (eg. in a [LangServe](/docs/langserve) server). This enables using the same code for prototypes and in production, with great performance, and the ability to handle many concurrent requests in the same server.
+
+[**Optimized parallel execution**](/docs/expression_language/primitives/parallel)
+Whenever your LCEL chains have steps that can be executed in parallel (eg if you fetch documents from multiple retrievers) we automatically do it, both in the sync and the async interfaces, for the smallest possible latency.
+
+[**Retries and fallbacks**](/docs/guides/productionization/fallbacks)
+Configure retries and fallbacks for any part of your LCEL chain. This is a great way to make your chains more reliable at scale. We’re currently working on adding streaming support for retries/fallbacks, so you can get the added reliability without any latency cost.
+
+[**Access intermediate results**](/docs/expression_language/interface#async-stream-events-beta)
+For more complex chains it’s often very useful to access the results of intermediate steps even before the final output is produced. This can be used to let end-users know something is happening, or even just to debug your chain. You can stream intermediate results, and it’s available on every [LangServe](/docs/langserve) server.
+
+[**Input and output schemas**](/docs/expression_language/interface#input-schema)
+Input and output schemas give every LCEL chain Pydantic and JSONSchema schemas inferred from the structure of your chain. This can be used for validation of inputs and outputs, and is an integral part of LangServe.
+
+[**Seamless LangSmith tracing**](/docs/langsmith)
+As your chains get more and more complex, it becomes increasingly important to understand what exactly is happening at every step.
+With LCEL, **all** steps are automatically logged to [LangSmith](/docs/langsmith/) for maximum observability and debuggability.
+
+[**Seamless LangServe deployment**](/docs/langserve)
+Any chain created with LCEL can be easily deployed using [LangServe](/docs/langserve).

docs/docs/expression_language/primitives/assign.ipynb

@@ -6,6 +6,7 @@
    "source": [
     "---\n",
     "sidebar_position: 6\n",
+    "title: \"Assign: Add values to state\"\n",
     "keywords: [RunnablePassthrough, assign, LCEL]\n",
     "---"
    ]
@@ -14,38 +15,32 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "# How to add values to a chain's state\n",
+    "# Adding values to chain state\n",
     "\n",
-    ":::info Prerequisites\n",
+    "The `RunnablePassthrough.assign(...)` static method takes an input value and adds the extra arguments passed to the assign function.\n",
     "\n",
-    "This guide assumes familiarity with the following concepts:\n",
-    "- [LangChain Expression Language (LCEL)](/docs/concepts/#langchain-expression-language)\n",
-    "- [Chaining runnables](/docs/how_to/sequence/)\n",
-    "- [Calling runnables in parallel](/docs/how_to/parallel/)\n",
-    "- [Custom functions](/docs/how_to/functions/)\n",
-    "- [Passing data through](/docs/how_to/passthrough)\n",
-    "\n",
-    ":::\n",
-    "\n",
-    "An alternate way of [passing data through](/docs/how_to/passthrough) steps of a chain is to leave the current values of the chain state unchanged while assigning a new value under a given key. The [`RunnablePassthrough.assign()`](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.passthrough.RunnablePassthrough.html#langchain_core.runnables.passthrough.RunnablePassthrough.assign) static method takes an input value and adds the extra arguments passed to the assign function.\n",
-    "\n",
-    "This is useful in the common [LangChain Expression Language](/docs/concepts/#langchain-expression-language) pattern of additively creating a dictionary to use as input to a later step.\n",
+    "This is useful when additively creating a dictionary to use as input to a later step, which is a common LCEL pattern.\n",
     "\n",
     "Here's an example:"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": null,
+   "execution_count": 1,
    "metadata": {},
-   "outputs": [],
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "\u001b[33mWARNING: You are using pip version 22.0.4; however, version 24.0 is available.\n",
+      "You should consider upgrading via the '/Users/jacoblee/.pyenv/versions/3.10.5/bin/python -m pip install --upgrade pip' command.\u001b[0m\u001b[33m\n",
+      "\u001b[0mNote: you may need to restart the kernel to use updated packages.\n"
+     ]
+    }
+   ],
    "source": [
-    "%pip install --upgrade --quiet langchain langchain-openai\n",
-    "\n",
-    "import os\n",
-    "from getpass import getpass\n",
-    "\n",
-    "os.environ[\"OPENAI_API_KEY\"] = getpass()"
+    "%pip install --upgrade --quiet langchain langchain-openai"
    ]
   },
   {
@@ -90,12 +85,12 @@
     "\n",
     "## Streaming\n",
     "\n",
-    "One convenient feature of this method is that it allows values to pass through as soon as they are available. To show this off, we'll use `RunnablePassthrough.assign()` to immediately return source docs in a retrieval chain:"
+    "One nice feature of this method is that it allows values to pass through as soon as they are available. To show this off, we'll use `RunnablePassthrough.assign()` to immediately return source docs in a retrieval chain:"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 3,
+   "execution_count": 4,
    "metadata": {},
    "outputs": [
     {
@@ -152,13 +147,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "We can see that the first chunk contains the original `\"question\"` since that is immediately available. The second chunk contains `\"context\"` since the retriever finishes second. Finally, the output from the `generation_chain` streams in chunks as soon as it is available.\n",
-    "\n",
-    "## Next steps\n",
-    "\n",
-    "Now you've learned how to pass data through your chains to help to help format the data flowing through your chains.\n",
-    "\n",
-    "To learn more, see the other how-to guides on runnables in this section."
+    "We can see that the first chunk contains the original `\"question\"` since that is immediately available. The second chunk contains `\"context\"` since the retriever finishes second. Finally, the output from the `generation_chain` streams in chunks as soon as it is available."
    ]
   },
   {
@@ -169,7 +158,7 @@
  ],
  "metadata": {
   "kernelspec": {
-   "display_name": "Python 3 (ipykernel)",
+   "display_name": "Python 3",
    "language": "python",
    "name": "python3"
   },
@@ -183,9 +172,9 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.9.1"
+   "version": "3.10.5"
   }
  },
  "nbformat": 4,
- "nbformat_minor": 4
+ "nbformat_minor": 2
 }

docs/docs/expression_language/primitives/binding.ipynb

@@ -7,6 +7,7 @@
    "source": [
     "---\n",
     "sidebar_position: 2\n",
+    "title: \"Binding: Attach runtime args\"\n",
     "keywords: [RunnableBinding, LCEL]\n",
     "---"
    ]
@@ -16,22 +17,11 @@
    "id": "711752cb-4f15-42a3-9838-a0c67f397771",
    "metadata": {},
    "source": [
-    "# How to add default invocation args to a Runnable\n",
+    "# Binding: Attach runtime args\n",
     "\n",
-    ":::info Prerequisites\n",
+    "Sometimes we want to invoke a Runnable within a Runnable sequence with constant arguments that are not part of the output of the preceding Runnable in the sequence, and which are not part of the user input. We can use `Runnable.bind()` to pass these arguments in.\n",
     "\n",
-    "This guide assumes familiarity with the following concepts:\n",
-    "- [LangChain Expression Language (LCEL)](/docs/concepts/#langchain-expression-language)\n",
-    "- [Chaining runnables](/docs/how_to/sequence/)\n",
-    "- [Tool calling](/docs/how_to/tool_calling)\n",
-    "\n",
-    ":::\n",
-    "\n",
-    "Sometimes we want to invoke a [`Runnable`](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.base.Runnable.html) within a [RunnableSequence](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.base.RunnableSequence.html) with constant arguments that are not part of the output of the preceding Runnable in the sequence, and which are not part of the user input. We can use the [`Runnable.bind()`](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.base.Runnable.html#langchain_core.runnables.base.Runnable.bind) method to set these arguments ahead of time.\n",
-    "\n",
-    "## Binding stop sequences\n",
-    "\n",
-    "Suppose we have a simple prompt + model chain:"
+    "Suppose we have a simple prompt + model sequence:"
    ]
   },
   {
@@ -41,20 +31,25 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "# | output: false\n",
-    "# | echo: false\n",
-    "\n",
-    "%pip install -qU langchain langchain_openai\n",
-    "\n",
-    "import os\n",
-    "from getpass import getpass\n",
-    "\n",
-    "os.environ[\"OPENAI_API_KEY\"] = getpass()"
+    "%pip install --upgrade --quiet  langchain langchain-openai"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 2,
+   "execution_count": 1,
+   "id": "950297ed-2d67-4091-8ea7-1d412d259d04",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain_core.output_parsers import StrOutputParser\n",
+    "from langchain_core.prompts import ChatPromptTemplate\n",
+    "from langchain_core.runnables import RunnablePassthrough\n",
+    "from langchain_openai import ChatOpenAI"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 11,
    "id": "f3fdf86d-155f-4587-b7cd-52d363970c1d",
    "metadata": {},
    "outputs": [
@@ -64,21 +59,19 @@
      "text": [
       "EQUATION: x^3 + 7 = 12\n",
       "\n",
-      "SOLUTION: \n",
-      "Subtract 7 from both sides:\n",
+      "SOLUTION:\n",
+      "Subtracting 7 from both sides of the equation, we get:\n",
+      "x^3 = 12 - 7\n",
       "x^3 = 5\n",
       "\n",
-      "Take the cube root of both sides:\n",
-      "x = ∛5\n"
+      "Taking the cube root of both sides, we get:\n",
+      "x = ∛5\n",
+      "\n",
+      "Therefore, the solution to the equation x^3 + 7 = 12 is x = ∛5.\n"
      ]
     }
    ],
    "source": [
-    "from langchain_core.output_parsers import StrOutputParser\n",
-    "from langchain_core.prompts import ChatPromptTemplate\n",
-    "from langchain_core.runnables import RunnablePassthrough\n",
-    "from langchain_openai import ChatOpenAI\n",
-    "\n",
     "prompt = ChatPromptTemplate.from_messages(\n",
     "    [\n",
     "        (\n",
@@ -88,9 +81,7 @@
     "        (\"human\", \"{equation_statement}\"),\n",
     "    ]\n",
     ")\n",
-    "\n",
     "model = ChatOpenAI(temperature=0)\n",
-    "\n",
     "runnable = (\n",
     "    {\"equation_statement\": RunnablePassthrough()} | prompt | model | StrOutputParser()\n",
     ")\n",
@@ -103,12 +94,12 @@
    "id": "929c9aba-a4a0-462c-adac-2cfc2156e117",
    "metadata": {},
    "source": [
-    "and want to call the model with certain `stop` words so that we shorten the output as is useful in certain types of prompting techniques. While we can pass some arguments into the constructor, other runtime args use the `.bind()` method as follows:"
+    "and want to call the model with certain `stop` words:"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 3,
+   "execution_count": 12,
    "id": "32e0484a-78c5-4570-a00b-20d597245a96",
    "metadata": {},
    "outputs": [
@@ -129,25 +120,92 @@
     "    | model.bind(stop=\"SOLUTION\")\n",
     "    | StrOutputParser()\n",
     ")\n",
-    "\n",
     "print(runnable.invoke(\"x raised to the third plus seven equals 12\"))"
    ]
   },
+  {
+   "cell_type": "markdown",
+   "id": "f4bd641f-6b58-4ca9-a544-f69095428f16",
+   "metadata": {},
+   "source": [
+    "## Attaching OpenAI functions\n",
+    "\n",
+    "One particularly useful application of binding is to attach OpenAI functions to a compatible OpenAI model:"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 3,
+   "id": "f66a0fe4-fde0-4706-8863-d60253f211c7",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "function = {\n",
+    "    \"name\": \"solver\",\n",
+    "    \"description\": \"Formulates and solves an equation\",\n",
+    "    \"parameters\": {\n",
+    "        \"type\": \"object\",\n",
+    "        \"properties\": {\n",
+    "            \"equation\": {\n",
+    "                \"type\": \"string\",\n",
+    "                \"description\": \"The algebraic expression of the equation\",\n",
+    "            },\n",
+    "            \"solution\": {\n",
+    "                \"type\": \"string\",\n",
+    "                \"description\": \"The solution to the equation\",\n",
+    "            },\n",
+    "        },\n",
+    "        \"required\": [\"equation\", \"solution\"],\n",
+    "    },\n",
+    "}"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 22,
+   "id": "f381f969-df8e-48a3-bf5c-d0397cfecde0",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "AIMessage(content='', additional_kwargs={'function_call': {'name': 'solver', 'arguments': '{\\n\"equation\": \"x^3 + 7 = 12\",\\n\"solution\": \"x = ∛5\"\\n}'}}, example=False)"
+      ]
+     },
+     "execution_count": 22,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "# Need gpt-4 to solve this one correctly\n",
+    "prompt = ChatPromptTemplate.from_messages(\n",
+    "    [\n",
+    "        (\n",
+    "            \"system\",\n",
+    "            \"Write out the following equation using algebraic symbols then solve it.\",\n",
+    "        ),\n",
+    "        (\"human\", \"{equation_statement}\"),\n",
+    "    ]\n",
+    ")\n",
+    "model = ChatOpenAI(model=\"gpt-4\", temperature=0).bind(\n",
+    "    function_call={\"name\": \"solver\"}, functions=[function]\n",
+    ")\n",
+    "runnable = {\"equation_statement\": RunnablePassthrough()} | prompt | model\n",
+    "runnable.invoke(\"x raised to the third plus seven equals 12\")"
+   ]
+  },
   {
    "cell_type": "markdown",
    "id": "f07d7528-9269-4d6f-b12e-3669592a9e03",
    "metadata": {},
    "source": [
-    "What you can bind to a Runnable will depend on the extra parameters you can pass when invoking it.\n",
-    "\n",
-    "## Attaching OpenAI tools\n",
-    "\n",
-    "Another common use-case is tool calling. While you should generally use the [`.bind_tools()`](/docs/how_to/tool_calling) method for tool-calling models, you can also bind provider-specific args directly if you want lower level control:"
+    "## Attaching OpenAI tools"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 4,
+   "execution_count": 5,
    "id": "2cdeeb4c-0c1f-43da-bd58-4f591d9e0671",
    "metadata": {},
    "outputs": [],
@@ -176,17 +234,17 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 5,
+   "execution_count": 9,
    "id": "2b65beab-48bb-46ff-a5a4-ef8ac95a513c",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "AIMessage(content='', additional_kwargs={'tool_calls': [{'id': 'call_z0OU2CytqENVrRTI6T8DkI3u', 'function': {'arguments': '{\"location\": \"San Francisco, CA\", \"unit\": \"celsius\"}', 'name': 'get_current_weather'}, 'type': 'function'}, {'id': 'call_ft96IJBh0cMKkQWrZjNg4bsw', 'function': {'arguments': '{\"location\": \"New York, NY\", \"unit\": \"celsius\"}', 'name': 'get_current_weather'}, 'type': 'function'}, {'id': 'call_tfbtGgCLmuBuWgZLvpPwvUMH', 'function': {'arguments': '{\"location\": \"Los Angeles, CA\", \"unit\": \"celsius\"}', 'name': 'get_current_weather'}, 'type': 'function'}]}, response_metadata={'token_usage': {'completion_tokens': 84, 'prompt_tokens': 85, 'total_tokens': 169}, 'model_name': 'gpt-3.5-turbo-1106', 'system_fingerprint': 'fp_77a673219d', 'finish_reason': 'tool_calls', 'logprobs': None}, id='run-d57ad5fa-b52a-4822-bc3e-74f838697e18-0', tool_calls=[{'name': 'get_current_weather', 'args': {'location': 'San Francisco, CA', 'unit': 'celsius'}, 'id': 'call_z0OU2CytqENVrRTI6T8DkI3u'}, {'name': 'get_current_weather', 'args': {'location': 'New York, NY', 'unit': 'celsius'}, 'id': 'call_ft96IJBh0cMKkQWrZjNg4bsw'}, {'name': 'get_current_weather', 'args': {'location': 'Los Angeles, CA', 'unit': 'celsius'}, 'id': 'call_tfbtGgCLmuBuWgZLvpPwvUMH'}])"
+       "AIMessage(content='', additional_kwargs={'tool_calls': [{'id': 'call_zHN0ZHwrxM7nZDdqTp6dkPko', 'function': {'arguments': '{\"location\": \"San Francisco, CA\", \"unit\": \"celsius\"}', 'name': 'get_current_weather'}, 'type': 'function'}, {'id': 'call_aqdMm9HBSlFW9c9rqxTa7eQv', 'function': {'arguments': '{\"location\": \"New York, NY\", \"unit\": \"celsius\"}', 'name': 'get_current_weather'}, 'type': 'function'}, {'id': 'call_cx8E567zcLzYV2WSWVgO63f1', 'function': {'arguments': '{\"location\": \"Los Angeles, CA\", \"unit\": \"celsius\"}', 'name': 'get_current_weather'}, 'type': 'function'}]})"
       ]
      },
-     "execution_count": 5,
+     "execution_count": 9,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -195,27 +253,13 @@
     "model = ChatOpenAI(model=\"gpt-3.5-turbo-1106\").bind(tools=tools)\n",
     "model.invoke(\"What's the weather in SF, NYC and LA?\")"
    ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "095001f7",
-   "metadata": {},
-   "source": [
-    "## Next steps\n",
-    "\n",
-    "You now know how to bind runtime arguments to a Runnable.\n",
-    "\n",
-    "To learn more, see the other how-to guides on runnables in this section, including:\n",
-    "\n",
-    "- [Using configurable fields and alternatives](/docs/how_to/configure) to change parameters of a step in a chain, or even swap out entire steps, at runtime"
-   ]
   }
  ],
  "metadata": {
   "kernelspec": {
-   "display_name": "Python 3 (ipykernel)",
+   "display_name": "poetry-venv",
    "language": "python",
-   "name": "python3"
+   "name": "poetry-venv"
   },
   "language_info": {
    "codemirror_mode": {

docs/docs/expression_language/primitives/configure.ipynb

@@ -7,6 +7,7 @@
    "source": [
     "---\n",
     "sidebar_position: 7\n",
+    "title: \"Configure runtime chain internals\"\n",
     "keywords: [ConfigurableField, configurable_fields, ConfigurableAlternatives, configurable_alternatives, LCEL]\n",
     "---"
    ]
@@ -16,24 +17,16 @@
    "id": "39eaf61b",
    "metadata": {},
    "source": [
-    "# How to configure runtime chain internals\n",
+    "# Configure chain internals at runtime\n",
     "\n",
-    ":::info Prerequisites\n",
-    "\n",
-    "This guide assumes familiarity with the following concepts:\n",
-    "- [LangChain Expression Language (LCEL)](/docs/concepts/#langchain-expression-language)\n",
-    "- [Chaining runnables](/docs/how_to/sequence/)\n",
-    "- [Binding runtime arguments](/docs/how_to/binding/)\n",
-    "\n",
-    ":::\n",
-    "\n",
-    "Sometimes you may want to experiment with, or even expose to the end user, multiple different ways of doing things within your chains.\n",
-    "This can include tweaking parameters such as temperature or even swapping out one model for another.\n",
+    "Oftentimes you may want to experiment with, or even expose to the end user, multiple different ways of doing things.\n",
     "In order to make this experience as easy as possible, we have defined two methods.\n",
     "\n",
-    "- A `configurable_fields` method. This lets you configure particular fields of a runnable.\n",
-    "  - This is related to the [`.bind`](/docs/how_to/binding) method on runnables, but allows you to specify parameters for a given step in a chain at runtime rather than specifying them beforehand.\n",
-    "- A `configurable_alternatives` method. With this method, you can list out alternatives for any particular runnable that can be set during runtime, and swap them for those specified alternatives."
+    "First, a `configurable_fields` method. \n",
+    "This lets you configure particular fields of a runnable.\n",
+    "\n",
+    "Second, a `configurable_alternatives` method.\n",
+    "With this method, you can list out alternatives for any particular runnable that can be set during runtime."
    ]
   },
   {
@@ -41,53 +34,34 @@
    "id": "f2347a11",
    "metadata": {},
    "source": [
-    "## Configurable Fields\n",
-    "\n",
-    "Let's walk through an example that configures chat model fields like temperature at runtime:"
+    "## Configuration Fields"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "a06f6e2d",
+   "metadata": {},
+   "source": [
+    "### With LLMs\n",
+    "With LLMs we can configure things like temperature"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 1,
+   "execution_count": null,
    "id": "40ed76a2",
    "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "\u001b[33mWARNING: You are using pip version 22.0.4; however, version 24.0 is available.\n",
-      "You should consider upgrading via the '/Users/jacoblee/.pyenv/versions/3.10.5/bin/python -m pip install --upgrade pip' command.\u001b[0m\u001b[33m\n",
-      "\u001b[0mNote: you may need to restart the kernel to use updated packages.\n"
-     ]
-    }
-   ],
+   "outputs": [],
    "source": [
-    "%pip install --upgrade --quiet langchain langchain-openai\n",
-    "\n",
-    "import os\n",
-    "from getpass import getpass\n",
-    "\n",
-    "os.environ[\"OPENAI_API_KEY\"] = getpass()"
+    "%pip install --upgrade --quiet  langchain langchain-openai"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 2,
+   "execution_count": 35,
    "id": "7ba735f4",
    "metadata": {},
-   "outputs": [
-    {
-     "data": {
-      "text/plain": [
-       "AIMessage(content='17', response_metadata={'token_usage': {'completion_tokens': 1, 'prompt_tokens': 11, 'total_tokens': 12}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_c2295e73ad', 'finish_reason': 'stop', 'logprobs': None}, id='run-ba26a0da-0a69-4533-ab7f-21178a73d303-0')"
-      ]
-     },
-     "execution_count": 2,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
+   "outputs": [],
    "source": [
     "from langchain_core.prompts import PromptTemplate\n",
     "from langchain_core.runnables import ConfigurableField\n",
@@ -99,32 +73,43 @@
     "        name=\"LLM Temperature\",\n",
     "        description=\"The temperature of the LLM\",\n",
     "    )\n",
-    ")\n",
-    "\n",
-    "model.invoke(\"pick a random number\")"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "b0f74589",
-   "metadata": {},
-   "source": [
-    "Above, we defined `temperature` as a [`ConfigurableField`](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.utils.ConfigurableField.html#langchain_core.runnables.utils.ConfigurableField) that we can set at runtime. To do so, we use the [`with_config`](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.base.Runnable.html#langchain_core.runnables.base.Runnable.with_config) method like this:"
+    ")"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 3,
+   "execution_count": 38,
+   "id": "63a71165",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "AIMessage(content='7')"
+      ]
+     },
+     "execution_count": 38,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "model.invoke(\"pick a random number\")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 39,
    "id": "4f83245c",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "AIMessage(content='12', response_metadata={'token_usage': {'completion_tokens': 1, 'prompt_tokens': 11, 'total_tokens': 12}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_c2295e73ad', 'finish_reason': 'stop', 'logprobs': None}, id='run-ba8422ad-be77-4cb1-ac45-ad0aae74e3d9-0')"
+       "AIMessage(content='34')"
       ]
      },
-     "execution_count": 3,
+     "execution_count": 39,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -138,48 +123,54 @@
    "id": "9da1fcd2",
    "metadata": {},
    "source": [
-    "Note that the passed `llm_temperature` entry in the dict has the same key as the `id` of the `ConfigurableField`.\n",
-    "\n",
-    "We can also do this to affect just one step that's part of a chain:"
+    "We can also do this when its used as part of a chain"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 4,
+   "execution_count": 40,
    "id": "e75ae678",
    "metadata": {},
+   "outputs": [],
+   "source": [
+    "prompt = PromptTemplate.from_template(\"Pick a random number above {x}\")\n",
+    "chain = prompt | model"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 41,
+   "id": "44886071",
+   "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "AIMessage(content='27', response_metadata={'token_usage': {'completion_tokens': 1, 'prompt_tokens': 14, 'total_tokens': 15}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_c2295e73ad', 'finish_reason': 'stop', 'logprobs': None}, id='run-ecd4cadd-1b72-4f92-b9a0-15e08091f537-0')"
+       "AIMessage(content='57')"
       ]
      },
-     "execution_count": 4,
+     "execution_count": 41,
      "metadata": {},
      "output_type": "execute_result"
     }
    ],
    "source": [
-    "prompt = PromptTemplate.from_template(\"Pick a random number above {x}\")\n",
-    "chain = prompt | model\n",
-    "\n",
     "chain.invoke({\"x\": 0})"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 5,
+   "execution_count": 42,
    "id": "c09fac15",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "AIMessage(content='35', response_metadata={'token_usage': {'completion_tokens': 1, 'prompt_tokens': 14, 'total_tokens': 15}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_c2295e73ad', 'finish_reason': 'stop', 'logprobs': None}, id='run-a916602b-3460-46d3-a4a8-7c926ec747c0-0')"
+       "AIMessage(content='6')"
       ]
      },
-     "execution_count": 5,
+     "execution_count": 42,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -200,9 +191,35 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 6,
+   "execution_count": 43,
+   "id": "7d5836b2",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain.runnables.hub import HubRunnable"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 46,
    "id": "9a9ea077",
    "metadata": {},
+   "outputs": [],
+   "source": [
+    "prompt = HubRunnable(\"rlm/rag-prompt\").configurable_fields(\n",
+    "    owner_repo_commit=ConfigurableField(\n",
+    "        id=\"hub_commit\",\n",
+    "        name=\"Hub Commit\",\n",
+    "        description=\"The Hub commit to pull from\",\n",
+    "    )\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 47,
+   "id": "c4a62cee",
+   "metadata": {},
    "outputs": [
     {
      "data": {
@@ -210,28 +227,18 @@
        "ChatPromptValue(messages=[HumanMessage(content=\"You are an assistant for question-answering tasks. Use the following pieces of retrieved context to answer the question. If you don't know the answer, just say that you don't know. Use three sentences maximum and keep the answer concise.\\nQuestion: foo \\nContext: bar \\nAnswer:\")])"
       ]
      },
-     "execution_count": 6,
+     "execution_count": 47,
      "metadata": {},
      "output_type": "execute_result"
     }
    ],
    "source": [
-    "from langchain.runnables.hub import HubRunnable\n",
-    "\n",
-    "prompt = HubRunnable(\"rlm/rag-prompt\").configurable_fields(\n",
-    "    owner_repo_commit=ConfigurableField(\n",
-    "        id=\"hub_commit\",\n",
-    "        name=\"Hub Commit\",\n",
-    "        description=\"The Hub commit to pull from\",\n",
-    "    )\n",
-    ")\n",
-    "\n",
     "prompt.invoke({\"question\": \"foo\", \"context\": \"bar\"})"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 7,
+   "execution_count": 49,
    "id": "f33f3cf2",
    "metadata": {},
    "outputs": [
@@ -241,7 +248,7 @@
        "ChatPromptValue(messages=[HumanMessage(content=\"[INST]<<SYS>> You are an assistant for question-answering tasks. Use the following pieces of retrieved context to answer the question. If you don't know the answer, just say that you don't know. Use three sentences maximum and keep the answer concise.<</SYS>> \\nQuestion: foo \\nContext: bar \\nAnswer: [/INST]\")])"
       ]
      },
-     "execution_count": 7,
+     "execution_count": 49,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -266,32 +273,22 @@
    "id": "ac733d35",
    "metadata": {},
    "source": [
-    "The `configurable_alternatives()` method allows us to swap out steps in a chain with an alternative. Below, we swap out one chat model for another:"
+    "### With LLMs\n",
+    "\n",
+    "Let's take a look at doing this with LLMs"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 8,
-   "id": "3db59f45",
+   "execution_count": 4,
+   "id": "430ab8cc",
    "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "\u001b[33mWARNING: You are using pip version 22.0.4; however, version 24.0 is available.\n",
-      "You should consider upgrading via the '/Users/jacoblee/.pyenv/versions/3.10.5/bin/python -m pip install --upgrade pip' command.\u001b[0m\u001b[33m\n",
-      "\u001b[0mNote: you may need to restart the kernel to use updated packages.\n"
-     ]
-    }
-   ],
+   "outputs": [],
    "source": [
-    "%pip install --upgrade --quiet langchain-anthropic\n",
-    "\n",
-    "import os\n",
-    "from getpass import getpass\n",
-    "\n",
-    "os.environ[\"ANTHROPIC_API_KEY\"] = getpass()"
+    "from langchain_community.chat_models import ChatAnthropic\n",
+    "from langchain_core.prompts import PromptTemplate\n",
+    "from langchain_core.runnables import ConfigurableField\n",
+    "from langchain_openai import ChatOpenAI"
    ]
   },
   {
@@ -299,27 +296,9 @@
    "execution_count": 18,
    "id": "71248a9f",
    "metadata": {},
-   "outputs": [
-    {
-     "data": {
-      "text/plain": [
-       "AIMessage(content=\"Here's a bear joke for you:\\n\\nWhy don't bears wear socks? \\nBecause they have bear feet!\\n\\nHow's that? I tried to come up with a simple, silly pun-based joke about bears. Puns and wordplay are a common way to create humorous bear jokes. Let me know if you'd like to hear another one!\", response_metadata={'id': 'msg_018edUHh5fUbWdiimhrC3dZD', 'model': 'claude-3-haiku-20240307', 'stop_reason': 'end_turn', 'stop_sequence': None, 'usage': {'input_tokens': 13, 'output_tokens': 80}}, id='run-775bc58c-28d7-4e6b-a268-48fa6661f02f-0')"
-      ]
-     },
-     "execution_count": 18,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
+   "outputs": [],
    "source": [
-    "from langchain_anthropic import ChatAnthropic\n",
-    "from langchain_core.prompts import PromptTemplate\n",
-    "from langchain_core.runnables import ConfigurableField\n",
-    "from langchain_openai import ChatOpenAI\n",
-    "\n",
-    "llm = ChatAnthropic(\n",
-    "    model=\"claude-3-haiku-20240307\", temperature=0\n",
-    ").configurable_alternatives(\n",
+    "llm = ChatAnthropic(temperature=0).configurable_alternatives(\n",
     "    # This gives this field an id\n",
     "    # When configuring the end runnable, we can then use this id to configure this field\n",
     "    ConfigurableField(id=\"llm\"),\n",
@@ -333,25 +312,44 @@
     "    # You can add more configuration options here\n",
     ")\n",
     "prompt = PromptTemplate.from_template(\"Tell me a joke about {topic}\")\n",
-    "chain = prompt | llm\n",
-    "\n",
+    "chain = prompt | llm"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 19,
+   "id": "e598b1f1",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "AIMessage(content=\" Here's a silly joke about bears:\\n\\nWhat do you call a bear with no teeth?\\nA gummy bear!\")"
+      ]
+     },
+     "execution_count": 19,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
     "# By default it will call Anthropic\n",
     "chain.invoke({\"topic\": \"bears\"})"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 19,
+   "execution_count": 20,
    "id": "48b45337",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "AIMessage(content=\"Why don't bears like fast food?\\n\\nBecause they can't catch it!\", response_metadata={'token_usage': {'completion_tokens': 15, 'prompt_tokens': 13, 'total_tokens': 28}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_c2295e73ad', 'finish_reason': 'stop', 'logprobs': None}, id='run-7bdaa992-19c9-4f0d-9a0c-1f326bc992d4-0')"
+       "AIMessage(content=\"Sure, here's a bear joke for you:\\n\\nWhy don't bears wear shoes?\\n\\nBecause they already have bear feet!\")"
       ]
      },
-     "execution_count": 19,
+     "execution_count": 20,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -363,17 +361,17 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 20,
+   "execution_count": 21,
    "id": "42647fb7",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "AIMessage(content=\"Here's a bear joke for you:\\n\\nWhy don't bears wear socks? \\nBecause they have bear feet!\\n\\nHow's that? I tried to come up with a simple, silly pun-based joke about bears. Puns and wordplay are a common way to create humorous bear jokes. Let me know if you'd like to hear another one!\", response_metadata={'id': 'msg_01BZvbmnEPGBtcxRWETCHkct', 'model': 'claude-3-haiku-20240307', 'stop_reason': 'end_turn', 'stop_sequence': None, 'usage': {'input_tokens': 13, 'output_tokens': 80}}, id='run-59b6ee44-a1cd-41b8-a026-28ee67cdd718-0')"
+       "AIMessage(content=\" Here's a silly joke about bears:\\n\\nWhat do you call a bear with no teeth?\\nA gummy bear!\")"
       ]
      },
-     "execution_count": 20,
+     "execution_count": 21,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -395,23 +393,12 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 22,
+   "execution_count": 25,
    "id": "9f6a7c6c",
    "metadata": {},
-   "outputs": [
-    {
-     "data": {
-      "text/plain": [
-       "AIMessage(content=\"Here's a bear joke for you:\\n\\nWhy don't bears wear socks? \\nBecause they have bear feet!\", response_metadata={'id': 'msg_01DtM1cssjNFZYgeS3gMZ49H', 'model': 'claude-3-haiku-20240307', 'stop_reason': 'end_turn', 'stop_sequence': None, 'usage': {'input_tokens': 13, 'output_tokens': 28}}, id='run-8199af7d-ea31-443d-b064-483693f2e0a1-0')"
-      ]
-     },
-     "execution_count": 22,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
+   "outputs": [],
    "source": [
-    "llm = ChatAnthropic(model=\"claude-3-haiku-20240307\", temperature=0)\n",
+    "llm = ChatAnthropic(temperature=0)\n",
     "prompt = PromptTemplate.from_template(\n",
     "    \"Tell me a joke about {topic}\"\n",
     ").configurable_alternatives(\n",
@@ -425,25 +412,44 @@
     "    poem=PromptTemplate.from_template(\"Write a short poem about {topic}\"),\n",
     "    # You can add more configuration options here\n",
     ")\n",
-    "chain = prompt | llm\n",
-    "\n",
+    "chain = prompt | llm"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 26,
+   "id": "97eda915",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "AIMessage(content=\" Here's a silly joke about bears:\\n\\nWhat do you call a bear with no teeth?\\nA gummy bear!\")"
+      ]
+     },
+     "execution_count": 26,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
     "# By default it will write a joke\n",
     "chain.invoke({\"topic\": \"bears\"})"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 23,
+   "execution_count": 27,
    "id": "927297a1",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "AIMessage(content=\"Here is a short poem about bears:\\n\\nMajestic bears, strong and true,\\nRoaming the forests, wild and free.\\nPowerful paws, fur soft and brown,\\nCommanding respect, nature's crown.\\n\\nForaging for berries, fishing streams,\\nProtecting their young, fierce and keen.\\nMighty bears, a sight to behold,\\nGuardians of the wilderness, untold.\\n\\nIn the wild they reign supreme,\\nEmbodying nature's grand theme.\\nBears, a symbol of strength and grace,\\nCaptivating all who see their face.\", response_metadata={'id': 'msg_01Wck3qPxrjURtutvtodaJFn', 'model': 'claude-3-haiku-20240307', 'stop_reason': 'end_turn', 'stop_sequence': None, 'usage': {'input_tokens': 13, 'output_tokens': 134}}, id='run-69414a1e-51d7-4bec-a307-b34b7d61025e-0')"
+       "AIMessage(content=' Here is a short poem about bears:\\n\\nThe bears awaken from their sleep\\nAnd lumber out into the deep\\nForests filled with trees so tall\\nForaging for food before nightfall \\nTheir furry coats and claws so sharp\\nSniffing for berries and fish to nab\\nLumbering about without a care\\nThe mighty grizzly and black bear\\nProud creatures, wild and free\\nRuling their domain majestically\\nWandering the woods they call their own\\nBefore returning to their dens alone')"
       ]
      },
-     "execution_count": 23,
+     "execution_count": 27,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -466,25 +472,12 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 25,
+   "execution_count": 28,
    "id": "97538c23",
    "metadata": {},
-   "outputs": [
-    {
-     "data": {
-      "text/plain": [
-       "AIMessage(content=\"In the forest deep and wide,\\nBears roam with grace and pride.\\nWith fur as dark as night,\\nThey rule the land with all their might.\\n\\nIn winter's chill, they hibernate,\\nIn spring they emerge, hungry and great.\\nWith claws sharp and eyes so keen,\\nThey hunt for food, fierce and lean.\\n\\nBut beneath their tough exterior,\\nLies a gentle heart, warm and superior.\\nThey love their cubs with all their might,\\nProtecting them through day and night.\\n\\nSo let us admire these majestic creatures,\\nIn awe of their strength and features.\\nFor in the wild, they reign supreme,\\nThe mighty bears, a timeless dream.\", response_metadata={'token_usage': {'completion_tokens': 133, 'prompt_tokens': 13, 'total_tokens': 146}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_c2295e73ad', 'finish_reason': 'stop', 'logprobs': None}, id='run-5eec0b96-d580-49fd-ac4e-e32a0803b49b-0')"
-      ]
-     },
-     "execution_count": 25,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
+   "outputs": [],
    "source": [
-    "llm = ChatAnthropic(\n",
-    "    model=\"claude-3-haiku-20240307\", temperature=0\n",
-    ").configurable_alternatives(\n",
+    "llm = ChatAnthropic(temperature=0).configurable_alternatives(\n",
     "    # This gives this field an id\n",
     "    # When configuring the end runnable, we can then use this id to configure this field\n",
     "    ConfigurableField(id=\"llm\"),\n",
@@ -510,8 +503,27 @@
     "    poem=PromptTemplate.from_template(\"Write a short poem about {topic}\"),\n",
     "    # You can add more configuration options here\n",
     ")\n",
-    "chain = prompt | llm\n",
-    "\n",
+    "chain = prompt | llm"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 29,
+   "id": "1dcc7ccc",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "AIMessage(content=\"In the forest, where tall trees sway,\\nA creature roams, both fierce and gray.\\nWith mighty paws and piercing eyes,\\nThe bear, a symbol of strength, defies.\\n\\nThrough snow-kissed mountains, it does roam,\\nA guardian of its woodland home.\\nWith fur so thick, a shield of might,\\nIt braves the coldest winter night.\\n\\nA gentle giant, yet wild and free,\\nThe bear commands respect, you see.\\nWith every step, it leaves a trace,\\nOf untamed power and ancient grace.\\n\\nFrom honeyed feast to salmon's leap,\\nIt takes its place, in nature's keep.\\nA symbol of untamed delight,\\nThe bear, a wonder, day and night.\\n\\nSo let us honor this noble beast,\\nIn forests where its soul finds peace.\\nFor in its presence, we come to know,\\nThe untamed spirit that in us also flows.\")"
+      ]
+     },
+     "execution_count": 29,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
     "# We can configure it write a poem with OpenAI\n",
     "chain.with_config(configurable={\"prompt\": \"poem\", \"llm\": \"openai\"}).invoke(\n",
     "    {\"topic\": \"bears\"}\n",
@@ -520,17 +532,17 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 26,
+   "execution_count": 30,
    "id": "e4ee9fbc",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "AIMessage(content=\"Why don't bears wear shoes?\\n\\nBecause they have bear feet!\", response_metadata={'token_usage': {'completion_tokens': 13, 'prompt_tokens': 13, 'total_tokens': 26}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_c2295e73ad', 'finish_reason': 'stop', 'logprobs': None}, id='run-c1b14c9c-4988-49b8-9363-15bfd479973a-0')"
+       "AIMessage(content=\"Sure, here's a bear joke for you:\\n\\nWhy don't bears wear shoes?\\n\\nBecause they have bear feet!\")"
       ]
      },
-     "execution_count": 26,
+     "execution_count": 30,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -552,41 +564,35 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 27,
+   "execution_count": 31,
    "id": "5cf53202",
    "metadata": {},
+   "outputs": [],
+   "source": [
+    "openai_joke = chain.with_config(configurable={\"llm\": \"openai\"})"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 32,
+   "id": "9486d701",
+   "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "AIMessage(content=\"Why did the bear break up with his girlfriend? \\nBecause he couldn't bear the relationship anymore!\", response_metadata={'token_usage': {'completion_tokens': 20, 'prompt_tokens': 13, 'total_tokens': 33}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_c2295e73ad', 'finish_reason': 'stop', 'logprobs': None}, id='run-391ebd55-9137-458b-9a11-97acaff6a892-0')"
+       "AIMessage(content=\"Why don't bears wear shoes?\\n\\nBecause they have bear feet!\")"
       ]
      },
-     "execution_count": 27,
+     "execution_count": 32,
      "metadata": {},
      "output_type": "execute_result"
     }
    ],
    "source": [
-    "openai_joke = chain.with_config(configurable={\"llm\": \"openai\"})\n",
-    "\n",
     "openai_joke.invoke({\"topic\": \"bears\"})"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "id": "76702b0e",
-   "metadata": {},
-   "source": [
-    "## Next steps\n",
-    "\n",
-    "You now know how to configure a chain's internal steps at runtime.\n",
-    "\n",
-    "To learn more, see the other how-to guides on runnables in this section, including:\n",
-    "\n",
-    "- Using [.bind()](/docs/how_to/binding) as a simpler way to set a runnable's runtime parameters"
-   ]
-  },
   {
    "cell_type": "code",
    "execution_count": null,
@@ -612,7 +618,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.9.1"
+   "version": "3.11.5"
   }
  },
  "nbformat": 4,

docs/docs/expression_language/primitives/functions.ipynb

@@ -7,6 +7,7 @@
    "source": [
     "---\n",
     "sidebar_position: 3\n",
+    "title: \"Lambda: Run custom functions\"\n",
     "keywords: [RunnableLambda, LCEL]\n",
     "---"
    ]
@@ -16,64 +17,27 @@
    "id": "fbc4bf6e",
    "metadata": {},
    "source": [
-    "# How to run custom functions\n",
+    "# Run custom functions\n",
     "\n",
-    ":::info Prerequisites\n",
+    "You can use arbitrary functions in the pipeline.\n",
     "\n",
-    "This guide assumes familiarity with the following concepts:\n",
-    "- [LangChain Expression Language (LCEL)](/docs/concepts/#langchain-expression-language)\n",
-    "- [Chaining runnables](/docs/how_to/sequence/)\n",
-    "\n",
-    ":::\n",
-    "\n",
-    "You can use arbitrary functions as [Runnables](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.base.Runnable.html#langchain_core.runnables.base.Runnable). This is useful for formatting or when you need functionality not provided by other LangChain components, and custom functions used as Runnables are called [`RunnableLambdas`](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.base.RunnableLambda.html).\n",
-    "\n",
-    "Note that all inputs to these functions need to be a SINGLE argument. If you have a function that accepts multiple arguments, you should write a wrapper that accepts a single dict input and unpacks it into multiple argument.\n",
-    "\n",
-    "This guide will cover:\n",
-    "\n",
-    "- How to explicitly create a runnable from a custom function using the `RunnableLambda` constructor and the convenience `@chain` decorator\n",
-    "- Coercion of custom functions into runnables when used in chains\n",
-    "- How to accept and use run metadata in your custom function\n",
-    "- How to stream with custom functions by having them return generators\n",
-    "\n",
-    "## Using the constructor\n",
-    "\n",
-    "Below, we explicitly wrap our custom logic using the `RunnableLambda` constructor:"
+    "Note that all inputs to these functions need to be a SINGLE argument. If you have a function that accepts multiple arguments, you should write a wrapper that accepts a single input and unpacks it into multiple argument."
    ]
   },
   {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "5c34d2af",
+   "cell_type": "raw",
+   "id": "9a5fe916",
    "metadata": {},
-   "outputs": [],
    "source": [
-    "%pip install -qU langchain langchain_openai\n",
-    "\n",
-    "import os\n",
-    "from getpass import getpass\n",
-    "\n",
-    "os.environ[\"OPENAI_API_KEY\"] = getpass()"
+    "%pip install --upgrade --quiet langchain langchain-openai"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 2,
+   "execution_count": 1,
    "id": "6bb221b3",
    "metadata": {},
-   "outputs": [
-    {
-     "data": {
-      "text/plain": [
-       "AIMessage(content='3 + 9 equals 12.', response_metadata={'token_usage': {'completion_tokens': 8, 'prompt_tokens': 14, 'total_tokens': 22}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_c2295e73ad', 'finish_reason': 'stop', 'logprobs': None}, id='run-73728de3-e483-49e3-ad54-51bd9570e71a-0')"
-      ]
-     },
-     "execution_count": 2,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
+   "outputs": [],
    "source": [
     "from operator import itemgetter\n",
     "\n",
@@ -94,9 +58,8 @@
     "    return _multiple_length_function(_dict[\"text1\"], _dict[\"text2\"])\n",
     "\n",
     "\n",
-    "model = ChatOpenAI()\n",
-    "\n",
     "prompt = ChatPromptTemplate.from_template(\"what is {a} + {b}\")\n",
+    "model = ChatOpenAI()\n",
     "\n",
     "chain1 = prompt | model\n",
     "\n",
@@ -108,56 +71,28 @@
     "    }\n",
     "    | prompt\n",
     "    | model\n",
-    ")\n",
-    "\n",
-    "chain.invoke({\"foo\": \"bar\", \"bar\": \"gah\"})"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "b7926002",
-   "metadata": {},
-   "source": [
-    "## The convenience `@chain` decorator\n",
-    "\n",
-    "You can also turn an arbitrary function into a chain by adding a `@chain` decorator. This is functionaly equivalent to wrapping the function in a `RunnableLambda` constructor as shown above. Here's an example:"
+    ")"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 3,
-   "id": "3142a516",
+   "execution_count": 2,
+   "id": "5488ec85",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "'The subject of the joke is the bear and his girlfriend.'"
+       "AIMessage(content='3 + 9 = 12', response_metadata={'token_usage': {'completion_tokens': 7, 'prompt_tokens': 14, 'total_tokens': 21}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_b28b39ffa8', 'finish_reason': 'stop', 'logprobs': None}, id='run-bd204541-81fd-429a-ad92-dd1913af9b1c-0')"
       ]
      },
-     "execution_count": 3,
+     "execution_count": 2,
      "metadata": {},
      "output_type": "execute_result"
     }
    ],
    "source": [
-    "from langchain_core.output_parsers import StrOutputParser\n",
-    "from langchain_core.runnables import chain\n",
-    "\n",
-    "prompt1 = ChatPromptTemplate.from_template(\"Tell me a joke about {topic}\")\n",
-    "prompt2 = ChatPromptTemplate.from_template(\"What is the subject of this joke: {joke}\")\n",
-    "\n",
-    "\n",
-    "@chain\n",
-    "def custom_chain(text):\n",
-    "    prompt_val1 = prompt1.invoke({\"topic\": text})\n",
-    "    output1 = ChatOpenAI().invoke(prompt_val1)\n",
-    "    parsed_output1 = StrOutputParser().invoke(output1)\n",
-    "    chain2 = prompt2 | ChatOpenAI() | StrOutputParser()\n",
-    "    return chain2.invoke({\"joke\": parsed_output1})\n",
-    "\n",
-    "\n",
-    "custom_chain.invoke(\"bears\")"
+    "chain.invoke({\"foo\": \"bar\", \"bar\": \"gah\"})"
    ]
   },
   {
@@ -165,78 +100,31 @@
    "id": "4728ddd9-914d-42ce-ae9b-72c9ce8ec940",
    "metadata": {},
    "source": [
-    "Above, the `@chain` decorator is used to convert `custom_chain` into a runnable, which we invoke with the `.invoke()` method.\n",
+    "## Accepting a Runnable Config\n",
     "\n",
-    "If you are using a tracing with [LangSmith](https://docs.smith.langchain.com/), you should see a `custom_chain` trace in there, with the calls to OpenAI nested underneath.\n",
-    "\n",
-    "## Automatic coercion in chains\n",
-    "\n",
-    "When using custom functions in chains with the pipe operator (`|`), you can omit the `RunnableLambda` or `@chain` constructor and rely on coercion. Here's a simple example with a function that takes the output from the model and returns the first five letters of it:"
+    "Runnable lambdas can optionally accept a [RunnableConfig](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.config.RunnableConfig.html#langchain_core.runnables.config.RunnableConfig), which they can use to pass callbacks, tags, and other configuration information to nested runs."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 3,
+   "id": "80b3b5f6-5d58-44b9-807e-cce9a46bf49f",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain_core.output_parsers import StrOutputParser\n",
+    "from langchain_core.runnables import RunnableConfig"
    ]
   },
   {
    "cell_type": "code",
    "execution_count": 4,
-   "id": "5ab39a87",
-   "metadata": {},
-   "outputs": [
-    {
-     "data": {
-      "text/plain": [
-       "'Once '"
-      ]
-     },
-     "execution_count": 4,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
-   "source": [
-    "prompt = ChatPromptTemplate.from_template(\"tell me a story about {topic}\")\n",
-    "\n",
-    "model = ChatOpenAI()\n",
-    "\n",
-    "chain_with_coerced_function = prompt | model | (lambda x: x.content[:5])\n",
-    "\n",
-    "chain_with_coerced_function.invoke({\"topic\": \"bears\"})"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "c9a481d1",
-   "metadata": {},
-   "source": [
-    "Note that we didn't need to wrap the custom function `(lambda x: x.content[:5])` in a `RunnableLambda` constructor because the `model` on the left of the pipe operator is already a Runnable. The custom function is **coerced** into a runnable. See [this section](/docs/how_to/sequence/#coercion) for more information.\n",
-    "\n",
-    "## Passing run metadata\n",
-    "\n",
-    "Runnable lambdas can optionally accept a [RunnableConfig](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.config.RunnableConfig.html#langchain_core.runnables.config.RunnableConfig) parameter, which they can use to pass callbacks, tags, and other configuration information to nested runs."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 5,
    "id": "ff0daf0c-49dd-4d21-9772-e5fa133c5f36",
    "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "{'foo': 'bar'}\n",
-      "Tokens Used: 62\n",
-      "\tPrompt Tokens: 56\n",
-      "\tCompletion Tokens: 6\n",
-      "Successful Requests: 1\n",
-      "Total Cost (USD): $9.6e-05\n"
-     ]
-    }
-   ],
+   "outputs": [],
    "source": [
     "import json\n",
     "\n",
-    "from langchain_core.runnables import RunnableConfig\n",
-    "\n",
     "\n",
     "def parse_or_fix(text: str, config: RunnableConfig):\n",
     "    fixing_chain = (\n",
@@ -244,7 +132,7 @@
     "            \"Fix the following text:\\n\\n```text\\n{input}\\n```\\nError: {error}\"\n",
     "            \" Don't narrate, just respond with the fixed data.\"\n",
     "        )\n",
-    "        | model\n",
+    "        | ChatOpenAI()\n",
     "        | StrOutputParser()\n",
     "    )\n",
     "    for _ in range(3):\n",
@@ -252,22 +140,12 @@
     "            return json.loads(text)\n",
     "        except Exception as e:\n",
     "            text = fixing_chain.invoke({\"input\": text, \"error\": e}, config)\n",
-    "    return \"Failed to parse\"\n",
-    "\n",
-    "\n",
-    "from langchain_community.callbacks import get_openai_callback\n",
-    "\n",
-    "with get_openai_callback() as cb:\n",
-    "    output = RunnableLambda(parse_or_fix).invoke(\n",
-    "        \"{foo: bar}\", {\"tags\": [\"my-tag\"], \"callbacks\": [cb]}\n",
-    "    )\n",
-    "    print(output)\n",
-    "    print(cb)"
+    "    return \"Failed to parse\""
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 6,
+   "execution_count": 5,
    "id": "1a5e709e-9d75-48c7-bb9c-503251990505",
    "metadata": {},
    "outputs": [
@@ -300,13 +178,9 @@
    "id": "922b48bd",
    "metadata": {},
    "source": [
-    "## Streaming\n",
+    "# Streaming\n",
     "\n",
-    ":::{.callout-note}\n",
-    "[RunnableLambda](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.base.RunnableLambda.html) is best suited for code that does not need to support streaming. If you need to support streaming (i.e., be able to operate on chunks of inputs and yield chunks of outputs), use [RunnableGenerator](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.base.RunnableGenerator.html) instead as in the example below.\n",
-    ":::\n",
-    "\n",
-    "You can use generator functions (ie. functions that use the `yield` keyword, and behave like iterators) in a chain.\n",
+    "You can use generator functions (ie. functions that use the `yield` keyword, and behave like iterators) in a LCEL pipeline.\n",
     "\n",
     "The signature of these generators should be `Iterator[Input] -> Iterator[Output]`. Or for async generators: `AsyncIterator[Input] -> AsyncIterator[Output]`.\n",
     "\n",
@@ -314,13 +188,30 @@
     "- implementing a custom output parser\n",
     "- modifying the output of a previous step, while preserving streaming capabilities\n",
     "\n",
-    "Here's an example of a custom output parser for comma-separated lists. First, we create a chain that generates such a list as text:"
+    "Here's an example of a custom output parser for comma-separated lists:"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 6,
+   "id": "29f55c38",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from typing import Iterator, List\n",
+    "\n",
+    "prompt = ChatPromptTemplate.from_template(\n",
+    "    \"Write a comma-separated list of 5 animals similar to: {animal}. Do not include numbers\"\n",
+    ")\n",
+    "model = ChatOpenAI(temperature=0.0)\n",
+    "\n",
+    "str_chain = prompt | model | StrOutputParser()"
    ]
   },
   {
    "cell_type": "code",
    "execution_count": 7,
-   "id": "29f55c38",
+   "id": "75aa946b",
    "metadata": {},
    "outputs": [
     {
@@ -332,44 +223,37 @@
     }
    ],
    "source": [
-    "from typing import Iterator, List\n",
-    "\n",
-    "prompt = ChatPromptTemplate.from_template(\n",
-    "    \"Write a comma-separated list of 5 animals similar to: {animal}. Do not include numbers\"\n",
-    ")\n",
-    "\n",
-    "str_chain = prompt | model | StrOutputParser()\n",
-    "\n",
     "for chunk in str_chain.stream({\"animal\": \"bear\"}):\n",
     "    print(chunk, end=\"\", flush=True)"
    ]
   },
   {
-   "cell_type": "markdown",
-   "id": "46345323",
+   "cell_type": "code",
+   "execution_count": 8,
+   "id": "d002a7fe",
    "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "'lion, tiger, wolf, gorilla, panda'"
+      ]
+     },
+     "execution_count": 8,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
    "source": [
-    "Next, we define a custom function that will aggregate the currently streamed output and yield it when the model generates the next comma in the list:"
+    "str_chain.invoke({\"animal\": \"bear\"})"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 8,
+   "execution_count": 9,
    "id": "f08b8a5b",
    "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "['lion']\n",
-      "['tiger']\n",
-      "['wolf']\n",
-      "['gorilla']\n",
-      "['raccoon']\n"
-     ]
-    }
-   ],
+   "outputs": [],
    "source": [
     "# This is a custom parser that splits an iterator of llm tokens\n",
     "# into a list of strings separated by commas\n",
@@ -388,58 +272,23 @@
     "            # save the rest for the next iteration\n",
     "            buffer = buffer[comma_index + 1 :]\n",
     "    # yield the last chunk\n",
-    "    yield [buffer.strip()]\n",
-    "\n",
-    "\n",
-    "list_chain = str_chain | split_into_list\n",
-    "\n",
-    "for chunk in list_chain.stream({\"animal\": \"bear\"}):\n",
-    "    print(chunk, flush=True)"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "0a5adb69",
-   "metadata": {},
-   "source": [
-    "Invoking it gives a full array of values:"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 9,
-   "id": "9ea4ddc6",
-   "metadata": {},
-   "outputs": [
-    {
-     "data": {
-      "text/plain": [
-       "['lion', 'tiger', 'wolf', 'gorilla', 'raccoon']"
-      ]
-     },
-     "execution_count": 9,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
-   "source": [
-    "list_chain.invoke({\"animal\": \"bear\"})"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "96e320ed",
-   "metadata": {},
-   "source": [
-    "## Async version\n",
-    "\n",
-    "If you are working in an `async` environment, here is an `async` version of the above example:"
+    "    yield [buffer.strip()]"
    ]
   },
   {
    "cell_type": "code",
    "execution_count": 10,
-   "id": "569dbbef",
+   "id": "02e414aa",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "list_chain = str_chain | split_into_list"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 11,
+   "id": "7ed8799d",
    "metadata": {},
    "outputs": [
     {
@@ -454,6 +303,46 @@
      ]
     }
    ],
+   "source": [
+    "for chunk in list_chain.stream({\"animal\": \"bear\"}):\n",
+    "    print(chunk, flush=True)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 12,
+   "id": "9ea4ddc6",
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "['lion', 'tiger', 'wolf', 'gorilla', 'elephant']"
+      ]
+     },
+     "execution_count": 12,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "list_chain.invoke({\"animal\": \"bear\"})"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "96e320ed",
+   "metadata": {},
+   "source": [
+    "## Async version"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 13,
+   "id": "569dbbef",
+   "metadata": {},
+   "outputs": [],
    "source": [
     "from typing import AsyncIterator\n",
     "\n",
@@ -473,15 +362,35 @@
     "    yield [buffer.strip()]\n",
     "\n",
     "\n",
-    "list_chain = str_chain | asplit_into_list\n",
-    "\n",
+    "list_chain = str_chain | asplit_into_list"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 14,
+   "id": "7a76b713",
+   "metadata": {},
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "['lion']\n",
+      "['tiger']\n",
+      "['wolf']\n",
+      "['gorilla']\n",
+      "['panda']\n"
+     ]
+    }
+   ],
+   "source": [
     "async for chunk in list_chain.astream({\"animal\": \"bear\"}):\n",
     "    print(chunk, flush=True)"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 11,
+   "execution_count": 15,
    "id": "3a650482",
    "metadata": {},
    "outputs": [
@@ -491,7 +400,7 @@
        "['lion', 'tiger', 'wolf', 'gorilla', 'panda']"
       ]
      },
-     "execution_count": 11,
+     "execution_count": 15,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -499,18 +408,6 @@
    "source": [
     "await list_chain.ainvoke({\"animal\": \"bear\"})"
    ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "3306ac3b",
-   "metadata": {},
-   "source": [
-    "## Next steps\n",
-    "\n",
-    "Now you've learned a few different ways to use custom logic within your chains, and how to implement streaming.\n",
-    "\n",
-    "To learn more, see the other how-to guides on runnables in this section."
-   ]
   }
  ],
  "metadata": {
@@ -529,7 +426,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.9.1"
+   "version": "3.10.5"
   }
  },
  "nbformat": 4,

docs/docs/expression_language/primitives/index.mdx

@@ -0,0 +1,15 @@
+---
+sidebar_class_name: hidden
+---
+
+# Primitives
+
+In addition to various [components](/docs/modules) that are usable with LCEL, LangChain also includes various primitives
+that help pass around and format data, bind arguments, invoke custom logic, and more.
+
+This section goes into greater depth on where and how some of these components are useful.
+
+import DocCardList from "@theme/DocCardList";
+import { useCurrentSidebarCategory } from '@docusaurus/theme-common';
+
+<DocCardList items={useCurrentSidebarCategory().items.filter((item) => item.href !== "/docs/expression_language/primitives/")} />

docs/docs/expression_language/primitives/parallel.ipynb

@@ -7,6 +7,7 @@
    "source": [
     "---\n",
     "sidebar_position: 1\n",
+    "title: \"Parallel: Format data\"\n",
     "keywords: [RunnableParallel, RunnableMap, LCEL]\n",
     "---"
    ]
@@ -16,33 +17,13 @@
    "id": "b022ab74-794d-4c54-ad47-ff9549ddb9d2",
    "metadata": {},
    "source": [
-    "# How to invoke runnables in parallel\n",
+    "# Formatting inputs & output\n",
     "\n",
-    ":::info Prerequisites\n",
+    "The `RunnableParallel` primitive is essentially a dict whose values are runnables (or things that can be coerced to runnables, like functions). It runs all of its values in parallel, and each value is called with the overall input of the `RunnableParallel`. The final return value is a dict with the results of each value under its appropriate key.\n",
     "\n",
-    "This guide assumes familiarity with the following concepts:\n",
-    "- [LangChain Expression Language (LCEL)](/docs/concepts/#langchain-expression-language)\n",
-    "- [Chaining runnables](/docs/how_to/sequence)\n",
+    "It is useful for parallelizing operations, but can also be useful for manipulating the output of one Runnable to match the input format of the next Runnable in a sequence.\n",
     "\n",
-    ":::\n",
-    "\n",
-    "The [`RunnableParallel`](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.base.RunnableParallel.html) primitive is essentially a dict whose values are runnables (or things that can be coerced to runnables, like functions). It runs all of its values in parallel, and each value is called with the overall input of the `RunnableParallel`. The final return value is a dict with the results of each value under its appropriate key.\n",
-    "\n",
-    "## Formatting with `RunnableParallels`\n",
-    "\n",
-    "`RunnableParallels` are useful for parallelizing operations, but can also be useful for manipulating the output of one Runnable to match the input format of the next Runnable in a sequence. You can use them to split or fork the chain so that multiple components can process the input in parallel. Later, other components can join or merge the results to synthesize a final response. This type of chain creates a computation graph that looks like the following:\n",
-    "\n",
-    "```text\n",
-    "     Input\n",
-    "      / \\\n",
-    "     /   \\\n",
-    " Branch1 Branch2\n",
-    "     \\   /\n",
-    "      \\ /\n",
-    "      Combine\n",
-    "```\n",
-    "\n",
-    "Below, the input to prompt is expected to be a map with keys `\"context\"` and `\"question\"`. The user input is just the question. So we need to get the context using our retriever and passthrough the user input under the `\"question\"` key.\n"
+    "Here the input to prompt is expected to be a map with keys \"context\" and \"question\". The user input is just the question. So we need to get the context using our retriever and passthrough the user input under the \"question\" key.\n"
    ]
   },
   {
@@ -52,20 +33,12 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "# | output: false\n",
-    "# | echo: false\n",
-    "\n",
-    "%pip install -qU langchain langchain_openai\n",
-    "\n",
-    "import os\n",
-    "from getpass import getpass\n",
-    "\n",
-    "os.environ[\"OPENAI_API_KEY\"] = getpass()"
+    "%pip install --upgrade --quiet  langchain langchain-openai"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 2,
+   "execution_count": 3,
    "id": "267d1460-53c1-4fdb-b2c3-b6a1eb7fccff",
    "metadata": {},
    "outputs": [
@@ -75,7 +48,7 @@
        "'Harrison worked at Kensho.'"
       ]
      },
-     "execution_count": 2,
+     "execution_count": 3,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -96,10 +69,7 @@
     "\n",
     "Question: {question}\n",
     "\"\"\"\n",
-    "\n",
-    "# The prompt expects input with keys for \"context\" and \"question\"\n",
     "prompt = ChatPromptTemplate.from_template(template)\n",
-    "\n",
     "model = ChatOpenAI()\n",
     "\n",
     "retrieval_chain = (\n",
@@ -132,8 +102,7 @@
     "```\n",
     "RunnableParallel(context=retriever, question=RunnablePassthrough())\n",
     "```\n",
-    "\n",
-    "See the section on [coercion for more](/docs/how_to/sequence/#coercion)."
+    "\n"
    ]
   },
   {
@@ -150,7 +119,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 3,
+   "execution_count": 6,
    "id": "84fc49e1-2daf-4700-ae33-a0a6ed47d5f6",
    "metadata": {},
    "outputs": [
@@ -160,7 +129,7 @@
        "'Harrison ha lavorato a Kensho.'"
       ]
      },
-     "execution_count": 3,
+     "execution_count": 6,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -209,23 +178,23 @@
    "source": [
     "## Parallelize steps\n",
     "\n",
-    "RunnableParallels make it easy to execute multiple Runnables in parallel, and to return the output of these Runnables as a map."
+    "RunnableParallel (aka. RunnableMap) makes it easy to execute multiple Runnables in parallel, and to return the output of these Runnables as a map."
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 4,
+   "execution_count": 1,
    "id": "31f18442-f837-463f-bef4-8729368f5f8b",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "{'joke': AIMessage(content=\"Why don't bears like fast food? Because they can't catch it!\", response_metadata={'token_usage': {'completion_tokens': 15, 'prompt_tokens': 13, 'total_tokens': 28}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_d9767fc5b9', 'finish_reason': 'stop', 'logprobs': None}, id='run-fe024170-c251-4b7a-bfd4-64a3737c67f2-0'),\n",
-       " 'poem': AIMessage(content='In the quiet of the forest, the bear roams free\\nMajestic and wild, a sight to see.', response_metadata={'token_usage': {'completion_tokens': 24, 'prompt_tokens': 15, 'total_tokens': 39}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_c2295e73ad', 'finish_reason': 'stop', 'logprobs': None}, id='run-2707913e-a743-4101-b6ec-840df4568a76-0')}"
+       "{'joke': AIMessage(content=\"Why don't bears wear shoes?\\n\\nBecause they have bear feet!\"),\n",
+       " 'poem': AIMessage(content=\"In the wild's embrace, bear roams free,\\nStrength and grace, a majestic decree.\")}"
       ]
      },
-     "execution_count": 4,
+     "execution_count": 1,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -258,7 +227,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 5,
+   "execution_count": 6,
    "id": "38e47834-45af-4281-991f-86f150001510",
    "metadata": {},
    "outputs": [
@@ -266,7 +235,7 @@
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "610 ms ± 64 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)\n"
+      "958 ms ± 402 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)\n"
      ]
     }
    ],
@@ -278,7 +247,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 6,
+   "execution_count": 7,
    "id": "d0cd40de-b37e-41fa-a2f6-8aaa49f368d6",
    "metadata": {},
    "outputs": [
@@ -286,7 +255,7 @@
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "599 ms ± 73.3 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)\n"
+      "1.22 s ± 508 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)\n"
      ]
     }
    ],
@@ -298,7 +267,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 7,
+   "execution_count": 8,
    "id": "799894e1-8e18-4a73-b466-f6aea6af3920",
    "metadata": {},
    "outputs": [
@@ -306,7 +275,7 @@
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "643 ms ± 77.8 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)\n"
+      "1.15 s ± 119 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)\n"
      ]
     }
    ],
@@ -315,26 +284,6 @@
     "\n",
     "map_chain.invoke({\"topic\": \"bear\"})"
    ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "7d4492e1",
-   "metadata": {},
-   "source": [
-    "## Next steps\n",
-    "\n",
-    "You now know some ways to format and parallelize chain steps with `RunnableParallel`.\n",
-    "\n",
-    "To learn more, see the other how-to guides on runnables in this section."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "4af8bebd",
-   "metadata": {},
-   "outputs": [],
-   "source": []
   }
  ],
  "metadata": {
@@ -353,7 +302,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.9.1"
+   "version": "3.11.6"
   }
  },
  "nbformat": 4,

docs/docs/expression_language/primitives/passthrough.ipynb

@@ -7,6 +7,7 @@
    "source": [
     "---\n",
     "sidebar_position: 5\n",
+    "title: \"Passthrough: Pass through inputs\"\n",
     "keywords: [RunnablePassthrough, LCEL]\n",
     "---"
    ]
@@ -16,20 +17,9 @@
    "id": "b022ab74-794d-4c54-ad47-ff9549ddb9d2",
    "metadata": {},
    "source": [
-    "# How to pass through arguments from one step to the next\n",
+    "# Passing data through\n",
     "\n",
-    ":::info Prerequisites\n",
-    "\n",
-    "This guide assumes familiarity with the following concepts:\n",
-    "- [LangChain Expression Language (LCEL)](/docs/concepts/#langchain-expression-language)\n",
-    "- [Chaining runnables](/docs/how_to/sequence/)\n",
-    "- [Calling runnables in parallel](/docs/how_to/parallel/)\n",
-    "- [Custom functions](/docs/how_to/functions/)\n",
-    "\n",
-    ":::\n",
-    "\n",
-    "\n",
-    "When composing chains with several steps, sometimes you will want to pass data from previous steps unchanged for use as input to a later step. The [`RunnablePassthrough`](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.passthrough.RunnablePassthrough.html) class allows you to do just this, and is typically is used in conjuction with a [RunnableParallel](/docs/how_to/parallel/) to pass data through to a later step in your constructed chains.\n",
+    "RunnablePassthrough on its own allows you to pass inputs unchanged. This typically is used in conjuction with RunnableParallel to pass data through to a new key in the map. \n",
     "\n",
     "See the example below:"
    ]
@@ -41,27 +31,22 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "%pip install -qU langchain langchain-openai\n",
-    "\n",
-    "import os\n",
-    "from getpass import getpass\n",
-    "\n",
-    "os.environ[\"OPENAI_API_KEY\"] = getpass()"
+    "%pip install --upgrade --quiet  langchain langchain-openai"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 2,
+   "execution_count": 11,
    "id": "03988b8d-d54c-4492-8707-1594372cf093",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "{'passed': {'num': 1}, 'modified': 2}"
+       "{'passed': {'num': 1}, 'extra': {'num': 1, 'mult': 3}, 'modified': 2}"
       ]
      },
-     "execution_count": 2,
+     "execution_count": 11,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -94,12 +79,12 @@
    "source": [
     "## Retrieval Example\n",
     "\n",
-    "In the example below, we see a more real-world use case where we use `RunnablePassthrough` along with `RunnableParallel` in a chain to properly format inputs to a prompt:"
+    "In the example below, we see a use case where we use `RunnablePassthrough` along with `RunnableParallel`. "
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 3,
+   "execution_count": 17,
    "id": "267d1460-53c1-4fdb-b2c3-b6a1eb7fccff",
    "metadata": {},
    "outputs": [
@@ -109,7 +94,7 @@
        "'Harrison worked at Kensho.'"
       ]
      },
-     "execution_count": 3,
+     "execution_count": 17,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -148,13 +133,7 @@
    "id": "392cd4c4-e7ed-4ab8-934d-f7a4eca55ee1",
    "metadata": {},
    "source": [
-    "Here the input to prompt is expected to be a map with keys \"context\" and \"question\". The user input is just the question. So we need to get the context using our retriever and passthrough the user input under the \"question\" key. The `RunnablePassthrough` allows us to pass on the user's question to the prompt and model. \n",
-    "\n",
-    "## Next steps\n",
-    "\n",
-    "Now you've learned how to pass data through your chains to help to help format the data flowing through your chains.\n",
-    "\n",
-    "To learn more, see the other how-to guides on runnables in this section."
+    "Here the input to prompt is expected to be a map with keys \"context\" and \"question\". The user input is just the question. So we need to get the context using our retriever and passthrough the user input under the \"question\" key. In this case, the RunnablePassthrough allows us to pass on the user's question to the prompt and model. \n"
    ]
   }
  ],
@@ -174,7 +153,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.9.1"
+   "version": "3.11.6"
   }
  },
  "nbformat": 4,

docs/docs/expression_language/primitives/sequence.ipynb

@@ -2,14 +2,12 @@
  "cells": [
   {
    "cell_type": "raw",
-   "metadata": {
-    "vscode": {
-     "languageId": "raw"
-    }
-   },
+   "metadata": {},
    "source": [
     "---\n",
-    "keywords: [Runnable, Runnables, RunnableSequence, LCEL, chain, chains, chaining]\n",
+    "sidebar_position: 0\n",
+    "title: \"Sequences: Chaining runnables\"\n",
+    "keywords: [Runnable, Runnables, LCEL]\n",
     "---"
    ]
   },
@@ -17,54 +15,22 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "# How to chain runnables\n",
+    "# Chaining runnables\n",
     "\n",
-    ":::info Prerequisites\n",
+    "One key advantage of the `Runnable` interface is that any two runnables can be \"chained\" together into sequences. The output of the previous runnable's `.invoke()` call is passed as input to the next runnable. This can be done using the pipe operator (`|`), or the more explicit `.pipe()` method, which does the same thing. The resulting `RunnableSequence` is itself a runnable, which means it can be invoked, streamed, or piped just like any other runnable.\n",
     "\n",
-    "This guide assumes familiarity with the following concepts:\n",
-    "- [LangChain Expression Language (LCEL)](/docs/concepts/#langchain-expression-language)\n",
-    "- [Prompt templates](/docs/concepts/#prompt-templates)\n",
-    "- [Chat models](/docs/concepts/#chat-models)\n",
-    "- [Output parser](/docs/concepts/#output-parsers)\n",
+    "## The pipe operator\n",
     "\n",
-    ":::\n",
-    "\n",
-    "One point about [LangChain Expression Language](/docs/concepts/#langchain-expression-language) is that any two runnables can be \"chained\" together into sequences. The output of the previous runnable's `.invoke()` call is passed as input to the next runnable. This can be done using the pipe operator (`|`), or the more explicit `.pipe()` method, which does the same thing.\n",
-    "\n",
-    "The resulting [`RunnableSequence`](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.base.RunnableSequence.html) is itself a runnable, which means it can be invoked, streamed, or further chained just like any other runnable. Advantages of chaining runnables in this way are efficient streaming (the sequence will stream output as soon as it is available), and debugging and tracing with tools like [LangSmith](/docs/how_to/debugging).\n",
-    "\n",
-    "## The pipe operator: `|`\n",
-    "\n",
-    "To show off how this works, let's go through an example. We'll walk through a common pattern in LangChain: using a [prompt template](/docs/how_to#prompt-templates) to format input into a [chat model](/docs/how_to#chat-models), and finally converting the chat message output into a string with an [output parser](/docs/how_to#output-parsers).\n",
-    "\n",
-    "```{=mdx}\n",
-    "import ChatModelTabs from \"@theme/ChatModelTabs\";\n",
-    "\n",
-    "<ChatModelTabs\n",
-    "  customVarName=\"model\"\n",
-    "/>\n",
-    "```"
+    "To show off how this works, let's go through an example. We'll walk through a common pattern in LangChain: using a [prompt template](/docs/modules/model_io/prompts/) to format input into a [chat model](/docs/modules/model_io/chat/), and finally converting the chat message output into a string with an [output parser](/docs/modules/model_io/output_parsers/)."
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 1,
+   "execution_count": null,
    "metadata": {},
    "outputs": [],
    "source": [
-    "# | output: false\n",
-    "# | echo: false\n",
-    "\n",
-    "%pip install -qU langchain langchain_anthropic\n",
-    "\n",
-    "import os\n",
-    "from getpass import getpass\n",
-    "\n",
-    "from langchain_anthropic import ChatAnthropic\n",
-    "\n",
-    "os.environ[\"ANTHROPIC_API_KEY\"] = getpass()\n",
-    "\n",
-    "model = ChatAnthropic(model=\"claude-3-sonnet-20240229\", temperature=0)"
+    "%pip install --upgrade --quiet langchain langchain-anthropic"
    ]
   },
   {
@@ -73,10 +39,12 @@
    "metadata": {},
    "outputs": [],
    "source": [
+    "from langchain_anthropic import ChatAnthropic\n",
     "from langchain_core.output_parsers import StrOutputParser\n",
     "from langchain_core.prompts import ChatPromptTemplate\n",
     "\n",
     "prompt = ChatPromptTemplate.from_template(\"tell me a joke about {topic}\")\n",
+    "model = ChatAnthropic(model_name=\"claude-3-haiku-20240307\")\n",
     "\n",
     "chain = prompt | model | StrOutputParser()"
    ]
@@ -96,7 +64,7 @@
     {
      "data": {
       "text/plain": [
-       "\"Here's a bear joke for you:\\n\\nWhy did the bear dissolve in water?\\nBecause it was a polar bear!\""
+       "\"Here's a bear joke for you:\\n\\nWhy don't bears wear socks? \\nBecause they have bear feet!\\n\\nHow's that? I tried to keep it light and silly. Bears can make for some fun puns and jokes. Let me know if you'd like to hear another one!\""
       ]
      },
      "execution_count": 3,
@@ -118,7 +86,7 @@
     "\n",
     "For example, let's say we wanted to compose the joke generating chain with another chain that evaluates whether or not the generated joke was funny.\n",
     "\n",
-    "We would need to be careful with how we format the input into the next chain. In the below example, the dict in the chain is automatically parsed and converted into a [`RunnableParallel`](/docs/how_to/parallel), which runs all of its values in parallel and returns a dict with the results.\n",
+    "We would need to be careful with how we format the input into the next chain. In the below example, the dict in the chain is automatically parsed and converted into a [`RunnableParallel`](/docs/expression_language/primitives/parallel), which runs all of its values in parallel and returns a dict with the results.\n",
     "\n",
     "This happens to be the same format the next prompt template expects. Here it is in action:"
    ]
@@ -127,25 +95,32 @@
    "cell_type": "code",
    "execution_count": 4,
    "metadata": {},
-   "outputs": [
-    {
-     "data": {
-      "text/plain": [
-       "'Haha, that\\'s a clever play on words! Using \"polar\" to imply the bear dissolved or became polar/polarized when put in water. Not the most hilarious joke ever, but it has a cute, groan-worthy pun that makes it mildly amusing. I appreciate a good pun or wordplay joke.'"
-      ]
-     },
-     "execution_count": 4,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
+   "outputs": [],
    "source": [
     "from langchain_core.output_parsers import StrOutputParser\n",
     "\n",
     "analysis_prompt = ChatPromptTemplate.from_template(\"is this a funny joke? {joke}\")\n",
     "\n",
-    "composed_chain = {\"joke\": chain} | analysis_prompt | model | StrOutputParser()\n",
-    "\n",
+    "composed_chain = {\"joke\": chain} | analysis_prompt | model | StrOutputParser()"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 5,
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "\"That's a pretty classic and well-known bear pun joke. Whether it's considered funny is quite subjective, as humor is very personal. Some people may find that type of pun-based joke amusing, while others may not find it that humorous. Ultimately, the funniness of a joke is in the eye (or ear) of the beholder. If you enjoyed the joke and got a chuckle out of it, then that's what matters most.\""
+      ]
+     },
+     "execution_count": 5,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
     "composed_chain.invoke({\"topic\": \"bears\"})"
    ]
   },
@@ -158,20 +133,9 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 5,
+   "execution_count": 6,
    "metadata": {},
-   "outputs": [
-    {
-     "data": {
-      "text/plain": [
-       "\"Haha, that's a cute and punny joke! I like how it plays on the idea of beets blushing or turning red like someone blushing. Food puns can be quite amusing. While not a total knee-slapper, it's a light-hearted, groan-worthy dad joke that would make me chuckle and shake my head. Simple vegetable humor!\""
-      ]
-     },
-     "execution_count": 5,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
+   "outputs": [],
    "source": [
     "composed_chain_with_lambda = (\n",
     "    chain\n",
@@ -179,8 +143,26 @@
     "    | analysis_prompt\n",
     "    | model\n",
     "    | StrOutputParser()\n",
-    ")\n",
-    "\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 7,
+   "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "'I appreciate the effort, but I have to be honest - I didn\\'t find that joke particularly funny. Beet-themed puns can be quite hit-or-miss, and this one falls more on the \"miss\" side for me. The premise is a bit too straightforward and predictable. While I can see the logic behind it, the punchline just doesn\\'t pack much of a comedic punch. \\n\\nThat said, I do admire your willingness to explore puns and wordplay around vegetables. Cultivating a good sense of humor takes practice, and not every joke is going to land. The important thing is to keep experimenting and finding what works. Maybe try for a more unexpected or creative twist on beet-related humor next time. But thanks for sharing - I always appreciate when humans test out jokes on me, even if they don\\'t always make me laugh out loud.'"
+      ]
+     },
+     "execution_count": 7,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
     "composed_chain_with_lambda.invoke({\"topic\": \"beets\"})"
    ]
   },
@@ -188,7 +170,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "However, keep in mind that using functions like this may interfere with operations like streaming. See [this section](/docs/how_to/functions) for more information."
+    "However, keep in mind that using functions like this may interfere with operations like streaming. See [this section](/docs/expression_language/primitives/functions) for more information."
    ]
   },
   {
@@ -202,20 +184,9 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 6,
+   "execution_count": 8,
    "metadata": {},
-   "outputs": [
-    {
-     "data": {
-      "text/plain": [
-       "\"I cannot reproduce any copyrighted material verbatim, but I can try to analyze the humor in the joke you provided without quoting it directly.\\n\\nThe joke plays on the idea that the Cylon raiders, who are the antagonists in the Battlestar Galactica universe, failed to locate the human survivors after attacking their home planets (the Twelve Colonies) due to using an outdated and poorly performing operating system (Windows Vista) for their targeting systems.\\n\\nThe humor stems from the juxtaposition of a futuristic science fiction setting with a relatable real-world frustration – the use of buggy, slow, or unreliable software or technology. It pokes fun at the perceived inadequacies of Windows Vista, which was widely criticized for its performance issues and other problems when it was released.\\n\\nBy attributing the Cylons' failure to locate the humans to their use of Vista, the joke creates an amusing and unexpected connection between a fictional advanced race of robots and a familiar technological annoyance experienced by many people in the real world.\\n\\nOverall, the joke relies on incongruity and relatability to generate humor, but without reproducing any copyrighted material directly.\""
-      ]
-     },
-     "execution_count": 6,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
+   "outputs": [],
    "source": [
     "from langchain_core.runnables import RunnableParallel\n",
     "\n",
@@ -224,42 +195,33 @@
     "    .pipe(analysis_prompt)\n",
     "    .pipe(model)\n",
     "    .pipe(StrOutputParser())\n",
-    ")\n",
-    "\n",
-    "composed_chain_with_pipe.invoke({\"topic\": \"battlestar galactica\"})"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "metadata": {},
-   "source": [
-    "Or the abbreviated:"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "composed_chain_with_pipe = RunnableParallel({\"joke\": chain}).pipe(\n",
-    "    analysis_prompt, model, StrOutputParser()\n",
     ")"
    ]
   },
   {
-   "cell_type": "markdown",
+   "cell_type": "code",
+   "execution_count": 9,
    "metadata": {},
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "'That\\'s a pretty good Battlestar Galactica-themed pun! I appreciated the clever play on words with \"Centurion\" and \"center on.\" It\\'s the kind of nerdy, science fiction-inspired humor that fans of the show would likely enjoy. The joke is clever and demonstrates a good understanding of the Battlestar Galactica universe. I\\'d be curious to hear any other Battlestar-related jokes you might have up your sleeve. As long as they don\\'t reproduce copyrighted material, I\\'m happy to provide my thoughts on the humor and appeal for fans of the show.'"
+      ]
+     },
+     "execution_count": 9,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
    "source": [
-    "## Related\n",
-    "\n",
-    "- [Streaming](/docs/how_to/streaming/): Check out the streaming guide to understand the streaming behavior of a chain\n"
+    "composed_chain_with_pipe.invoke({\"topic\": \"battlestar galactica\"})"
    ]
   }
  ],
  "metadata": {
   "kernelspec": {
-   "display_name": "Python 3 (ipykernel)",
+   "display_name": "Python 3",
    "language": "python",
    "name": "python3"
   },
@@ -273,9 +235,9 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.9.1"
+   "version": "3.10.5"
   }
  },
  "nbformat": 4,
- "nbformat_minor": 4
+ "nbformat_minor": 2
 }

docs/docs/get_started/installation.mdx

@@ -2,14 +2,11 @@
 sidebar_position: 2
 ---
 
-# How to install LangChain packages
-
-The LangChain ecosystem is split into different packages, which allow you to choose exactly which pieces of
-functionality to install.
+# Installation
 
 ## Official release
 
-To install the main LangChain package, run:
+To install LangChain run:
 
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
@@ -24,24 +21,11 @@ import CodeBlock from "@theme/CodeBlock";
   </TabItem>
 </Tabs>
 
-While this package acts as a sane starting point to using LangChain,
-much of the value of LangChain comes when integrating it with various model providers, datastores, etc.
+This will install the bare minimum requirements of LangChain.
+A lot of the value of LangChain comes when integrating it with various model providers, datastores, etc.
 By default, the dependencies needed to do that are NOT installed. You will need to install the dependencies for specific integrations separately.
-We'll show how to do that in the next sections of this guide.
 
-## Ecosystem packages
-
-With the exception of the `langsmith` SDK, all packages in the LangChain ecosystem depend on `langchain-core`, which contains base
-classes and abstractions that other packages use. The dependency graph below shows how the difference packages are related.
-A directed arrow indicates that the source package depends on the target package:
-
-![](/img/ecosystem_packages.png)
-
-When installing a package, you do not need to explicitly install that package's explicit dependencies (such as `langchain-core`).
-However, you may choose to if you are using a feature only available in a certain version of that dependency.
-If you do, you should make sure that the installed or pinned version is compatible with any other integration packages you use.
-
-### From source
+## From source
 
 If you want to install from source, you can do so by cloning the repo and be sure that the directory is `PATH/TO/REPO/langchain/libs/langchain` running:
 
@@ -49,21 +33,21 @@ If you want to install from source, you can do so by cloning the repo and be sur
 pip install -e .
 ```
 
-### LangChain core
+## LangChain core
 The `langchain-core` package contains base abstractions that the rest of the LangChain ecosystem uses, along with the LangChain Expression Language. It is automatically installed by `langchain`, but can also be used separately. Install with:
 
 ```bash
 pip install langchain-core
 ```
 
-### LangChain community
-The `langchain-community` package contains third-party integrations. Install with:
+## LangChain community
+The `langchain-community` package contains third-party integrations. It is automatically installed by `langchain`, but can also be used separately. Install with:
 
 ```bash
 pip install langchain-community
 ```
 
-### LangChain experimental
+## LangChain experimental
 The `langchain-experimental` package holds experimental LangChain code, intended for research and experimental uses.
 Install with:
 
@@ -71,15 +55,14 @@ Install with:
 pip install langchain-experimental
 ```
 
-### LangGraph
-`langgraph` is a library for building stateful, multi-actor applications with LLMs. It integrates smoothly with LangChain, but can be used without it.
+## LangGraph
+`langgraph` is a library for building stateful, multi-actor applications with LLMs, built on top of (and intended to be used with) LangChain.
 Install with:
 
 ```bash
 pip install langgraph
 ```
-
-### LangServe
+## LangServe
 LangServe helps developers deploy LangChain runnables and chains as a REST API.
 LangServe is automatically installed by LangChain CLI.
 If not using LangChain CLI, install with:
@@ -97,10 +80,9 @@ Install with:
 pip install langchain-cli
 ```
 
-### LangSmith SDK
-The LangSmith SDK is automatically installed by LangChain. However, it does not depend on
-`langchain-core`, and can be installed and used independently if desired.
-If you are not using LangChain, you can install it with:
+## LangSmith SDK
+The LangSmith SDK is automatically installed by LangChain.
+If not using LangChain, install with:
 
 ```bash
 pip install langsmith

docs/docs/get_started/introduction.mdx

@@ -0,0 +1,101 @@
+---
+sidebar_position: 0
+sidebar_class_name: hidden
+---
+
+# Introduction
+
+**LangChain** is a framework for developing applications powered by large language models (LLMs).
+
+LangChain simplifies every stage of the LLM application lifecycle:
+- **Development**: Build your applications using LangChain's open-source [building blocks](/docs/expression_language/) and [components](/docs/modules/). Hit the ground running using [third-party integrations](/docs/integrations/platforms/) and [Templates](/docs/templates).
+- **Productionization**: Use [LangSmith](/docs/langsmith/) to inspect, monitor and evaluate your chains, so that you can continuously optimize and deploy with confidence.
+- **Deployment**: Turn any chain into an API with [LangServe](/docs/langserve).
+
+import ThemedImage from '@theme/ThemedImage';
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+<ThemedImage
+  alt="Diagram outlining the hierarchical organization of the LangChain framework, displaying the interconnected parts across multiple layers."
+  sources={{
+    light: useBaseUrl('/svg/langchain_stack.svg'),
+    dark: useBaseUrl('/svg/langchain_stack_dark.svg'),
+  }}
+  title="LangChain Framework Overview"
+/>
+
+Concretely, the framework consists of the following open-source libraries:
+
+- **`langchain-core`**: Base abstractions and LangChain Expression Language.
+- **`langchain-community`**: Third party integrations.
+  - Partner packages (e.g. **`langchain-openai`**, **`langchain-anthropic`**, etc.): Some integrations have been further split into their own lightweight packages that only depend on **`langchain-core`**.
+- **`langchain`**: Chains, agents, and retrieval strategies that make up an application's cognitive architecture.
+- **[langgraph](/docs/langgraph)**: Build robust and stateful multi-actor applications with LLMs by modeling steps as edges and nodes in a graph.
+- **[langserve](/docs/langserve)**: Deploy LangChain chains as REST APIs.
+
+The broader ecosystem includes:
+
+- **[LangSmith](/docs/langsmith)**: A developer platform that lets you debug, test, evaluate, and monitor LLM applications and seamlessly integrates with LangChain.
+
+## Get started
+
+We recommend following our [Quickstart](/docs/get_started/quickstart) guide to familiarize yourself with the framework by building your first LangChain application.
+
+[See here](/docs/get_started/installation) for instructions on how to install LangChain, set up your environment, and start building.
+
+:::note
+
+These docs focus on the Python LangChain library. [Head here](https://js.langchain.com) for docs on the JavaScript LangChain library.
+
+:::
+
+## Use cases
+
+If you're looking to build something specific or are more of a hands-on learner, check out our [use-cases](/docs/use_cases).
+They're walkthroughs and techniques for common end-to-end tasks, such as:
+
+- [Question answering with RAG](/docs/use_cases/question_answering/)
+- [Extracting structured output](/docs/use_cases/extraction/)
+- [Chatbots](/docs/use_cases/chatbots/)
+- and more!
+
+
+## Expression Language
+
+LangChain Expression Language (LCEL) is the foundation of many of LangChain's components, and is a declarative way to compose chains. LCEL was designed from day 1 to support putting prototypes in production, with no code changes, from the simplest “prompt + LLM” chain to the most complex chains.
+
+- **[Get started](/docs/expression_language/)**: LCEL and its benefits
+- **[Runnable interface](/docs/expression_language/interface)**: The standard interface for LCEL objects
+- **[Primitives](/docs/expression_language/primitives)**: More on the primitives LCEL includes
+- and more!
+
+## Ecosystem
+
+### [🦜🛠️ LangSmith](/docs/langsmith)
+Trace and evaluate your language model applications and intelligent agents to help you move from prototype to production.
+
+### [🦜🕸️ LangGraph](/docs/langgraph)
+Build stateful, multi-actor applications with LLMs, built on top of (and intended to be used with) LangChain primitives.
+
+### [🦜🏓 LangServe](/docs/langserve)
+Deploy LangChain runnables and chains as REST APIs.
+
+## [Security](/docs/security)
+Read up on our [Security](/docs/security) best practices to make sure you're developing safely with LangChain.
+
+## Additional resources
+
+### [Components](/docs/modules/)
+LangChain provides standard, extendable interfaces and integrations for many different components, including:
+
+### [Integrations](/docs/integrations/providers/)
+LangChain is part of a rich ecosystem of tools that integrate with our framework and build on top of it. Check out our growing list of [integrations](/docs/integrations/providers/).
+
+### [Guides](/docs/guides/)
+Best practices for developing with LangChain.
+
+### [API reference](https://api.python.langchain.com)
+Head to the reference section for full documentation of all classes and methods in the LangChain and LangChain Experimental Python packages.
+
+### [Contributing](/docs/contributing)
+Check out the developer's guide for guidelines on contributing and help getting your dev environment set up.

docs/docs/get_started/quickstart.mdx

@@ -0,0 +1,685 @@
+---
+sidebar_position: 1
+---
+
+# Quickstart
+
+In this quickstart we'll show you how to:
+- Get setup with LangChain, LangSmith and LangServe
+- Use the most basic and common components of LangChain: prompt templates, models, and output parsers
+- Use LangChain Expression Language, the protocol that LangChain is built on and which facilitates component chaining
+- Build a simple application with LangChain
+- Trace your application with LangSmith
+- Serve your application with LangServe
+
+That's a fair amount to cover! Let's dive in.
+
+## Setup
+
+### Jupyter Notebook
+
+This guide (and most of the other guides in the documentation) uses [Jupyter notebooks](https://jupyter.org/) and assumes the reader is as well. Jupyter notebooks are perfect for learning how to work with LLM systems because oftentimes things can go wrong (unexpected output, API down, etc) and going through guides in an interactive environment is a great way to better understand them.
+
+You do not NEED to go through the guide in a Jupyter Notebook, but it is recommended. See [here](https://jupyter.org/install) for instructions on how to install.
+
+### Installation
+
+To install LangChain run:
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+import CodeBlock from "@theme/CodeBlock";
+
+<Tabs>
+  <TabItem value="pip" label="Pip" default>
+    <CodeBlock language="bash">pip install langchain</CodeBlock>
+  </TabItem>
+  <TabItem value="conda" label="Conda">
+    <CodeBlock language="bash">conda install langchain -c conda-forge</CodeBlock>
+  </TabItem>
+</Tabs>
+
+
+For more details, see our [Installation guide](/docs/get_started/installation).
+
+### LangSmith
+
+Many of the applications you build with LangChain will contain multiple steps with multiple invocations of LLM calls.
+As these applications get more and more complex, it becomes crucial to be able to inspect what exactly is going on inside your chain or agent.
+The best way to do this is with [LangSmith](https://smith.langchain.com).
+
+Note that LangSmith is not needed, but it is helpful.
+If you do want to use LangSmith, after you sign up at the link above, make sure to set your environment variables to start logging traces:
+
+```shell
+export LANGCHAIN_TRACING_V2="true"
+export LANGCHAIN_API_KEY="..."
+```
+
+## Building with LangChain
+
+LangChain enables building application that connect external sources of data and computation to LLMs.
+In this quickstart, we will walk through a few different ways of doing that.
+We will start with a simple LLM chain, which just relies on information in the prompt template to respond.
+Next, we will build a retrieval chain, which fetches data from a separate database and passes that into the prompt template.
+We will then add in chat history, to create a conversation retrieval chain. This allows you to interact in a chat manner with this LLM, so it remembers previous questions.
+Finally, we will build an agent - which utilizes an LLM to determine whether or not it needs to fetch data to answer questions.
+We will cover these at a high level, but there are lot of details to all of these!
+We will link to relevant docs.
+
+## LLM Chain
+
+We'll show how to use models available via API, like OpenAI, and local open source models, using integrations like Ollama.
+
+<Tabs>
+  <TabItem value="openai" label="OpenAI" default>
+
+First we'll need to import the LangChain x OpenAI integration package.
+
+```shell
+pip install langchain-openai
+```
+
+Accessing the API requires an API key, which you can get by creating an account and heading [here](https://platform.openai.com/account/api-keys). Once we have a key we'll want to set it as an environment variable by running:
+
+```shell
+export OPENAI_API_KEY="..."
+```
+
+We can then initialize the model:
+
+```python
+from langchain_openai import ChatOpenAI
+
+llm = ChatOpenAI()
+```
+
+If you'd prefer not to set an environment variable you can pass the key in directly via the `api_key` named parameter when initiating the OpenAI LLM class:
+
+```python
+from langchain_openai import ChatOpenAI
+
+llm = ChatOpenAI(api_key="...")
+```
+
+  </TabItem>
+  <TabItem value="local" label="Local (using Ollama)">
+
+[Ollama](https://ollama.ai/) allows you to run open-source large language models, such as Llama 2, locally.
+
+First, follow [these instructions](https://github.com/jmorganca/ollama) to set up and run a local Ollama instance:
+
+* [Download](https://ollama.ai/download)
+* Fetch a model via `ollama pull llama2`
+
+Then, make sure the Ollama server is running. After that, you can do:
+```python
+from langchain_community.llms import Ollama
+llm = Ollama(model="llama2")
+```
+
+  </TabItem>
+  <TabItem value="anthropic" label="Anthropic">
+
+First we'll need to import the LangChain x Anthropic package.
+
+```shell
+pip install langchain-anthropic
+```
+
+Accessing the API requires an API key, which you can get by creating an account [here](https://claude.ai/login). Once we have a key we'll want to set it as an environment variable by running:
+
+```shell
+export ANTHROPIC_API_KEY="..."
+```
+
+We can then initialize the model:
+
+```python
+from langchain_anthropic import ChatAnthropic
+
+llm = ChatAnthropic(model="claude-3-sonnet-20240229", temperature=0.2, max_tokens=1024)
+```
+
+If you'd prefer not to set an environment variable you can pass the key in directly via the `api_key` named parameter when initiating the Anthropic Chat Model class:
+
+```python
+llm = ChatAnthropic(api_key="...")
+```
+
+  </TabItem>
+  <TabItem value="cohere" label="Cohere">
+
+First we'll need to import the Cohere SDK package.
+
+```shell
+pip install langchain-cohere
+```
+
+Accessing the API requires an API key, which you can get by creating an account and heading [here](https://dashboard.cohere.com/api-keys). Once we have a key we'll want to set it as an environment variable by running:
+
+```shell
+export COHERE_API_KEY="..."
+```
+
+We can then initialize the model:
+
+```python
+from langchain_cohere import ChatCohere
+
+llm = ChatCohere()
+```
+
+If you'd prefer not to set an environment variable you can pass the key in directly via the `cohere_api_key` named parameter when initiating the Cohere LLM class:
+
+```python
+from langchain_cohere import ChatCohere
+
+llm = ChatCohere(cohere_api_key="...")
+```
+
+  </TabItem>
+</Tabs>
+
+Once you've installed and initialized the LLM of your choice, we can try using it!
+Let's ask it what LangSmith is - this is something that wasn't present in the training data so it shouldn't have a very good response.
+
+```python
+llm.invoke("how can langsmith help with testing?")
+```
+
+We can also guide its response with a prompt template.
+Prompt templates convert raw user input to better input to the LLM.
+
+```python
+from langchain_core.prompts import ChatPromptTemplate
+prompt = ChatPromptTemplate.from_messages([
+    ("system", "You are a world class technical documentation writer."),
+    ("user", "{input}")
+])
+```
+
+We can now combine these into a simple LLM chain:
+
+```python
+chain = prompt | llm 
+```
+
+We can now invoke it and ask the same question. It still won't know the answer, but it should respond in a more proper tone for a technical writer!
+
+```python
+chain.invoke({"input": "how can langsmith help with testing?"})
+```
+
+The output of a ChatModel (and therefore, of this chain) is a message. However, it's often much more convenient to work with strings. Let's add a simple output parser to convert the chat message to a string.
+
+```python
+from langchain_core.output_parsers import StrOutputParser
+
+output_parser = StrOutputParser()
+```
+
+We can now add this to the previous chain:
+
+```python
+chain = prompt | llm | output_parser
+```
+
+We can now invoke it and ask the same question. The answer will now be a string (rather than a ChatMessage).
+
+```python
+chain.invoke({"input": "how can langsmith help with testing?"})
+```
+
+### Diving Deeper
+
+We've now successfully set up a basic LLM chain. We only touched on the basics of prompts, models, and output parsers - for a deeper dive into everything mentioned here, see [this section of documentation](/docs/modules/model_io).
+
+
+## Retrieval Chain
+
+To properly answer the original question ("how can langsmith help with testing?"), we need to provide additional context to the LLM.
+We can do this via *retrieval*.
+Retrieval is useful when you have **too much data** to pass to the LLM directly.
+You can then use a retriever to fetch only the most relevant pieces and pass those in.
+
+In this process, we will look up relevant documents from a *Retriever* and then pass them into the prompt.
+A Retriever can be backed by anything - a SQL table, the internet, etc - but in this instance we will populate a vector store and use that as a retriever. For more information on vectorstores, see [this documentation](/docs/modules/data_connection/vectorstores).
+
+First, we need to load the data that we want to index. To do this, we will use the WebBaseLoader. This requires installing [BeautifulSoup](https://beautiful-soup-4.readthedocs.io/en/latest/):
+
+```shell
+pip install beautifulsoup4
+```
+
+After that, we can import and use WebBaseLoader.
+
+
+```python
+from langchain_community.document_loaders import WebBaseLoader
+loader = WebBaseLoader("https://docs.smith.langchain.com/user_guide")
+
+docs = loader.load()
+```
+
+Next, we need to index it into a vectorstore. This requires a few components, namely an [embedding model](/docs/modules/data_connection/text_embedding) and a [vectorstore](/docs/modules/data_connection/vectorstores).
+
+For embedding models, we once again provide examples for accessing via API or by running local models.
+
+<Tabs>
+  <TabItem value="openai" label="OpenAI (API)" default>
+  
+Make sure you have the `langchain_openai` package installed an the appropriate environment variables set (these are the same as needed for the LLM).
+
+```python
+from langchain_openai import OpenAIEmbeddings
+
+embeddings = OpenAIEmbeddings()
+```
+
+</TabItem>
+<TabItem value="local" label="Local (using Ollama)">
+
+Make sure you have Ollama running (same set up as with the LLM).
+
+```python
+from langchain_community.embeddings import OllamaEmbeddings
+
+embeddings = OllamaEmbeddings()
+```
+  </TabItem>
+<TabItem value="cohere" label="Cohere (API)" default>
+
+Make sure you have the `cohere` package installed and the appropriate environment variables set (these are the same as needed for the LLM).
+
+```python
+from langchain_cohere.embeddings import CohereEmbeddings
+
+embeddings = CohereEmbeddings()
+```
+
+</TabItem>
+</Tabs>
+
+Now, we can use this embedding model to ingest documents into a vectorstore.
+We will use a simple local vectorstore, [FAISS](/docs/integrations/vectorstores/faiss), for simplicity's sake.
+
+First we need to install the required packages for that:
+
+```shell
+pip install faiss-cpu
+```
+
+Then we can build our index:
+
+```python
+from langchain_community.vectorstores import FAISS
+from langchain_text_splitters import RecursiveCharacterTextSplitter
+
+
+text_splitter = RecursiveCharacterTextSplitter()
+documents = text_splitter.split_documents(docs)
+vector = FAISS.from_documents(documents, embeddings)
+```
+
+Now that we have this data indexed in a vectorstore, we will create a retrieval chain.
+This chain will take an incoming question, look up relevant documents, then pass those documents along with the original question into an LLM and ask it to answer the original question.
+
+First, let's set up the chain that takes a question and the retrieved documents and generates an answer.
+
+```python
+from langchain.chains.combine_documents import create_stuff_documents_chain
+
+prompt = ChatPromptTemplate.from_template("""Answer the following question based only on the provided context:
+
+<context>
+{context}
+</context>
+
+Question: {input}""")
+
+document_chain = create_stuff_documents_chain(llm, prompt)
+```
+
+If we wanted to, we could run this ourselves by passing in documents directly:
+
+```python
+from langchain_core.documents import Document
+
+document_chain.invoke({
+    "input": "how can langsmith help with testing?",
+    "context": [Document(page_content="langsmith can let you visualize test results")]
+})
+```
+
+However, we want the documents to first come from the retriever we just set up.
+That way, we can use the retriever to dynamically select the most relevant documents and pass those in for a given question.
+
+```python
+from langchain.chains import create_retrieval_chain
+
+retriever = vector.as_retriever()
+retrieval_chain = create_retrieval_chain(retriever, document_chain)
+```
+
+We can now invoke this chain. This returns a dictionary - the response from the LLM is in the `answer` key
+
+```python
+response = retrieval_chain.invoke({"input": "how can langsmith help with testing?"})
+print(response["answer"])
+
+# LangSmith offers several features that can help with testing:...
+```
+
+This answer should be much more accurate!
+
+### Diving Deeper
+
+We've now successfully set up a basic retrieval chain. We only touched on the basics of retrieval - for a deeper dive into everything mentioned here, see [this section of documentation](/docs/modules/data_connection).
+
+## Conversation Retrieval Chain
+
+The chain we've created so far can only answer single questions. One of the main types of LLM applications that people are building are chat bots. So how do we turn this chain into one that can answer follow up questions?
+
+We can still use the `create_retrieval_chain` function, but we need to change two things:
+
+1. The retrieval method should now not just work on the most recent input, but rather should take the whole history into account.
+2. The final LLM chain should likewise take the whole history into account
+
+**Updating Retrieval**
+
+In order to update retrieval, we will create a new chain. This chain will take in the most recent input (`input`) and the conversation history (`chat_history`) and use an LLM to generate a search query.
+
+```python
+from langchain.chains import create_history_aware_retriever
+from langchain_core.prompts import MessagesPlaceholder
+
+# First we need a prompt that we can pass into an LLM to generate this search query
+
+prompt = ChatPromptTemplate.from_messages([
+    MessagesPlaceholder(variable_name="chat_history"),
+    ("user", "{input}"),
+    ("user", "Given the above conversation, generate a search query to look up to get information relevant to the conversation")
+])
+retriever_chain = create_history_aware_retriever(llm, retriever, prompt)
+```
+
+We can test this out by passing in an instance where the user asks a follow-up question.
+
+```python
+from langchain_core.messages import HumanMessage, AIMessage
+
+chat_history = [HumanMessage(content="Can LangSmith help test my LLM applications?"), AIMessage(content="Yes!")]
+retriever_chain.invoke({
+    "chat_history": chat_history,
+    "input": "Tell me how"
+})
+```
+You should see that this returns documents about testing in LangSmith. This is because the LLM generated a new query, combining the chat history with the follow-up question.
+
+Now that we have this new retriever, we can create a new chain to continue the conversation with these retrieved documents in mind.
+
+```python
+prompt = ChatPromptTemplate.from_messages([
+    ("system", "Answer the user's questions based on the below context:\n\n{context}"),
+    MessagesPlaceholder(variable_name="chat_history"),
+    ("user", "{input}"),
+])
+document_chain = create_stuff_documents_chain(llm, prompt)
+
+retrieval_chain = create_retrieval_chain(retriever_chain, document_chain)
+```
+
+We can now test this out end-to-end:
+
+```python
+chat_history = [HumanMessage(content="Can LangSmith help test my LLM applications?"), AIMessage(content="Yes!")]
+retrieval_chain.invoke({
+    "chat_history": chat_history,
+    "input": "Tell me how"
+})
+```
+We can see that this gives a coherent answer - we've successfully turned our retrieval chain into a chatbot!
+
+## Agent
+
+We've so far created examples of chains - where each step is known ahead of time.
+The final thing we will create is an agent - where the LLM decides what steps to take.
+
+**NOTE: for this example we will only show how to create an agent using OpenAI models, as local models are not reliable enough yet.**
+
+One of the first things to do when building an agent is to decide what tools it should have access to.
+For this example, we will give the agent access to two tools:
+
+1. The retriever we just created. This will let it easily answer questions about LangSmith
+2. A search tool. This will let it easily answer questions that require up-to-date information.
+
+First, let's set up a tool for the retriever we just created:
+
+```python
+from langchain.tools.retriever import create_retriever_tool
+
+retriever_tool = create_retriever_tool(
+    retriever,
+    "langsmith_search",
+    "Search for information about LangSmith. For any questions about LangSmith, you must use this tool!",
+)
+```
+
+
+The search tool that we will use is [Tavily](/docs/integrations/retrievers/tavily). This will require an API key (they have generous free tier). After creating it on their platform, you need to set it as an environment variable:
+
+```shell
+export TAVILY_API_KEY=...
+```
+If you do not want to set up an API key, you can skip creating this tool.
+
+```python
+from langchain_community.tools.tavily_search import TavilySearchResults
+
+search = TavilySearchResults()
+```
+
+We can now create a list of the tools we want to work with:
+
+```python
+tools = [retriever_tool, search]
+```
+
+Now that we have the tools, we can create an agent to use them. We will go over this pretty quickly - for a deeper dive into what exactly is going on, check out the [Agent's Getting Started documentation](/docs/modules/agents)
+
+Install langchain hub first
+```bash
+pip install langchainhub
+```
+Install the langchain-openai package
+To interact with OpenAI we need to use langchain-openai which connects with OpenAI SDK[https://github.com/langchain-ai/langchain/tree/master/libs/partners/openai].  
+```bash
+pip install langchain-openai
+```
+
+Now we can use it to get a predefined prompt
+
+```python
+from langchain_openai import ChatOpenAI
+from langchain import hub
+from langchain.agents import create_openai_functions_agent
+from langchain.agents import AgentExecutor
+
+# Get the prompt to use - you can modify this!
+prompt = hub.pull("hwchase17/openai-functions-agent")
+
+# You need to set OPENAI_API_KEY environment variable or pass it as argument `api_key`.
+llm = ChatOpenAI(model="gpt-3.5-turbo", temperature=0)
+agent = create_openai_functions_agent(llm, tools, prompt)
+agent_executor = AgentExecutor(agent=agent, tools=tools, verbose=True)
+```
+
+We can now invoke the agent and see how it responds! We can ask it questions about LangSmith:
+
+```python
+agent_executor.invoke({"input": "how can langsmith help with testing?"})
+```
+
+We can ask it about the weather:
+
+```python
+agent_executor.invoke({"input": "what is the weather in SF?"})
+```
+
+We can have conversations with it:
+
+```python
+chat_history = [HumanMessage(content="Can LangSmith help test my LLM applications?"), AIMessage(content="Yes!")]
+agent_executor.invoke({
+    "chat_history": chat_history,
+    "input": "Tell me how"
+})
+```
+
+### Diving Deeper
+
+We've now successfully set up a basic agent. We only touched on the basics of agents - for a deeper dive into everything mentioned here, see [this section of documentation](/docs/modules/agents).
+
+
+## Serving with LangServe
+
+Now that we've built an application, we need to serve it. That's where LangServe comes in.
+LangServe helps developers deploy LangChain chains as a REST API. You do not need to use LangServe to use LangChain, but in this guide we'll show how you can deploy your app with LangServe.
+
+While the first part of this guide was intended to be run in a Jupyter Notebook, we will now move out of that. We will be creating a Python file and then interacting with it from the command line.
+
+Install with:
+```bash
+pip install "langserve[all]"
+```
+
+### Server
+
+To create a server for our application we'll make a `serve.py` file. This will contain our logic for serving our application. It consists of three things:
+1. The definition of our chain that we just built above
+2. Our FastAPI app
+3. A definition of a route from which to serve the chain, which is done with `langserve.add_routes`
+
+```python
+#!/usr/bin/env python
+from typing import List
+
+from fastapi import FastAPI
+from langchain_core.prompts import ChatPromptTemplate
+from langchain_openai import ChatOpenAI
+from langchain_community.document_loaders import WebBaseLoader
+from langchain_openai import OpenAIEmbeddings
+from langchain_community.vectorstores import FAISS
+from langchain_text_splitters import RecursiveCharacterTextSplitter
+from langchain.tools.retriever import create_retriever_tool
+from langchain_community.tools.tavily_search import TavilySearchResults
+from langchain import hub
+from langchain.agents import create_openai_functions_agent
+from langchain.agents import AgentExecutor
+from langchain.pydantic_v1 import BaseModel, Field
+from langchain_core.messages import BaseMessage
+from langserve import add_routes
+
+# 1. Load Retriever
+loader = WebBaseLoader("https://docs.smith.langchain.com/user_guide")
+docs = loader.load()
+text_splitter = RecursiveCharacterTextSplitter()
+documents = text_splitter.split_documents(docs)
+embeddings = OpenAIEmbeddings()
+vector = FAISS.from_documents(documents, embeddings)
+retriever = vector.as_retriever()
+
+# 2. Create Tools
+retriever_tool = create_retriever_tool(
+    retriever,
+    "langsmith_search",
+    "Search for information about LangSmith. For any questions about LangSmith, you must use this tool!",
+)
+search = TavilySearchResults()
+tools = [retriever_tool, search]
+
+
+# 3. Create Agent
+prompt = hub.pull("hwchase17/openai-functions-agent")
+llm = ChatOpenAI(model="gpt-3.5-turbo", temperature=0)
+agent = create_openai_functions_agent(llm, tools, prompt)
+agent_executor = AgentExecutor(agent=agent, tools=tools, verbose=True)
+
+
+# 4. App definition
+app = FastAPI(
+  title="LangChain Server",
+  version="1.0",
+  description="A simple API server using LangChain's Runnable interfaces",
+)
+
+# 5. Adding chain route
+
+# We need to add these input/output schemas because the current AgentExecutor
+# is lacking in schemas.
+
+class Input(BaseModel):
+    input: str
+    chat_history: List[BaseMessage] = Field(
+        ...,
+        extra={"widget": {"type": "chat", "input": "location"}},
+    )
+
+
+class Output(BaseModel):
+    output: str
+
+add_routes(
+    app,
+    agent_executor.with_types(input_type=Input, output_type=Output),
+    path="/agent",
+)
+
+if __name__ == "__main__":
+    import uvicorn
+
+    uvicorn.run(app, host="localhost", port=8000)
+```
+
+And that's it! If we execute this file:
+```bash
+python serve.py
+```
+we should see our chain being served at localhost:8000.
+
+### Playground
+
+Every LangServe service comes with a simple built-in UI for configuring and invoking the application with streaming output and visibility into intermediate steps.
+Head to http://localhost:8000/agent/playground/ to try it out! Pass in the same question as before - "how can langsmith help with testing?" - and it should respond same as before.
+
+### Client
+
+Now let's set up a client for programmatically interacting with our service. We can easily do this with the `[langserve.RemoteRunnable](/docs/langserve#client)`.
+Using this, we can interact with the served chain as if it were running client-side.
+
+```python
+from langserve import RemoteRunnable
+
+remote_chain = RemoteRunnable("http://localhost:8000/agent/")
+remote_chain.invoke({
+    "input": "how can langsmith help with testing?",
+    "chat_history": []  # Providing an empty list as this is the first call
+})
+```
+
+To learn more about the many other features of LangServe [head here](/docs/langserve).
+
+## Next steps
+
+We've touched on how to build an application with LangChain, how to trace it with LangSmith, and how to serve it with LangServe.
+There are a lot more features in all three of these than we can cover here.
+To continue on your journey, we recommend you read the following (in order):
+
+- All of these features are backed by [LangChain Expression Language (LCEL)](/docs/expression_language) - a way to chain these components together. Check out that documentation to better understand how to create custom chains.
+- [Model IO](/docs/modules/model_io) covers more details of prompts, LLMs, and output parsers.
+- [Retrieval](/docs/modules/data_connection) covers more details of everything related to retrieval
+- [Agents](/docs/modules/agents) covers details of everything related to agents
+- Explore common [end-to-end use cases](/docs/use_cases/) and [template applications](/docs/templates)
+- [Read up on LangSmith](/docs/langsmith/), the platform for debugging, testing, monitoring and more
+- Learn more about serving your applications with [LangServe](/docs/langserve)

docs/docs/guides/development/debugging.md

@@ -0,0 +1,661 @@
+# Debugging
+
+If you're building with LLMs, at some point something will break, and you'll need to debug. A model call will fail, or the model output will be misformatted, or there will be some nested model calls and it won't be clear where along the way an incorrect output was created.
+
+Here are a few different tools and functionalities to aid in debugging.
+
+
+
+## Tracing
+
+Platforms with tracing capabilities like [LangSmith](/docs/langsmith/) are the most comprehensive solutions for debugging. These platforms make it easy to not only log and visualize LLM apps, but also to actively debug, test and refine them.
+
+When building production-grade LLM applications, platforms like this are essential.
+
+![Screenshot of the LangSmith debugging interface showing an AgentExecutor run with input and output details, and a run tree visualization.](../../../static/img/run_details.png "LangSmith Debugging Interface")
+
+## `set_debug` and `set_verbose`
+
+If you're prototyping in Jupyter Notebooks or running Python scripts, it can be helpful to print out the intermediate steps of a Chain run. 
+
+There are a number of ways to enable printing at varying degrees of verbosity.
+
+Let's suppose we have a simple agent, and want to visualize the actions it takes and tool outputs it receives. Without any debugging, here's what we see:
+
+
+```python
+from langchain.agents import AgentType, initialize_agent, load_tools
+from langchain_openai import ChatOpenAI
+
+llm = ChatOpenAI(model="gpt-4", temperature=0)
+tools = load_tools(["ddg-search", "llm-math"], llm=llm)
+agent = initialize_agent(tools, llm, agent=AgentType.ZERO_SHOT_REACT_DESCRIPTION)
+```
+
+
+```python
+agent.run("Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?")
+```
+
+<CodeOutputBlock lang="python">
+
+```
+    'The director of the 2023 film Oppenheimer is Christopher Nolan and he is approximately 19345 days old in 2023.'
+```
+
+</CodeOutputBlock>
+
+### `set_debug(True)`
+
+Setting the global `debug` flag will cause all LangChain components with callback support (chains, models, agents, tools, retrievers) to print the inputs they receive and outputs they generate. This is the most verbose setting and will fully log raw inputs and outputs.
+
+
+```python
+from langchain.globals import set_debug
+
+set_debug(True)
+
+agent.run("Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?")
+```
+
+<details> <summary>Console output</summary>
+
+<CodeOutputBlock lang="python">
+
+```
+    [chain/start] [1:RunTypeEnum.chain:AgentExecutor] Entering Chain run with input:
+    {
+      "input": "Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?"
+    }
+    [chain/start] [1:RunTypeEnum.chain:AgentExecutor > 2:RunTypeEnum.chain:LLMChain] Entering Chain run with input:
+    {
+      "input": "Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?",
+      "agent_scratchpad": "",
+      "stop": [
+        "\nObservation:",
+        "\n\tObservation:"
+      ]
+    }
+    [llm/start] [1:RunTypeEnum.chain:AgentExecutor > 2:RunTypeEnum.chain:LLMChain > 3:RunTypeEnum.llm:ChatOpenAI] Entering LLM run with input:
+    {
+      "prompts": [
+        "Human: Answer the following questions as best you can. You have access to the following tools:\n\nduckduckgo_search: A wrapper around DuckDuckGo Search. Useful for when you need to answer questions about current events. Input should be a search query.\nCalculator: Useful for when you need to answer questions about math.\n\nUse the following format:\n\nQuestion: the input question you must answer\nThought: you should always think about what to do\nAction: the action to take, should be one of [duckduckgo_search, Calculator]\nAction Input: the input to the action\nObservation: the result of the action\n... (this Thought/Action/Action Input/Observation can repeat N times)\nThought: I now know the final answer\nFinal Answer: the final answer to the original input question\n\nBegin!\n\nQuestion: Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?\nThought:"
+      ]
+    }
+    [llm/end] [1:RunTypeEnum.chain:AgentExecutor > 2:RunTypeEnum.chain:LLMChain > 3:RunTypeEnum.llm:ChatOpenAI] [5.53s] Exiting LLM run with output:
+    {
+      "generations": [
+        [
+          {
+            "text": "I need to find out who directed the 2023 film Oppenheimer and their age. Then, I need to calculate their age in days. I will use DuckDuckGo to find out the director and their age.\nAction: duckduckgo_search\nAction Input: \"Director of the 2023 film Oppenheimer and their age\"",
+            "generation_info": {
+              "finish_reason": "stop"
+            },
+            "message": {
+              "lc": 1,
+              "type": "constructor",
+              "id": [
+                "langchain",
+                "schema",
+                "messages",
+                "AIMessage"
+              ],
+              "kwargs": {
+                "content": "I need to find out who directed the 2023 film Oppenheimer and their age. Then, I need to calculate their age in days. I will use DuckDuckGo to find out the director and their age.\nAction: duckduckgo_search\nAction Input: \"Director of the 2023 film Oppenheimer and their age\"",
+                "additional_kwargs": {}
+              }
+            }
+          }
+        ]
+      ],
+      "llm_output": {
+        "token_usage": {
+          "prompt_tokens": 206,
+          "completion_tokens": 71,
+          "total_tokens": 277
+        },
+        "model_name": "gpt-4"
+      },
+      "run": null
+    }
+    [chain/end] [1:RunTypeEnum.chain:AgentExecutor > 2:RunTypeEnum.chain:LLMChain] [5.53s] Exiting Chain run with output:
+    {
+      "text": "I need to find out who directed the 2023 film Oppenheimer and their age. Then, I need to calculate their age in days. I will use DuckDuckGo to find out the director and their age.\nAction: duckduckgo_search\nAction Input: \"Director of the 2023 film Oppenheimer and their age\""
+    }
+    [tool/start] [1:RunTypeEnum.chain:AgentExecutor > 4:RunTypeEnum.tool:duckduckgo_search] Entering Tool run with input:
+    "Director of the 2023 film Oppenheimer and their age"
+    [tool/end] [1:RunTypeEnum.chain:AgentExecutor > 4:RunTypeEnum.tool:duckduckgo_search] [1.51s] Exiting Tool run with output:
+    "Capturing the mad scramble to build the first atomic bomb required rapid-fire filming, strict set rules and the construction of an entire 1940s western town. By Jada Yuan. July 19, 2023 at 5:00 a ... In Christopher Nolan's new film, "Oppenheimer," Cillian Murphy stars as J. Robert Oppenheimer, the American physicist who oversaw the Manhattan Project in Los Alamos, N.M. Universal Pictures... Oppenheimer: Directed by Christopher Nolan. With Cillian Murphy, Emily Blunt, Robert Downey Jr., Alden Ehrenreich. The story of American scientist J. Robert Oppenheimer and his role in the development of the atomic bomb. Christopher Nolan goes deep on 'Oppenheimer,' his most 'extreme' film to date. By Kenneth Turan. July 11, 2023 5 AM PT. For Subscribers. Christopher Nolan is photographed in Los Angeles ... Oppenheimer is a 2023 epic biographical thriller film written and directed by Christopher Nolan.It is based on the 2005 biography American Prometheus by Kai Bird and Martin J. Sherwin about J. Robert Oppenheimer, a theoretical physicist who was pivotal in developing the first nuclear weapons as part of the Manhattan Project and thereby ushering in the Atomic Age."
+    [chain/start] [1:RunTypeEnum.chain:AgentExecutor > 5:RunTypeEnum.chain:LLMChain] Entering Chain run with input:
+    {
+      "input": "Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?",
+      "agent_scratchpad": "I need to find out who directed the 2023 film Oppenheimer and their age. Then, I need to calculate their age in days. I will use DuckDuckGo to find out the director and their age.\nAction: duckduckgo_search\nAction Input: \"Director of the 2023 film Oppenheimer and their age\"\nObservation: Capturing the mad scramble to build the first atomic bomb required rapid-fire filming, strict set rules and the construction of an entire 1940s western town. By Jada Yuan. July 19, 2023 at 5:00 a ... In Christopher Nolan's new film, \"Oppenheimer,\" Cillian Murphy stars as J. Robert Oppenheimer, the American physicist who oversaw the Manhattan Project in Los Alamos, N.M. Universal Pictures... Oppenheimer: Directed by Christopher Nolan. With Cillian Murphy, Emily Blunt, Robert Downey Jr., Alden Ehrenreich. The story of American scientist J. Robert Oppenheimer and his role in the development of the atomic bomb. Christopher Nolan goes deep on 'Oppenheimer,' his most 'extreme' film to date. By Kenneth Turan. July 11, 2023 5 AM PT. For Subscribers. Christopher Nolan is photographed in Los Angeles ... Oppenheimer is a 2023 epic biographical thriller film written and directed by Christopher Nolan.It is based on the 2005 biography American Prometheus by Kai Bird and Martin J. Sherwin about J. Robert Oppenheimer, a theoretical physicist who was pivotal in developing the first nuclear weapons as part of the Manhattan Project and thereby ushering in the Atomic Age.\nThought:",
+      "stop": [
+        "\nObservation:",
+        "\n\tObservation:"
+      ]
+    }
+    [llm/start] [1:RunTypeEnum.chain:AgentExecutor > 5:RunTypeEnum.chain:LLMChain > 6:RunTypeEnum.llm:ChatOpenAI] Entering LLM run with input:
+    {
+      "prompts": [
+        "Human: Answer the following questions as best you can. You have access to the following tools:\n\nduckduckgo_search: A wrapper around DuckDuckGo Search. Useful for when you need to answer questions about current events. Input should be a search query.\nCalculator: Useful for when you need to answer questions about math.\n\nUse the following format:\n\nQuestion: the input question you must answer\nThought: you should always think about what to do\nAction: the action to take, should be one of [duckduckgo_search, Calculator]\nAction Input: the input to the action\nObservation: the result of the action\n... (this Thought/Action/Action Input/Observation can repeat N times)\nThought: I now know the final answer\nFinal Answer: the final answer to the original input question\n\nBegin!\n\nQuestion: Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?\nThought:I need to find out who directed the 2023 film Oppenheimer and their age. Then, I need to calculate their age in days. I will use DuckDuckGo to find out the director and their age.\nAction: duckduckgo_search\nAction Input: \"Director of the 2023 film Oppenheimer and their age\"\nObservation: Capturing the mad scramble to build the first atomic bomb required rapid-fire filming, strict set rules and the construction of an entire 1940s western town. By Jada Yuan. July 19, 2023 at 5:00 a ... In Christopher Nolan's new film, \"Oppenheimer,\" Cillian Murphy stars as J. Robert Oppenheimer, the American physicist who oversaw the Manhattan Project in Los Alamos, N.M. Universal Pictures... Oppenheimer: Directed by Christopher Nolan. With Cillian Murphy, Emily Blunt, Robert Downey Jr., Alden Ehrenreich. The story of American scientist J. Robert Oppenheimer and his role in the development of the atomic bomb. Christopher Nolan goes deep on 'Oppenheimer,' his most 'extreme' film to date. By Kenneth Turan. July 11, 2023 5 AM PT. For Subscribers. Christopher Nolan is photographed in Los Angeles ... Oppenheimer is a 2023 epic biographical thriller film written and directed by Christopher Nolan.It is based on the 2005 biography American Prometheus by Kai Bird and Martin J. Sherwin about J. Robert Oppenheimer, a theoretical physicist who was pivotal in developing the first nuclear weapons as part of the Manhattan Project and thereby ushering in the Atomic Age.\nThought:"
+      ]
+    }
+    [llm/end] [1:RunTypeEnum.chain:AgentExecutor > 5:RunTypeEnum.chain:LLMChain > 6:RunTypeEnum.llm:ChatOpenAI] [4.46s] Exiting LLM run with output:
+    {
+      "generations": [
+        [
+          {
+            "text": "The director of the 2023 film Oppenheimer is Christopher Nolan. Now I need to find out his age.\nAction: duckduckgo_search\nAction Input: \"Christopher Nolan age\"",
+            "generation_info": {
+              "finish_reason": "stop"
+            },
+            "message": {
+              "lc": 1,
+              "type": "constructor",
+              "id": [
+                "langchain",
+                "schema",
+                "messages",
+                "AIMessage"
+              ],
+              "kwargs": {
+                "content": "The director of the 2023 film Oppenheimer is Christopher Nolan. Now I need to find out his age.\nAction: duckduckgo_search\nAction Input: \"Christopher Nolan age\"",
+                "additional_kwargs": {}
+              }
+            }
+          }
+        ]
+      ],
+      "llm_output": {
+        "token_usage": {
+          "prompt_tokens": 550,
+          "completion_tokens": 39,
+          "total_tokens": 589
+        },
+        "model_name": "gpt-4"
+      },
+      "run": null
+    }
+    [chain/end] [1:RunTypeEnum.chain:AgentExecutor > 5:RunTypeEnum.chain:LLMChain] [4.46s] Exiting Chain run with output:
+    {
+      "text": "The director of the 2023 film Oppenheimer is Christopher Nolan. Now I need to find out his age.\nAction: duckduckgo_search\nAction Input: \"Christopher Nolan age\""
+    }
+    [tool/start] [1:RunTypeEnum.chain:AgentExecutor > 7:RunTypeEnum.tool:duckduckgo_search] Entering Tool run with input:
+    "Christopher Nolan age"
+    [tool/end] [1:RunTypeEnum.chain:AgentExecutor > 7:RunTypeEnum.tool:duckduckgo_search] [1.33s] Exiting Tool run with output:
+    "Christopher Edward Nolan CBE (born 30 July 1970) is a British and American filmmaker. Known for his Hollywood blockbusters with complex storytelling, Nolan is considered a leading filmmaker of the 21st century. His films have grossed $5 billion worldwide. The recipient of many accolades, he has been nominated for five Academy Awards, five BAFTA Awards and six Golden Globe Awards. July 30, 1970 (age 52) London England Notable Works: "Dunkirk" "Tenet" "The Prestige" See all related content → Recent News Jul. 13, 2023, 11:11 AM ET (AP) Cillian Murphy, playing Oppenheimer, finally gets to lead a Christopher Nolan film July 11, 2023 5 AM PT For Subscribers Christopher Nolan is photographed in Los Angeles. (Joe Pugliese / For The Times) This is not the story I was supposed to write. Oppenheimer director Christopher Nolan, Cillian Murphy, Emily Blunt and Matt Damon on the stakes of making a three-hour, CGI-free summer film. Christopher Nolan, the director behind such films as "Dunkirk," "Inception," "Interstellar," and the "Dark Knight" trilogy, has spent the last three years living in Oppenheimer's world, writing ..."
+    [chain/start] [1:RunTypeEnum.chain:AgentExecutor > 8:RunTypeEnum.chain:LLMChain] Entering Chain run with input:
+    {
+      "input": "Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?",
+      "agent_scratchpad": "I need to find out who directed the 2023 film Oppenheimer and their age. Then, I need to calculate their age in days. I will use DuckDuckGo to find out the director and their age.\nAction: duckduckgo_search\nAction Input: \"Director of the 2023 film Oppenheimer and their age\"\nObservation: Capturing the mad scramble to build the first atomic bomb required rapid-fire filming, strict set rules and the construction of an entire 1940s western town. By Jada Yuan. July 19, 2023 at 5:00 a ... In Christopher Nolan's new film, \"Oppenheimer,\" Cillian Murphy stars as J. Robert Oppenheimer, the American physicist who oversaw the Manhattan Project in Los Alamos, N.M. Universal Pictures... Oppenheimer: Directed by Christopher Nolan. With Cillian Murphy, Emily Blunt, Robert Downey Jr., Alden Ehrenreich. The story of American scientist J. Robert Oppenheimer and his role in the development of the atomic bomb. Christopher Nolan goes deep on 'Oppenheimer,' his most 'extreme' film to date. By Kenneth Turan. July 11, 2023 5 AM PT. For Subscribers. Christopher Nolan is photographed in Los Angeles ... Oppenheimer is a 2023 epic biographical thriller film written and directed by Christopher Nolan.It is based on the 2005 biography American Prometheus by Kai Bird and Martin J. Sherwin about J. Robert Oppenheimer, a theoretical physicist who was pivotal in developing the first nuclear weapons as part of the Manhattan Project and thereby ushering in the Atomic Age.\nThought:The director of the 2023 film Oppenheimer is Christopher Nolan. Now I need to find out his age.\nAction: duckduckgo_search\nAction Input: \"Christopher Nolan age\"\nObservation: Christopher Edward Nolan CBE (born 30 July 1970) is a British and American filmmaker. Known for his Hollywood blockbusters with complex storytelling, Nolan is considered a leading filmmaker of the 21st century. His films have grossed $5 billion worldwide. The recipient of many accolades, he has been nominated for five Academy Awards, five BAFTA Awards and six Golden Globe Awards. July 30, 1970 (age 52) London England Notable Works: \"Dunkirk\" \"Tenet\" \"The Prestige\" See all related content → Recent News Jul. 13, 2023, 11:11 AM ET (AP) Cillian Murphy, playing Oppenheimer, finally gets to lead a Christopher Nolan film July 11, 2023 5 AM PT For Subscribers Christopher Nolan is photographed in Los Angeles. (Joe Pugliese / For The Times) This is not the story I was supposed to write. Oppenheimer director Christopher Nolan, Cillian Murphy, Emily Blunt and Matt Damon on the stakes of making a three-hour, CGI-free summer film. Christopher Nolan, the director behind such films as \"Dunkirk,\" \"Inception,\" \"Interstellar,\" and the \"Dark Knight\" trilogy, has spent the last three years living in Oppenheimer's world, writing ...\nThought:",
+      "stop": [
+        "\nObservation:",
+        "\n\tObservation:"
+      ]
+    }
+    [llm/start] [1:RunTypeEnum.chain:AgentExecutor > 8:RunTypeEnum.chain:LLMChain > 9:RunTypeEnum.llm:ChatOpenAI] Entering LLM run with input:
+    {
+      "prompts": [
+        "Human: Answer the following questions as best you can. You have access to the following tools:\n\nduckduckgo_search: A wrapper around DuckDuckGo Search. Useful for when you need to answer questions about current events. Input should be a search query.\nCalculator: Useful for when you need to answer questions about math.\n\nUse the following format:\n\nQuestion: the input question you must answer\nThought: you should always think about what to do\nAction: the action to take, should be one of [duckduckgo_search, Calculator]\nAction Input: the input to the action\nObservation: the result of the action\n... (this Thought/Action/Action Input/Observation can repeat N times)\nThought: I now know the final answer\nFinal Answer: the final answer to the original input question\n\nBegin!\n\nQuestion: Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?\nThought:I need to find out who directed the 2023 film Oppenheimer and their age. Then, I need to calculate their age in days. I will use DuckDuckGo to find out the director and their age.\nAction: duckduckgo_search\nAction Input: \"Director of the 2023 film Oppenheimer and their age\"\nObservation: Capturing the mad scramble to build the first atomic bomb required rapid-fire filming, strict set rules and the construction of an entire 1940s western town. By Jada Yuan. July 19, 2023 at 5:00 a ... In Christopher Nolan's new film, \"Oppenheimer,\" Cillian Murphy stars as J. Robert Oppenheimer, the American physicist who oversaw the Manhattan Project in Los Alamos, N.M. Universal Pictures... Oppenheimer: Directed by Christopher Nolan. With Cillian Murphy, Emily Blunt, Robert Downey Jr., Alden Ehrenreich. The story of American scientist J. Robert Oppenheimer and his role in the development of the atomic bomb. Christopher Nolan goes deep on 'Oppenheimer,' his most 'extreme' film to date. By Kenneth Turan. July 11, 2023 5 AM PT. For Subscribers. Christopher Nolan is photographed in Los Angeles ... Oppenheimer is a 2023 epic biographical thriller film written and directed by Christopher Nolan.It is based on the 2005 biography American Prometheus by Kai Bird and Martin J. Sherwin about J. Robert Oppenheimer, a theoretical physicist who was pivotal in developing the first nuclear weapons as part of the Manhattan Project and thereby ushering in the Atomic Age.\nThought:The director of the 2023 film Oppenheimer is Christopher Nolan. Now I need to find out his age.\nAction: duckduckgo_search\nAction Input: \"Christopher Nolan age\"\nObservation: Christopher Edward Nolan CBE (born 30 July 1970) is a British and American filmmaker. Known for his Hollywood blockbusters with complex storytelling, Nolan is considered a leading filmmaker of the 21st century. His films have grossed $5 billion worldwide. The recipient of many accolades, he has been nominated for five Academy Awards, five BAFTA Awards and six Golden Globe Awards. July 30, 1970 (age 52) London England Notable Works: \"Dunkirk\" \"Tenet\" \"The Prestige\" See all related content → Recent News Jul. 13, 2023, 11:11 AM ET (AP) Cillian Murphy, playing Oppenheimer, finally gets to lead a Christopher Nolan film July 11, 2023 5 AM PT For Subscribers Christopher Nolan is photographed in Los Angeles. (Joe Pugliese / For The Times) This is not the story I was supposed to write. Oppenheimer director Christopher Nolan, Cillian Murphy, Emily Blunt and Matt Damon on the stakes of making a three-hour, CGI-free summer film. Christopher Nolan, the director behind such films as \"Dunkirk,\" \"Inception,\" \"Interstellar,\" and the \"Dark Knight\" trilogy, has spent the last three years living in Oppenheimer's world, writing ...\nThought:"
+      ]
+    }
+    [llm/end] [1:RunTypeEnum.chain:AgentExecutor > 8:RunTypeEnum.chain:LLMChain > 9:RunTypeEnum.llm:ChatOpenAI] [2.69s] Exiting LLM run with output:
+    {
+      "generations": [
+        [
+          {
+            "text": "Christopher Nolan was born on July 30, 1970, which makes him 52 years old in 2023. Now I need to calculate his age in days.\nAction: Calculator\nAction Input: 52*365",
+            "generation_info": {
+              "finish_reason": "stop"
+            },
+            "message": {
+              "lc": 1,
+              "type": "constructor",
+              "id": [
+                "langchain",
+                "schema",
+                "messages",
+                "AIMessage"
+              ],
+              "kwargs": {
+                "content": "Christopher Nolan was born on July 30, 1970, which makes him 52 years old in 2023. Now I need to calculate his age in days.\nAction: Calculator\nAction Input: 52*365",
+                "additional_kwargs": {}
+              }
+            }
+          }
+        ]
+      ],
+      "llm_output": {
+        "token_usage": {
+          "prompt_tokens": 868,
+          "completion_tokens": 46,
+          "total_tokens": 914
+        },
+        "model_name": "gpt-4"
+      },
+      "run": null
+    }
+    [chain/end] [1:RunTypeEnum.chain:AgentExecutor > 8:RunTypeEnum.chain:LLMChain] [2.69s] Exiting Chain run with output:
+    {
+      "text": "Christopher Nolan was born on July 30, 1970, which makes him 52 years old in 2023. Now I need to calculate his age in days.\nAction: Calculator\nAction Input: 52*365"
+    }
+    [tool/start] [1:RunTypeEnum.chain:AgentExecutor > 10:RunTypeEnum.tool:Calculator] Entering Tool run with input:
+    "52*365"
+    [chain/start] [1:RunTypeEnum.chain:AgentExecutor > 10:RunTypeEnum.tool:Calculator > 11:RunTypeEnum.chain:LLMMathChain] Entering Chain run with input:
+    {
+      "question": "52*365"
+    }
+    [chain/start] [1:RunTypeEnum.chain:AgentExecutor > 10:RunTypeEnum.tool:Calculator > 11:RunTypeEnum.chain:LLMMathChain > 12:RunTypeEnum.chain:LLMChain] Entering Chain run with input:
+    {
+      "question": "52*365",
+      "stop": [
+        "```output"
+      ]
+    }
+    [llm/start] [1:RunTypeEnum.chain:AgentExecutor > 10:RunTypeEnum.tool:Calculator > 11:RunTypeEnum.chain:LLMMathChain > 12:RunTypeEnum.chain:LLMChain > 13:RunTypeEnum.llm:ChatOpenAI] Entering LLM run with input:
+    {
+      "prompts": [
+        "Human: Translate a math problem into a expression that can be executed using Python's numexpr library. Use the output of running this code to answer the question.\n\nQuestion: ${Question with math problem.}\n```text\n${single line mathematical expression that solves the problem}\n```\n...numexpr.evaluate(text)...\n```output\n${Output of running the code}\n```\nAnswer: ${Answer}\n\nBegin.\n\nQuestion: What is 37593 * 67?\n```text\n37593 * 67\n```\n...numexpr.evaluate(\"37593 * 67\")...\n```output\n2518731\n```\nAnswer: 2518731\n\nQuestion: 37593^(1/5)\n```text\n37593**(1/5)\n```\n...numexpr.evaluate(\"37593**(1/5)\")...\n```output\n8.222831614237718\n```\nAnswer: 8.222831614237718\n\nQuestion: 52*365"
+      ]
+    }
+    [llm/end] [1:RunTypeEnum.chain:AgentExecutor > 10:RunTypeEnum.tool:Calculator > 11:RunTypeEnum.chain:LLMMathChain > 12:RunTypeEnum.chain:LLMChain > 13:RunTypeEnum.llm:ChatOpenAI] [2.89s] Exiting LLM run with output:
+    {
+      "generations": [
+        [
+          {
+            "text": "```text\n52*365\n```\n...numexpr.evaluate(\"52*365\")...\n",
+            "generation_info": {
+              "finish_reason": "stop"
+            },
+            "message": {
+              "lc": 1,
+              "type": "constructor",
+              "id": [
+                "langchain",
+                "schema",
+                "messages",
+                "AIMessage"
+              ],
+              "kwargs": {
+                "content": "```text\n52*365\n```\n...numexpr.evaluate(\"52*365\")...\n",
+                "additional_kwargs": {}
+              }
+            }
+          }
+        ]
+      ],
+      "llm_output": {
+        "token_usage": {
+          "prompt_tokens": 203,
+          "completion_tokens": 19,
+          "total_tokens": 222
+        },
+        "model_name": "gpt-4"
+      },
+      "run": null
+    }
+    [chain/end] [1:RunTypeEnum.chain:AgentExecutor > 10:RunTypeEnum.tool:Calculator > 11:RunTypeEnum.chain:LLMMathChain > 12:RunTypeEnum.chain:LLMChain] [2.89s] Exiting Chain run with output:
+    {
+      "text": "```text\n52*365\n```\n...numexpr.evaluate(\"52*365\")...\n"
+    }
+    [chain/end] [1:RunTypeEnum.chain:AgentExecutor > 10:RunTypeEnum.tool:Calculator > 11:RunTypeEnum.chain:LLMMathChain] [2.90s] Exiting Chain run with output:
+    {
+      "answer": "Answer: 18980"
+    }
+    [tool/end] [1:RunTypeEnum.chain:AgentExecutor > 10:RunTypeEnum.tool:Calculator] [2.90s] Exiting Tool run with output:
+    "Answer: 18980"
+    [chain/start] [1:RunTypeEnum.chain:AgentExecutor > 14:RunTypeEnum.chain:LLMChain] Entering Chain run with input:
+    {
+      "input": "Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?",
+      "agent_scratchpad": "I need to find out who directed the 2023 film Oppenheimer and their age. Then, I need to calculate their age in days. I will use DuckDuckGo to find out the director and their age.\nAction: duckduckgo_search\nAction Input: \"Director of the 2023 film Oppenheimer and their age\"\nObservation: Capturing the mad scramble to build the first atomic bomb required rapid-fire filming, strict set rules and the construction of an entire 1940s western town. By Jada Yuan. July 19, 2023 at 5:00 a ... In Christopher Nolan's new film, \"Oppenheimer,\" Cillian Murphy stars as J. Robert Oppenheimer, the American physicist who oversaw the Manhattan Project in Los Alamos, N.M. Universal Pictures... Oppenheimer: Directed by Christopher Nolan. With Cillian Murphy, Emily Blunt, Robert Downey Jr., Alden Ehrenreich. The story of American scientist J. Robert Oppenheimer and his role in the development of the atomic bomb. Christopher Nolan goes deep on 'Oppenheimer,' his most 'extreme' film to date. By Kenneth Turan. July 11, 2023 5 AM PT. For Subscribers. Christopher Nolan is photographed in Los Angeles ... Oppenheimer is a 2023 epic biographical thriller film written and directed by Christopher Nolan.It is based on the 2005 biography American Prometheus by Kai Bird and Martin J. Sherwin about J. Robert Oppenheimer, a theoretical physicist who was pivotal in developing the first nuclear weapons as part of the Manhattan Project and thereby ushering in the Atomic Age.\nThought:The director of the 2023 film Oppenheimer is Christopher Nolan. Now I need to find out his age.\nAction: duckduckgo_search\nAction Input: \"Christopher Nolan age\"\nObservation: Christopher Edward Nolan CBE (born 30 July 1970) is a British and American filmmaker. Known for his Hollywood blockbusters with complex storytelling, Nolan is considered a leading filmmaker of the 21st century. His films have grossed $5 billion worldwide. The recipient of many accolades, he has been nominated for five Academy Awards, five BAFTA Awards and six Golden Globe Awards. July 30, 1970 (age 52) London England Notable Works: \"Dunkirk\" \"Tenet\" \"The Prestige\" See all related content → Recent News Jul. 13, 2023, 11:11 AM ET (AP) Cillian Murphy, playing Oppenheimer, finally gets to lead a Christopher Nolan film July 11, 2023 5 AM PT For Subscribers Christopher Nolan is photographed in Los Angeles. (Joe Pugliese / For The Times) This is not the story I was supposed to write. Oppenheimer director Christopher Nolan, Cillian Murphy, Emily Blunt and Matt Damon on the stakes of making a three-hour, CGI-free summer film. Christopher Nolan, the director behind such films as \"Dunkirk,\" \"Inception,\" \"Interstellar,\" and the \"Dark Knight\" trilogy, has spent the last three years living in Oppenheimer's world, writing ...\nThought:Christopher Nolan was born on July 30, 1970, which makes him 52 years old in 2023. Now I need to calculate his age in days.\nAction: Calculator\nAction Input: 52*365\nObservation: Answer: 18980\nThought:",
+      "stop": [
+        "\nObservation:",
+        "\n\tObservation:"
+      ]
+    }
+    [llm/start] [1:RunTypeEnum.chain:AgentExecutor > 14:RunTypeEnum.chain:LLMChain > 15:RunTypeEnum.llm:ChatOpenAI] Entering LLM run with input:
+    {
+      "prompts": [
+        "Human: Answer the following questions as best you can. You have access to the following tools:\n\nduckduckgo_search: A wrapper around DuckDuckGo Search. Useful for when you need to answer questions about current events. Input should be a search query.\nCalculator: Useful for when you need to answer questions about math.\n\nUse the following format:\n\nQuestion: the input question you must answer\nThought: you should always think about what to do\nAction: the action to take, should be one of [duckduckgo_search, Calculator]\nAction Input: the input to the action\nObservation: the result of the action\n... (this Thought/Action/Action Input/Observation can repeat N times)\nThought: I now know the final answer\nFinal Answer: the final answer to the original input question\n\nBegin!\n\nQuestion: Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?\nThought:I need to find out who directed the 2023 film Oppenheimer and their age. Then, I need to calculate their age in days. I will use DuckDuckGo to find out the director and their age.\nAction: duckduckgo_search\nAction Input: \"Director of the 2023 film Oppenheimer and their age\"\nObservation: Capturing the mad scramble to build the first atomic bomb required rapid-fire filming, strict set rules and the construction of an entire 1940s western town. By Jada Yuan. July 19, 2023 at 5:00 a ... In Christopher Nolan's new film, \"Oppenheimer,\" Cillian Murphy stars as J. Robert Oppenheimer, the American physicist who oversaw the Manhattan Project in Los Alamos, N.M. Universal Pictures... Oppenheimer: Directed by Christopher Nolan. With Cillian Murphy, Emily Blunt, Robert Downey Jr., Alden Ehrenreich. The story of American scientist J. Robert Oppenheimer and his role in the development of the atomic bomb. Christopher Nolan goes deep on 'Oppenheimer,' his most 'extreme' film to date. By Kenneth Turan. July 11, 2023 5 AM PT. For Subscribers. Christopher Nolan is photographed in Los Angeles ... Oppenheimer is a 2023 epic biographical thriller film written and directed by Christopher Nolan.It is based on the 2005 biography American Prometheus by Kai Bird and Martin J. Sherwin about J. Robert Oppenheimer, a theoretical physicist who was pivotal in developing the first nuclear weapons as part of the Manhattan Project and thereby ushering in the Atomic Age.\nThought:The director of the 2023 film Oppenheimer is Christopher Nolan. Now I need to find out his age.\nAction: duckduckgo_search\nAction Input: \"Christopher Nolan age\"\nObservation: Christopher Edward Nolan CBE (born 30 July 1970) is a British and American filmmaker. Known for his Hollywood blockbusters with complex storytelling, Nolan is considered a leading filmmaker of the 21st century. His films have grossed $5 billion worldwide. The recipient of many accolades, he has been nominated for five Academy Awards, five BAFTA Awards and six Golden Globe Awards. July 30, 1970 (age 52) London England Notable Works: \"Dunkirk\" \"Tenet\" \"The Prestige\" See all related content → Recent News Jul. 13, 2023, 11:11 AM ET (AP) Cillian Murphy, playing Oppenheimer, finally gets to lead a Christopher Nolan film July 11, 2023 5 AM PT For Subscribers Christopher Nolan is photographed in Los Angeles. (Joe Pugliese / For The Times) This is not the story I was supposed to write. Oppenheimer director Christopher Nolan, Cillian Murphy, Emily Blunt and Matt Damon on the stakes of making a three-hour, CGI-free summer film. Christopher Nolan, the director behind such films as \"Dunkirk,\" \"Inception,\" \"Interstellar,\" and the \"Dark Knight\" trilogy, has spent the last three years living in Oppenheimer's world, writing ...\nThought:Christopher Nolan was born on July 30, 1970, which makes him 52 years old in 2023. Now I need to calculate his age in days.\nAction: Calculator\nAction Input: 52*365\nObservation: Answer: 18980\nThought:"
+      ]
+    }
+    [llm/end] [1:RunTypeEnum.chain:AgentExecutor > 14:RunTypeEnum.chain:LLMChain > 15:RunTypeEnum.llm:ChatOpenAI] [3.52s] Exiting LLM run with output:
+    {
+      "generations": [
+        [
+          {
+            "text": "I now know the final answer\nFinal Answer: The director of the 2023 film Oppenheimer is Christopher Nolan and he is 52 years old. His age in days is approximately 18980 days.",
+            "generation_info": {
+              "finish_reason": "stop"
+            },
+            "message": {
+              "lc": 1,
+              "type": "constructor",
+              "id": [
+                "langchain",
+                "schema",
+                "messages",
+                "AIMessage"
+              ],
+              "kwargs": {
+                "content": "I now know the final answer\nFinal Answer: The director of the 2023 film Oppenheimer is Christopher Nolan and he is 52 years old. His age in days is approximately 18980 days.",
+                "additional_kwargs": {}
+              }
+            }
+          }
+        ]
+      ],
+      "llm_output": {
+        "token_usage": {
+          "prompt_tokens": 926,
+          "completion_tokens": 43,
+          "total_tokens": 969
+        },
+        "model_name": "gpt-4"
+      },
+      "run": null
+    }
+    [chain/end] [1:RunTypeEnum.chain:AgentExecutor > 14:RunTypeEnum.chain:LLMChain] [3.52s] Exiting Chain run with output:
+    {
+      "text": "I now know the final answer\nFinal Answer: The director of the 2023 film Oppenheimer is Christopher Nolan and he is 52 years old. His age in days is approximately 18980 days."
+    }
+    [chain/end] [1:RunTypeEnum.chain:AgentExecutor] [21.96s] Exiting Chain run with output:
+    {
+      "output": "The director of the 2023 film Oppenheimer is Christopher Nolan and he is 52 years old. His age in days is approximately 18980 days."
+    }
+
+
+
+
+
+    'The director of the 2023 film Oppenheimer is Christopher Nolan and he is 52 years old. His age in days is approximately 18980 days.'
+```
+
+</CodeOutputBlock>
+
+</details>
+
+### `set_verbose(True)`
+
+Setting the `verbose` flag will print out inputs and outputs in a slightly more readable format and will skip logging certain raw outputs (like the token usage stats for an LLM call) so that you can focus on application logic.
+
+
+```python
+from langchain.globals import set_verbose
+
+set_verbose(True)
+
+agent.run("Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?")
+```
+
+<details> <summary>Console output</summary>
+
+<CodeOutputBlock lang="python">
+
+```
+    
+    
+    > Entering new AgentExecutor chain...
+    
+    
+    > Entering new LLMChain chain...
+    Prompt after formatting:
+    Answer the following questions as best you can. You have access to the following tools:
+    
+    duckduckgo_search: A wrapper around DuckDuckGo Search. Useful for when you need to answer questions about current events. Input should be a search query.
+    Calculator: Useful for when you need to answer questions about math.
+    
+    Use the following format:
+    
+    Question: the input question you must answer
+    Thought: you should always think about what to do
+    Action: the action to take, should be one of [duckduckgo_search, Calculator]
+    Action Input: the input to the action
+    Observation: the result of the action
+    ... (this Thought/Action/Action Input/Observation can repeat N times)
+    Thought: I now know the final answer
+    Final Answer: the final answer to the original input question
+    
+    Begin!
+    
+    Question: Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?
+    Thought:
+    
+    > Finished chain.
+    First, I need to find out who directed the film Oppenheimer in 2023 and their birth date to calculate their age.
+    Action: duckduckgo_search
+    Action Input: "Director of the 2023 film Oppenheimer"
+    Observation: Oppenheimer: Directed by Christopher Nolan. With Cillian Murphy, Emily Blunt, Robert Downey Jr., Alden Ehrenreich. The story of American scientist J. Robert Oppenheimer and his role in the development of the atomic bomb. In Christopher Nolan's new film, "Oppenheimer," Cillian Murphy stars as J. Robert ... 2023, 12:16 p.m. ET. ... including his role as the director of the Manhattan Engineer District, better ... J Robert Oppenheimer was the director of the secret Los Alamos Laboratory. It was established under US president Franklin D Roosevelt as part of the Manhattan Project to build the first atomic bomb. He oversaw the first atomic bomb detonation in the New Mexico desert in July 1945, code-named "Trinity". In this opening salvo of 2023's Oscar battle, Nolan has enjoined a star-studded cast for a retelling of the brilliant and haunted life of J. Robert Oppenheimer, the American physicist whose... Oppenheimer is a 2023 epic biographical thriller film written and directed by Christopher Nolan.It is based on the 2005 biography American Prometheus by Kai Bird and Martin J. Sherwin about J. Robert Oppenheimer, a theoretical physicist who was pivotal in developing the first nuclear weapons as part of the Manhattan Project and thereby ushering in the Atomic Age.
+    Thought:
+    
+    > Entering new LLMChain chain...
+    Prompt after formatting:
+    Answer the following questions as best you can. You have access to the following tools:
+    
+    duckduckgo_search: A wrapper around DuckDuckGo Search. Useful for when you need to answer questions about current events. Input should be a search query.
+    Calculator: Useful for when you need to answer questions about math.
+    
+    Use the following format:
+    
+    Question: the input question you must answer
+    Thought: you should always think about what to do
+    Action: the action to take, should be one of [duckduckgo_search, Calculator]
+    Action Input: the input to the action
+    Observation: the result of the action
+    ... (this Thought/Action/Action Input/Observation can repeat N times)
+    Thought: I now know the final answer
+    Final Answer: the final answer to the original input question
+    
+    Begin!
+    
+    Question: Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?
+    Thought:First, I need to find out who directed the film Oppenheimer in 2023 and their birth date to calculate their age.
+    Action: duckduckgo_search
+    Action Input: "Director of the 2023 film Oppenheimer"
+    Observation: Oppenheimer: Directed by Christopher Nolan. With Cillian Murphy, Emily Blunt, Robert Downey Jr., Alden Ehrenreich. The story of American scientist J. Robert Oppenheimer and his role in the development of the atomic bomb. In Christopher Nolan's new film, "Oppenheimer," Cillian Murphy stars as J. Robert ... 2023, 12:16 p.m. ET. ... including his role as the director of the Manhattan Engineer District, better ... J Robert Oppenheimer was the director of the secret Los Alamos Laboratory. It was established under US president Franklin D Roosevelt as part of the Manhattan Project to build the first atomic bomb. He oversaw the first atomic bomb detonation in the New Mexico desert in July 1945, code-named "Trinity". In this opening salvo of 2023's Oscar battle, Nolan has enjoined a star-studded cast for a retelling of the brilliant and haunted life of J. Robert Oppenheimer, the American physicist whose... Oppenheimer is a 2023 epic biographical thriller film written and directed by Christopher Nolan.It is based on the 2005 biography American Prometheus by Kai Bird and Martin J. Sherwin about J. Robert Oppenheimer, a theoretical physicist who was pivotal in developing the first nuclear weapons as part of the Manhattan Project and thereby ushering in the Atomic Age.
+    Thought:
+    
+    > Finished chain.
+    The director of the 2023 film Oppenheimer is Christopher Nolan. Now I need to find out his birth date to calculate his age.
+    Action: duckduckgo_search
+    Action Input: "Christopher Nolan birth date"
+    Observation: July 30, 1970 (age 52) London England Notable Works: "Dunkirk" "Tenet" "The Prestige" See all related content → Recent News Jul. 13, 2023, 11:11 AM ET (AP) Cillian Murphy, playing Oppenheimer, finally gets to lead a Christopher Nolan film Christopher Edward Nolan CBE (born 30 July 1970) is a British and American filmmaker. Known for his Hollywood blockbusters with complex storytelling, Nolan is considered a leading filmmaker of the 21st century. His films have grossed $5 billion worldwide. The recipient of many accolades, he has been nominated for five Academy Awards, five BAFTA Awards and six Golden Globe Awards. Christopher Nolan is currently 52 according to his birthdate July 30, 1970 Sun Sign Leo Born Place Westminster, London, England, United Kingdom Residence Los Angeles, California, United States Nationality Education Chris attended Haileybury and Imperial Service College, in Hertford Heath, Hertfordshire. Christopher Nolan's next movie will study the man who developed the atomic bomb, J. Robert Oppenheimer. Here's the release date, plot, trailers & more. July 2023 sees the release of Christopher Nolan's new film, Oppenheimer, his first movie since 2020's Tenet and his split from Warner Bros. Billed as an epic thriller about "the man who ...
+    Thought:
+    
+    > Entering new LLMChain chain...
+    Prompt after formatting:
+    Answer the following questions as best you can. You have access to the following tools:
+    
+    duckduckgo_search: A wrapper around DuckDuckGo Search. Useful for when you need to answer questions about current events. Input should be a search query.
+    Calculator: Useful for when you need to answer questions about math.
+    
+    Use the following format:
+    
+    Question: the input question you must answer
+    Thought: you should always think about what to do
+    Action: the action to take, should be one of [duckduckgo_search, Calculator]
+    Action Input: the input to the action
+    Observation: the result of the action
+    ... (this Thought/Action/Action Input/Observation can repeat N times)
+    Thought: I now know the final answer
+    Final Answer: the final answer to the original input question
+    
+    Begin!
+    
+    Question: Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?
+    Thought:First, I need to find out who directed the film Oppenheimer in 2023 and their birth date to calculate their age.
+    Action: duckduckgo_search
+    Action Input: "Director of the 2023 film Oppenheimer"
+    Observation: Oppenheimer: Directed by Christopher Nolan. With Cillian Murphy, Emily Blunt, Robert Downey Jr., Alden Ehrenreich. The story of American scientist J. Robert Oppenheimer and his role in the development of the atomic bomb. In Christopher Nolan's new film, "Oppenheimer," Cillian Murphy stars as J. Robert ... 2023, 12:16 p.m. ET. ... including his role as the director of the Manhattan Engineer District, better ... J Robert Oppenheimer was the director of the secret Los Alamos Laboratory. It was established under US president Franklin D Roosevelt as part of the Manhattan Project to build the first atomic bomb. He oversaw the first atomic bomb detonation in the New Mexico desert in July 1945, code-named "Trinity". In this opening salvo of 2023's Oscar battle, Nolan has enjoined a star-studded cast for a retelling of the brilliant and haunted life of J. Robert Oppenheimer, the American physicist whose... Oppenheimer is a 2023 epic biographical thriller film written and directed by Christopher Nolan.It is based on the 2005 biography American Prometheus by Kai Bird and Martin J. Sherwin about J. Robert Oppenheimer, a theoretical physicist who was pivotal in developing the first nuclear weapons as part of the Manhattan Project and thereby ushering in the Atomic Age.
+    Thought:The director of the 2023 film Oppenheimer is Christopher Nolan. Now I need to find out his birth date to calculate his age.
+    Action: duckduckgo_search
+    Action Input: "Christopher Nolan birth date"
+    Observation: July 30, 1970 (age 52) London England Notable Works: "Dunkirk" "Tenet" "The Prestige" See all related content → Recent News Jul. 13, 2023, 11:11 AM ET (AP) Cillian Murphy, playing Oppenheimer, finally gets to lead a Christopher Nolan film Christopher Edward Nolan CBE (born 30 July 1970) is a British and American filmmaker. Known for his Hollywood blockbusters with complex storytelling, Nolan is considered a leading filmmaker of the 21st century. His films have grossed $5 billion worldwide. The recipient of many accolades, he has been nominated for five Academy Awards, five BAFTA Awards and six Golden Globe Awards. Christopher Nolan is currently 52 according to his birthdate July 30, 1970 Sun Sign Leo Born Place Westminster, London, England, United Kingdom Residence Los Angeles, California, United States Nationality Education Chris attended Haileybury and Imperial Service College, in Hertford Heath, Hertfordshire. Christopher Nolan's next movie will study the man who developed the atomic bomb, J. Robert Oppenheimer. Here's the release date, plot, trailers & more. July 2023 sees the release of Christopher Nolan's new film, Oppenheimer, his first movie since 2020's Tenet and his split from Warner Bros. Billed as an epic thriller about "the man who ...
+    Thought:
+    
+    > Finished chain.
+    Christopher Nolan was born on July 30, 1970. Now I need to calculate his age in 2023 and then convert it into days.
+    Action: Calculator
+    Action Input: (2023 - 1970) * 365
+    
+    > Entering new LLMMathChain chain...
+    (2023 - 1970) * 365
+    
+    > Entering new LLMChain chain...
+    Prompt after formatting:
+    Translate a math problem into a expression that can be executed using Python's numexpr library. Use the output of running this code to answer the question.
+    
+    Question: ${Question with math problem.}
+    ```text
+    ${single line mathematical expression that solves the problem}
+    ```
+    ...numexpr.evaluate(text)...
+    ```output
+    ${Output of running the code}
+    ```
+    Answer: ${Answer}
+    
+    Begin.
+    
+    Question: What is 37593 * 67?
+    ```text
+    37593 * 67
+    ```
+    ...numexpr.evaluate("37593 * 67")...
+    ```output
+    2518731
+    ```
+    Answer: 2518731
+    
+    Question: 37593^(1/5)
+    ```text
+    37593**(1/5)
+    ```
+    ...numexpr.evaluate("37593**(1/5)")...
+    ```output
+    8.222831614237718
+    ```
+    Answer: 8.222831614237718
+    
+    Question: (2023 - 1970) * 365
+    
+    
+    > Finished chain.
+    ```text
+    (2023 - 1970) * 365
+    ```
+    ...numexpr.evaluate("(2023 - 1970) * 365")...
+    
+    Answer: 19345
+    > Finished chain.
+    
+    Observation: Answer: 19345
+    Thought:
+    
+    > Entering new LLMChain chain...
+    Prompt after formatting:
+    Answer the following questions as best you can. You have access to the following tools:
+    
+    duckduckgo_search: A wrapper around DuckDuckGo Search. Useful for when you need to answer questions about current events. Input should be a search query.
+    Calculator: Useful for when you need to answer questions about math.
+    
+    Use the following format:
+    
+    Question: the input question you must answer
+    Thought: you should always think about what to do
+    Action: the action to take, should be one of [duckduckgo_search, Calculator]
+    Action Input: the input to the action
+    Observation: the result of the action
+    ... (this Thought/Action/Action Input/Observation can repeat N times)
+    Thought: I now know the final answer
+    Final Answer: the final answer to the original input question
+    
+    Begin!
+    
+    Question: Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?
+    Thought:First, I need to find out who directed the film Oppenheimer in 2023 and their birth date to calculate their age.
+    Action: duckduckgo_search
+    Action Input: "Director of the 2023 film Oppenheimer"
+    Observation: Oppenheimer: Directed by Christopher Nolan. With Cillian Murphy, Emily Blunt, Robert Downey Jr., Alden Ehrenreich. The story of American scientist J. Robert Oppenheimer and his role in the development of the atomic bomb. In Christopher Nolan's new film, "Oppenheimer," Cillian Murphy stars as J. Robert ... 2023, 12:16 p.m. ET. ... including his role as the director of the Manhattan Engineer District, better ... J Robert Oppenheimer was the director of the secret Los Alamos Laboratory. It was established under US president Franklin D Roosevelt as part of the Manhattan Project to build the first atomic bomb. He oversaw the first atomic bomb detonation in the New Mexico desert in July 1945, code-named "Trinity". In this opening salvo of 2023's Oscar battle, Nolan has enjoined a star-studded cast for a retelling of the brilliant and haunted life of J. Robert Oppenheimer, the American physicist whose... Oppenheimer is a 2023 epic biographical thriller film written and directed by Christopher Nolan.It is based on the 2005 biography American Prometheus by Kai Bird and Martin J. Sherwin about J. Robert Oppenheimer, a theoretical physicist who was pivotal in developing the first nuclear weapons as part of the Manhattan Project and thereby ushering in the Atomic Age.
+    Thought:The director of the 2023 film Oppenheimer is Christopher Nolan. Now I need to find out his birth date to calculate his age.
+    Action: duckduckgo_search
+    Action Input: "Christopher Nolan birth date"
+    Observation: July 30, 1970 (age 52) London England Notable Works: "Dunkirk" "Tenet" "The Prestige" See all related content → Recent News Jul. 13, 2023, 11:11 AM ET (AP) Cillian Murphy, playing Oppenheimer, finally gets to lead a Christopher Nolan film Christopher Edward Nolan CBE (born 30 July 1970) is a British and American filmmaker. Known for his Hollywood blockbusters with complex storytelling, Nolan is considered a leading filmmaker of the 21st century. His films have grossed $5 billion worldwide. The recipient of many accolades, he has been nominated for five Academy Awards, five BAFTA Awards and six Golden Globe Awards. Christopher Nolan is currently 52 according to his birthdate July 30, 1970 Sun Sign Leo Born Place Westminster, London, England, United Kingdom Residence Los Angeles, California, United States Nationality Education Chris attended Haileybury and Imperial Service College, in Hertford Heath, Hertfordshire. Christopher Nolan's next movie will study the man who developed the atomic bomb, J. Robert Oppenheimer. Here's the release date, plot, trailers & more. July 2023 sees the release of Christopher Nolan's new film, Oppenheimer, his first movie since 2020's Tenet and his split from Warner Bros. Billed as an epic thriller about "the man who ...
+    Thought:Christopher Nolan was born on July 30, 1970. Now I need to calculate his age in 2023 and then convert it into days.
+    Action: Calculator
+    Action Input: (2023 - 1970) * 365
+    Observation: Answer: 19345
+    Thought:
+    
+    > Finished chain.
+    I now know the final answer
+    Final Answer: The director of the 2023 film Oppenheimer is Christopher Nolan and he is 53 years old in 2023. His age in days is 19345 days.
+    
+    > Finished chain.
+
+
+    'The director of the 2023 film Oppenheimer is Christopher Nolan and he is 53 years old in 2023. His age in days is 19345 days.'
+```
+
+</CodeOutputBlock>
+
+</details>
+
+### `Chain(..., verbose=True)`
+
+You can also scope verbosity down to a single object, in which case only the inputs and outputs to that object are printed (along with any additional callbacks calls made specifically by that object).
+
+
+```python
+# Passing verbose=True to initialize_agent will pass that along to the AgentExecutor (which is a Chain).
+agent = initialize_agent(
+    tools, 
+    llm, 
+    agent=AgentType.ZERO_SHOT_REACT_DESCRIPTION,
+    verbose=True,
+)
+
+agent.run("Who directed the 2023 film Oppenheimer and what is their age? What is their age in days (assume 365 days per year)?")
+```
+
+<details> <summary>Console output</summary>
+
+<CodeOutputBlock lang="python">
+
+```
+    > Entering new AgentExecutor chain...
+    First, I need to find out who directed the film Oppenheimer in 2023 and their birth date. Then, I can calculate their age in years and days.
+    Action: duckduckgo_search
+    Action Input: "Director of 2023 film Oppenheimer"
+    Observation: Oppenheimer: Directed by Christopher Nolan. With Cillian Murphy, Emily Blunt, Robert Downey Jr., Alden Ehrenreich. The story of American scientist J. Robert Oppenheimer and his role in the development of the atomic bomb. In Christopher Nolan's new film, "Oppenheimer," Cillian Murphy stars as J. Robert Oppenheimer, the American physicist who oversaw the Manhattan Project in Los Alamos, N.M. Universal Pictures... J Robert Oppenheimer was the director of the secret Los Alamos Laboratory. It was established under US president Franklin D Roosevelt as part of the Manhattan Project to build the first atomic bomb. He oversaw the first atomic bomb detonation in the New Mexico desert in July 1945, code-named "Trinity". A Review of Christopher Nolan's new film 'Oppenheimer' , the story of the man who fathered the Atomic Bomb. Cillian Murphy leads an all star cast ... Release Date: July 21, 2023. Director ... For his new film, "Oppenheimer," starring Cillian Murphy and Emily Blunt, director Christopher Nolan set out to build an entire 1940s western town.
+    Thought:The director of the 2023 film Oppenheimer is Christopher Nolan. Now I need to find out his birth date to calculate his age.
+    Action: duckduckgo_search
+    Action Input: "Christopher Nolan birth date"
+    Observation: July 30, 1970 (age 52) London England Notable Works: "Dunkirk" "Tenet" "The Prestige" See all related content → Recent News Jul. 13, 2023, 11:11 AM ET (AP) Cillian Murphy, playing Oppenheimer, finally gets to lead a Christopher Nolan film Christopher Edward Nolan CBE (born 30 July 1970) is a British and American filmmaker. Known for his Hollywood blockbusters with complex storytelling, Nolan is considered a leading filmmaker of the 21st century. His films have grossed $5 billion worldwide. The recipient of many accolades, he has been nominated for five Academy Awards, five BAFTA Awards and six Golden Globe Awards. Christopher Nolan is currently 52 according to his birthdate July 30, 1970 Sun Sign Leo Born Place Westminster, London, England, United Kingdom Residence Los Angeles, California, United States Nationality Education Chris attended Haileybury and Imperial Service College, in Hertford Heath, Hertfordshire. Christopher Nolan's next movie will study the man who developed the atomic bomb, J. Robert Oppenheimer. Here's the release date, plot, trailers & more. Date of Birth: 30 July 1970 . ... Christopher Nolan is a British-American film director, producer, and screenwriter. His films have grossed more than US$5 billion worldwide, and have garnered 11 Academy Awards from 36 nominations. ...
+    Thought:Christopher Nolan was born on July 30, 1970. Now I can calculate his age in years and then in days.
+    Action: Calculator
+    Action Input: {"operation": "subtract", "operands": [2023, 1970]}
+    Observation: Answer: 53
+    Thought:Christopher Nolan is 53 years old in 2023. Now I need to calculate his age in days.
+    Action: Calculator
+    Action Input: {"operation": "multiply", "operands": [53, 365]}
+    Observation: Answer: 19345
+    Thought:I now know the final answer
+    Final Answer: The director of the 2023 film Oppenheimer is Christopher Nolan. He is 53 years old in 2023, which is approximately 19345 days.
+    
+    > Finished chain.
+
+
+    'The director of the 2023 film Oppenheimer is Christopher Nolan. He is 53 years old in 2023, which is approximately 19345 days.'
+```
+
+</CodeOutputBlock>
+
+</details>
+
+## Other callbacks
+
+`Callbacks` are what we use to execute any functionality within a component outside the primary component logic. All of the above solutions use `Callbacks` under the hood to log intermediate steps of components. There are a number of `Callbacks` relevant for debugging that come with LangChain out of the box, like the [FileCallbackHandler](/docs/modules/callbacks/filecallbackhandler). You can also implement your own callbacks to execute custom functionality.
+
+See here for more info on [Callbacks](/docs/modules/callbacks/), how to use them, and customize them.

docs/docs/guides/development/extending_langchain.mdx

@@ -0,0 +1,13 @@
+---
+hide_table_of_contents: true
+---
+
+# Extending LangChain
+
+Extending LangChain's base abstractions, whether you're planning to contribute back to the open-source repo or build a bespoke internal integration, is encouraged.
+
+Check out these guides for building your own custom classes for the following modules:
+
+- [Chat models](/docs/modules/model_io/chat/custom_chat_model) for interfacing with chat-tuned language models.
+- [LLMs](/docs/modules/model_io/llms/custom_llm) for interfacing with text language models.
+- [Output parsers](/docs/modules/model_io/output_parsers/custom) for handling language model outputs.

docs/docs/guides/development/index.mdx

@@ -0,0 +1,13 @@
+---
+sidebar_position: 1
+sidebar_class_name: hidden
+---
+
+# Development
+
+This section contains guides with general information around building apps with LangChain.
+
+import DocCardList from "@theme/DocCardList";
+import { useCurrentSidebarCategory } from '@docusaurus/theme-common';
+
+<DocCardList items={useCurrentSidebarCategory().items.filter((item) => item.href !== "/docs/guides/development/")} />

docs/docs/guides/development/local_llms.ipynb

@@ -32,7 +32,7 @@
     "1. `Base model`: What is the base-model and how was it trained?\n",
     "2. `Fine-tuning approach`: Was the base-model fine-tuned and, if so, what [set of instructions](https://cameronrwolfe.substack.com/p/beyond-llama-the-power-of-open-llms#%C2%A7alpaca-an-instruction-following-llama-model) was used?\n",
     "\n",
-    "![Image description](../../static/img/OSS_LLM_overview.png)\n",
+    "![Image description](../../../static/img/OSS_LLM_overview.png)\n",
     "\n",
     "The relative performance of these models can be assessed using several leaderboards, including:\n",
     "\n",
@@ -56,7 +56,7 @@
     "\n",
     "In particular, see [this excellent post](https://finbarr.ca/how-is-llama-cpp-possible/) on the importance of quantization.\n",
     "\n",
-    "![Image description](../../static/img/llama-memory-weights.png)\n",
+    "![Image description](../../../static/img/llama-memory-weights.png)\n",
     "\n",
     "With less precision, we radically decrease the memory needed to store the LLM in memory.\n",
     "\n",
@@ -64,7 +64,7 @@
     "\n",
     "A Mac M2 Max is 5-6x faster than a M1 for inference due to the larger GPU memory bandwidth.\n",
     "\n",
-    "![Image description](../../static/img/llama_t_put.png)\n",
+    "![Image description](../../../static/img/llama_t_put.png)\n",
     "\n",
     "## Quickstart\n",
     "\n",
@@ -134,7 +134,8 @@
     }
    ],
    "source": [
-    "from langchain_core.callbacks import CallbackManager, StreamingStdOutCallbackHandler\n",
+    "from langchain.callbacks.manager import CallbackManager\n",
+    "from langchain.callbacks.streaming_stdout import StreamingStdOutCallbackHandler\n",
     "\n",
     "llm = Ollama(\n",
     "    model=\"llama2\", callback_manager=CallbackManager([StreamingStdOutCallbackHandler()])\n",
@@ -287,8 +288,9 @@
    "metadata": {},
    "outputs": [],
    "source": [
+    "from langchain.callbacks.manager import CallbackManager\n",
+    "from langchain.callbacks.streaming_stdout import StreamingStdOutCallbackHandler\n",
     "from langchain_community.llms import LlamaCpp\n",
-    "from langchain_core.callbacks import CallbackManager, StreamingStdOutCallbackHandler\n",
     "\n",
     "llm = LlamaCpp(\n",
     "    model_path=\"/Users/rlm/Desktop/Code/llama.cpp/models/openorca-platypus2-13b.gguf.q4_0.bin\",\n",
@@ -637,9 +639,9 @@
    "source": [
     "## Use cases\n",
     "\n",
-    "Given an `llm` created from one of the models above, you can use it for [many use cases](/docs/how_to#use-cases).\n",
+    "Given an `llm` created from one of the models above, you can use it for [many use cases](/docs/use_cases/).\n",
     "\n",
-    "For example, here is a guide to [RAG](/docs/tutorials/local_rag) with local LLMs.\n",
+    "For example, here is a guide to [RAG](/docs/use_cases/question_answering/local_retrieval_qa) with local LLMs.\n",
     "\n",
     "In general, use cases for local LLMs can be driven by at least two factors:\n",
     "\n",

docs/docs/guides/development/pydantic_compatibility.md

@@ -1,4 +1,4 @@
-# How to use LangChain with different Pydantic versions
+# Pydantic compatibility
 
 - Pydantic v2 was released in June, 2023 (https://docs.pydantic.dev/2.0/blog/pydantic-v2-final/)
 - v2 contains has a number of breaking changes (https://docs.pydantic.dev/2.0/migration/)
@@ -22,7 +22,6 @@ the case of inheritance and in the case of passing objects to LangChain.
 
 ```python
 from pydantic.v1 import root_validator, validator
-from langchain_core.tools import BaseTool
 
 class CustomTool(BaseTool): # BaseTool is v1 code
     x: int = Field(default=1)
@@ -49,7 +48,6 @@ Mixing Pydantic v2 primitives with Pydantic v1 primitives can raise cryptic erro
 
 ```python
 from pydantic import Field, field_validator # pydantic v2
-from langchain_core.tools import BaseTool
 
 class CustomTool(BaseTool): # BaseTool is v1 code
     x: int = Field(default=1)
@@ -104,4 +102,4 @@ Tool.from_function( # <-- tool uses v1 namespace
     description="useful for when you need to answer questions about math",
     args_schema=CalculatorInput
 )
-```
+```

docs/docs/guides/index.mdx

@@ -0,0 +1,3 @@
+# Guides
+
+This section contains deeper dives into the LangChain framework and how to apply it.

docs/docs/guides/productionization/deployments/index.mdx

@@ -0,0 +1,115 @@
+# Deployment
+
+In today's fast-paced technological landscape, the use of Large Language Models (LLMs) is rapidly expanding. As a result, it is crucial for developers to understand how to effectively deploy these models in production environments. LLM interfaces typically fall into two categories:
+
+- **Case 1: Utilizing External LLM Providers (OpenAI, Anthropic, etc.)**
+    In this scenario, most of the computational burden is handled by the LLM providers, while LangChain simplifies the implementation of business logic around these services. This approach includes features such as prompt templating, chat message generation, caching, vector embedding database creation, preprocessing, etc.
+
+- **Case 2: Self-hosted Open-Source Models**
+    Alternatively, developers can opt to use smaller, yet comparably capable, self-hosted open-source LLM models. This approach can significantly decrease costs, latency, and privacy concerns associated with transferring data to external LLM providers.
+
+Regardless of the framework that forms the backbone of your product, deploying LLM applications comes with its own set of challenges. It's vital to understand the trade-offs and key considerations when evaluating serving frameworks.
+
+## Outline
+
+This guide aims to provide a comprehensive overview of the requirements for deploying LLMs in a production setting, focusing on:
+
+- **Designing a Robust LLM Application Service**
+- **Maintaining Cost-Efficiency**
+- **Ensuring Rapid Iteration**
+
+Understanding these components is crucial when assessing serving systems. LangChain integrates with several open-source projects designed to tackle these issues, providing a robust framework for productionizing your LLM applications. Some notable frameworks include:
+
+- [Ray Serve](/docs/integrations/providers/ray_serve)
+- [BentoML](https://github.com/bentoml/BentoML)
+- [OpenLLM](/docs/integrations/providers/openllm)
+- [Modal](/docs/integrations/providers/modal)
+- [Jina](/docs/integrations/providers/jina)
+
+These links will provide further information on each ecosystem, assisting you in finding the best fit for your LLM deployment needs.
+
+## Designing a Robust LLM Application Service
+
+When deploying an LLM service in production, it's imperative to provide a seamless user experience free from outages. Achieving 24/7 service availability involves creating and maintaining several sub-systems surrounding your application.
+
+### Monitoring
+
+Monitoring forms an integral part of any system running in a production environment. In the context of LLMs, it is essential to monitor both performance and quality metrics.
+
+**Performance Metrics:** These metrics provide insights into the efficiency and capacity of your model. Here are some key examples:
+
+- Query per second (QPS): This measures the number of queries your model processes in a second, offering insights into its utilization.
+- Latency: This metric quantifies the delay from when your client sends a request to when they receive a response.
+- Tokens Per Second (TPS): This represents the number of tokens your model can generate in a second.
+
+**Quality Metrics:** These metrics are typically customized according to the business use-case. For instance, how does the output of your system compare to a baseline, such as a previous version? Although these metrics can be calculated offline, you need to log the necessary data to use them later.
+
+### Fault tolerance
+
+Your application may encounter errors such as exceptions in your model inference or business logic code, causing failures and disrupting traffic. Other potential issues could arise from the machine running your application, such as unexpected hardware breakdowns or loss of spot-instances during high-demand periods. One way to mitigate these risks is by increasing redundancy through replica scaling and implementing recovery mechanisms for failed replicas. However, model replicas aren't the only potential points of failure. It's essential to build resilience against various failures that could occur at any point in your stack.
+
+
+### Zero down time upgrade
+
+System upgrades are often necessary but can result in service disruptions if not handled correctly. One way to prevent downtime during upgrades is by implementing a smooth transition process from the old version to the new one. Ideally, the new version of your LLM service is deployed, and traffic gradually shifts from the old to the new version, maintaining a constant QPS throughout the process.
+
+
+### Load balancing
+
+Load balancing, in simple terms, is a technique to distribute work evenly across multiple computers, servers, or other resources to optimize the utilization of the system, maximize throughput, minimize response time, and avoid overload of any single resource. Think of it as a traffic officer directing cars (requests) to different roads (servers) so that no single road becomes too congested.
+
+There are several strategies for load balancing. For example, one common method is the *Round Robin* strategy, where each request is sent to the next server in line, cycling back to the first when all servers have received a request. This works well when all servers are equally capable. However, if some servers are more powerful than others, you might use a *Weighted Round Robin* or *Least Connections* strategy, where more requests are sent to the more powerful servers, or to those currently handling the fewest active requests. Let's imagine you're running a LLM chain. If your application becomes popular, you could have hundreds or even thousands of users asking questions at the same time. If one server gets too busy (high load), the load balancer would direct new requests to another server that is less busy. This way, all your users get a timely response and the system remains stable.
+
+
+
+## Maintaining Cost-Efficiency and Scalability
+
+Deploying LLM services can be costly, especially when you're handling a large volume of user interactions. Charges by LLM providers are usually based on tokens used, making a chat system inference on these models potentially expensive. However, several strategies can help manage these costs without compromising the quality of the service.
+
+
+### Self-hosting models
+
+Several smaller and open-source LLMs are emerging to tackle the issue of reliance on LLM providers. Self-hosting allows you to maintain similar quality to LLM provider models while managing costs. The challenge lies in building a reliable, high-performing LLM serving system on your own machines. 
+
+### Resource Management and Auto-Scaling
+
+Computational logic within your application requires precise resource allocation. For instance, if part of your traffic is served by an OpenAI endpoint and another part by a self-hosted model, it's crucial to allocate suitable resources for each. Auto-scaling—adjusting resource allocation based on traffic—can significantly impact the cost of running your application. This strategy requires a balance between cost and responsiveness, ensuring neither resource over-provisioning nor compromised application responsiveness.
+
+### Utilizing Spot Instances
+
+On platforms like AWS, spot instances offer substantial cost savings, typically priced at about a third of on-demand instances. The trade-off is a higher crash rate, necessitating a robust fault-tolerance mechanism for effective use.
+
+### Independent Scaling
+
+When self-hosting your models, you should consider independent scaling. For example, if you have two translation models, one fine-tuned for French and another for Spanish, incoming requests might necessitate different scaling requirements for each.
+
+### Batching requests
+
+In the context of Large Language Models, batching requests can enhance efficiency by better utilizing your GPU resources. GPUs are inherently parallel processors, designed to handle multiple tasks simultaneously. If you send individual requests to the model, the GPU might not be fully utilized as it's only working on a single task at a time. On the other hand, by batching requests together, you're allowing the GPU to work on multiple tasks at once, maximizing its utilization and improving inference speed. This not only leads to cost savings but can also improve the overall latency of your LLM service.
+
+
+In summary, managing costs while scaling your LLM services requires a strategic approach. Utilizing self-hosting models, managing resources effectively, employing auto-scaling, using spot instances, independently scaling models, and batching requests are key strategies to consider. Open-source libraries such as Ray Serve and BentoML are designed to deal with these complexities. 
+
+
+
+## Ensuring Rapid Iteration
+
+The LLM landscape is evolving at an unprecedented pace, with new libraries and model architectures being introduced constantly. Consequently, it's crucial to avoid tying yourself to a solution specific to one particular framework. This is especially relevant in serving, where changes to your infrastructure can be time-consuming, expensive, and risky. Strive for infrastructure that is not locked into any specific machine learning library or framework, but instead offers a general-purpose, scalable serving layer. Here are some aspects where flexibility plays a key role:
+
+### Model composition
+
+Deploying systems like LangChain demands the ability to piece together different models and connect them via logic. Take the example of building a natural language input SQL query engine. Querying an LLM and obtaining the SQL command is only part of the system. You need to extract metadata from the connected database, construct a prompt for the LLM, run the SQL query on an engine, collect and feedback the response to the LLM as the query runs, and present the results to the user. This demonstrates the need to seamlessly integrate various complex components built in Python into a dynamic chain of logical blocks that can be served together.
+
+## Cloud providers
+
+Many hosted solutions are restricted to a single cloud provider, which can limit your options in today's multi-cloud world. Depending on where your other infrastructure components are built, you might prefer to stick with your chosen cloud provider.
+
+
+## Infrastructure as Code (IaC)
+
+Rapid iteration also involves the ability to recreate your infrastructure quickly and reliably. This is where Infrastructure as Code (IaC) tools like Terraform, CloudFormation, or Kubernetes YAML files come into play. They allow you to define your infrastructure in code files, which can be version controlled and quickly deployed, enabling faster and more reliable iterations.
+
+
+## CI/CD
+
+In a fast-paced environment, implementing CI/CD pipelines can significantly speed up the iteration process. They help automate the testing and deployment of your LLM applications, reducing the risk of errors and enabling faster feedback and iteration.

docs/docs/guides/productionization/deployments/template_repos.mdx

@@ -0,0 +1,7 @@
+# LangChain Templates
+
+For more information on LangChain Templates, visit 
+
+- [LangChain Templates Quickstart](https://github.com/langchain-ai/langchain/blob/master/templates/README.md)
+- [LangChain Templates Index](https://github.com/langchain-ai/langchain/blob/master/templates/docs/INDEX.md)
+- [Full List of Templates](https://github.com/langchain-ai/langchain/blob/master/templates/)

docs/docs/guides/productionization/evaluation/comparison/custom.ipynb

@@ -0,0 +1,293 @@
+{
+ "cells": [
+  {
+   "cell_type": "raw",
+   "id": "5046d96f-d578-4d5b-9a7e-43b28cafe61d",
+   "metadata": {},
+   "source": [
+    "---\n",
+    "sidebar_position: 2\n",
+    "title: Custom pairwise evaluator\n",
+    "---"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "657d2c8c-54b4-42a3-9f02-bdefa0ed6728",
+   "metadata": {},
+   "source": [
+    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/langchain-ai/langchain/blob/master/docs/docs/guides/evaluation/comparison/custom.ipynb)\n",
+    "\n",
+    "You can make your own pairwise string evaluators by inheriting from `PairwiseStringEvaluator` class and overwriting the `_evaluate_string_pairs` method (and the `_aevaluate_string_pairs` method if you want to use the evaluator asynchronously).\n",
+    "\n",
+    "In this example, you will make a simple custom evaluator that just returns whether the first prediction has more whitespace tokenized 'words' than the second.\n",
+    "\n",
+    "You can check out the reference docs for the [PairwiseStringEvaluator interface](https://api.python.langchain.com/en/latest/evaluation/langchain.evaluation.schema.PairwiseStringEvaluator.html#langchain.evaluation.schema.PairwiseStringEvaluator) for more info.\n"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 1,
+   "id": "93f3a653-d198-4291-973c-8d1adba338b2",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "from typing import Any, Optional\n",
+    "\n",
+    "from langchain.evaluation import PairwiseStringEvaluator\n",
+    "\n",
+    "\n",
+    "class LengthComparisonPairwiseEvaluator(PairwiseStringEvaluator):\n",
+    "    \"\"\"\n",
+    "    Custom evaluator to compare two strings.\n",
+    "    \"\"\"\n",
+    "\n",
+    "    def _evaluate_string_pairs(\n",
+    "        self,\n",
+    "        *,\n",
+    "        prediction: str,\n",
+    "        prediction_b: str,\n",
+    "        reference: Optional[str] = None,\n",
+    "        input: Optional[str] = None,\n",
+    "        **kwargs: Any,\n",
+    "    ) -> dict:\n",
+    "        score = int(len(prediction.split()) > len(prediction_b.split()))\n",
+    "        return {\"score\": score}"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 2,
+   "id": "7d4a77c3-07a7-4076-8e7f-f9bca0d6c290",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "{'score': 1}"
+      ]
+     },
+     "execution_count": 2,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "evaluator = LengthComparisonPairwiseEvaluator()\n",
+    "\n",
+    "evaluator.evaluate_string_pairs(\n",
+    "    prediction=\"The quick brown fox jumped over the lazy dog.\",\n",
+    "    prediction_b=\"The quick brown fox jumped over the dog.\",\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "d90f128f-6f49-42a1-b05a-3aea568ee03b",
+   "metadata": {},
+   "source": [
+    "## LLM-Based Example\n",
+    "\n",
+    "That example was simple to illustrate the API, but it wasn't very useful in practice. Below, use an LLM with some custom instructions to form a simple preference scorer similar to the built-in [PairwiseStringEvalChain](https://api.python.langchain.com/en/latest/evaluation/langchain.evaluation.comparison.eval_chain.PairwiseStringEvalChain.html#langchain.evaluation.comparison.eval_chain.PairwiseStringEvalChain). We will use `ChatAnthropic` for the evaluator chain."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 3,
+   "id": "b4b43098-4d96-417b-a8a9-b3e75779cfe8",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "%pip install --upgrade --quiet  anthropic\n",
+    "# %env ANTHROPIC_API_KEY=YOUR_API_KEY"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 4,
+   "id": "b6e978ab-48f1-47ff-9506-e13b1a50be6e",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "from typing import Any, Optional\n",
+    "\n",
+    "from langchain.chains import LLMChain\n",
+    "from langchain.evaluation import PairwiseStringEvaluator\n",
+    "from langchain_community.chat_models import ChatAnthropic\n",
+    "\n",
+    "\n",
+    "class CustomPreferenceEvaluator(PairwiseStringEvaluator):\n",
+    "    \"\"\"\n",
+    "    Custom evaluator to compare two strings using a custom LLMChain.\n",
+    "    \"\"\"\n",
+    "\n",
+    "    def __init__(self) -> None:\n",
+    "        llm = ChatAnthropic(model=\"claude-2\", temperature=0)\n",
+    "        self.eval_chain = LLMChain.from_string(\n",
+    "            llm,\n",
+    "            \"\"\"Which option is preferred? Do not take order into account. Evaluate based on accuracy and helpfulness. If neither is preferred, respond with C. Provide your reasoning, then finish with Preference: A/B/C\n",
+    "\n",
+    "Input: How do I get the path of the parent directory in python 3.8?\n",
+    "Option A: You can use the following code:\n",
+    "```python\n",
+    "import os\n",
+    "\n",
+    "os.path.dirname(os.path.dirname(os.path.abspath(__file__)))\n",
+    "```\n",
+    "Option B: You can use the following code:\n",
+    "```python\n",
+    "from pathlib import Path\n",
+    "Path(__file__).absolute().parent\n",
+    "```\n",
+    "Reasoning: Both options return the same result. However, since option B is more concise and easily understand, it is preferred.\n",
+    "Preference: B\n",
+    "\n",
+    "Which option is preferred? Do not take order into account. Evaluate based on accuracy and helpfulness. If neither is preferred, respond with C. Provide your reasoning, then finish with Preference: A/B/C\n",
+    "Input: {input}\n",
+    "Option A: {prediction}\n",
+    "Option B: {prediction_b}\n",
+    "Reasoning:\"\"\",\n",
+    "        )\n",
+    "\n",
+    "    @property\n",
+    "    def requires_input(self) -> bool:\n",
+    "        return True\n",
+    "\n",
+    "    @property\n",
+    "    def requires_reference(self) -> bool:\n",
+    "        return False\n",
+    "\n",
+    "    def _evaluate_string_pairs(\n",
+    "        self,\n",
+    "        *,\n",
+    "        prediction: str,\n",
+    "        prediction_b: str,\n",
+    "        reference: Optional[str] = None,\n",
+    "        input: Optional[str] = None,\n",
+    "        **kwargs: Any,\n",
+    "    ) -> dict:\n",
+    "        result = self.eval_chain(\n",
+    "            {\n",
+    "                \"input\": input,\n",
+    "                \"prediction\": prediction,\n",
+    "                \"prediction_b\": prediction_b,\n",
+    "                \"stop\": [\"Which option is preferred?\"],\n",
+    "            },\n",
+    "            **kwargs,\n",
+    "        )\n",
+    "\n",
+    "        response_text = result[\"text\"]\n",
+    "        reasoning, preference = response_text.split(\"Preference:\", maxsplit=1)\n",
+    "        preference = preference.strip()\n",
+    "        score = 1.0 if preference == \"A\" else (0.0 if preference == \"B\" else None)\n",
+    "        return {\"reasoning\": reasoning.strip(), \"value\": preference, \"score\": score}"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 6,
+   "id": "5cbd8b1d-2cb0-4f05-b435-a1a00074d94a",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "evaluator = CustomPreferenceEvaluator()"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 7,
+   "id": "2c0a7fb7-b976-4443-9f0e-e707a6dfbdf7",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "{'reasoning': 'Option B is preferred over option A for importing from a relative directory, because it is more straightforward and concise.\\n\\nOption A uses the importlib module, which allows importing a module by specifying the full name as a string. While this works, it is less clear compared to option B.\\n\\nOption B directly imports from the relative path using dot notation, which clearly shows that it is a relative import. This is the recommended way to do relative imports in Python.\\n\\nIn summary, option B is more accurate and helpful as it uses the standard Python relative import syntax.',\n",
+       " 'value': 'B',\n",
+       " 'score': 0.0}"
+      ]
+     },
+     "execution_count": 7,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "evaluator.evaluate_string_pairs(\n",
+    "    input=\"How do I import from a relative directory?\",\n",
+    "    prediction=\"use importlib! importlib.import_module('.my_package', '.')\",\n",
+    "    prediction_b=\"from .sibling import foo\",\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 13,
+   "id": "f13a1346-7dbe-451d-b3a3-99e8fc7b753b",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "CustomPreferenceEvaluator requires an input string.\n"
+     ]
+    }
+   ],
+   "source": [
+    "# Setting requires_input to return True adds additional validation to avoid returning a grade when insufficient data is provided to the chain.\n",
+    "\n",
+    "try:\n",
+    "    evaluator.evaluate_string_pairs(\n",
+    "        prediction=\"use importlib! importlib.import_module('.my_package', '.')\",\n",
+    "        prediction_b=\"from .sibling import foo\",\n",
+    "    )\n",
+    "except ValueError as e:\n",
+    "    print(e)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "e7829cc3-ebd1-4628-ae97-15166202e9cc",
+   "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/docs/guides/productionization/evaluation/comparison/index.mdx

@@ -0,0 +1,28 @@
+---
+sidebar_position: 3 
+---
+# Comparison Evaluators
+
+Comparison evaluators in LangChain help measure two different chains or LLM outputs. These evaluators are helpful for comparative analyses, such as A/B testing between two language models, or comparing different versions of the same model. They can also be useful for things like generating preference scores for ai-assisted reinforcement learning.
+
+These evaluators inherit from the `PairwiseStringEvaluator` class, providing a comparison interface for two strings - typically, the outputs from two different prompts or models, or two versions of the same model. In essence, a comparison evaluator performs an evaluation on a pair of strings and returns a dictionary containing the evaluation score and other relevant details.
+
+To create a custom comparison evaluator, inherit from the `PairwiseStringEvaluator` class and overwrite the `_evaluate_string_pairs` method. If you require asynchronous evaluation, also overwrite the `_aevaluate_string_pairs` method.
+
+Here's a summary of the key methods and properties of a comparison evaluator:
+
+- `evaluate_string_pairs`: Evaluate the output string pairs. This function should be overwritten when creating custom evaluators.
+- `aevaluate_string_pairs`: Asynchronously evaluate the output string pairs. This function should be overwritten for asynchronous evaluation.
+- `requires_input`: This property indicates whether this evaluator requires an input string.
+- `requires_reference`: This property specifies whether this evaluator requires a reference label.
+
+:::note LangSmith Support
+The [run_on_dataset](https://api.python.langchain.com/en/latest/langchain_api_reference.html#module-langchain.smith) evaluation method is designed to evaluate only a single model at a time, and thus, doesn't support these evaluators.
+:::
+
+Detailed information about creating custom evaluators and the available built-in comparison evaluators is provided in the following sections.
+
+import DocCardList from "@theme/DocCardList";
+
+<DocCardList />
+

docs/docs/guides/productionization/evaluation/comparison/pairwise_embedding_distance.ipynb

@@ -0,0 +1,242 @@
+{
+ "cells": [
+  {
+   "cell_type": "raw",
+   "metadata": {},
+   "source": [
+    "---\n",
+    "sidebar_position: 1\n",
+    "title: Pairwise embedding distance\n",
+    "---"
+   ]
+  },
+  {
+   "attachments": {},
+   "cell_type": "markdown",
+   "metadata": {
+    "tags": []
+   },
+   "source": [
+    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/langchain-ai/langchain/blob/master/docs/docs/guides/evaluation/comparison/pairwise_embedding_distance.ipynb)\n",
+    "\n",
+    "One way to measure the similarity (or dissimilarity) between two predictions on a shared or similar input is to embed the predictions and compute a vector distance between the two embeddings.<a name=\"cite_ref-1\"></a>[<sup>[1]</sup>](#cite_note-1)\n",
+    "\n",
+    "You can load the `pairwise_embedding_distance` evaluator to do this.\n",
+    "\n",
+    "**Note:** This returns a **distance** score, meaning that the lower the number, the **more** similar the outputs are, according to their embedded representation.\n",
+    "\n",
+    "Check out the reference docs for the [PairwiseEmbeddingDistanceEvalChain](https://api.python.langchain.com/en/latest/evaluation/langchain.evaluation.embedding_distance.base.PairwiseEmbeddingDistanceEvalChain.html#langchain.evaluation.embedding_distance.base.PairwiseEmbeddingDistanceEvalChain) for more info."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 1,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "from langchain.evaluation import load_evaluator\n",
+    "\n",
+    "evaluator = load_evaluator(\"pairwise_embedding_distance\")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 2,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "{'score': 0.0966466944859925}"
+      ]
+     },
+     "execution_count": 2,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "evaluator.evaluate_string_pairs(\n",
+    "    prediction=\"Seattle is hot in June\", prediction_b=\"Seattle is cool in June.\"\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 3,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "{'score': 0.03761174337464557}"
+      ]
+     },
+     "execution_count": 3,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "evaluator.evaluate_string_pairs(\n",
+    "    prediction=\"Seattle is warm in June\", prediction_b=\"Seattle is cool in June.\"\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "## Select the Distance Metric\n",
+    "\n",
+    "By default, the evaluator uses cosine distance. You can choose a different distance metric if you'd like. "
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 4,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "[<EmbeddingDistance.COSINE: 'cosine'>,\n",
+       " <EmbeddingDistance.EUCLIDEAN: 'euclidean'>,\n",
+       " <EmbeddingDistance.MANHATTAN: 'manhattan'>,\n",
+       " <EmbeddingDistance.CHEBYSHEV: 'chebyshev'>,\n",
+       " <EmbeddingDistance.HAMMING: 'hamming'>]"
+      ]
+     },
+     "execution_count": 4,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "from langchain.evaluation import EmbeddingDistance\n",
+    "\n",
+    "list(EmbeddingDistance)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 5,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "evaluator = load_evaluator(\n",
+    "    \"pairwise_embedding_distance\", distance_metric=EmbeddingDistance.EUCLIDEAN\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "## Select Embeddings to Use\n",
+    "\n",
+    "The constructor uses `OpenAI` embeddings by default, but you can configure this however you want. Below, use huggingface local embeddings"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "from langchain_community.embeddings import HuggingFaceEmbeddings\n",
+    "\n",
+    "embedding_model = HuggingFaceEmbeddings()\n",
+    "hf_evaluator = load_evaluator(\"pairwise_embedding_distance\", embeddings=embedding_model)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 10,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "{'score': 0.5486443280477362}"
+      ]
+     },
+     "execution_count": 10,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "hf_evaluator.evaluate_string_pairs(\n",
+    "    prediction=\"Seattle is hot in June\", prediction_b=\"Seattle is cool in June.\"\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 12,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "{'score': 0.21018880025138598}"
+      ]
+     },
+     "execution_count": 12,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "hf_evaluator.evaluate_string_pairs(\n",
+    "    prediction=\"Seattle is warm in June\", prediction_b=\"Seattle is cool in June.\"\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "<a name=\"cite_note-1\"></a><i>1. Note: When it comes to semantic similarity, this often gives better results than older string distance metrics (such as those in the `PairwiseStringDistanceEvalChain`), though it tends to be less reliable than evaluators that use the LLM directly (such as the `PairwiseStringEvalChain`) </i>"
+   ]
+  }
+ ],
+ "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": 4
+}

docs/docs/guides/productionization/evaluation/comparison/pairwise_string.ipynb

@@ -0,0 +1,392 @@
+{
+ "cells": [
+  {
+   "cell_type": "raw",
+   "id": "dcfcf124-78fe-4d67-85a4-cfd3409a1ff6",
+   "metadata": {},
+   "source": [
+    "---\n",
+    "sidebar_position: 0\n",
+    "title: Pairwise string comparison\n",
+    "---"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "2da95378",
+   "metadata": {},
+   "source": [
+    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/langchain-ai/langchain/blob/master/docs/docs/guides/evaluation/comparison/pairwise_string.ipynb)\n",
+    "\n",
+    "Often you will want to compare predictions of an LLM, Chain, or Agent for a given input. The `StringComparison` evaluators facilitate this so you can answer questions like:\n",
+    "\n",
+    "- Which LLM or prompt produces a preferred output for a given question?\n",
+    "- Which examples should I include for few-shot example selection?\n",
+    "- Which output is better to include for fine-tuning?\n",
+    "\n",
+    "The simplest and often most reliable automated way to choose a preferred prediction for a given input is to use the `pairwise_string` evaluator.\n",
+    "\n",
+    "Check out the reference docs for the [PairwiseStringEvalChain](https://api.python.langchain.com/en/latest/evaluation/langchain.evaluation.comparison.eval_chain.PairwiseStringEvalChain.html#langchain.evaluation.comparison.eval_chain.PairwiseStringEvalChain) for more info."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 1,
+   "id": "f6790c46",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "from langchain.evaluation import load_evaluator\n",
+    "\n",
+    "evaluator = load_evaluator(\"labeled_pairwise_string\")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 2,
+   "id": "49ad9139",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "{'reasoning': 'Both responses are relevant to the question asked, as they both provide a numerical answer to the question about the number of dogs in the park. However, Response A is incorrect according to the reference answer, which states that there are four dogs. Response B, on the other hand, is correct as it matches the reference answer. Neither response demonstrates depth of thought, as they both simply provide a numerical answer without any additional information or context. \\n\\nBased on these criteria, Response B is the better response.\\n',\n",
+       " 'value': 'B',\n",
+       " 'score': 0}"
+      ]
+     },
+     "execution_count": 2,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "evaluator.evaluate_string_pairs(\n",
+    "    prediction=\"there are three dogs\",\n",
+    "    prediction_b=\"4\",\n",
+    "    input=\"how many dogs are in the park?\",\n",
+    "    reference=\"four\",\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "7491d2e6-4e77-4b17-be6b-7da966785c1d",
+   "metadata": {},
+   "source": [
+    "## Methods\n",
+    "\n",
+    "\n",
+    "The pairwise string evaluator can be called using [evaluate_string_pairs](https://api.python.langchain.com/en/latest/evaluation/langchain.evaluation.comparison.eval_chain.PairwiseStringEvalChain.html#langchain.evaluation.comparison.eval_chain.PairwiseStringEvalChain.evaluate_string_pairs) (or async [aevaluate_string_pairs](https://api.python.langchain.com/en/latest/evaluation/langchain.evaluation.comparison.eval_chain.PairwiseStringEvalChain.html#langchain.evaluation.comparison.eval_chain.PairwiseStringEvalChain.aevaluate_string_pairs)) methods, which accept:\n",
+    "\n",
+    "- prediction (str) – The predicted response of the first model, chain, or prompt.\n",
+    "- prediction_b (str) – The predicted response of the second model, chain, or prompt.\n",
+    "- input (str) – The input question, prompt, or other text.\n",
+    "- reference (str) – (Only for the labeled_pairwise_string variant) The reference response.\n",
+    "\n",
+    "They return a dictionary with the following values:\n",
+    "\n",
+    "- value: 'A' or 'B', indicating whether `prediction` or `prediction_b` is preferred, respectively\n",
+    "- score: Integer 0 or 1 mapped from the 'value', where a score of 1 would mean that the first `prediction` is preferred, and a score of 0 would mean `prediction_b` is preferred.\n",
+    "- reasoning: String \"chain of thought reasoning\" from the LLM generated prior to creating the score"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "ed353b93-be71-4479-b9c0-8c97814c2e58",
+   "metadata": {},
+   "source": [
+    "## Without References\n",
+    "\n",
+    "When references aren't available, you can still predict the preferred response.\n",
+    "The results will reflect the evaluation model's preference, which is less reliable and may result\n",
+    "in preferences that are factually incorrect."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 3,
+   "id": "586320da",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "from langchain.evaluation import load_evaluator\n",
+    "\n",
+    "evaluator = load_evaluator(\"pairwise_string\")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 4,
+   "id": "7f56c76e-a39b-4509-8b8a-8a2afe6c3da1",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "{'reasoning': 'Both responses are correct and relevant to the question. However, Response B is more helpful and insightful as it provides a more detailed explanation of what addition is. Response A is correct but lacks depth as it does not explain what the operation of addition entails. \\n\\nFinal Decision: [[B]]',\n",
+       " 'value': 'B',\n",
+       " 'score': 0}"
+      ]
+     },
+     "execution_count": 4,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "evaluator.evaluate_string_pairs(\n",
+    "    prediction=\"Addition is a mathematical operation.\",\n",
+    "    prediction_b=\"Addition is a mathematical operation that adds two numbers to create a third number, the 'sum'.\",\n",
+    "    input=\"What is addition?\",\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "4a09b21d-9851-47e8-93d3-90044b2945b0",
+   "metadata": {
+    "tags": []
+   },
+   "source": [
+    "## Defining the Criteria\n",
+    "\n",
+    "By default, the LLM is instructed to select the 'preferred' response based on helpfulness, relevance, correctness, and depth of thought. You can customize the criteria by passing in a `criteria` argument, where the criteria could take any of the following forms:\n",
+    "\n",
+    "- [`Criteria`](https://api.python.langchain.com/en/latest/evaluation/langchain.evaluation.criteria.eval_chain.Criteria.html#langchain.evaluation.criteria.eval_chain.Criteria) enum or its string value - to use one of the default criteria and their descriptions\n",
+    "- [Constitutional principal](https://api.python.langchain.com/en/latest/chains/langchain.chains.constitutional_ai.models.ConstitutionalPrinciple.html#langchain.chains.constitutional_ai.models.ConstitutionalPrinciple) - use one any of the constitutional principles defined in langchain\n",
+    "- Dictionary: a list of custom criteria, where the key is the name of the criteria, and the value is the description.\n",
+    "- A list of criteria or constitutional principles - to combine multiple criteria in one.\n",
+    "\n",
+    "Below is an example for determining preferred writing responses based on a custom style."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 5,
+   "id": "8539e7d9-f7b0-4d32-9c45-593a7915c093",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "custom_criteria = {\n",
+    "    \"simplicity\": \"Is the language straightforward and unpretentious?\",\n",
+    "    \"clarity\": \"Are the sentences clear and easy to understand?\",\n",
+    "    \"precision\": \"Is the writing precise, with no unnecessary words or details?\",\n",
+    "    \"truthfulness\": \"Does the writing feel honest and sincere?\",\n",
+    "    \"subtext\": \"Does the writing suggest deeper meanings or themes?\",\n",
+    "}\n",
+    "evaluator = load_evaluator(\"pairwise_string\", criteria=custom_criteria)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 6,
+   "id": "fec7bde8-fbdc-4730-8366-9d90d033c181",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "{'reasoning': 'Response A is simple, clear, and precise. It uses straightforward language to convey a deep and sincere message about families. The metaphor of joy and sorrow as music is effective and easy to understand.\\n\\nResponse B, on the other hand, is more complex and less clear. The language is more pretentious, with words like \"domicile,\" \"resounds,\" \"abode,\" \"dissonant,\" and \"elegy.\" While it conveys a similar message to Response A, it does so in a more convoluted way. The precision is also lacking due to the use of unnecessary words and details.\\n\\nBoth responses suggest deeper meanings or themes about the shared joy and unique sorrow in families. However, Response A does so in a more effective and accessible way.\\n\\nTherefore, the better response is [[A]].',\n",
+       " 'value': 'A',\n",
+       " 'score': 1}"
+      ]
+     },
+     "execution_count": 6,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "evaluator.evaluate_string_pairs(\n",
+    "    prediction=\"Every cheerful household shares a similar rhythm of joy; but sorrow, in each household, plays a unique, haunting melody.\",\n",
+    "    prediction_b=\"Where one finds a symphony of joy, every domicile of happiness resounds in harmonious,\"\n",
+    "    \" identical notes; yet, every abode of despair conducts a dissonant orchestra, each\"\n",
+    "    \" playing an elegy of grief that is peculiar and profound to its own existence.\",\n",
+    "    input=\"Write some prose about families.\",\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "a25b60b2-627c-408a-be4b-a2e5cbc10726",
+   "metadata": {},
+   "source": [
+    "## Customize the LLM\n",
+    "\n",
+    "By default, the loader uses `gpt-4` in the evaluation chain. You can customize this when loading."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 7,
+   "id": "de84a958-1330-482b-b950-68bcf23f9e35",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain_community.chat_models import ChatAnthropic\n",
+    "\n",
+    "llm = ChatAnthropic(temperature=0)\n",
+    "\n",
+    "evaluator = load_evaluator(\"labeled_pairwise_string\", llm=llm)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 8,
+   "id": "e162153f-d50a-4a7c-a033-019dabbc954c",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "{'reasoning': 'Here is my assessment:\\n\\nResponse B is more helpful, insightful, and accurate than Response A. Response B simply states \"4\", which directly answers the question by providing the exact number of dogs mentioned in the reference answer. In contrast, Response A states \"there are three dogs\", which is incorrect according to the reference answer. \\n\\nIn terms of helpfulness, Response B gives the precise number while Response A provides an inaccurate guess. For relevance, both refer to dogs in the park from the question. However, Response B is more correct and factual based on the reference answer. Response A shows some attempt at reasoning but is ultimately incorrect. Response B requires less depth of thought to simply state the factual number.\\n\\nIn summary, Response B is superior in terms of helpfulness, relevance, correctness, and depth. My final decision is: [[B]]\\n',\n",
+       " 'value': 'B',\n",
+       " 'score': 0}"
+      ]
+     },
+     "execution_count": 8,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "evaluator.evaluate_string_pairs(\n",
+    "    prediction=\"there are three dogs\",\n",
+    "    prediction_b=\"4\",\n",
+    "    input=\"how many dogs are in the park?\",\n",
+    "    reference=\"four\",\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "e0e89c13-d0ad-4f87-8fcb-814399bafa2a",
+   "metadata": {},
+   "source": [
+    "## Customize the Evaluation Prompt\n",
+    "\n",
+    "You can use your own custom evaluation prompt to add more task-specific instructions or to instruct the evaluator to score the output.\n",
+    "\n",
+    "*Note: If you use a prompt that expects generates a result in a unique format, you may also have to pass in a custom output parser (`output_parser=your_parser()`) instead of the default `PairwiseStringResultOutputParser`"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 9,
+   "id": "fb817efa-3a4d-439d-af8c-773b89d97ec9",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "from langchain_core.prompts import PromptTemplate\n",
+    "\n",
+    "prompt_template = PromptTemplate.from_template(\n",
+    "    \"\"\"Given the input context, which do you prefer: A or B?\n",
+    "Evaluate based on the following criteria:\n",
+    "{criteria}\n",
+    "Reason step by step and finally, respond with either [[A]] or [[B]] on its own line.\n",
+    "\n",
+    "DATA\n",
+    "----\n",
+    "input: {input}\n",
+    "reference: {reference}\n",
+    "A: {prediction}\n",
+    "B: {prediction_b}\n",
+    "---\n",
+    "Reasoning:\n",
+    "\n",
+    "\"\"\"\n",
+    ")\n",
+    "evaluator = load_evaluator(\"labeled_pairwise_string\", prompt=prompt_template)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 10,
+   "id": "d40aa4f0-cfd5-4cb4-83c8-8d2300a04c2f",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "input_variables=['prediction', 'reference', 'prediction_b', 'input'] output_parser=None partial_variables={'criteria': 'helpfulness: Is the submission helpful, insightful, and appropriate?\\nrelevance: Is the submission referring to a real quote from the text?\\ncorrectness: Is the submission correct, accurate, and factual?\\ndepth: Does the submission demonstrate depth of thought?'} template='Given the input context, which do you prefer: A or B?\\nEvaluate based on the following criteria:\\n{criteria}\\nReason step by step and finally, respond with either [[A]] or [[B]] on its own line.\\n\\nDATA\\n----\\ninput: {input}\\nreference: {reference}\\nA: {prediction}\\nB: {prediction_b}\\n---\\nReasoning:\\n\\n' template_format='f-string' validate_template=True\n"
+     ]
+    }
+   ],
+   "source": [
+    "# The prompt was assigned to the evaluator\n",
+    "print(evaluator.prompt)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 11,
+   "id": "9467bb42-7a31-4071-8f66-9ed2c6f06dcd",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "data": {
+      "text/plain": [
+       "{'reasoning': 'Helpfulness: Both A and B are helpful as they provide a direct answer to the question.\\nRelevance: A is relevant as it refers to the correct name of the dog from the text. B is not relevant as it provides a different name.\\nCorrectness: A is correct as it accurately states the name of the dog. B is incorrect as it provides a different name.\\nDepth: Both A and B demonstrate a similar level of depth as they both provide a straightforward answer to the question.\\n\\nGiven these evaluations, the preferred response is:\\n',\n",
+       " 'value': 'A',\n",
+       " 'score': 1}"
+      ]
+     },
+     "execution_count": 11,
+     "metadata": {},
+     "output_type": "execute_result"
+    }
+   ],
+   "source": [
+    "evaluator.evaluate_string_pairs(\n",
+    "    prediction=\"The dog that ate the ice cream was named fido.\",\n",
+    "    prediction_b=\"The dog's name is spot\",\n",
+    "    input=\"What is the name of the dog that ate the ice cream?\",\n",
+    "    reference=\"The dog's name is fido\",\n",
+    ")"
+   ]
+  }
+ ],
+ "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/docs/guides/productionization/evaluation/examples/comparisons.ipynb

@@ -0,0 +1,456 @@
+{
+ "cells": [
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "# Comparing Chain Outputs\n",
+    "[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/langchain-ai/langchain/blob/master/docs/docs/guides/evaluation/examples/comparisons.ipynb)\n",
+    "\n",
+    "Suppose you have two different prompts (or LLMs). How do you know which will generate \"better\" results?\n",
+    "\n",
+    "One automated way to predict the preferred configuration is to use a `PairwiseStringEvaluator` like the `PairwiseStringEvalChain`<a name=\"cite_ref-1\"></a>[<sup>[1]</sup>](#cite_note-1). This chain prompts an LLM to select which output is preferred, given a specific input.\n",
+    "\n",
+    "For this evaluation, we will need 3 things:\n",
+    "1. An evaluator\n",
+    "2. A dataset of inputs\n",
+    "3. 2 (or more) LLMs, Chains, or Agents to compare\n",
+    "\n",
+    "Then we will aggregate the results to determine the preferred model.\n",
+    "\n",
+    "### Step 1. Create the Evaluator\n",
+    "\n",
+    "In this example, you will use gpt-4 to select which output is preferred."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "%pip install --upgrade --quiet  langchain langchain-openai"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 1,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "from langchain.evaluation import load_evaluator\n",
+    "\n",
+    "eval_chain = load_evaluator(\"pairwise_string\")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "### Step 2. Select Dataset\n",
+    "\n",
+    "If you already have real usage data for your LLM, you can use a representative sample. More examples\n",
+    "provide more reliable results. We will use some example queries someone might have about how to use langchain here."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 2,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "name": "stderr",
+     "output_type": "stream",
+     "text": [
+      "Found cached dataset parquet (/Users/wfh/.cache/huggingface/datasets/LangChainDatasets___parquet/LangChainDatasets--langchain-howto-queries-bbb748bbee7e77aa/0.0.0/14a00e99c0d15a23649d0db8944380ac81082d4b021f398733dd84f3a6c569a7)\n"
+     ]
+    },
+    {
+     "data": {
+      "application/vnd.jupyter.widget-view+json": {
+       "model_id": "a2358d37246640ce95e0f9940194590a",
+       "version_major": 2,
+       "version_minor": 0
+      },
+      "text/plain": [
+       "  0%|          | 0/1 [00:00<?, ?it/s]"
+      ]
+     },
+     "metadata": {},
+     "output_type": "display_data"
+    }
+   ],
+   "source": [
+    "from langchain.evaluation.loading import load_dataset\n",
+    "\n",
+    "dataset = load_dataset(\"langchain-howto-queries\")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "### Step 3. Define Models to Compare\n",
+    "\n",
+    "We will be comparing two agents in this case."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 3,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "from langchain.agents import AgentType, Tool, initialize_agent\n",
+    "from langchain_community.utilities import SerpAPIWrapper\n",
+    "from langchain_openai import ChatOpenAI\n",
+    "\n",
+    "# Initialize the language model\n",
+    "# You can add your own OpenAI API key by adding openai_api_key=\"<your_api_key>\"\n",
+    "llm = ChatOpenAI(temperature=0, model=\"gpt-3.5-turbo-0613\")\n",
+    "\n",
+    "# Initialize the SerpAPIWrapper for search functionality\n",
+    "# Replace <your_api_key> in openai_api_key=\"<your_api_key>\" with your actual SerpAPI key.\n",
+    "search = SerpAPIWrapper()\n",
+    "\n",
+    "# Define a list of tools offered by the agent\n",
+    "tools = [\n",
+    "    Tool(\n",
+    "        name=\"Search\",\n",
+    "        func=search.run,\n",
+    "        coroutine=search.arun,\n",
+    "        description=\"Useful when you need to answer questions about current events. You should ask targeted questions.\",\n",
+    "    ),\n",
+    "]"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 4,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "functions_agent = initialize_agent(\n",
+    "    tools, llm, agent=AgentType.OPENAI_MULTI_FUNCTIONS, verbose=False\n",
+    ")\n",
+    "conversations_agent = initialize_agent(\n",
+    "    tools, llm, agent=AgentType.CHAT_ZERO_SHOT_REACT_DESCRIPTION, verbose=False\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "### Step 4. Generate Responses\n",
+    "\n",
+    "We will generate outputs for each of the models before evaluating them."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 5,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "data": {
+      "application/vnd.jupyter.widget-view+json": {
+       "model_id": "87277cb39a1a4726bb7cc533a24e2ea4",
+       "version_major": 2,
+       "version_minor": 0
+      },
+      "text/plain": [
+       "  0%|          | 0/20 [00:00<?, ?it/s]"
+      ]
+     },
+     "metadata": {},
+     "output_type": "display_data"
+    }
+   ],
+   "source": [
+    "import asyncio\n",
+    "\n",
+    "from tqdm.notebook import tqdm\n",
+    "\n",
+    "results = []\n",
+    "agents = [functions_agent, conversations_agent]\n",
+    "concurrency_level = 6  # How many concurrent agents to run. May need to decrease if OpenAI is rate limiting.\n",
+    "\n",
+    "# We will only run the first 20 examples of this dataset to speed things up\n",
+    "# This will lead to larger confidence intervals downstream.\n",
+    "batch = []\n",
+    "for example in tqdm(dataset[:20]):\n",
+    "    batch.extend([agent.acall(example[\"inputs\"]) for agent in agents])\n",
+    "    if len(batch) >= concurrency_level:\n",
+    "        batch_results = await asyncio.gather(*batch, return_exceptions=True)\n",
+    "        results.extend(list(zip(*[iter(batch_results)] * 2)))\n",
+    "        batch = []\n",
+    "if batch:\n",
+    "    batch_results = await asyncio.gather(*batch, return_exceptions=True)\n",
+    "    results.extend(list(zip(*[iter(batch_results)] * 2)))"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "## Step 5. Evaluate Pairs\n",
+    "\n",
+    "Now it's time to evaluate the results. For each agent response, run the evaluation chain to select which output is preferred (or return a tie).\n",
+    "\n",
+    "Randomly select the input order to reduce the likelihood that one model will be preferred just because it is presented first."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 6,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "import random\n",
+    "\n",
+    "\n",
+    "def predict_preferences(dataset, results) -> list:\n",
+    "    preferences = []\n",
+    "\n",
+    "    for example, (res_a, res_b) in zip(dataset, results):\n",
+    "        input_ = example[\"inputs\"]\n",
+    "        # Flip a coin to reduce persistent position bias\n",
+    "        if random.random() < 0.5:\n",
+    "            pred_a, pred_b = res_a, res_b\n",
+    "            a, b = \"a\", \"b\"\n",
+    "        else:\n",
+    "            pred_a, pred_b = res_b, res_a\n",
+    "            a, b = \"b\", \"a\"\n",
+    "        eval_res = eval_chain.evaluate_string_pairs(\n",
+    "            prediction=pred_a[\"output\"] if isinstance(pred_a, dict) else str(pred_a),\n",
+    "            prediction_b=pred_b[\"output\"] if isinstance(pred_b, dict) else str(pred_b),\n",
+    "            input=input_,\n",
+    "        )\n",
+    "        if eval_res[\"value\"] == \"A\":\n",
+    "            preferences.append(a)\n",
+    "        elif eval_res[\"value\"] == \"B\":\n",
+    "            preferences.append(b)\n",
+    "        else:\n",
+    "            preferences.append(None)  # No preference\n",
+    "    return preferences"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 7,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "preferences = predict_preferences(dataset, results)"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {
+    "tags": []
+   },
+   "source": [
+    "**Print out the ratio of preferences.**"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 8,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "OpenAI Functions Agent: 95.00%\n",
+      "None: 5.00%\n"
+     ]
+    }
+   ],
+   "source": [
+    "from collections import Counter\n",
+    "\n",
+    "name_map = {\n",
+    "    \"a\": \"OpenAI Functions Agent\",\n",
+    "    \"b\": \"Structured Chat Agent\",\n",
+    "}\n",
+    "counts = Counter(preferences)\n",
+    "pref_ratios = {k: v / len(preferences) for k, v in counts.items()}\n",
+    "for k, v in pref_ratios.items():\n",
+    "    print(f\"{name_map.get(k)}: {v:.2%}\")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "### Estimate Confidence Intervals\n",
+    "\n",
+    "The results seem pretty clear, but if you want to have a better sense of how confident we are, that model \"A\" (the OpenAI Functions Agent) is the preferred model, we can calculate confidence intervals. \n",
+    "\n",
+    "Below, use the Wilson score to estimate the confidence interval."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 9,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "from math import sqrt\n",
+    "\n",
+    "\n",
+    "def wilson_score_interval(\n",
+    "    preferences: list, which: str = \"a\", z: float = 1.96\n",
+    ") -> tuple:\n",
+    "    \"\"\"Estimate the confidence interval using the Wilson score.\n",
+    "\n",
+    "    See: https://en.wikipedia.org/wiki/Binomial_proportion_confidence_interval#Wilson_score_interval\n",
+    "    for more details, including when to use it and when it should not be used.\n",
+    "    \"\"\"\n",
+    "    total_preferences = preferences.count(\"a\") + preferences.count(\"b\")\n",
+    "    n_s = preferences.count(which)\n",
+    "\n",
+    "    if total_preferences == 0:\n",
+    "        return (0, 0)\n",
+    "\n",
+    "    p_hat = n_s / total_preferences\n",
+    "\n",
+    "    denominator = 1 + (z**2) / total_preferences\n",
+    "    adjustment = (z / denominator) * sqrt(\n",
+    "        p_hat * (1 - p_hat) / total_preferences\n",
+    "        + (z**2) / (4 * total_preferences * total_preferences)\n",
+    "    )\n",
+    "    center = (p_hat + (z**2) / (2 * total_preferences)) / denominator\n",
+    "    lower_bound = min(max(center - adjustment, 0.0), 1.0)\n",
+    "    upper_bound = min(max(center + adjustment, 0.0), 1.0)\n",
+    "\n",
+    "    return (lower_bound, upper_bound)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 10,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "The \"OpenAI Functions Agent\" would be preferred between 83.18% and 100.00% percent of the time (with 95% confidence).\n",
+      "The \"Structured Chat Agent\" would be preferred between 0.00% and 16.82% percent of the time (with 95% confidence).\n"
+     ]
+    }
+   ],
+   "source": [
+    "for which_, name in name_map.items():\n",
+    "    low, high = wilson_score_interval(preferences, which=which_)\n",
+    "    print(\n",
+    "        f'The \"{name}\" would be preferred between {low:.2%} and {high:.2%} percent of the time (with 95% confidence).'\n",
+    "    )"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "**Print out the p-value.**"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 11,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "The p-value is 0.00000. If the null hypothesis is true (i.e., if the selected eval chain actually has no preference between the models),\n",
+      "then there is a 0.00038% chance of observing the OpenAI Functions Agent be preferred at least 19\n",
+      "times out of 19 trials.\n"
+     ]
+    },
+    {
+     "name": "stderr",
+     "output_type": "stream",
+     "text": [
+      "/var/folders/gf/6rnp_mbx5914kx7qmmh7xzmw0000gn/T/ipykernel_15978/384907688.py:6: DeprecationWarning: 'binom_test' is deprecated in favour of 'binomtest' from version 1.7.0 and will be removed in Scipy 1.12.0.\n",
+      "  p_value = stats.binom_test(successes, n, p=0.5, alternative=\"two-sided\")\n"
+     ]
+    }
+   ],
+   "source": [
+    "from scipy import stats\n",
+    "\n",
+    "preferred_model = max(pref_ratios, key=pref_ratios.get)\n",
+    "successes = preferences.count(preferred_model)\n",
+    "n = len(preferences) - preferences.count(None)\n",
+    "p_value = stats.binom_test(successes, n, p=0.5, alternative=\"two-sided\")\n",
+    "print(\n",
+    "    f\"\"\"The p-value is {p_value:.5f}. If the null hypothesis is true (i.e., if the selected eval chain actually has no preference between the models),\n",
+    "then there is a {p_value:.5%} chance of observing the {name_map.get(preferred_model)} be preferred at least {successes}\n",
+    "times out of {n} trials.\"\"\"\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "<a name=\"cite_note-1\"></a>_1. Note: Automated evals are still an open research topic and are best used alongside other evaluation approaches. \n",
+    "LLM preferences exhibit biases, including banal ones like the order of outputs.\n",
+    "In choosing preferences, \"ground truth\" may not be taken into account, which may lead to scores that aren't grounded in utility._"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "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.11.2"
+  }
+ },
+ "nbformat": 4,
+ "nbformat_minor": 4
+}

docs/docs/guides/productionization/evaluation/examples/index.mdx

@@ -0,0 +1,12 @@
+---
+sidebar_position: 5
+---
+# Examples
+
+🚧 _Docs under construction_ 🚧
+
+Below are some examples for inspecting and checking different chains.
+
+import DocCardList from "@theme/DocCardList";
+
+<DocCardList />

docs/docs/guides/productionization/evaluation/index.mdx

@@ -0,0 +1,43 @@
+import DocCardList from "@theme/DocCardList";
+
+# Evaluation
+
+Building applications with language models involves many moving parts. One of the most critical components is ensuring that the outcomes produced by your models are reliable and useful across a broad array of inputs, and that they work well with your application's other software components. Ensuring reliability usually boils down to some combination of application design, testing & evaluation, and runtime checks. 
+
+The guides in this section review the APIs and functionality LangChain provides to help you better evaluate your applications. Evaluation and testing are both critical when thinking about deploying LLM applications, since production environments require repeatable and useful outcomes.
+
+LangChain offers various types of evaluators to help you measure performance and integrity on diverse data, and we hope to encourage the community to create and share other useful evaluators so everyone can improve. These docs will introduce the evaluator types, how to use them, and provide some examples of their use in real-world scenarios.
+These built-in evaluators all integrate smoothly with [LangSmith](/docs/langsmith), and allow you to create feedback loops that improve your application over time and prevent regressions.
+
+Each evaluator type in LangChain comes with ready-to-use implementations and an extensible API that allows for customization according to your unique requirements. Here are some of the types of evaluators we offer:
+
+- [String Evaluators](/docs/guides/productionization/evaluation/string/): These evaluators assess the predicted string for a given input, usually comparing it against a reference string.
+- [Trajectory Evaluators](/docs/guides/productionization/evaluation/trajectory/): These are used to evaluate the entire trajectory of agent actions.
+- [Comparison Evaluators](/docs/guides/productionization/evaluation/comparison/): These evaluators are designed to compare predictions from two runs on a common input.
+
+These evaluators can be used across various scenarios and can be applied to different chain and LLM implementations in the LangChain library.
+
+We also are working to share guides and cookbooks that demonstrate how to use these evaluators in real-world scenarios, such as:
+
+- [Chain Comparisons](/docs/guides/productionization/evaluation/examples/comparisons): This example uses a comparison evaluator to predict the preferred output. It reviews ways to measure confidence intervals to select statistically significant differences in aggregate preference scores across different models or prompts.
+
+
+## LangSmith Evaluation
+
+LangSmith provides an integrated evaluation and tracing framework that allows you to check for regressions, compare systems, and easily identify and fix any sources of errors and performance issues. Check out the docs on [LangSmith Evaluation](https://docs.smith.langchain.com/evaluation) and additional [cookbooks](https://docs.smith.langchain.com/cookbook) for more detailed information on evaluating your applications.
+
+## LangChain benchmarks
+
+Your application quality is a function both of the LLM you choose and the prompting and data retrieval strategies you employ to provide model contexet. We have published a number of benchmark tasks within the [LangChain Benchmarks](https://langchain-ai.github.io/langchain-benchmarks/) package to grade different LLM systems on tasks such as:
+
+- Agent tool use
+- Retrieval-augmented question-answering
+- Structured Extraction 
+
+Check out the docs for examples and leaderboard information.
+
+## Reference Docs
+
+For detailed information on the available evaluators, including how to instantiate, configure, and customize them, check out the [reference documentation](https://api.python.langchain.com/en/latest/langchain_api_reference.html#module-langchain.evaluation) directly.
+
+<DocCardList />