core[minor]: update @tool inferred schema and description

.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/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

@@ -537,9 +537,7 @@ if __name__ == "__main__":
         "nfcampos",
         "efriis",
         "eyurtsev",
-        "rlancemartin",
-        "ccurme",
-        "vbarda",
+        "rlancemartin"
     }
     hidden_logins = {
         "dev2049",

.github/scripts/check_diff.py

@@ -1,11 +1,7 @@
 import json
 import sys
 import os
-from typing import Dict, List, Set
-
-import tomllib
-from collections import defaultdict
-import glob
+from typing import Dict
 
 LANGCHAIN_DIRS = [
     "libs/core",
@@ -15,34 +11,6 @@ LANGCHAIN_DIRS = [
     "libs/experimental",
 ]
 
-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)
-
-
 if __name__ == "__main__":
     files = sys.argv[1:]
 
@@ -113,16 +81,14 @@ if __name__ == "__main__":
                 docs_edited = True
             dirs_to_run["lint"].add(".")
 
-    dependents = dependents_graph()
-
     outputs = {
-        "dirs-to-lint": add_dependents(
-            dirs_to_run["lint"] | dirs_to_run["test"] | dirs_to_run["extended-test"], dependents
+        "dirs-to-lint": list(
+            dirs_to_run["lint"] | dirs_to_run["test"] | dirs_to_run["extended-test"]
         ),
-        "dirs-to-test": add_dependents(dirs_to_run["test"] | dirs_to_run["extended-test"], dependents),
+        "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 "",
     }
     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

@@ -76,4 +76,4 @@ if __name__ == "__main__":
 
     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

@@ -24,7 +24,6 @@ jobs:
           - "3.9"
           - "3.10"
           - "3.11"
-          - "3.12"
     name: "poetry run pytest -m compile tests/integration_tests #${{ matrix.python-version }}"
     steps:
       - uses: actions/checkout@v4

.github/workflows/_dependencies.yml

@@ -28,7 +28,6 @@ jobs:
           - "3.9"
           - "3.10"
           - "3.11"
-          - "3.12"
     name: dependency checks ${{ matrix.python-version }}
     steps:
       - uses: actions/checkout@v4

.github/workflows/_integration_test.yml

@@ -12,6 +12,7 @@ env:
 
 jobs:
   build:
+    environment: Scheduled testing
     defaults:
       run:
         working-directory: ${{ inputs.working-directory }}
@@ -52,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

@@ -34,7 +34,7 @@ jobs:
         # so linting on fewer versions makes CI faster.
         python-version:
           - "3.8"
-          - "3.12"
+          - "3.11"
     steps:
       - uses: actions/checkout@v4
 

.github/workflows/_release.yml

@@ -72,67 +72,10 @@ 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 "# Release $TAG"
-            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
     with:
@@ -143,7 +86,6 @@ jobs:
   pre-release-checks:
     needs:
       - build
-      - release-notes
       - test-pypi-publish
     runs-on: ubuntu-latest
     steps:
@@ -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 }}
 
@@ -280,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
@@ -329,7 +269,6 @@ jobs:
   mark-release:
     needs:
       - build
-      - release-notes
       - test-pypi-publish
       - pre-release-checks
       - publish
@@ -366,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

@@ -28,7 +28,6 @@ jobs:
           - "3.9"
           - "3.10"
           - "3.11"
-          - "3.12"
     name: "make test #${{ matrix.python-version }}"
     steps:
       - uses: actions/checkout@v4

.github/workflows/_test_doc_imports.yml

@@ -12,7 +12,7 @@ jobs:
     strategy:
       matrix:
         python-version:
-          - "3.12"
+          - "3.11"
     name: "check doc imports #${{ matrix.python-version }}"
     steps:
       - uses: actions/checkout@v4

.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,7 +26,7 @@ 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
@@ -104,7 +104,6 @@ jobs:
           - "3.9"
           - "3.10"
           - "3.11"
-          - "3.12"
     runs-on: ubuntu-latest
     defaults:
       run:
@@ -124,9 +123,7 @@ jobs:
         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,31 +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
-      - 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/scheduled_test.yml

@@ -10,8 +10,6 @@ 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
@@ -27,45 +25,16 @@ jobs:
           - "libs/partners/groq"
           - "libs/partners/mistralai"
           - "libs/partners/together"
-          - "libs/partners/cohere"
-          - "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-cohere
-          path: langchain-cohere
-      - 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 \
-            langchain/libs/partners/cohere
-          mv langchain-google/libs/genai langchain/libs/partners/google-genai
-          mv langchain-google/libs/vertexai langchain/libs/partners/google-vertexai
-          mv langchain-cohere/libs/cohere langchain/libs/partners/cohere
-          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'
@@ -74,20 +43,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 }}
@@ -102,25 +67,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/cohere \
-            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
@@ -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,17 +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)
-[![](https://dcbadge.vercel.app/api/server/6adMQxSpJS?compact=true&style=flat)](https://discord.gg/6adMQxSpJS)
+[![Downloads](https://static.pepy.tech/badge/langchain-core/month)](https://pepy.tech/project/langchain-core)
+[![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).
 
@@ -38,22 +38,22 @@ conda install langchain -c conda-forge
 
 For these applications, LangChain simplifies the entire application lifecycle:
 
-- **Open-source libraries**: Build your applications using LangChain's [modular building blocks](https://python.langchain.com/v0.2/docs/concepts/#langchain-expression-language-lcel) and [components](https://python.langchain.com/v0.2/docs/concepts/#components). Integrate with hundreds of [third-party providers](https://python.langchain.com/v0.2/docs/integrations/platforms/).
-- **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 any chain into a REST API with [LangServe](https://python.langchain.com/v0.2/docs/langserve/).
+- **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.
+- **[`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:
-- **[LangServe](https://python.langchain.com/v0.2/docs/langserve/)**: A library for deploying LangChain chains as REST APIs.
+- **[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.svg "LangChain Architecture Overview")
 
@@ -61,20 +61,20 @@ For these applications, LangChain simplifies the entire application lifecycle:
 
 **❓ 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,50 +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 the [LangGraph](https://github.com/langchain-ai/langgraph) extension 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/): Tracing and evaluating your language model applications and intelligent agents to help you move from prototype to production.
-- [🦜🕸️ LangGraph](https://langchain-ai.github.io/langgraph/): Creating stateful, multi-actor applications with LLMs, built on top of (and intended to be used with) LangChain primitives.
+- [🦜🛠️ 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/v0.2/docs/templates/): Example applications hosted with LangServe.
+  - [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\""

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 find ../libs/partners -mindepth 1 -maxdepth 1 -type d -exec test -e "{}/pyproject.toml" \; -print | grep -vE "airbyte|ibm|ai21" | tr '\n' ' ')
 
 PORT ?= 3001
 
@@ -35,16 +35,19 @@ 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/
+
 copy-infra:
 	mkdir -p $(OUTPUT_NEW_DIR)
 	cp -r src $(OUTPUT_NEW_DIR)
@@ -66,9 +69,9 @@ md-sync:
 generate-references:
 	$(PYTHON) scripts/generate_api_reference_links.py --docs_dir $(OUTPUT_NEW_DOCS_DIR)
 
-build: install-py-deps generate-files copy-infra render md-sync
+build: install-py-deps generate-files copy-infra render md-sync generate-references
 
-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

docs/api_reference/create_api_rst.py

@@ -128,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)
@@ -187,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
 
@@ -364,7 +364,7 @@ def main(dirs: Optional[list] = None) -> None:
         dirs += [
             dir_
             for dir_ in os.listdir(ROOT_DIR / "libs" / "partners")
-            if os.path.isdir(ROOT_DIR / "libs" / "partners" / dir_)
+            if os.path.isdir(dir_)
             and "pyproject.toml" in os.listdir(ROOT_DIR / "libs" / "partners" / dir_)
         ]
     for dir_ in dirs:

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/how_to#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/concepts.mdx

@@ -11,7 +11,7 @@ LangChain as a framework consists of a number of packages.
 
 ### `langchain-core`
 This package contains base abstractions of different components and ways to compose them together.
-The interfaces for core components like LLMs, vector stores, retrievers and more are defined here.
+The interfaces for core components like LLMs, vectorstores, retrievers and more are defined here.
 No third party integrations are defined here.
 The dependencies are kept purposefully very lightweight.
 
@@ -30,21 +30,21 @@ All chains, agents, and retrieval strategies here are NOT specific to any one in
 
 This package contains third party integrations that are maintained by the LangChain community.
 Key partner packages are separated out (see below).
-This contains all integrations for various components (LLMs, vector stores, retrievers).
+This contains all integrations for various components (LLMs, vectorstores, retrievers).
 All dependencies in this package are optional to keep the package as lightweight as possible.
 
-### [`langgraph`](https://langchain-ai.github.io/langgraph)
+### [`langgraph`](/docs/langgraph)
 
 `langgraph` is an extension of `langchain` aimed at
 building robust and stateful multi-actor applications with LLMs by modeling steps as edges and nodes in a graph.
 
-LangGraph exposes high level interfaces for creating common types of agents, as well as a low-level API for composing custom flows.
+LangGraph exposes high level interfaces for creating common types of agents, as well as a low-level API for constructing more contr
 
 ### [`langserve`](/docs/langserve)
 
 A package to deploy LangChain chains as REST APIs. Makes it easy to get a production ready API up and running.
 
-### [LangSmith](https://docs.smith.langchain.com)
+### [LangSmith](/docs/langsmith)
 
 A developer platform that lets you debug, test, evaluate, and monitor LLM applications.
 
@@ -58,7 +58,6 @@ A developer platform that lets you debug, test, evaluate, and monitor LLM applic
 />
 
 ## LangChain Expression Language (LCEL)
-<span data-heading-keywords="lcel"></span>
 
 LangChain Expression Language, or LCEL, is a declarative way to chain LangChain components.
 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:
@@ -67,7 +66,7 @@ LCEL was designed from day 1 to **support putting prototypes in production, with
 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**
-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.
+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/langsmith) 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**
 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.
@@ -81,24 +80,23 @@ For more complex chains it’s often very useful to access the results of interm
 **Input and output schemas**
 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**](https://docs.smith.langchain.com)
+[**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](https://docs.smith.langchain.com/) for maximum observability and debuggability.
+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).
 
 ### Runnable interface
-<span data-heading-keywords="invoke"></span>
 
 To make it as easy as possible to create custom chains, we've implemented a ["Runnable"](https://api.python.langchain.com/en/stable/runnables/langchain_core.runnables.base.Runnable.html#langchain_core.runnables.base.Runnable) protocol. Many LangChain components implement the `Runnable` protocol, including chat models, LLMs, output parsers, retrievers, prompt templates, and more. There are also several useful primitives for working with runnables, which you can read about below.
 
 This is a standard interface, which makes it easy to define custom chains as well as invoke them in a standard way.
 The standard interface includes:
 
-- `stream`: stream back chunks of the response
-- `invoke`: call the chain on an input
-- `batch`: call the chain on a list of inputs
+- [`stream`](#stream): stream back chunks of the response
+- [`invoke`](#invoke): call the chain on an input
+- [`batch`](#batch): call the chain on a list of inputs
 
 These also have corresponding async methods that should be used with [asyncio](https://docs.python.org/3/library/asyncio.html) `await` syntax for concurrency:
 
@@ -130,54 +128,30 @@ LangChain provides standard, extendable interfaces and external integrations for
 Some components LangChain implements, some components we rely on third-party integrations for, and others are a mix.
 
 ### Chat models
-<span data-heading-keywords="chat model,chat models"></span>
-
 Language models that use a sequence of messages as inputs and return chat messages as outputs (as opposed to using plain text).
-These are traditionally newer models (older models are generally `LLMs`, see below).
+These are traditionally newer models (older models are generally `LLMs`, see above).
 Chat models support the assignment of distinct roles to conversation messages, helping to distinguish messages from the AI, users, and instructions such as system messages.
 
-Although the underlying models are messages in, message out, the LangChain wrappers also allow these models to take a string as input. This means you can easily use chat models in place of LLMs.
+Although the underlying models are messages in, message out, the LangChain wrappers also allow these models to take a string as input.
+This makes them interchangeable with LLMs (and simpler to use).
+When a string is passed in as input, it will be converted to a HumanMessage under the hood before being passed to the underlying model.
 
-When a string is passed in as input, it is converted to a `HumanMessage` and then passed to the underlying model.
-
-LangChain does not host any Chat Models, rather we rely on third party integrations.
+LangChain does not provide any ChatModels, rather we rely on third party integrations.
 
 We have some standardized parameters when constructing ChatModels:
 - `model`: the name of the model
 
 ChatModels also accept other parameters that are specific to that integration.
 
-:::important
-**Tool Calling** Some chat models have been fine-tuned for tool calling and provide a dedicated API for tool calling.
-Generally, such models are better at tool calling than non-fine-tuned models, and are recommended for use cases that require tool calling.
-Please see the [tool calling section](/docs/concepts/#functiontool-calling) for more information.
-:::
-
-For specifics on how to use chat models, see the [relevant how-to guides here](/docs/how_to/#chat-models).
-
-#### Multimodality
-
-Some chat models are multimodal, accepting images, audio and even video as inputs. These are still less common, meaning model providers haven't standardized on the "best" way to define the API. Multimodal **outputs** are even less common. As such, we've kept our multimodal abstractions fairly light weight and plan to further solidify the multimodal APIs and interaction patterns as the field matures.
-
-In LangChain, most chat models that support multimodal inputs also accept those values in OpenAI's content blocks format. So far this is restricted to image inputs. For models like Gemini which support video and other bytes input, the APIs also support the native, model-specific representations.
-
-For specifics on how to use multimodal models, see the [relevant how-to guides here](/docs/how_to/#multimodal).
-
-For a full list of LangChain model providers with multimodal models, [check out this table](/docs/integrations/chat/#advanced-features).
-
 ### LLMs
-<span data-heading-keywords="llm,llms"></span>
-
 Language models that takes a string as input and returns a string.
-These are traditionally older models (newer models generally are [Chat Models](/docs/concepts/#chat-models), see below).
+These are traditionally older models (newer models generally are `ChatModels`, see below).
 
 Although the underlying models are string in, string out, the LangChain wrappers also allow these models to take messages as input.
-This gives them the same interface as [Chat Models](/docs/concepts/#chat-models).
+This makes them interchangeable with ChatModels.
 When messages are passed in as input, they will be formatted into a string under the hood before being passed to the underlying model.
 
-LangChain does not host any LLMs, rather we rely on third party integrations.
-
-For specifics on how to use LLMs, see the [relevant how-to guides here](/docs/how_to/#llms).
+LangChain does not provide any LLMs, rather we rely on third party integrations.
 
 ### Messages
 
@@ -192,7 +166,7 @@ The `content` property describes the content of the message.
 This can be a few different things:
 
 - A string (most models deal this type of content)
-- A List of dictionaries (this is used for multimodal input, where the dictionary contains information about that input type and that input location)
+- A List of dictionaries (this is used for multi-modal input, where the dictionary contains information about that input type and that input location)
 
 #### HumanMessage
 
@@ -232,8 +206,6 @@ This represents the result of a tool call. This is distinct from a FunctionMessa
 
 
 ### Prompt templates
-<span data-heading-keywords="prompt,prompttemplate,chatprompttemplate"></span>
-
 Prompt templates help to translate user input and parameters into instructions for a language model.
 This can be used to guide a model's response, helping it understand the context and generate relevant and coherent language-based output.
 
@@ -242,7 +214,7 @@ Prompt Templates take as input a dictionary, where each key represents a variabl
 Prompt Templates output a PromptValue. This PromptValue can be passed to an LLM or a ChatModel, and can also be cast to a string or a list of messages.
 The reason this PromptValue exists is to make it easy to switch between strings and messages.
 
-There are a few different types of prompt templates:
+There are a few different types of prompt templates
 
 #### String PromptTemplates
 
@@ -267,7 +239,7 @@ from langchain_core.prompts import ChatPromptTemplate
 
 prompt_template = ChatPromptTemplate.from_messages([
     ("system", "You are a helpful assistant"),
-    ("user", "Tell me a joke about {topic}")
+    ("user", "Tell me a joke about {topic}"
 ])
 
 prompt_template.invoke({"topic": "cats"})
@@ -278,7 +250,6 @@ The first is a system message, that has no variables to format.
 The second is a HumanMessage, and will be formatted by the `topic` variable the user passes in.
 
 #### MessagesPlaceholder
-<span data-heading-keywords="messagesplaceholder"></span>
 
 This prompt template is responsible for adding a list of messages in a particular place.
 In the above ChatPromptTemplate, we saw how we could format two messages, each one a string.
@@ -310,18 +281,14 @@ prompt_template = ChatPromptTemplate.from_messages([
 ])
 ```
 
-For specifics on how to use prompt templates, see the [relevant how-to guides here](/docs/how_to/#prompt-templates).
-
 ### Example selectors
 One common prompting technique for achieving better performance is to include examples as part of the prompt.
 This gives the language model concrete examples of how it should behave.
 Sometimes these examples are hardcoded into the prompt, but for more advanced situations it may be nice to dynamically select them.
 Example Selectors are classes responsible for selecting and then formatting examples into prompts.
 
-For specifics on how to use example selectors, see the [relevant how-to guides here](/docs/how_to/#example-selectors).
 
 ### Output parsers
-<span data-heading-keywords="output parser"></span>
 
 :::note
 
@@ -365,19 +332,16 @@ LangChain has lots of different types of output parsers. This is a list of outpu
 | [Datetime](https://api.python.langchain.com/en/latest/output_parsers/langchain.output_parsers.datetime.DatetimeOutputParser.html#langchain.output_parsers.datetime.DatetimeOutputParser)        |                    | ✅                             |           | `str` \| `Message`                 | `datetime.datetime`  | Parses response into a datetime string.                                                                                                                                                                                                                  |
 | [Structured](https://api.python.langchain.com/en/latest/output_parsers/langchain.output_parsers.structured.StructuredOutputParser.html#langchain.output_parsers.structured.StructuredOutputParser)      |                    | ✅                             |           | `str` \| `Message`                 | `Dict[str, str]`     | An output parser that returns structured information. It is less powerful than other output parsers since it only allows for fields to be strings. This can be useful when you are working with smaller LLMs.                                            |
 
-For specifics on how to use output parsers, see the [relevant how-to guides here](/docs/how_to/#output-parsers).
-
 ### Chat history
 Most LLM applications have a conversational interface.
 An essential component of a conversation is being able to refer to information introduced earlier in the conversation.
 At bare minimum, a conversational system should be able to access some window of past messages directly.
 
 The concept of `ChatHistory` refers to a class in LangChain which can be used to wrap an arbitrary chain.
-This `ChatHistory` will keep track of inputs and outputs of the underlying chain, and append them as messages to a message database.
+This `ChatHistory` will keep track of inputs and outputs of the underlying chain, and append them as messages to a message database
 Future interactions will then load those messages and pass them into the chain as part of the input.
 
 ### Documents
-<span data-heading-keywords="document,documents"></span>
 
 A Document object in LangChain contains information about some data. It has two attributes:
 
@@ -385,7 +349,6 @@ A Document object in LangChain contains information about some data. It has two
 - `metadata: dict`: Arbitrary metadata associated with this document. Can track the document id, file name, etc.
 
 ### Document loaders
-<span data-heading-keywords="document loader,document loaders"></span>
 
 These classes load Document objects. LangChain has hundreds of integrations with various data sources to load data from: Slack, Notion, Google Drive, etc.
 
@@ -401,8 +364,6 @@ loader = CSVLoader(
 data = loader.load()
 ```
 
-For specifics on how to use document loaders, see the [relevant how-to guides here](/docs/how_to/#document-loaders).
-
 ### Text splitters
 
 Once you've loaded documents, you'll often want to transform them to better suit your application. The simplest example is you may want to split a long document into smaller chunks that can fit into your model's context window. LangChain has a number of built-in document transformers that make it easy to split, combine, filter, and otherwise manipulate documents.
@@ -420,34 +381,18 @@ That means there are two different axes along which you can customize your text
 1. How the text is split
 2. How the chunk size is measured
 
-For specifics on how to use text splitters, see the [relevant how-to guides here](/docs/how_to/#text-splitters).
-
 ### Embedding models
-<span data-heading-keywords="embedding,embeddings"></span>
+The Embeddings class is a class designed for interfacing with text embedding models. There are lots of embedding model providers (OpenAI, Cohere, Hugging Face, etc) - this class is designed to provide a standard interface for all of them.
 
-Embedding models create a vector representation of a piece of text. You can think of a vector as an array of numbers that captures the semantic meaning of the text.
-By representing the text in this way, you can perform mathematical operations that allow you to do things like search for other pieces of text that are most similar in meaning.
-These natural language search capabilities underpin many types of [context retrieval](/docs/concepts/#retrieval),
-where we provide an LLM with the relevant data it needs to effectively respond to a query.
-
-![](/img/embeddings.png)
-
-The `Embeddings` class is a class designed for interfacing with text embedding models. There are many different embedding model providers (OpenAI, Cohere, Hugging Face, etc) and local models, and this class is designed to provide a standard interface for all of them.
+Embeddings create a vector representation of a piece of text. This is useful because it means we can think about text in the vector space, and do things like semantic search where we look for pieces of text that are most similar in the vector space.
 
 The base Embeddings class in LangChain provides two methods: one for embedding documents and one for embedding a query. The former takes as input multiple texts, while the latter takes a single text. The reason for having these as two separate methods is that some embedding providers have different embedding methods for documents (to be searched over) vs queries (the search query itself).
 
-For specifics on how to use embedding models, see the [relevant how-to guides here](/docs/how_to/#embedding-models).
-
 ### Vector stores
-<span data-heading-keywords="vector,vectorstore,vectorstores,vector store,vector stores"></span>
-
 One of the most common ways to store and search over unstructured data is to embed it and store the resulting embedding vectors,
 and then at query time to embed the unstructured query and retrieve the embedding vectors that are 'most similar' to the embedded query.
 A vector store takes care of storing embedded data and performing vector search for you.
 
-Most vector stores can also store metadata about embedded vectors and support filtering on that metadata before
-similarity search, allowing you more control over returned documents.
-
 Vector stores can be converted to the retriever interface by doing:
 
 ```python
@@ -455,48 +400,31 @@ vectorstore = MyVectorStore()
 retriever = vectorstore.as_retriever()
 ```
 
-For specifics on how to use vector stores, see the [relevant how-to guides here](/docs/how_to/#vector-stores).
-
 ### Retrievers
-<span data-heading-keywords="retriever,retrievers"></span>
-
 A retriever is an interface that returns documents given an unstructured query.
 It is more general than a vector store.
 A retriever does not need to be able to store documents, only to return (or retrieve) them.
-Retrievers can be created from vector stores, but are also broad enough to include [Wikipedia search](/docs/integrations/retrievers/wikipedia/) and [Amazon Kendra](/docs/integrations/retrievers/amazon_kendra_retriever/).
+Retrievers can be created from vectorstores, but are also broad enough to include [Wikipedia search](/docs/integrations/retrievers/wikipedia/) and [Amazon Kendra](/docs/integrations/retrievers/amazon_kendra_retriever/).
 
 Retrievers accept a string query as input and return a list of Document's as output.
 
-For specifics on how to use retrievers, see the [relevant how-to guides here](/docs/how_to/#retrievers).
-
 ### Tools
-<span data-heading-keywords="tool,tools"></span>
-
-Tools are interfaces that an agent, a chain, or a chat model / LLM can use to interact with the world.
-
-A tool consists of the following components:
+Tools are interfaces that an agent, chain, or LLM can use to interact with the world.
+They combine a few things:
 
 1. The name of the tool
-2. A description of what the tool does
+2. A description of what the tool is
 3. JSON schema of what the inputs to the tool are
 4. The function to call
-5. Whether the result of a tool should be returned directly to the user (only relevant for agents)
+5. Whether the result of a tool should be returned directly to the user
 
-The name, description and JSON schema are provided as context
-to the LLM, allowing the LLM to determine how to use the tool
-appropriately.
+It is useful to have all this information because this information can be used to build action-taking systems! The name, description, and JSON schema can be used to prompt the LLM so it knows how to specify what action to take, and then the function to call is equivalent to taking that action.
 
-Given a list of available tools and a prompt, an LLM can request
-that one or more tools be invoked with appropriate arguments.
+The simpler the input to a tool is, the easier it is for an LLM to be able to use it.
+Many agents will only work with tools that have a single string input.
 
-Generally, when designing tools to be used by a chat model or LLM, it is important to keep in mind the following:
+Importantly, the name, description, and JSON schema (if used) are all used in the prompt. Therefore, it is really important that they are clear and describe exactly how the tool should be used. You may need to change the default name, description, or JSON schema if the LLM is not understanding how to use the tool.
 
-- Chat models that have been fine-tuned for tool calling will be better at tool calling than non-fine-tuned models.
-- Non fine-tuned models may not be able to use tools at all, especially if the tools are complex or require multiple tool calls.
-- Models will perform better if the tools have well-chosen names, descriptions, and JSON schemas.
-- Simpler tools are generally easier for models to use than more complex tools.
-
-For specifics on how to use tools, see the [relevant how-to guides here](/docs/how_to/#tools).
 
 ### Toolkits
 
@@ -517,7 +445,7 @@ tools = toolkit.get_tools()
 
 By themselves, language models can't take actions - they just output text.
 A big use case for LangChain is creating **agents**.
-Agents are systems that use an LLM as a reasoning engine to determine which actions to take and what the inputs to those actions should be.
+Agents are systems that use an LLM as a reasoning enginer to determine which actions to take and what the inputs to those actions should be.
 The results of those actions can then be fed back into the agent and it determine whether more actions are needed, or whether it is okay to finish.
 
 [LangGraph](https://github.com/langchain-ai/langgraph) is an extension of LangChain specifically aimed at creating highly controllable and customizable agents.
@@ -530,296 +458,17 @@ In order to solve that we built LangGraph to be this flexible, highly-controllab
 
 If you are still using AgentExecutor, do not fear: we still have a guide on [how to use AgentExecutor](/docs/how_to/agent_executor).
 It is recommended, however, that you start to transition to LangGraph.
-In order to assist in this we have put together a [transition guide on how to do so](/docs/how_to/migrate_agent).
-
-### Callbacks
-
-LangChain provides a callbacks system that allows you to hook into the various stages of your LLM application. This is useful for logging, monitoring, streaming, and other tasks.
-
-You can subscribe to these events by using the `callbacks` argument available throughout the API. This argument is list of handler objects, which are expected to implement one or more of the methods described below in more detail.
-
-#### Callback Events
-
-| Event            | Event Trigger                               | Associated Method     |
-|------------------|---------------------------------------------|-----------------------|
-| Chat model start | When a chat model starts                    | `on_chat_model_start` |
-| LLM start        | When a llm starts                           | `on_llm_start`        |
-| LLM new token    | When an llm OR chat model emits a new token | `on_llm_new_token`    |
-| LLM ends         | When an llm OR chat model ends              | `on_llm_end`          |
-| LLM errors       | When an llm OR chat model errors            | `on_llm_error`        |
-| Chain start      | When a chain starts running                 | `on_chain_start`      |
-| Chain end        | When a chain ends                           | `on_chain_end`        |
-| Chain error      | When a chain errors                         | `on_chain_error`      |
-| Tool start       | When a tool starts running                  | `on_tool_start`       |
-| Tool end         | When a tool ends                            | `on_tool_end`         |
-| Tool error       | When a tool errors                          | `on_tool_error`       |
-| Agent action     | When an agent takes an action               | `on_agent_action`     |
-| Agent finish     | When an agent ends                          | `on_agent_finish`     |
-| Retriever start  | When a retriever starts                     | `on_retriever_start`  |
-| Retriever end    | When a retriever ends                       | `on_retriever_end`    |
-| Retriever error  | When a retriever errors                     | `on_retriever_error`  |
-| Text             | When arbitrary text is run                  | `on_text`             |
-| Retry            | When a retry event is run                   | `on_retry`            |
-
-#### Callback handlers
-
-Callback handlers can either be `sync` or `async`:
-
-* Sync callback handlers implement the [BaseCallbackHandler](https://api.python.langchain.com/en/latest/callbacks/langchain_core.callbacks.base.BaseCallbackHandler.html) interface.
-* Async callback handlers implement the [AsyncCallbackHandler](https://api.python.langchain.com/en/latest/callbacks/langchain_core.callbacks.base.AsyncCallbackHandler.html) interface.
-
-During run-time LangChain configures an appropriate callback manager (e.g., [CallbackManager](https://api.python.langchain.com/en/latest/callbacks/langchain_core.callbacks.manager.CallbackManager.html) or [AsyncCallbackManager](https://api.python.langchain.com/en/latest/callbacks/langchain_core.callbacks.manager.AsyncCallbackManager.html) which will be responsible for calling the appropriate method on each "registered" callback handler when the event is triggered.
-
-#### Passing callbacks
-
-The `callbacks` property is available on most objects throughout the API (Models, Tools, Agents, etc.) in two different places:
-
-The callbacks are available on most objects throughout the API (Models, Tools, Agents, etc.) in two different places:
-
-- **Request time callbacks**: Passed at the time of the request in addition to the input data.
-    Available on all standard `Runnable` objects. These callbacks are INHERITED by all children
-    of the object they are defined on. For example, `chain.invoke({"number": 25}, {"callbacks": [handler]})`.
-- **Constructor callbacks**: `chain = TheNameOfSomeChain(callbacks=[handler])`. These callbacks
-    are passed as arguments to the constructor of the object. The callbacks are scoped
-    only to the object they are defined on, and are **not** inherited by any children of the object.
-
-:::warning
-Constructor callbacks are scoped only to the object they are defined on. They are **not** inherited by children
-of the object.
-:::
-
-If you're creating a custom chain or runnable, you need to remember to propagate request time
-callbacks to any child objects.
-
-:::important Async in Python<=3.10
-
-Any `RunnableLambda`, a `RunnableGenerator`, or `Tool` that invokes other runnables
-and is running async in python<=3.10, will have to propagate callbacks to child
-objects manually. This is because LangChain cannot automatically propagate
-callbacks to child objects in this case.
-
-This is a common reason why you may fail to see events being emitted from custom
-runnables or tools.
-:::
-
-For specifics on how to use callbacks, see the [relevant how-to guides here](/docs/how_to/#callbacks).
+In order to assist in this we have put together a [transition guide on how to do so](/docs/how_to/migrate_agent)
 
 ## Techniques
 
-### Streaming
-<span data-heading-keywords="stream,streaming"></span>
-
-Individual LLM calls often run for much longer than traditional resource requests.
-This compounds when you build more complex chains or agents that require multiple reasoning steps.
-
-Fortunately, LLMs generate output iteratively, which means it's possible to show sensible intermediate results
-before the final response is ready. Consuming output as soon as it becomes available has therefore become a vital part of the UX
-around building apps with LLMs to help alleviate latency issues, and LangChain aims to have first-class support for streaming.
-
-Below, we'll discuss some concepts and considerations around streaming in LangChain.
-
-#### `.stream()` and `.astream()`
-
-Most modules in LangChain include the `.stream()` method (and the equivalent `.astream()` method for [async](https://docs.python.org/3/library/asyncio.html) environments) as an ergonomic streaming interface.
-`.stream()` returns an iterator, which you can consume with a simple `for` loop. Here's an example with a chat model:
-
-```python
-from langchain_anthropic import ChatAnthropic
-
-model = ChatAnthropic(model="claude-3-sonnet-20240229")
-
-for chunk in model.stream("what color is the sky?"):
-    print(chunk.content, end="|", flush=True)
-```
-
-For models (or other components) that don't support streaming natively, this iterator would just yield a single chunk, but
-you could still use the same general pattern when calling them. Using `.stream()` will also automatically call the model in streaming mode
-without the need to provide additional config.
-
-The type of each outputted chunk depends on the type of component - for example, chat models yield [`AIMessageChunks`](https://api.python.langchain.com/en/latest/messages/langchain_core.messages.ai.AIMessageChunk.html).
-Because this method is part of [LangChain Expression Language](/docs/concepts/#langchain-expression-language-lcel),
-you can handle formatting differences from different outputs using an [output parser](/docs/concepts/#output-parsers) to transform
-each yielded chunk.
-
-You can check out [this guide](/docs/how_to/streaming/#using-stream) for more detail on how to use `.stream()`.
-
-#### `.astream_events()`
-<span data-heading-keywords="astream_events,stream_events,stream events"></span>
-
-While the `.stream()` method is intuitive, it can only return the final generated value of your chain. This is fine for single LLM calls,
-but as you build more complex chains of several LLM calls together, you may want to use the intermediate values of
-the chain alongside the final output - for example, returning sources alongside the final generation when building a chat
-over documents app.
-
-There are ways to do this [using callbacks](/docs/concepts/#callbacks-1), or by constructing your chain in such a way that it passes intermediate
-values to the end with something like chained [`.assign()`](/docs/how_to/passthrough/) calls, but LangChain also includes an
-`.astream_events()` method that combines the flexibility of callbacks with the ergonomics of `.stream()`. When called, it returns an iterator
-which yields [various types of events](/docs/how_to/streaming/#event-reference) that you can filter and process according
-to the needs of your project.
-
-Here's one small example that prints just events containing streamed chat model output:
-
-```python
-from langchain_core.output_parsers import StrOutputParser
-from langchain_core.prompts import ChatPromptTemplate
-from langchain_anthropic import ChatAnthropic
-
-model = ChatAnthropic(model="claude-3-sonnet-20240229")
-
-prompt = ChatPromptTemplate.from_template("tell me a joke about {topic}")
-parser = StrOutputParser()
-chain = prompt | model | parser
-
-async for event in chain.astream_events({"topic": "parrot"}, version="v2"):
-    kind = event["event"]
-    if kind == "on_chat_model_stream":
-        print(event, end="|", flush=True)
-```
-
-You can roughly think of it as an iterator over callback events (though the format differs) - and you can use it on almost all LangChain components!
-
-See [this guide](/docs/how_to/streaming/#using-stream-events) for more detailed information on how to use `.astream_events()`,
-including a table listing available events.
-
-#### Callbacks
-
-The lowest level way to stream outputs from LLMs in LangChain is via the [callbacks](/docs/concepts/#callbacks) system. You can pass a
-callback handler that handles the [`on_llm_new_token`](https://api.python.langchain.com/en/latest/callbacks/langchain.callbacks.streaming_aiter.AsyncIteratorCallbackHandler.html#langchain.callbacks.streaming_aiter.AsyncIteratorCallbackHandler.on_llm_new_token) event into LangChain components. When that component is invoked, any
-[LLM](/docs/concepts/#llms) or [chat model](/docs/concepts/#chat-models) contained in the component calls
-the callback with the generated token. Within the callback, you could pipe the tokens into some other destination, e.g. a HTTP response.
-You can also handle the [`on_llm_end`](https://api.python.langchain.com/en/latest/callbacks/langchain.callbacks.streaming_aiter.AsyncIteratorCallbackHandler.html#langchain.callbacks.streaming_aiter.AsyncIteratorCallbackHandler.on_llm_end) event to perform any necessary cleanup.
-
-You can see [this how-to section](/docs/how_to/#callbacks) for more specifics on using callbacks.
-
-Callbacks were the first technique for streaming introduced in LangChain. While powerful and generalizable,
-they can be unwieldy for developers. For example:
-
-- You need to explicitly initialize and manage some aggregator or other stream to collect results.
-- The execution order isn't explicitly guaranteed, and you could theoretically have a callback run after the `.invoke()` method finishes.
-- Providers would often make you pass an additional parameter to stream outputs instead of returning them all at once.
-- You would often ignore the result of the actual model call in favor of callback results.
-
-#### Tokens
-
-The unit that most model providers use to measure input and output is via a unit called a **token**.
-Tokens are the basic units that language models read and generate when processing or producing text.
-The exact definition of a token can vary depending on the specific way the model was trained -
-for instance, in English, a token could be a single word like "apple", or a part of a word like "app".
-
-When you send a model a prompt, the words and characters in the prompt are encoded into tokens using a **tokenizer**.
-The model then streams back generated output tokens, which the tokenizer decodes into human-readable text.
-The below example shows how OpenAI models tokenize `LangChain is cool!`:
-
-![](/img/tokenization.png)
-
-You can see that it gets split into 5 different tokens, and that the boundaries between tokens are not exactly the same as word boundaries.
-
-The reason language models use tokens rather than something more immediately intuitive like "characters"
-has to do with how they process and understand text. At a high-level, language models iteratively predict their next generated output based on
-the initial input and their previous generations. Training the model using tokens language models to handle linguistic
-units (like words or subwords) that carry meaning, rather than individual characters, which makes it easier for the model
-to learn and understand the structure of the language, including grammar and context.
-Furthermore, using tokens can also improve efficiency, since the model processes fewer units of text compared to character-level processing.
-
-### Structured output
-
-LLMs are capable of generating arbitrary text. This enables the model to respond appropriately to a wide
-range of inputs, but for some use-cases, it can be useful to constrain the LLM's output
-to a specific format or structure. This is referred to as **structured output**.
-
-For example, if the output is to be stored in a relational database,
-it is much easier if the model generates output that adheres to a defined schema or format.
-[Extracting specific information](/docs/tutorials/extraction/) from unstructured text is another
-case where this is particularly useful. Most commonly, the output format will be JSON,
-though other formats such as [YAML](/docs/how_to/output_parser_yaml/) can be useful too. Below, we'll discuss
-a few ways to get structured output from models in LangChain.
-
-#### `.with_structured_output()`
-
-For convenience, some LangChain chat models support a `.with_structured_output()` method.
-This method only requires a schema as input, and returns a dict or Pydantic object.
-Generally, this method is only present on models that support one of the more advanced methods described below,
-and will use one of them under the hood. It takes care of importing a suitable output parser and
-formatting the schema in the right format for the model.
-
-For more information, check out this [how-to guide](/docs/how_to/structured_output/#the-with_structured_output-method).
-
-#### Raw prompting
-
-The most intuitive way to get a model to structure output is to ask nicely.
-In addition to your query, you can give instructions describing what kind of output you'd like, then
-parse the output using an [output parser](/docs/concepts/#output-parsers) to convert the raw
-model message or string output into something more easily manipulated.
-
-The biggest benefit to raw prompting is its flexibility:
-
-- Raw prompting does not require any special model features, only sufficient reasoning capability to understand
-the passed schema.
-- You can prompt for any format you'd like, not just JSON. This can be useful if the model you
-are using is more heavily trained on a certain type of data, such as XML or YAML.
-
-However, there are some drawbacks too:
-
-- LLMs are non-deterministic, and prompting a LLM to consistently output data in the exactly correct format
-for smooth parsing can be surprisingly difficult and model-specific.
-- Individual models have quirks depending on the data they were trained on, and optimizing prompts can be quite difficult.
-Some may be better at interpreting [JSON schema](https://json-schema.org/), others may be best with TypeScript definitions,
-and still others may prefer XML.
-
-While we'll next go over some ways that you can take advantage of features offered by
-model providers to increase reliability, prompting techniques remain important for tuning your
-results no matter what method you choose.
-
-#### JSON mode
-<span data-heading-keywords="json mode"></span>
-
-Some models, such as [Mistral](/docs/integrations/chat/mistralai/), [OpenAI](/docs/integrations/chat/openai/),
-[Together AI](/docs/integrations/chat/together/) and [Ollama](/docs/integrations/chat/ollama/),
-support a feature called **JSON mode**, usually enabled via config.
-
-When enabled, JSON mode will constrain the model's output to always be some sort of valid JSON.
-Often they require some custom prompting, but it's usually much less burdensome and along the lines of,
-`"you must always return JSON"`, and the [output is easier to parse](/docs/how_to/output_parser_json/).
-
-It's also generally simpler and more commonly available than tool calling.
-
-Here's an example:
-
-```python
-from langchain_core.prompts import ChatPromptTemplate
-from langchain_openai import ChatOpenAI
-from langchain.output_parsers.json import SimpleJsonOutputParser
-
-model = ChatOpenAI(
-    model="gpt-4o",
-    model_kwargs={ "response_format": { "type": "json_object" } },
-)
-
-prompt = ChatPromptTemplate.from_template(
-    "Answer the user's question to the best of your ability."
-    'You must always output a JSON object with an "answer" key and a "followup_question" key.'
-    "{question}"
-)
-
-chain = prompt | model | SimpleJsonOutputParser()
-
-chain.invoke({ "question": "What is the powerhouse of the cell?" })
-```
-
-```
-{'answer': 'The powerhouse of the cell is the mitochondrion. It is responsible for producing energy in the form of ATP through cellular respiration.',
- 'followup_question': 'Would you like to know more about how mitochondria produce energy?'}
-```
-
-For a full list of model providers that support JSON mode, see [this table](/docs/integrations/chat/#advanced-features).
-
-#### Function/tool calling
+### Function/tool calling
 
 :::info
 We use the term tool calling interchangeably with function calling. Although
 function calling is sometimes meant to refer to invocations of a single function,
 we treat all models as though they can return multiple tool or function calls in
-each message
+each message.
 :::
 
 Tool calling allows a model to respond to a given prompt by generating output that
@@ -831,10 +480,8 @@ from unstructured text, you could give the model an "extraction" tool that takes
 parameters matching the desired schema, then treat the generated output as your final
 result.
 
-For models that support it, tool calling can be very convenient. It removes the
-guesswork around how best to prompt schemas in favor of a built-in model feature. It can also
-more naturally support agentic flows, since you can just pass multiple tool schemas instead
-of fiddling with enums or unions.
+A tool call includes a name, arguments dict, and an optional identifier. The
+arguments dict is structured `{argument_name: argument_value}`.
 
 Many LLM providers, including [Anthropic](https://www.anthropic.com/),
 [Cohere](https://cohere.com/), [Google](https://cloud.google.com/vertex-ai),
@@ -847,178 +494,37 @@ receive the tool call, execute it, and return the output to the LLM to inform it
 response. LangChain includes a suite of [built-in tools](/docs/integrations/tools/)
 and supports several methods for defining your own [custom tools](/docs/how_to/custom_tools).
 
-LangChain provides a standardized interface for tool calling that is consistent across different models.
-
-The standard interface consists of:
-
-* `ChatModel.bind_tools()`: a method for specifying which tools are available for a model to call. This method accepts [LangChain tools](/docs/concepts/#tools) here.
-* `AIMessage.tool_calls`: an attribute on the `AIMessage` returned from the model for accessing the tool calls requested by the model.
-
-The following how-to guides are good practical resources for using function/tool calling:
+There are two main use cases for function/tool calling:
 
 - [How to return structured data from an LLM](/docs/how_to/structured_output/)
 - [How to use a model to call tools](/docs/how_to/tool_calling/)
 
-For a full list of model providers that support tool calling, [see this table](/docs/integrations/chat/#advanced-features).
 
 ### Retrieval
 
-LLMs are trained on a large but fixed dataset, limiting their ability to reason over private or recent information. Fine-tuning an LLM with specific facts is one way to mitigate this, but is often [poorly suited for factual recall](https://www.anyscale.com/blog/fine-tuning-is-for-form-not-facts) and [can be costly](https://www.glean.com/blog/how-to-build-an-ai-assistant-for-the-enterprise). 
-Retrieval is the process of providing relevant information to an LLM to improve its response for a given input. Retrieval augmented generation (RAG) is the process of grounding the LLM generation (output) using the retrieved information.
+LangChain provides several advanced retrieval types. A full list is below, along with the following information:
 
-:::tip
+**Name**: Name of the retrieval algorithm.
 
-* See our RAG from Scratch [code](https://github.com/langchain-ai/rag-from-scratch) and [video series](https://youtube.com/playlist?list=PLfaIDFEXuae2LXbO1_PKyVJiQ23ZztA0x&feature=shared).
-* For a high-level guide on retrieval, see this [tutorial on RAG](/docs/tutorials/rag/).
+**Index Type**: Which index type (if any) this relies on.
 
-:::
+**Uses an LLM**: Whether this retrieval method uses an LLM.
 
-RAG is only as good as the retrieved documents’ relevance and quality. Fortunately, an emerging set of techniques can be employed to design and improve RAG systems. We've focused on taxonomizing and summarizing many of these techniques (see below figure) and will share some high-level strategic guidance in the following sections.
-You can and should experiment with using different pieces together. You might also find [this LangSmith guide](https://docs.smith.langchain.com/how_to_guides/evaluation/evaluate_llm_application) useful for showing how to evaluate different iterations of your app.
+**When to Use**: Our commentary on when you should considering using this retrieval method.
 
-![](/img/rag_landscape.png)
-
-#### Query Translation
-
-First, consider the user input(s) to your RAG system. Ideally, a RAG system can handle a wide range of inputs, from poorly worded questions to complex multi-part queries.
-**Using an LLM to review and optionally modify the input is the central idea behind query translation.** This serves as a general buffer, optimizing raw user inputs for your retrieval system. 
-For example, this can be as simple as extracting keywords or as complex as generating multiple sub-questions for a complex query.
-
-| Name          | When to use | Description |
-|---------------|-------------|-------------|
-| [Multi-query](/docs/how_to/MultiQueryRetriever/)   | When you need to cover multiple perspectives of a question. | Rewrite the user question from multiple perspectives, retrieve documents for each rewritten question, return the unique documents for all queries. |
-| [Decomposition](https://github.com/langchain-ai/rag-from-scratch/blob/main/rag_from_scratch_5_to_9.ipynb) | When a question can be broken down into smaller subproblems. | Decompose a question into a set of subproblems / questions, which can either be solved sequentially (use the answer from first + retrieval to answer the second) or in parallel (consolidate each answer into final answer). |
-| [Step-back](https://github.com/langchain-ai/rag-from-scratch/blob/main/rag_from_scratch_5_to_9.ipynb)     | When a higher-level conceptual understanding is required. | First prompt the LLM to ask a generic step-back question about higher-level concepts or principles, and retrieve relevant facts about them. Use this grounding to help answer the user question. |
-| [HyDE](https://github.com/langchain-ai/rag-from-scratch/blob/main/rag_from_scratch_5_to_9.ipynb)          | If you have challenges retrieving relevant documents using the raw user inputs. | Use an LLM to convert questions into hypothetical documents that answer the question. Use the embedded hypothetical documents to retrieve real documents with the premise that doc-doc similarity search can produce more relevant matches. |
-
-:::tip
-
-See our RAG from Scratch videos for a few different specific approaches:
-- [Multi-query](https://youtu.be/JChPi0CRnDY?feature=shared)
-- [Decomposition](https://youtu.be/h0OPWlEOank?feature=shared)
-- [Step-back](https://youtu.be/xn1jEjRyJ2U?feature=shared)
-- [HyDE](https://youtu.be/SaDzIVkYqyY?feature=shared)
-
-:::
-
-#### Routing
-
-Second, consider the data sources available to your RAG system. You want to query across more than one database or across structured and unstructured data sources. **Using an LLM to review the input and route it to the appropriate data source is a simple and effective approach for querying across sources.**
-
-| Name             | When to use                                | Description |
-|------------------|--------------------------------------------|-------------|
-| [Logical routing](/docs/how_to/routing/#using-a-runnablebranch)  | When you can prompt an LLM with rules to decide where to route the input. | Logical routing can use an LLM to reason about the query and choose which datastore is most appropriate. |
-| [Semantic routing](/docs/how_to/routing/#using-a-runnablebranch) | When semantic similarity is an effective way to determine where to route the input. | Semantic routing embeds both query and, typically a set of prompts. It then chooses the appropriate prompt based upon similarity. |
-
-:::tip
-
-See our RAG from Scratch video on [routing](https://youtu.be/pfpIndq7Fi8?feature=shared).  
-
-:::
-
-#### Query Construction
-
-Third, consider whether any of your data sources require specific query formats. Many structured databases use SQL. Vector stores often have specific syntax for applying keyword filters to document metadata. **Using an LLM to convert a natural language query into a query syntax is a popular and powerful approach.**
-In particular, [text-to-SQL](/docs/tutorials/sql_qa/), [text-to-Cypher](/docs/tutorials/graph/), and [query analysis for metadata filters](/docs/tutorials/query_analysis/#query-analysis) are useful ways to interact with structured, graph, and vector databases respectively. 
-
-| Name                                        | When to Use                                                                                                                                   | Description                                                                                                                                                                                                                                                                                      |
-|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| [Text to SQL](/docs/tutorials/sql_qa/)      | If users are asking questions that require information housed in a relational database, accessible via SQL.                                   | This uses an LLM to transform user input into a SQL query.                                             |
-| [Text-to-Cypher](/docs/tutorials/graph/)    | If users are asking questions that require information housed in a graph database, accessible via Cypher.                                     | This uses an LLM to transform user input into a Cypher query.                                              |
-| [Self Query](/docs/how_to/self_query/)      | If users are asking questions that are better answered by fetching documents based on metadata rather than similarity with the text.          | This uses an LLM to transform user input into two things: (1) a string to look up semantically, (2) a metadata filter to go along with it. This is useful because oftentimes questions are about the METADATA of documents (not the content itself).                                              |
-
-:::tip
-
-See our [blog post overview](https://blog.langchain.dev/query-construction/) and RAG from Scratch video on [query construction](https://youtu.be/kl6NwWYxvbM?feature=shared), the process of text-to-DSL where DSL is a domain specific language required to interact with a given database. This converts user questions into structured queries. 
-
-:::
-
-#### Indexing
-
-Fouth, consider the design of your document index. A simple and powerful idea is to **decouple the documents that you index for retrieval from the documents that you pass to the LLM for generation.** Indexing frequently uses embedding models with vector stores, which [compress the semantic information in documents to fixed-size vectors](/docs/concepts/#embedding-models).
-
-Many RAG approaches focus on splitting documents into chunks and retrieving some number based on similarity to an input question for the LLM. But chunk size and chunk number can be difficult to set and affect results if they do not provide full context for the LLM to answer a question. Furthermore, LLMs are increasingly capable of processing millions of tokens. 
-
-Two approaches can address this tension: (1) [Multi Vector](/docs/how_to/multi_vector/) retriever using an LLM to translate documents into any form (e.g., often into a summary) that is well-suited for indexing, but returns full documents to the LLM for generation. (2) [ParentDocument](/docs/how_to/parent_document_retriever/) retriever embeds document chunks, but also returns full documents. The idea is to get the best of both worlds: use concise representations (summaries or chunks) for retrieval, but use the full documents for answer generation.
-
-| Name                      | Index Type                   | Uses an LLM               | When to Use                                                                                                                                   | Description                                                                                                                                                                                                                                                                                      |
-|---------------------------|------------------------------|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| [Vector store](/docs/how_to/vectorstore_retriever/)               | Vector store                  | No                        | If you are just getting started and looking for something quick and easy.                                                                     | This is the simplest method and the one that is easiest to get started with. It involves creating embeddings for each piece of text.                                                                                                                                                             |
-| [ParentDocument](/docs/how_to/parent_document_retriever/)            | Vector store + Document Store | No                        | If your pages have lots of smaller pieces of distinct information that are best indexed by themselves, but best retrieved all together.       | This involves indexing multiple chunks for each document. Then you find the chunks that are most similar in embedding space, but you retrieve the whole parent document and return that (rather than individual chunks).                                                                         |
-| [Multi Vector](/docs/how_to/multi_vector/)              | Vector store + Document Store | Sometimes during indexing | If you are able to extract information from documents that you think is more relevant to index than the text itself.                          | This involves creating multiple vectors for each document. Each vector could be created in a myriad of ways - examples include summaries of the text and hypothetical questions.                                                                                                                 |
-| [Time-Weighted Vector store](/docs/how_to/time_weighted_vectorstore/) | Vector store                  | No                        | If you have timestamps associated with your documents, and you want to retrieve the most recent ones                                          | This fetches documents based on a combination of semantic similarity (as in normal vector retrieval) and recency (looking at timestamps of indexed documents)                                                                                                                                    |
-
-:::tip
-
-- See our RAG from Scratch video on [indexing fundamentals](https://youtu.be/bjb_EMsTDKI?feature=shared)
-- See our RAG from Scratch video on [multi vector retriever](https://youtu.be/gTCU9I6QqCE?feature=shared)
-
-:::
-
-Fifth, consider ways to improve the quality of your similarity search itself. Embedding models compress text into fixed-length (vector) representations that capture the semantic content of the document. This compression is useful for search / retrieval, but puts a heavy burden on that single vector representation to capture the semantic nuance / detail of the document. In some cases, irrelevant or redundant content can dilute the semantic usefulness of the embedding.
-
-[ColBERT](https://docs.google.com/presentation/d/1IRhAdGjIevrrotdplHNcc4aXgIYyKamUKTWtB3m3aMU/edit?usp=sharing) is an interesting approach to address this with a higher granularity embeddings: (1) produce a contextually influenced embedding for each token in the document and query, (2) score similarity between each query token and all document tokens, (3) take the max, (4) do this for all query tokens, and (5) take the sum of the max scores (in step 3) for all query tokens to get a query-document similarity score; this token-wise scoring can yield strong results. 
-
-![](/img/colbert.png)
-
-There are some additional tricks to improve the quality of your retrieval. Embeddings excel at capturing semantic information, but may struggle with keyword-based queries. Many [vector stores](https://python.langchain.com/v0.2/docs/integrations/retrievers/pinecone_hybrid_search/) offer built-in [hybrid-search](https://docs.pinecone.io/guides/data/understanding-hybrid-search) to combine keyword and semantic similarity, which marries the benefits of both approaches. Furthermore, many vector stores have [maximal marginal relevance](https://python.langchain.com/v0.1/docs/modules/model_io/prompts/example_selectors/mmr/), which attempts to diversify the results of a search to avoid returning similar and redundant documents. 
-
-| Name              | When to use                                              | Description |
-|-------------------|----------------------------------------------------------|-------------|
-| [ColBERT](/docs/integrations/providers/ragatouille/#using-colbert-as-a-reranker)           | When higher granularity embeddings are needed.           | ColBERT uses contextually influenced embeddings for each token in the document and query to get a granular query-document similarity score. |
-| [Hybrid search](/docs/integrations/retrievers/pinecone_hybrid_search/)     | When combining keyword-based and semantic similarity.    | Hybrid search combines keyword and semantic similarity, marrying the benefits of both approaches. |
-| [Maximal Marginal Relevance (MMR) ](/docs/integrations/vectorstores/pinecone/#maximal-marginal-relevance-searches) | When needing to diversify search results. | MMR attempts to diversify the results of a search to avoid returning similar and redundant documents. |
-
-:::tip
-
-See our RAG from Scratch video on [ColBERT](https://youtu.be/cN6S0Ehm7_8?feature=shared>).
-
-:::
-
-#### Post-processing
-
-Sixth, consider ways to filter or rank retrieved documents. This is very useful if you are [combining documents returned from multiple sources](/docs/integrations/retrievers/cohere-reranker/#doing-reranking-with-coherererank), since it can can down-rank less relevant documents and / or [compress similar documents](/docs/how_to/contextual_compression/#more-built-in-compressors-filters). 
+**Description**: Description of what this retrieval algorithm is doing.
 
 | Name                      | Index Type                   | Uses an LLM               | When to Use                                                                                                                                   | Description                                                                                                                                                                                                                                                                                      |
 |---------------------------|------------------------------|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [Vectorstore](/docs/how_to/vectorstore_retriever/)               | Vectorstore                  | No                        | If you are just getting started and looking for something quick and easy.                                                                     | This is the simplest method and the one that is easiest to get started with. It involves creating embeddings for each piece of text.                                                                                                                                                             |
+| [ParentDocument](/docs/how_to/parent_document_retriever/)            | Vectorstore + Document Store | No                        | If your pages have lots of smaller pieces of distinct information that are best indexed by themselves, but best retrieved all together.       | This involves indexing multiple chunks for each document. Then you find the chunks that are most similar in embedding space, but you retrieve the whole parent document and return that (rather than individual chunks).                                                                         |
+| [Multi Vector](/docs/how_to/multi_vector/)              | Vectorstore + Document Store | Sometimes during indexing | If you are able to extract information from documents that you think is more relevant to index than the text itself.                          | This involves creating multiple vectors for each document. Each vector could be created in a myriad of ways - examples include summaries of the text and hypothetical questions.                                                                                                                 |
+| [Self Query](/docs/how_to/self_query/)               | Vectorstore                  | Yes                       | If users are asking questions that are better answered by fetching documents based on metadata rather than similarity with the text.          | This uses an LLM to transform user input into two things: (1) a string to look up semantically, (2) a metadata filer to go along with it. This is useful because oftentimes questions are about the METADATA of documents (not the content itself).                                              |
 | [Contextual Compression](/docs/how_to/contextual_compression/)    | Any                          | Sometimes                 | If you are finding that your retrieved documents contain too much irrelevant information and are distracting the LLM.                         | This puts a post-processing step on top of another retriever and extracts only the most relevant information from retrieved documents. This can be done with embeddings or an LLM.                                                                                                               |
+| [Time-Weighted Vectorstore](/docs/how_to/time_weighted_vectorstore/) | Vectorstore                  | No                        | If you have timestamps associated with your documents, and you want to retrieve the most recent ones                                          | This fetches documents based on a combination of semantic similarity (as in normal vector retrieval) and recency (looking at timestamps of indexed documents)                                                                                                                                    |
+| [Multi-Query Retriever](/docs/how_to/MultiQueryRetriever/)     | Any                          | Yes                       | If users are asking questions that are complex and require multiple pieces of distinct information to respond                                 | This uses an LLM to generate multiple queries from the original one. This is useful when the original query needs pieces of information about multiple topics to be properly answered. By generating multiple queries, we can then fetch documents for each of them.                             |
 | [Ensemble](/docs/how_to/ensemble_retriever/)                  | Any                          | No                        | If you have multiple retrieval methods and want to try combining them.                                                                        | This fetches documents from multiple retrievers and then combines them.                                                                                                                                                                                                                          |
-| [Re-ranking](/docs/integrations/retrievers/cohere-reranker/)                  | Any                          | Yes                        |  If you want to rank retrieved documents based upon relevance, especially if you want to combine results from multiple retrieval methods .                                                                         | Given a query and a list of documents, Rerank indexes the documents from most to least semantically relevant to the query.                                                                                                                                                                                                                         |
 
-:::tip
-
-See our RAG from Scratch video on [RAG-Fusion](https://youtu.be/77qELPbNgxA?feature=shared), on approach for post-processing across multiple queries:  Rewrite the user question from multiple perspectives, retrieve documents for each rewritten question, and combine the ranks of multiple search result lists to produce a single, unified ranking with [Reciprocal Rank Fusion (RRF)](https://towardsdatascience.com/forget-rag-the-future-is-rag-fusion-1147298d8ad1).
-
-:::
-
-#### Generation
-
-**Finally, consider ways to build self-correction into your RAG system.** RAG systems can suffer from low quality retrieval (e.g., if a user question is out of the domain for the index) and / or hallucinations in generation. A naive retrieve-generate pipeline has no ability to detect or self-correct from these kinds of errors. The concept of ["flow engineering"](https://x.com/karpathy/status/1748043513156272416) has been introduced [in the context of code generation](https://arxiv.org/abs/2401.08500): iteratively build an answer to a code question with unit tests to check and self-correct errors. Several works have applied this RAG, such as Self-RAG and Corrective-RAG. In both cases, checks for document relevance, hallucinations, and / or answer quality are performed in the RAG answer generation flow.
-
-We've found that graphs are a great way to reliably express logical flows and have implemented ideas from several of these papers [using LangGraph](https://github.com/langchain-ai/langgraph/tree/main/examples/rag), as shown in the figure below (red - routing, blue - fallback, green - self-correction):
-- **Routing:**  Adaptive RAG ([paper](https://arxiv.org/abs/2403.14403)). Route questions to different retrieval approaches, as discussed above 
-- **Fallback:** Corrective RAG ([paper](https://arxiv.org/pdf/2401.15884.pdf)). Fallback to web search if docs are not relevant to query
-- **Self-correction:** Self-RAG ([paper](https://arxiv.org/abs/2310.11511)). Fix answers w/ hallucinations or don’t address question
-
-![](/img/langgraph_rag.png)
-
-| Name              | When to use                                               | Description |
-|-------------------|-----------------------------------------------------------|-------------|
-| Self-RAG          | When needing to fix answers with hallucinations or irrelevant content. | Self-RAG performs checks for document relevance, hallucinations, and answer quality during the RAG answer generation flow, iteratively building an answer and self-correcting errors. |
-| Corrective-RAG    | When needing a fallback mechanism for low relevance docs. | Corrective-RAG includes a fallback (e.g., to web search) if the retrieved documents are not relevant to the query, ensuring higher quality and more relevant retrieval. |
-
-:::tip
-
-See several videos and cookbooks showcasing RAG with LangGraph: 
-- [LangGraph Corrective RAG](https://www.youtube.com/watch?v=E2shqsYwxck)
-- [LangGraph combining Adaptive, Self-RAG, and Corrective RAG](https://www.youtube.com/watch?v=-ROS6gfYIts) 
-- [Cookbooks for RAG using LangGraph ](https://github.com/langchain-ai/langgraph/tree/main/examples/rag)
-
-See our LangGraph RAG recipes with partners:
-- [Meta](https://github.com/meta-llama/llama-recipes/tree/main/recipes/use_cases/agents/langchain) 
-- [Mistral](https://github.com/mistralai/cookbook/tree/main/third_party/langchain)
-
-:::
 
 ### Text splitting
 
@@ -1044,7 +550,3 @@ Table columns:
 | Character  | [CharacterTextSplitter](/docs/how_to/character_text_splitter/)                                                                                                                | A user defined character                                                                                        |               | Splits text based on a user defined character. One of the simpler methods.                                                                                                                                                                                                   |
 | Semantic Chunker (Experimental) | [SemanticChunker](/docs/how_to/semantic-chunker/)                                                                                                                             | Sentences                                                                                                       |               | First splits on sentences. Then combines ones next to each other if they are semantically similar enough. Taken from [Greg Kamradt](https://github.com/FullStackRetrieval-com/RetrievalTutorials/blob/main/tutorials/LevelsOfTextSplitting/5_Levels_Of_Text_Splitting.ipynb) |
 | Integration: AI21 Semantic | [AI21SemanticTextSplitter](/docs/integrations/document_transformers/ai21_semantic_text_splitter/)                                                                                                                    |    ✅           | Identifies distinct topics that form coherent pieces of text and splits along those.                                                                                                                                                                                         |
-
-
-
-

docs/docs/contributing/code.mdx

@@ -206,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.
@@ -214,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/documentation/style_guide.mdx

@@ -55,7 +55,7 @@ The below sections are listed roughly in order of increasing level of abstractio
 
 ### Expression Language
 
-[LangChain Expression Language (LCEL)](/docs/concepts#langchain-expression-language-lcel) is the fundamental way that most LangChain components fit together, and this section is designed to teach
+[LangChain Expression Language (LCEL)](/docs/concepts#langchain-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,
@@ -88,7 +88,7 @@ Concepts covered in `Integrations` should generally exist in `langchain_communit
 
 ### Guides and Ecosystem
 
-The [Guides](/docs/tutorials) and [Ecosystem](https://docs.smith.langchain.com/) sections should contain guides that address higher-level problems than the sections above.
+The [Guides](/docs/tutorials) 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**.

docs/docs/contributing/documentation/technical_logistics.mdx

@@ -71,8 +71,6 @@ make docs_clean
 make api_docs_clean
 ```
 
-
-
 Next, you can build the documentation as outlined below:
 
 ```bash
@@ -80,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

@@ -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/repo_structure.mdx

@@ -6,7 +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.
+LangChain is organized as a [monorep](https://en.wikipedia.org/wiki/Monorepo) that contains multiple packages.
 
 Here's the structure visualized as a tree:
 
@@ -15,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

docs/docs/how_to/HTML_section_aware_splitter.ipynb

@@ -132,7 +132,7 @@
     }
    ],
    "source": [
-    "from langchain_text_splitters import RecursiveCharacterTextSplitter\n",
+    "from langchain.text_splitter import RecursiveCharacterTextSplitter\n",
     "\n",
     "html_string = \"\"\"\n",
     "    <!DOCTYPE html>\n",

docs/docs/how_to/MultiQueryRetriever.ipynb

@@ -138,10 +138,20 @@
    "execution_count": 5,
    "id": "d9afb0ca",
    "metadata": {},
-   "outputs": [],
+   "outputs": [
+    {
+     "name": "stderr",
+     "output_type": "stream",
+     "text": [
+      "/Users/chestercurme/.pyenv/versions/3.10.4/envs/sandbox310/lib/python3.10/site-packages/langchain_core/_api/deprecation.py:119: LangChainDeprecationWarning: The class `LLMChain` was deprecated in LangChain 0.1.17 and will be removed in 0.3.0. Use RunnableSequence, e.g., `prompt | llm` instead.\n",
+      "  warn_deprecated(\n"
+     ]
+    }
+   ],
    "source": [
     "from typing import List\n",
     "\n",
+    "from langchain.chains import LLMChain\n",
     "from langchain_core.output_parsers import BaseOutputParser\n",
     "from langchain_core.prompts import PromptTemplate\n",
     "from langchain_core.pydantic_v1 import BaseModel, Field\n",
@@ -170,7 +180,7 @@
     "llm = ChatOpenAI(temperature=0)\n",
     "\n",
     "# Chain\n",
-    "llm_chain = QUERY_PROMPT | llm | output_parser\n",
+    "llm_chain = LLMChain(llm=llm, prompt=QUERY_PROMPT, output_parser=output_parser)\n",
     "\n",
     "# Other inputs\n",
     "question = \"What are the approaches to Task Decomposition?\""
@@ -179,14 +189,14 @@
   {
    "cell_type": "code",
    "execution_count": 6,
-   "id": "59c75c56-dbd7-4887-b9ba-0b5b21069f51",
+   "id": "2eca2d96-8057-4ed9-873d-fa1064c09acf",
    "metadata": {},
    "outputs": [
     {
      "name": "stderr",
      "output_type": "stream",
      "text": [
-      "INFO:langchain.retrievers.multi_query:Generated queries: ['1. Can you provide insights on regression from the course material?', '2. How is regression discussed in the course content?', '3. What information does the course offer about regression?', '4. In what way is regression covered in the course?', '5. What are the teachings of the course regarding regression?']\n"
+      "INFO:langchain.retrievers.multi_query:Generated queries: ['1. Can you provide insights on regression from the course material?', '2. How is regression discussed in the course content?', '3. What information does the course offer about regression analysis?', '4. What are the teachings of the course regarding regression?', '5. In what manner is regression covered in the course curriculum?']\n"
      ]
     },
     {

docs/docs/how_to/agent_executor.ipynb

@@ -15,18 +15,18 @@
    "id": "f4c03f40-1328-412d-8a48-1db0cd481b77",
    "metadata": {},
    "source": [
-    "# Build an Agent with AgentExecutor (Legacy)\n",
-    "\n",
-    ":::{.callout-important}\n",
-    "This section will cover building with the legacy LangChain AgentExecutor. These are fine for getting started, but past a certain point, you will likely want flexibility and control that they do not offer. For working with more advanced agents, we'd recommend checking out [LangGraph Agents](/docs/concepts/#langgraph) or the [migration guide](/docs/how_to/migrate_agent/)\n",
-    ":::\n",
+    "# Build an Agent\n",
     "\n",
     "By themselves, language models can't take actions - they just output text.\n",
     "A big use case for LangChain is creating **agents**.\n",
-    "Agents are systems that use an LLM as a reasoning engine to determine which actions to take and what the inputs to those actions should be.\n",
-    "The results of those actions can then be fed back into the agent and it determines whether more actions are needed, or whether it is okay to finish.\n",
+    "Agents are systems that use an LLM as a reasoning enginer to determine which actions to take and what the inputs to those actions should be.\n",
+    "The results of those actions can then be fed back into the agent and it determine whether more actions are needed, or whether it is okay to finish.\n",
     "\n",
-    "In this tutorial, we will build an agent that can interact with multiple different tools: one being a local database, the other being a search engine. You will be able to ask this agent questions, watch it call tools, and have conversations with it.\n",
+    "In this tutorial we will build an agent that can interact with multiple different tools: one being a local database, the other being a search engine. You will be able to ask this agent questions, watch it call tools, and have conversations with it.\n",
+    "\n",
+    ":::{.callout-important}\n",
+    "This section will cover building with LangChain Agents. LangChain Agents are fine for getting started, but past a certain point you will likely want flexibility and control that they do not offer. For working with more advanced agents, we'd reccommend checking out [LangGraph](/docs/concepts/#langgraph)\n",
+    ":::\n",
     "\n",
     "## Concepts\n",
     "\n",
@@ -34,7 +34,7 @@
     "- Using [language models](/docs/concepts/#chat-models), in particular their tool calling ability\n",
     "- Creating a [Retriever](/docs/concepts/#retrievers) to expose specific information to our agent\n",
     "- Using a Search [Tool](/docs/concepts/#tools) to look up things online\n",
-    "- [`Chat History`](/docs/concepts/#chat-history), which allows a chatbot to \"remember\" past interactions and take them into account when responding to follow-up questions. \n",
+    "- [`Chat History`](/docs/concepts/#chat-history), which allows a chatbot to \"remember\" past interactions and take them into account when responding to followup questions. \n",
     "- Debugging and tracing your application using [LangSmith](/docs/concepts/#langsmith)\n",
     "\n",
     "## Setup\n",
@@ -66,7 +66,7 @@
     "```\n",
     "\n",
     "\n",
-    "For more details, see our [Installation guide](/docs/how_to/installation).\n",
+    "For more details, see our [Installation guide](/docs/installation).\n",
     "\n",
     "### LangSmith\n",
     "\n",

docs/docs/how_to/binding.ipynb

@@ -16,7 +16,7 @@
    "id": "711752cb-4f15-42a3-9838-a0c67f397771",
    "metadata": {},
    "source": [
-    "# How to add default invocation args to a Runnable\n",
+    "# How to attach runtime arguments to a Runnable\n",
     "\n",
     ":::info Prerequisites\n",
     "\n",

docs/docs/how_to/callbacks_async.ipynb

@@ -1,179 +0,0 @@
-{
- "cells": [
-  {
-   "cell_type": "markdown",
-   "metadata": {},
-   "source": [
-    "# How to use callbacks in async environments\n",
-    "\n",
-    ":::info Prerequisites\n",
-    "\n",
-    "This guide assumes familiarity with the following concepts:\n",
-    "\n",
-    "- [Callbacks](/docs/concepts/#callbacks)\n",
-    "- [Custom callback handlers](/docs/how_to/custom_callbacks)\n",
-    ":::\n",
-    "\n",
-    "If you are planning to use the async APIs, it is recommended to use and extend [`AsyncCallbackHandler`](https://api.python.langchain.com/en/latest/callbacks/langchain_core.callbacks.base.AsyncCallbackHandler.html) to avoid blocking the event.\n",
-    "\n",
-    "\n",
-    ":::{.callout-warning}\n",
-    "If you use a sync `CallbackHandler` while using an async method to run your LLM / Chain / Tool / Agent, it will still work. However, under the hood, it will be called with [`run_in_executor`](https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.loop.run_in_executor) which can cause issues if your `CallbackHandler` is not thread-safe.\n",
-    ":::\n",
-    "\n",
-    ":::{.callout-danger}\n",
-    "\n",
-    "If you're on `python<=3.10`, you need to remember to propagate `config` or `callbacks` when invoking other `runnable` from within a `RunnableLambda`, `RunnableGenerator` or `@tool`. If you do not do this,\n",
-    "the callbacks will not be propagated to the child runnables being invoked.\n",
-    ":::"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "# | output: false\n",
-    "# | echo: false\n",
-    "\n",
-    "%pip install -qU langchain langchain_anthropic\n",
-    "\n",
-    "import getpass\n",
-    "import os\n",
-    "\n",
-    "os.environ[\"ANTHROPIC_API_KEY\"] = getpass.getpass()"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 2,
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "zzzz....\n",
-      "Hi! I just woke up. Your llm is starting\n",
-      "Sync handler being called in a `thread_pool_executor`: token: Here\n",
-      "Sync handler being called in a `thread_pool_executor`: token: 's\n",
-      "Sync handler being called in a `thread_pool_executor`: token:  a\n",
-      "Sync handler being called in a `thread_pool_executor`: token:  little\n",
-      "Sync handler being called in a `thread_pool_executor`: token:  joke\n",
-      "Sync handler being called in a `thread_pool_executor`: token:  for\n",
-      "Sync handler being called in a `thread_pool_executor`: token:  you\n",
-      "Sync handler being called in a `thread_pool_executor`: token: :\n",
-      "Sync handler being called in a `thread_pool_executor`: token: \n",
-      "\n",
-      "Why\n",
-      "Sync handler being called in a `thread_pool_executor`: token:  can\n",
-      "Sync handler being called in a `thread_pool_executor`: token: 't\n",
-      "Sync handler being called in a `thread_pool_executor`: token:  a\n",
-      "Sync handler being called in a `thread_pool_executor`: token:  bicycle\n",
-      "Sync handler being called in a `thread_pool_executor`: token:  stan\n",
-      "Sync handler being called in a `thread_pool_executor`: token: d up\n",
-      "Sync handler being called in a `thread_pool_executor`: token:  by\n",
-      "Sync handler being called in a `thread_pool_executor`: token:  itself\n",
-      "Sync handler being called in a `thread_pool_executor`: token: ?\n",
-      "Sync handler being called in a `thread_pool_executor`: token:  Because\n",
-      "Sync handler being called in a `thread_pool_executor`: token:  it\n",
-      "Sync handler being called in a `thread_pool_executor`: token: 's\n",
-      "Sync handler being called in a `thread_pool_executor`: token:  two\n",
-      "Sync handler being called in a `thread_pool_executor`: token: -\n",
-      "Sync handler being called in a `thread_pool_executor`: token: tire\n",
-      "zzzz....\n",
-      "Hi! I just woke up. Your llm is ending\n"
-     ]
-    },
-    {
-     "data": {
-      "text/plain": [
-       "LLMResult(generations=[[ChatGeneration(text=\"Here's a little joke for you:\\n\\nWhy can't a bicycle stand up by itself? Because it's two-tire\", message=AIMessage(content=\"Here's a little joke for you:\\n\\nWhy can't a bicycle stand up by itself? Because it's two-tire\", id='run-8afc89e8-02c0-4522-8480-d96977240bd4-0'))]], llm_output={}, run=[RunInfo(run_id=UUID('8afc89e8-02c0-4522-8480-d96977240bd4'))])"
-      ]
-     },
-     "execution_count": 2,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
-   "source": [
-    "import asyncio\n",
-    "from typing import Any, Dict, List\n",
-    "\n",
-    "from langchain_anthropic import ChatAnthropic\n",
-    "from langchain_core.callbacks import AsyncCallbackHandler, BaseCallbackHandler\n",
-    "from langchain_core.messages import HumanMessage\n",
-    "from langchain_core.outputs import LLMResult\n",
-    "\n",
-    "\n",
-    "class MyCustomSyncHandler(BaseCallbackHandler):\n",
-    "    def on_llm_new_token(self, token: str, **kwargs) -> None:\n",
-    "        print(f\"Sync handler being called in a `thread_pool_executor`: token: {token}\")\n",
-    "\n",
-    "\n",
-    "class MyCustomAsyncHandler(AsyncCallbackHandler):\n",
-    "    \"\"\"Async callback handler that can be used to handle callbacks from langchain.\"\"\"\n",
-    "\n",
-    "    async def on_llm_start(\n",
-    "        self, serialized: Dict[str, Any], prompts: List[str], **kwargs: Any\n",
-    "    ) -> None:\n",
-    "        \"\"\"Run when chain starts running.\"\"\"\n",
-    "        print(\"zzzz....\")\n",
-    "        await asyncio.sleep(0.3)\n",
-    "        class_name = serialized[\"name\"]\n",
-    "        print(\"Hi! I just woke up. Your llm is starting\")\n",
-    "\n",
-    "    async def on_llm_end(self, response: LLMResult, **kwargs: Any) -> None:\n",
-    "        \"\"\"Run when chain ends running.\"\"\"\n",
-    "        print(\"zzzz....\")\n",
-    "        await asyncio.sleep(0.3)\n",
-    "        print(\"Hi! I just woke up. Your llm is ending\")\n",
-    "\n",
-    "\n",
-    "# To enable streaming, we pass in `streaming=True` to the ChatModel constructor\n",
-    "# Additionally, we pass in a list with our custom handler\n",
-    "chat = ChatAnthropic(\n",
-    "    model=\"claude-3-sonnet-20240229\",\n",
-    "    max_tokens=25,\n",
-    "    streaming=True,\n",
-    "    callbacks=[MyCustomSyncHandler(), MyCustomAsyncHandler()],\n",
-    ")\n",
-    "\n",
-    "await chat.agenerate([[HumanMessage(content=\"Tell me a joke\")]])"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "metadata": {},
-   "source": [
-    "## Next steps\n",
-    "\n",
-    "You've now learned how to create your own custom callback handlers.\n",
-    "\n",
-    "Next, check out the other how-to guides in this section, such as [how to attach callbacks to a runnable](/docs/how_to/callbacks_attach)."
-   ]
-  }
- ],
- "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.6"
-  }
- },
- "nbformat": 4,
- "nbformat_minor": 4
-}

docs/docs/how_to/callbacks_attach.ipynb

@@ -1,149 +0,0 @@
-{
- "cells": [
-  {
-   "cell_type": "markdown",
-   "metadata": {},
-   "source": [
-    "# How to attach callbacks to a runnable\n",
-    "\n",
-    ":::info Prerequisites\n",
-    "\n",
-    "This guide assumes familiarity with the following concepts:\n",
-    "\n",
-    "- [Callbacks](/docs/concepts/#callbacks)\n",
-    "- [Custom callback handlers](/docs/how_to/custom_callbacks)\n",
-    "- [Chaining runnables](/docs/how_to/sequence)\n",
-    "- [Attach runtime arguments to a Runnable](/docs/how_to/binding)\n",
-    "\n",
-    ":::\n",
-    "\n",
-    "If you are composing a chain of runnables and want to reuse callbacks across multiple executions, you can attach callbacks with 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. This saves you the need to pass callbacks in each time you invoke the chain.\n",
-    "\n",
-    ":::{.callout-important}\n",
-    "\n",
-    "`with_config()` binds a configuration which will be interpreted as **runtime** configuration. So these callbacks will propagate to all child components.\n",
-    ":::\n",
-    "\n",
-    "Here's an example:"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "# | output: false\n",
-    "# | echo: false\n",
-    "\n",
-    "%pip install -qU langchain langchain_anthropic\n",
-    "\n",
-    "import getpass\n",
-    "import os\n",
-    "\n",
-    "os.environ[\"ANTHROPIC_API_KEY\"] = getpass.getpass()"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 1,
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "Chain RunnableSequence started\n",
-      "Chain ChatPromptTemplate started\n",
-      "Chain ended, outputs: messages=[HumanMessage(content='What is 1 + 2?')]\n",
-      "Chat model started\n",
-      "Chat model ended, response: generations=[[ChatGeneration(text='1 + 2 = 3', message=AIMessage(content='1 + 2 = 3', response_metadata={'id': 'msg_01NTYMsH9YxkoWsiPYs4Lemn', 'model': 'claude-3-sonnet-20240229', 'stop_reason': 'end_turn', 'stop_sequence': None, 'usage': {'input_tokens': 16, 'output_tokens': 13}}, id='run-d6bcfd72-9c94-466d-bac0-f39e456ad6e3-0'))]] llm_output={'id': 'msg_01NTYMsH9YxkoWsiPYs4Lemn', 'model': 'claude-3-sonnet-20240229', 'stop_reason': 'end_turn', 'stop_sequence': None, 'usage': {'input_tokens': 16, 'output_tokens': 13}} run=None\n",
-      "Chain ended, outputs: content='1 + 2 = 3' response_metadata={'id': 'msg_01NTYMsH9YxkoWsiPYs4Lemn', 'model': 'claude-3-sonnet-20240229', 'stop_reason': 'end_turn', 'stop_sequence': None, 'usage': {'input_tokens': 16, 'output_tokens': 13}} id='run-d6bcfd72-9c94-466d-bac0-f39e456ad6e3-0'\n"
-     ]
-    },
-    {
-     "data": {
-      "text/plain": [
-       "AIMessage(content='1 + 2 = 3', response_metadata={'id': 'msg_01NTYMsH9YxkoWsiPYs4Lemn', 'model': 'claude-3-sonnet-20240229', 'stop_reason': 'end_turn', 'stop_sequence': None, 'usage': {'input_tokens': 16, 'output_tokens': 13}}, id='run-d6bcfd72-9c94-466d-bac0-f39e456ad6e3-0')"
-      ]
-     },
-     "execution_count": 1,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
-   "source": [
-    "from typing import Any, Dict, List\n",
-    "\n",
-    "from langchain_anthropic import ChatAnthropic\n",
-    "from langchain_core.callbacks import BaseCallbackHandler\n",
-    "from langchain_core.messages import BaseMessage\n",
-    "from langchain_core.outputs import LLMResult\n",
-    "from langchain_core.prompts import ChatPromptTemplate\n",
-    "\n",
-    "\n",
-    "class LoggingHandler(BaseCallbackHandler):\n",
-    "    def on_chat_model_start(\n",
-    "        self, serialized: Dict[str, Any], messages: List[List[BaseMessage]], **kwargs\n",
-    "    ) -> None:\n",
-    "        print(\"Chat model started\")\n",
-    "\n",
-    "    def on_llm_end(self, response: LLMResult, **kwargs) -> None:\n",
-    "        print(f\"Chat model ended, response: {response}\")\n",
-    "\n",
-    "    def on_chain_start(\n",
-    "        self, serialized: Dict[str, Any], inputs: Dict[str, Any], **kwargs\n",
-    "    ) -> None:\n",
-    "        print(f\"Chain {serialized.get('name')} started\")\n",
-    "\n",
-    "    def on_chain_end(self, outputs: Dict[str, Any], **kwargs) -> None:\n",
-    "        print(f\"Chain ended, outputs: {outputs}\")\n",
-    "\n",
-    "\n",
-    "callbacks = [LoggingHandler()]\n",
-    "llm = ChatAnthropic(model=\"claude-3-sonnet-20240229\")\n",
-    "prompt = ChatPromptTemplate.from_template(\"What is 1 + {number}?\")\n",
-    "\n",
-    "chain = prompt | llm\n",
-    "\n",
-    "chain_with_callbacks = chain.with_config(callbacks=callbacks)\n",
-    "\n",
-    "chain_with_callbacks.invoke({\"number\": \"2\"})"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "metadata": {},
-   "source": [
-    "The bound callbacks will run for all nested module runs.\n",
-    "\n",
-    "## Next steps\n",
-    "\n",
-    "You've now learned how to attach callbacks to a chain.\n",
-    "\n",
-    "Next, check out the other how-to guides in this section, such as how to [pass callbacks in at runtime](/docs/how_to/callbacks_runtime)."
-   ]
-  }
- ],
- "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.4"
-  }
- },
- "nbformat": 4,
- "nbformat_minor": 4
-}

docs/docs/how_to/callbacks_constructor.ipynb

@@ -1,141 +0,0 @@
-{
- "cells": [
-  {
-   "cell_type": "markdown",
-   "metadata": {},
-   "source": [
-    "# How to propagate callbacks  constructor\n",
-    "\n",
-    ":::info Prerequisites\n",
-    "\n",
-    "This guide assumes familiarity with the following concepts:\n",
-    "\n",
-    "- [Callbacks](/docs/concepts/#callbacks)\n",
-    "- [Custom callback handlers](/docs/how_to/custom_callbacks)\n",
-    "\n",
-    ":::\n",
-    "\n",
-    "Most LangChain modules allow you to pass `callbacks` directly into the constructor (i.e., initializer). In this case, the callbacks will only be called for that instance (and any nested runs).\n",
-    "\n",
-    ":::{.callout-warning}\n",
-    "Constructor callbacks are scoped only to the object they are defined on. They are **not** inherited by children of the object. This can lead to confusing behavior,\n",
-    "and it's generally better to pass callbacks as a run time argument.\n",
-    ":::\n",
-    "\n",
-    "Here's an example:"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 1,
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "# | output: false\n",
-    "# | echo: false\n",
-    "\n",
-    "%pip install -qU langchain langchain_anthropic\n",
-    "\n",
-    "import getpass\n",
-    "import os\n",
-    "\n",
-    "os.environ[\"ANTHROPIC_API_KEY\"] = getpass.getpass()"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 18,
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "Chat model started\n",
-      "Chat model ended, response: generations=[[ChatGeneration(text='1 + 2 = 3', message=AIMessage(content='1 + 2 = 3', response_metadata={'id': 'msg_01CdKsRmeS9WRb8BWnHDEHm7', 'model': 'claude-3-sonnet-20240229', 'stop_reason': 'end_turn', 'stop_sequence': None, 'usage': {'input_tokens': 16, 'output_tokens': 13}}, id='run-2d7fdf2a-7405-4e17-97c0-67e6b2a65305-0'))]] llm_output={'id': 'msg_01CdKsRmeS9WRb8BWnHDEHm7', 'model': 'claude-3-sonnet-20240229', 'stop_reason': 'end_turn', 'stop_sequence': None, 'usage': {'input_tokens': 16, 'output_tokens': 13}} run=None\n"
-     ]
-    },
-    {
-     "data": {
-      "text/plain": [
-       "AIMessage(content='1 + 2 = 3', response_metadata={'id': 'msg_01CdKsRmeS9WRb8BWnHDEHm7', 'model': 'claude-3-sonnet-20240229', 'stop_reason': 'end_turn', 'stop_sequence': None, 'usage': {'input_tokens': 16, 'output_tokens': 13}}, id='run-2d7fdf2a-7405-4e17-97c0-67e6b2a65305-0')"
-      ]
-     },
-     "execution_count": 18,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
-   "source": [
-    "from typing import Any, Dict, List\n",
-    "\n",
-    "from langchain_anthropic import ChatAnthropic\n",
-    "from langchain_core.callbacks import BaseCallbackHandler\n",
-    "from langchain_core.messages import BaseMessage\n",
-    "from langchain_core.outputs import LLMResult\n",
-    "from langchain_core.prompts import ChatPromptTemplate\n",
-    "\n",
-    "\n",
-    "class LoggingHandler(BaseCallbackHandler):\n",
-    "    def on_chat_model_start(\n",
-    "        self, serialized: Dict[str, Any], messages: List[List[BaseMessage]], **kwargs\n",
-    "    ) -> None:\n",
-    "        print(\"Chat model started\")\n",
-    "\n",
-    "    def on_llm_end(self, response: LLMResult, **kwargs) -> None:\n",
-    "        print(f\"Chat model ended, response: {response}\")\n",
-    "\n",
-    "    def on_chain_start(\n",
-    "        self, serialized: Dict[str, Any], inputs: Dict[str, Any], **kwargs\n",
-    "    ) -> None:\n",
-    "        print(f\"Chain {serialized.get('name')} started\")\n",
-    "\n",
-    "    def on_chain_end(self, outputs: Dict[str, Any], **kwargs) -> None:\n",
-    "        print(f\"Chain ended, outputs: {outputs}\")\n",
-    "\n",
-    "\n",
-    "callbacks = [LoggingHandler()]\n",
-    "llm = ChatAnthropic(model=\"claude-3-sonnet-20240229\", callbacks=callbacks)\n",
-    "prompt = ChatPromptTemplate.from_template(\"What is 1 + {number}?\")\n",
-    "\n",
-    "chain = prompt | llm\n",
-    "\n",
-    "chain.invoke({\"number\": \"2\"})"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "metadata": {},
-   "source": [
-    "You can see that we only see events from the chat model run - no chain events from the prompt or broader chain.\n",
-    "\n",
-    "## Next steps\n",
-    "\n",
-    "You've now learned how to pass callbacks into a constructor.\n",
-    "\n",
-    "Next, check out the other how-to guides in this section, such as how to [pass callbacks at runtime](/docs/how_to/callbacks_runtime)."
-   ]
-  }
- ],
- "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.4"
-  }
- },
- "nbformat": 4,
- "nbformat_minor": 4
-}

docs/docs/how_to/callbacks_runtime.ipynb

@@ -1,140 +0,0 @@
-{
- "cells": [
-  {
-   "cell_type": "markdown",
-   "metadata": {},
-   "source": [
-    "# How to pass callbacks in at runtime\n",
-    "\n",
-    ":::info Prerequisites\n",
-    "\n",
-    "This guide assumes familiarity with the following concepts:\n",
-    "\n",
-    "- [Callbacks](/docs/concepts/#callbacks)\n",
-    "- [Custom callback handlers](/docs/how_to/custom_callbacks)\n",
-    "\n",
-    ":::\n",
-    "\n",
-    "In many cases, it is advantageous to pass in handlers instead when running the object. When we pass through [`CallbackHandlers`](https://api.python.langchain.com/en/latest/callbacks/langchain_core.callbacks.base.BaseCallbackHandler.html#langchain-core-callbacks-base-basecallbackhandler) using the `callbacks` keyword arg when executing an run, those callbacks will be issued by all nested objects involved in the execution. For example, when a handler is passed through to an Agent, it will be used for all callbacks related to the agent and all the objects involved in the agent's execution, in this case, the Tools and LLM.\n",
-    "\n",
-    "This prevents us from having to manually attach the handlers to each individual nested object. Here's an example:"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 1,
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "# | output: false\n",
-    "# | echo: false\n",
-    "\n",
-    "%pip install -qU langchain langchain_anthropic\n",
-    "\n",
-    "import getpass\n",
-    "import os\n",
-    "\n",
-    "os.environ[\"ANTHROPIC_API_KEY\"] = getpass.getpass()"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 4,
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "Chain RunnableSequence started\n",
-      "Chain ChatPromptTemplate started\n",
-      "Chain ended, outputs: messages=[HumanMessage(content='What is 1 + 2?')]\n",
-      "Chat model started\n",
-      "Chat model ended, response: generations=[[ChatGeneration(text='1 + 2 = 3', message=AIMessage(content='1 + 2 = 3', response_metadata={'id': 'msg_01D8Tt5FdtBk5gLTfBPm2tac', 'model': 'claude-3-sonnet-20240229', 'stop_reason': 'end_turn', 'stop_sequence': None, 'usage': {'input_tokens': 16, 'output_tokens': 13}}, id='run-bb0dddd8-85f3-4e6b-8553-eaa79f859ef8-0'))]] llm_output={'id': 'msg_01D8Tt5FdtBk5gLTfBPm2tac', 'model': 'claude-3-sonnet-20240229', 'stop_reason': 'end_turn', 'stop_sequence': None, 'usage': {'input_tokens': 16, 'output_tokens': 13}} run=None\n",
-      "Chain ended, outputs: content='1 + 2 = 3' response_metadata={'id': 'msg_01D8Tt5FdtBk5gLTfBPm2tac', 'model': 'claude-3-sonnet-20240229', 'stop_reason': 'end_turn', 'stop_sequence': None, 'usage': {'input_tokens': 16, 'output_tokens': 13}} id='run-bb0dddd8-85f3-4e6b-8553-eaa79f859ef8-0'\n"
-     ]
-    },
-    {
-     "data": {
-      "text/plain": [
-       "AIMessage(content='1 + 2 = 3', response_metadata={'id': 'msg_01D8Tt5FdtBk5gLTfBPm2tac', 'model': 'claude-3-sonnet-20240229', 'stop_reason': 'end_turn', 'stop_sequence': None, 'usage': {'input_tokens': 16, 'output_tokens': 13}}, id='run-bb0dddd8-85f3-4e6b-8553-eaa79f859ef8-0')"
-      ]
-     },
-     "execution_count": 4,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
-   "source": [
-    "from typing import Any, Dict, List\n",
-    "\n",
-    "from langchain_anthropic import ChatAnthropic\n",
-    "from langchain_core.callbacks import BaseCallbackHandler\n",
-    "from langchain_core.messages import BaseMessage\n",
-    "from langchain_core.outputs import LLMResult\n",
-    "from langchain_core.prompts import ChatPromptTemplate\n",
-    "\n",
-    "\n",
-    "class LoggingHandler(BaseCallbackHandler):\n",
-    "    def on_chat_model_start(\n",
-    "        self, serialized: Dict[str, Any], messages: List[List[BaseMessage]], **kwargs\n",
-    "    ) -> None:\n",
-    "        print(\"Chat model started\")\n",
-    "\n",
-    "    def on_llm_end(self, response: LLMResult, **kwargs) -> None:\n",
-    "        print(f\"Chat model ended, response: {response}\")\n",
-    "\n",
-    "    def on_chain_start(\n",
-    "        self, serialized: Dict[str, Any], inputs: Dict[str, Any], **kwargs\n",
-    "    ) -> None:\n",
-    "        print(f\"Chain {serialized.get('name')} started\")\n",
-    "\n",
-    "    def on_chain_end(self, outputs: Dict[str, Any], **kwargs) -> None:\n",
-    "        print(f\"Chain ended, outputs: {outputs}\")\n",
-    "\n",
-    "\n",
-    "callbacks = [LoggingHandler()]\n",
-    "llm = ChatAnthropic(model=\"claude-3-sonnet-20240229\")\n",
-    "prompt = ChatPromptTemplate.from_template(\"What is 1 + {number}?\")\n",
-    "\n",
-    "chain = prompt | llm\n",
-    "\n",
-    "chain.invoke({\"number\": \"2\"}, config={\"callbacks\": callbacks})"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "metadata": {},
-   "source": [
-    "If there are already existing callbacks associated with a module, these will run in addition to any passed in at runtime.\n",
-    "\n",
-    "## Next steps\n",
-    "\n",
-    "You've now learned how to pass callbacks at runtime.\n",
-    "\n",
-    "Next, check out the other how-to guides in this section, such as how to [pass callbacks into a module constructor](/docs/how_to/custom_callbacks)."
-   ]
-  }
- ],
- "metadata": {
-  "kernelspec": {
-   "display_name": "Python 3",
-   "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.5"
-  }
- },
- "nbformat": 4,
- "nbformat_minor": 2
-}

docs/docs/how_to/character_text_splitter.ipynb

@@ -1,19 +1,5 @@
 {
  "cells": [
-  {
-   "cell_type": "raw",
-   "id": "f781411d",
-   "metadata": {
-    "vscode": {
-     "languageId": "raw"
-    }
-   },
-   "source": [
-    "---\n",
-    "keywords: [charactertextsplitter]\n",
-    "---"
-   ]
-  },
   {
    "cell_type": "markdown",
    "id": "c3ee8d00",

docs/docs/how_to/chat_model_caching.ipynb

@@ -170,7 +170,7 @@
    "outputs": [],
    "source": [
     "# We can do the same thing with a SQLite cache\n",
-    "from langchain_community.cache import SQLiteCache\n",
+    "from langchain.cache import SQLiteCache\n",
     "\n",
     "set_llm_cache(SQLiteCache(database_path=\".langchain.db\"))"
    ]

docs/docs/how_to/chat_models_universal_init.ipynb

@@ -1,157 +0,0 @@
-{
- "cells": [
-  {
-   "cell_type": "markdown",
-   "id": "cfdf4f09-8125-4ed1-8063-6feed57da8a3",
-   "metadata": {},
-   "source": [
-    "# How to init any model in one line\n",
-    "\n",
-    "Many LLM applications let end users specify what model provider and model they want the application to be powered by. This requires writing some logic to initialize different ChatModels based on some user configuration. The `init_chat_model()` helper method makes it easy to initialize a number of different model integrations without having to worry about import paths and class names.\n",
-    "\n",
-    ":::tip Supported models\n",
-    "\n",
-    "See the [init_chat_model()](https://api.python.langchain.com/en/latest/chat_models/langchain.chat_models.base.init_chat_model.html) API reference for a full list of supported integrations.\n",
-    "\n",
-    "Make sure you have the integration packages installed for any model providers you want to support. E.g. you should have `langchain-openai` installed to init an OpenAI model.\n",
-    "\n",
-    ":::"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "165b0de6-9ae3-4e3d-aa98-4fc8a97c4a06",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "%pip install -qU langchain langchain-openai langchain-anthropic langchain-google-vertexai"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "ea2c9f57-a796-45f8-b6f4-3efd3f361a9b",
-   "metadata": {},
-   "source": [
-    "## Basic usage"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 5,
-   "id": "79e14913-803c-4382-9009-5c6af3d75d35",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "GPT-4o: I'm an AI created by OpenAI, and I don't have a personal name. You can call me Assistant! How can I help you today?\n",
-      "\n",
-      "Claude Opus: My name is Claude. It's nice to meet you!\n",
-      "\n",
-      "Gemini 1.5: I am a large language model, trained by Google. I do not have a name. \n",
-      "\n",
-      "\n"
-     ]
-    }
-   ],
-   "source": [
-    "from langchain.chat_models import init_chat_model\n",
-    "\n",
-    "# Returns a langchain_openai.ChatOpenAI instance.\n",
-    "gpt_4o = init_chat_model(\"gpt-4o\", model_provider=\"openai\", temperature=0)\n",
-    "# Returns a langchain_anthropic.ChatAnthropic instance.\n",
-    "claude_opus = init_chat_model(\n",
-    "    \"claude-3-opus-20240229\", model_provider=\"anthropic\", temperature=0\n",
-    ")\n",
-    "# Returns a langchain_google_vertexai.ChatVertexAI instance.\n",
-    "gemini_15 = init_chat_model(\n",
-    "    \"gemini-1.5-pro\", model_provider=\"google_vertexai\", temperature=0\n",
-    ")\n",
-    "\n",
-    "# Since all model integrations implement the ChatModel interface, you can use them in the same way.\n",
-    "print(\"GPT-4o: \" + gpt_4o.invoke(\"what's your name\").content + \"\\n\")\n",
-    "print(\"Claude Opus: \" + claude_opus.invoke(\"what's your name\").content + \"\\n\")\n",
-    "print(\"Gemini 1.5: \" + gemini_15.invoke(\"what's your name\").content + \"\\n\")"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "fff9a4c8-b6ee-4a1a-8d3d-0ecaa312d4ed",
-   "metadata": {},
-   "source": [
-    "## Simple config example"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "75c25d39-bf47-4b51-a6c6-64d9c572bfd6",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "user_config = {\n",
-    "    \"model\": \"...user-specified...\",\n",
-    "    \"model_provider\": \"...user-specified...\",\n",
-    "    \"temperature\": 0,\n",
-    "    \"max_tokens\": 1000,\n",
-    "}\n",
-    "\n",
-    "llm = init_chat_model(**user_config)\n",
-    "llm.invoke(\"what's your name\")"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "f811f219-5e78-4b62-b495-915d52a22532",
-   "metadata": {},
-   "source": [
-    "## Inferring model provider\n",
-    "\n",
-    "For common and distinct model names `init_chat_model()` will attempt to infer the model provider. See the [API reference](https://api.python.langchain.com/en/latest/chat_models/langchain.chat_models.base.init_chat_model.html) for a full list of inference behavior. E.g. any model that starts with `gpt-3...` or `gpt-4...` will be inferred as using model provider `openai`."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 4,
-   "id": "0378ccc6-95bc-4d50-be50-fccc193f0a71",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "gpt_4o = init_chat_model(\"gpt-4o\", temperature=0)\n",
-    "claude_opus = init_chat_model(\"claude-3-opus-20240229\", temperature=0)\n",
-    "gemini_15 = init_chat_model(\"gemini-1.5-pro\", temperature=0)"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "da07b5c0-d2e6-42e4-bfcd-2efcfaae6221",
-   "metadata": {},
-   "outputs": [],
-   "source": []
-  }
- ],
- "metadata": {
-  "kernelspec": {
-   "display_name": "poetry-venv-2",
-   "language": "python",
-   "name": "poetry-venv-2"
-  },
-  "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/how_to/chat_token_usage_tracking.ipynb

@@ -14,51 +14,35 @@
     "\n",
     ":::\n",
     "\n",
-    "Tracking token usage to calculate cost is an important part of putting your app in production. This guide goes over how to obtain this information from your LangChain model calls.\n",
-    "\n",
-    "This guide requires `langchain-openai >= 0.1.8`."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "9c7d1338-dd1b-4d06-b33d-d5cffc49fd6a",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "%pip install --upgrade --quiet langchain langchain-openai"
+    "Tracking token usage to calculate cost is an important part of putting your app in production. This guide goes over how to obtain this information from your LangChain model calls."
    ]
   },
   {
    "cell_type": "markdown",
-   "id": "598ae1e2-a52d-4459-81fd-cdc68b06742a",
+   "id": "1a55e87a-3291-4e7f-8e8e-4c69b0854384",
    "metadata": {},
    "source": [
-    "## Using LangSmith\n",
+    "## Using AIMessage.response_metadata\n",
     "\n",
-    "You can use [LangSmith](https://www.langchain.com/langsmith) to help track token usage in your LLM application. See the [LangSmith quick start guide](https://docs.smith.langchain.com/).\n",
-    "\n",
-    "## Using AIMessage.usage_metadata\n",
-    "\n",
-    "A number of model providers return token usage information as part of the chat generation response. When available, this information will be included on the `AIMessage` objects produced by the corresponding model.\n",
-    "\n",
-    "LangChain `AIMessage` objects include a [usage_metadata](https://api.python.langchain.com/en/latest/messages/langchain_core.messages.ai.AIMessage.html#langchain_core.messages.ai.AIMessage.usage_metadata) attribute. When populated, this attribute will be a [UsageMetadata](https://api.python.langchain.com/en/latest/messages/langchain_core.messages.ai.UsageMetadata.html) dictionary with standard keys (e.g., `\"input_tokens\"` and `\"output_tokens\"`).\n",
-    "\n",
-    "Examples:\n",
-    "\n",
-    "**OpenAI**:"
+    "A number of model providers return token usage information as part of the chat generation response. When available, this is included in the [`AIMessage.response_metadata`](/docs/how_to/response_metadata) field. Here's an example with OpenAI:"
    ]
   },
   {
    "cell_type": "code",
    "execution_count": 1,
-   "id": "b39bf807-4125-4db4-bbf7-28a46afff6b4",
+   "id": "467ccdeb-6b62-45e5-816e-167cd24d2586",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "{'input_tokens': 8, 'output_tokens': 9, 'total_tokens': 17}"
+       "{'token_usage': {'completion_tokens': 225,\n",
+       "  'prompt_tokens': 17,\n",
+       "  'total_tokens': 242},\n",
+       " 'model_name': 'gpt-4-turbo',\n",
+       " 'system_fingerprint': 'fp_76f018034d',\n",
+       " 'finish_reason': 'stop',\n",
+       " 'logprobs': None}"
       ]
      },
      "execution_count": 1,
@@ -67,33 +51,37 @@
     }
    ],
    "source": [
-    "# # !pip install -qU langchain-openai\n",
+    "# !pip install -qU langchain-openai\n",
     "\n",
     "from langchain_openai import ChatOpenAI\n",
     "\n",
-    "llm = ChatOpenAI(model=\"gpt-3.5-turbo-0125\")\n",
-    "openai_response = llm.invoke(\"hello\")\n",
-    "openai_response.usage_metadata"
+    "llm = ChatOpenAI(model=\"gpt-4-turbo\")\n",
+    "msg = llm.invoke([(\"human\", \"What's the oldest known example of cuneiform\")])\n",
+    "msg.response_metadata"
    ]
   },
   {
    "cell_type": "markdown",
-   "id": "2299c44a-2fe6-4d52-a6a2-99ff6d231c73",
+   "id": "9d5026e9-3ad4-41e6-9946-9f1a26f4a21f",
    "metadata": {},
    "source": [
-    "**Anthropic**:"
+    "And here's an example with Anthropic:"
    ]
   },
   {
    "cell_type": "code",
    "execution_count": 2,
-   "id": "9c82ff80-ec4e-4049-b019-5f0bbd7df82a",
+   "id": "145404f1-e088-4824-b468-236c486a9903",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "{'input_tokens': 8, 'output_tokens': 12, 'total_tokens': 20}"
+       "{'id': 'msg_01P61rdHbapEo6h3fjpfpCQT',\n",
+       " 'model': 'claude-3-sonnet-20240229',\n",
+       " 'stop_reason': 'end_turn',\n",
+       " 'stop_sequence': None,\n",
+       " 'usage': {'input_tokens': 17, 'output_tokens': 306}}"
       ]
      },
      "execution_count": 2,
@@ -106,222 +94,9 @@
     "\n",
     "from langchain_anthropic import ChatAnthropic\n",
     "\n",
-    "llm = ChatAnthropic(model=\"claude-3-haiku-20240307\")\n",
-    "anthropic_response = llm.invoke(\"hello\")\n",
-    "anthropic_response.usage_metadata"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "6d4efc15-ba9f-4b3d-9278-8e01f99f263f",
-   "metadata": {},
-   "source": [
-    "### Using AIMessage.response_metadata\n",
-    "\n",
-    "Metadata from the model response is also included in the AIMessage [response_metadata](https://api.python.langchain.com/en/latest/messages/langchain_core.messages.ai.AIMessage.html#langchain_core.messages.ai.AIMessage.response_metadata) attribute. These data are typically not standardized. Note that different providers adopt different conventions for representing token counts:"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 3,
-   "id": "f156f9da-21f2-4c81-a714-54cbf9ad393e",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "OpenAI: {'completion_tokens': 9, 'prompt_tokens': 8, 'total_tokens': 17}\n",
-      "\n",
-      "Anthropic: {'input_tokens': 8, 'output_tokens': 12}\n"
-     ]
-    }
-   ],
-   "source": [
-    "print(f'OpenAI: {openai_response.response_metadata[\"token_usage\"]}\\n')\n",
-    "print(f'Anthropic: {anthropic_response.response_metadata[\"usage\"]}')"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "b4ef2c43-0ff6-49eb-9782-e4070c9da8d7",
-   "metadata": {},
-   "source": [
-    "### Streaming\n",
-    "\n",
-    "Some providers support token count metadata in a streaming context.\n",
-    "\n",
-    "#### OpenAI\n",
-    "\n",
-    "For example, OpenAI will return a message [chunk](https://api.python.langchain.com/en/latest/messages/langchain_core.messages.ai.AIMessageChunk.html) at the end of a stream with token usage information. This behavior is supported by `langchain-openai >= 0.1.8` and can be enabled by setting `stream_options={\"include_usage\": True}`.\n",
-    "\n",
-    "```{=mdx}\n",
-    ":::note\n",
-    "By default, the last message chunk in a stream will include a `\"finish_reason\"` in the message's `response_metadata` attribute. If we include token usage in streaming mode, an additional chunk containing usage metadata will be added to the end of the stream, such that `\"finish_reason\"` appears on the second to last message chunk.\n",
-    ":::\n",
-    "```"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 4,
-   "id": "07f0c872-6b6c-4fed-a129-9b5a858505be",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "content='' id='run-b40e502e-d30e-4617-94ad-95b4dfee14bf'\n",
-      "content='Hello' id='run-b40e502e-d30e-4617-94ad-95b4dfee14bf'\n",
-      "content='!' id='run-b40e502e-d30e-4617-94ad-95b4dfee14bf'\n",
-      "content=' How' id='run-b40e502e-d30e-4617-94ad-95b4dfee14bf'\n",
-      "content=' can' id='run-b40e502e-d30e-4617-94ad-95b4dfee14bf'\n",
-      "content=' I' id='run-b40e502e-d30e-4617-94ad-95b4dfee14bf'\n",
-      "content=' assist' id='run-b40e502e-d30e-4617-94ad-95b4dfee14bf'\n",
-      "content=' you' id='run-b40e502e-d30e-4617-94ad-95b4dfee14bf'\n",
-      "content=' today' id='run-b40e502e-d30e-4617-94ad-95b4dfee14bf'\n",
-      "content='?' id='run-b40e502e-d30e-4617-94ad-95b4dfee14bf'\n",
-      "content='' response_metadata={'finish_reason': 'stop'} id='run-b40e502e-d30e-4617-94ad-95b4dfee14bf'\n",
-      "content='' id='run-b40e502e-d30e-4617-94ad-95b4dfee14bf' usage_metadata={'input_tokens': 8, 'output_tokens': 9, 'total_tokens': 17}\n"
-     ]
-    }
-   ],
-   "source": [
-    "llm = ChatOpenAI(model=\"gpt-3.5-turbo-0125\")\n",
-    "\n",
-    "aggregate = None\n",
-    "for chunk in llm.stream(\"hello\", stream_options={\"include_usage\": True}):\n",
-    "    print(chunk)\n",
-    "    aggregate = chunk if aggregate is None else aggregate + chunk"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "dd809ded-8b13-4d5f-be5e-277b79d51802",
-   "metadata": {},
-   "source": [
-    "Note that the usage metadata will be included in the sum of the individual message chunks:"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 5,
-   "id": "3db7bc03-a7d4-4704-92ab-f8ba92ef59ae",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "Hello! How can I assist you today?\n",
-      "{'input_tokens': 8, 'output_tokens': 9, 'total_tokens': 17}\n"
-     ]
-    }
-   ],
-   "source": [
-    "print(aggregate.content)\n",
-    "print(aggregate.usage_metadata)"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "7dba63e8-0ed7-4533-8f0f-78e19c38a25c",
-   "metadata": {},
-   "source": [
-    "To disable streaming token counts for OpenAI, set `\"include_usage\"` to False in `stream_options`, or omit it from the parameters:"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 6,
-   "id": "67117f2b-ce68-4c1e-9556-2d3849f90e1b",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "content='' id='run-0085d64c-13d2-431b-a0fa-399be8cd3c52'\n",
-      "content='Hello' id='run-0085d64c-13d2-431b-a0fa-399be8cd3c52'\n",
-      "content='!' id='run-0085d64c-13d2-431b-a0fa-399be8cd3c52'\n",
-      "content=' How' id='run-0085d64c-13d2-431b-a0fa-399be8cd3c52'\n",
-      "content=' can' id='run-0085d64c-13d2-431b-a0fa-399be8cd3c52'\n",
-      "content=' I' id='run-0085d64c-13d2-431b-a0fa-399be8cd3c52'\n",
-      "content=' assist' id='run-0085d64c-13d2-431b-a0fa-399be8cd3c52'\n",
-      "content=' you' id='run-0085d64c-13d2-431b-a0fa-399be8cd3c52'\n",
-      "content=' today' id='run-0085d64c-13d2-431b-a0fa-399be8cd3c52'\n",
-      "content='?' id='run-0085d64c-13d2-431b-a0fa-399be8cd3c52'\n",
-      "content='' response_metadata={'finish_reason': 'stop'} id='run-0085d64c-13d2-431b-a0fa-399be8cd3c52'\n"
-     ]
-    }
-   ],
-   "source": [
-    "aggregate = None\n",
-    "for chunk in llm.stream(\"hello\"):\n",
-    "    print(chunk)"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "6a5d9617-be3a-419a-9276-de9c29fa50ae",
-   "metadata": {},
-   "source": [
-    "You can also enable streaming token usage by setting `model_kwargs` when instantiating the chat model. This can be useful when incorporating chat models into LangChain [chains](/docs/concepts#langchain-expression-language-lcel): usage metadata can be monitored when [streaming intermediate steps](/docs/how_to/streaming#using-stream-events) or using tracing software such as [LangSmith](https://docs.smith.langchain.com/).\n",
-    "\n",
-    "See the below example, where we return output structured to a desired schema, but can still observe token usage streamed from intermediate steps."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 8,
-   "id": "57dec1fb-bd9c-4c98-8798-8fbbe67f6b2c",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "Token usage: {'input_tokens': 79, 'output_tokens': 23, 'total_tokens': 102}\n",
-      "\n",
-      "setup='Why was the math book sad?' punchline='Because it had too many problems.'\n"
-     ]
-    }
-   ],
-   "source": [
-    "from langchain_core.pydantic_v1 import BaseModel, Field\n",
-    "\n",
-    "\n",
-    "class Joke(BaseModel):\n",
-    "    \"\"\"Joke to tell user.\"\"\"\n",
-    "\n",
-    "    setup: str = Field(description=\"question to set up a joke\")\n",
-    "    punchline: str = Field(description=\"answer to resolve the joke\")\n",
-    "\n",
-    "\n",
-    "llm = ChatOpenAI(\n",
-    "    model=\"gpt-3.5-turbo-0125\",\n",
-    "    model_kwargs={\"stream_options\": {\"include_usage\": True}},\n",
-    ")\n",
-    "# Under the hood, .with_structured_output binds tools to the\n",
-    "# chat model and appends a parser.\n",
-    "structured_llm = llm.with_structured_output(Joke)\n",
-    "\n",
-    "async for event in structured_llm.astream_events(\"Tell me a joke\", version=\"v2\"):\n",
-    "    if event[\"event\"] == \"on_chat_model_end\":\n",
-    "        print(f'Token usage: {event[\"data\"][\"output\"].usage_metadata}\\n')\n",
-    "    elif event[\"event\"] == \"on_chain_end\":\n",
-    "        print(event[\"data\"][\"output\"])\n",
-    "    else:\n",
-    "        pass"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "2bc8d313-4bef-463e-89a5-236d8bb6ab2f",
-   "metadata": {},
-   "source": [
-    "Token usage is also visible in the corresponding [LangSmith trace](https://smith.langchain.com/public/fe6513d5-7212-4045-82e0-fefa28bc7656/r) in the payload from the chat model."
+    "llm = ChatAnthropic(model=\"claude-3-sonnet-20240229\")\n",
+    "msg = llm.invoke([(\"human\", \"What's the oldest known example of cuneiform\")])\n",
+    "msg.response_metadata"
    ]
   },
   {
@@ -340,7 +115,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 9,
+   "execution_count": 5,
    "id": "31667d54",
    "metadata": {},
    "outputs": [
@@ -348,11 +123,11 @@
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "Tokens Used: 27\n",
+      "Tokens Used: 26\n",
       "\tPrompt Tokens: 11\n",
-      "\tCompletion Tokens: 16\n",
+      "\tCompletion Tokens: 15\n",
       "Successful Requests: 1\n",
-      "Total Cost (USD): $2.95e-05\n"
+      "Total Cost (USD): $0.00056\n"
      ]
     }
    ],
@@ -361,7 +136,7 @@
     "\n",
     "from langchain_community.callbacks.manager import get_openai_callback\n",
     "\n",
-    "llm = ChatOpenAI(model=\"gpt-3.5-turbo-0125\", temperature=0)\n",
+    "llm = ChatOpenAI(model=\"gpt-4-turbo\", temperature=0)\n",
     "\n",
     "with get_openai_callback() as cb:\n",
     "    result = llm.invoke(\"Tell me a joke\")\n",
@@ -378,7 +153,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 10,
+   "execution_count": 6,
    "id": "e09420f4",
    "metadata": {},
    "outputs": [
@@ -386,7 +161,7 @@
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "55\n"
+      "52\n"
      ]
     }
    ],
@@ -397,39 +172,6 @@
     "    print(cb.total_tokens)"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "id": "9ac51188-c8f4-4230-90fd-3cd78cdd955d",
-   "metadata": {},
-   "source": [
-    "```{=mdx}\n",
-    ":::note\n",
-    "Cost information is currently not available in streaming mode. This is because model names are currently not propagated through chunks in streaming mode, and the model name is used to look up the correct pricing. Token counts however are available:\n",
-    ":::\n",
-    "```"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 11,
-   "id": "b241069a-265d-4497-af34-b0a5f95ae67f",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "28\n"
-     ]
-    }
-   ],
-   "source": [
-    "with get_openai_callback() as cb:\n",
-    "    for chunk in llm.stream(\"Tell me a joke\", stream_options={\"include_usage\": True}):\n",
-    "        pass\n",
-    "    print(cb.total_tokens)"
-   ]
-  },
   {
    "cell_type": "markdown",
    "id": "d8186e7b",
@@ -440,7 +182,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 12,
+   "execution_count": 17,
    "id": "5d1125c6",
    "metadata": {},
    "outputs": [],
@@ -469,15 +211,15 @@
    "source": [
     "```{=mdx}\n",
     ":::note\n",
-    "We have to set `stream_runnable=False` for cost information, as described above. By default the AgentExecutor will stream the underlying agent so that you can get the most granular results when streaming events via AgentExecutor.stream_events.\n",
+    "We have to set `stream_runnable=False` for token counting to work. By default the AgentExecutor will stream the underlying agent so that you can get the most granular results when streaming events via AgentExecutor.stream_events. However, OpenAI does not return token counts when streaming model responses, so we need to turn off the underlying streaming.\n",
     ":::\n",
     "```"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 13,
-   "id": "3950d88b-8bfb-4294-b75b-e6fd421e633c",
+   "execution_count": 18,
+   "id": "2f98c536",
    "metadata": {},
    "outputs": [
     {
@@ -488,51 +230,46 @@
       "\n",
       "\u001b[1m> Entering new AgentExecutor chain...\u001b[0m\n",
       "\u001b[32;1m\u001b[1;3m\n",
-      "Invoking: `wikipedia` with `{'query': 'hummingbird scientific name'}`\n",
+      "Invoking: `wikipedia` with `Hummingbird`\n",
       "\n",
       "\n",
       "\u001b[0m\u001b[36;1m\u001b[1;3mPage: Hummingbird\n",
-      "Summary: Hummingbirds are birds native to the Americas and comprise the biological family Trochilidae. With approximately 366 species and 113 genera, they occur from Alaska to Tierra del Fuego, but most species are found in Central and South America. As of 2024, 21 hummingbird species are listed as endangered or critically endangered, with numerous species declining in population.\n",
-      "Hummingbirds have varied specialized characteristics to enable rapid, maneuverable flight: exceptional metabolic capacity, adaptations to high altitude, sensitive visual and communication abilities, and long-distance migration in some species. Among all birds, male hummingbirds have the widest diversity of plumage color, particularly in blues, greens, and purples. Hummingbirds are the smallest mature birds, measuring 7.5–13 cm (3–5 in) in length. The smallest is the 5 cm (2.0 in) bee hummingbird, which weighs less than 2.0 g (0.07 oz), and the largest is the 23 cm (9 in) giant hummingbird, weighing 18–24 grams (0.63–0.85 oz). Noted for long beaks, hummingbirds are specialized for feeding on flower nectar, but all species also consume small insects.\n",
+      "Summary: Hummingbirds are birds native to the Americas and comprise the biological family Trochilidae. With approximately 366 species and 113 genera, they occur from Alaska to Tierra del Fuego, but most species are found in Central and South America. As of 2024, 21 hummingbird species are listed as endangered or critically endangered, with numerous species declining in population.Hummingbirds have varied specialized characteristics to enable rapid, maneuverable flight: exceptional metabolic capacity, adaptations to high altitude, sensitive visual and communication abilities, and long-distance migration in some species. Among all birds, male hummingbirds have the widest diversity of plumage color, particularly in blues, greens, and purples. Hummingbirds are the smallest mature birds, measuring 7.5–13 cm (3–5 in) in length. The smallest is the 5 cm (2.0 in) bee hummingbird, which weighs less than 2.0 g (0.07 oz), and the largest is the 23 cm (9 in) giant hummingbird, weighing 18–24 grams (0.63–0.85 oz). Noted for long beaks, hummingbirds are specialized for feeding on flower nectar, but all species also consume small insects.\n",
       "They are known as hummingbirds because of the humming sound created by their beating wings, which flap at high frequencies audible to other birds and humans. They hover at rapid wing-flapping rates, which vary from around 12 beats per second in the largest species to 80 per second in small hummingbirds.\n",
       "Hummingbirds have the highest mass-specific metabolic rate of any homeothermic animal. To conserve energy when food is scarce and at night when not foraging, they can enter torpor, a state similar to hibernation, and slow their metabolic rate to 1⁄15 of its normal rate. While most hummingbirds do not migrate, the rufous hummingbird has one of the longest migrations among birds, traveling twice per year between Alaska and Mexico, a distance of about 3,900 miles (6,300 km).\n",
       "Hummingbirds split from their sister group, the swifts and treeswifts, around 42 million years ago. The oldest known fossil hummingbird is Eurotrochilus, from the Rupelian Stage of Early Oligocene Europe.\n",
       "\n",
-      "Page: Rufous hummingbird\n",
-      "Summary: The rufous hummingbird (Selasphorus rufus) is a small hummingbird, about 8 cm (3.1 in) long with a long, straight and slender bill. These birds are known for their extraordinary flight skills, flying 2,000 mi (3,200 km) during their migratory transits. It is one of nine species in the genus Selasphorus.\n",
       "\n",
       "\n",
+      "Page: Bee hummingbird\n",
+      "Summary: The bee hummingbird, zunzuncito or Helena hummingbird (Mellisuga helenae) is a species of hummingbird, native to the island of Cuba in the Caribbean. It is the smallest known bird. The bee hummingbird feeds on nectar of flowers and bugs found in Cuba.\n",
       "\n",
-      "Page: Anna's hummingbird\n",
-      "Summary: Anna's hummingbird (Calypte anna) is a North American species of hummingbird. It was named after Anna Masséna, Duchess of Rivoli.\n",
-      "It is native to western coastal regions of North America. In the early 20th century, Anna's hummingbirds bred only in northern Baja California and Southern California. The transplanting of exotic ornamental plants in residential areas throughout the Pacific coast and inland deserts provided expanded nectar and nesting sites, allowing the species to expand its breeding range. Year-round residence of Anna's hummingbirds in the Pacific Northwest is an example of ecological release dependent on acclimation to colder winter temperatures, introduced plants, and human provision of nectar feeders during winter.\n",
-      "These birds feed on nectar from flowers using a long extendable tongue. They also consume small insects and other arthropods caught in flight or gleaned from vegetation.\u001b[0m\u001b[32;1m\u001b[1;3m\n",
-      "Invoking: `wikipedia` with `{'query': 'fastest bird species'}`\n",
+      "Page: Hummingbird cake\n",
+      "Summary: Hummingbird cake is a banana-pineapple spice cake originating in Jamaica and a popular dessert in the southern United States since the 1970s. Ingredients include flour, sugar, salt, vegetable oil, ripe banana, pineapple, cinnamon, pecans, vanilla extract, eggs, and leavening agent. It is often served with cream cheese frosting.\u001b[0m\u001b[32;1m\u001b[1;3m\n",
+      "Invoking: `wikipedia` with `Fastest bird`\n",
       "\n",
       "\n",
-      "\u001b[0m\u001b[36;1m\u001b[1;3mPage: List of birds by flight speed\n",
-      "Summary: This is a list of the fastest flying birds in the world. A bird's velocity is necessarily variable; a hunting bird will reach much greater speeds while diving to catch prey than when flying horizontally. The bird that can achieve the greatest airspeed is the peregrine falcon (Falco peregrinus), able to exceed 320 km/h (200 mph) in its dives. A close relative of the common swift, the white-throated needletail (Hirundapus caudacutus), is commonly reported as the fastest bird in level flight with a reported top speed of 169 km/h (105 mph). This record remains unconfirmed as the measurement methods have never been published or verified. The record for the fastest confirmed level flight by a bird is 111.5 km/h (69.3 mph) held by the common swift.\n",
-      "\n",
-      "\n",
-      "\n",
-      "Page: Fastest animals\n",
+      "\u001b[0m\u001b[36;1m\u001b[1;3mPage: Fastest animals\n",
       "Summary: This is a list of the fastest animals in the world, by types of animal.\n",
       "\n",
       "\n",
       "\n",
-      "Page: Falcon\n",
-      "Summary: Falcons () are birds of prey in the genus Falco, which includes about 40 species. Falcons are widely distributed on all continents of the world except Antarctica, though closely related raptors did occur there in the Eocene.\n",
-      "Adult falcons have thin, tapered wings, which enable them to fly at high speed and change direction rapidly. Fledgling falcons, in their first year of flying, have longer flight feathers, which make their configuration more like that of a general-purpose bird such as a broad wing. This makes flying easier while learning the exceptional skills required to be effective hunters as adults.\n",
-      "The falcons are the largest genus in the Falconinae subfamily of Falconidae, which itself also includes another subfamily comprising caracaras and a few other species. All these birds kill with their beaks, using a tomial \"tooth\" on the side of their beaks—unlike the hawks, eagles, and other birds of prey in the Accipitridae, which use their feet.\n",
-      "The largest falcon is the gyrfalcon at up to 65 cm in length.  The smallest falcon species is the pygmy falcon, which measures just 20 cm.  As with hawks and owls, falcons exhibit sexual dimorphism, with the females typically larger than the males, thus allowing a wider range of prey species.\n",
-      "Some small falcons with long, narrow wings are called \"hobbies\" and some which hover while hunting are called \"kestrels\".\n",
-      "As is the case with many birds of prey, falcons have exceptional powers of vision; the visual acuity of one species has been measured at 2.6 times that of a normal human. Peregrine falcons have been recorded diving at speeds of 320 km/h (200 mph), making them the fastest-moving creatures on Earth; the fastest recorded dive attained a vertical speed of 390 km/h (240 mph).\u001b[0m\u001b[32;1m\u001b[1;3mThe scientific name for a hummingbird is Trochilidae. The fastest bird species is the peregrine falcon (Falco peregrinus), which can exceed speeds of 320 km/h (200 mph) in its dives.\u001b[0m\n",
+      "Page: List of birds by flight speed\n",
+      "Summary: This is a list of the fastest flying birds in the world. A bird's velocity is necessarily variable; a hunting bird will reach much greater speeds while diving to catch prey than when flying horizontally. The bird that can achieve the greatest airspeed is the peregrine falcon, able to exceed 320 km/h (200 mph) in its dives. A close relative of the common swift, the white-throated needletail (Hirundapus caudacutus), is commonly reported as the fastest bird in level flight with a reported top speed of 169 km/h (105 mph). This record remains unconfirmed as the measurement methods have never been published or verified. The record for the fastest confirmed level flight by a bird is 111.5 km/h (69.3 mph) held by the common swift.\n",
+      "\n",
+      "Page: Ostrich\n",
+      "Summary: Ostriches are large flightless birds. They are the heaviest and largest living birds, with adult common ostriches weighing anywhere between 63.5 and 145 kilograms and laying the largest eggs of any living land animal. With the ability to run at 70 km/h (43.5 mph), they are the fastest birds on land. They are farmed worldwide, with significant industries in the Philippines and in Namibia. Ostrich leather is a lucrative commodity, and the large feathers are used as plumes for the decoration of ceremonial headgear. Ostrich eggs have been used by humans for millennia.\n",
+      "Ostriches are of the genus Struthio in the order Struthioniformes, part of the infra-class Palaeognathae, a diverse group of flightless birds also known as ratites that includes the emus, rheas, cassowaries, kiwis and the extinct elephant birds and moas. There are two living species of ostrich: the common ostrich, native to large areas of sub-Saharan Africa, and the Somali ostrich, native to the Horn of Africa.  The common ostrich was historically native to the Arabian Peninsula, and ostriches were present across Asia as far east as China and Mongolia during the Late Pleistocene and possibly into the Holocene.\u001b[0m\u001b[32;1m\u001b[1;3m### Hummingbird's Scientific Name\n",
+      "The scientific name for the bee hummingbird, which is the smallest known bird and a species of hummingbird, is **Mellisuga helenae**. It is native to Cuba.\n",
+      "\n",
+      "### Fastest Bird Species\n",
+      "The fastest bird in terms of airspeed is the **peregrine falcon**, which can exceed speeds of 320 km/h (200 mph) during its diving flight. In level flight, the fastest confirmed speed is held by the **common swift**, which can fly at 111.5 km/h (69.3 mph).\u001b[0m\n",
       "\n",
       "\u001b[1m> Finished chain.\u001b[0m\n",
-      "Total Tokens: 1787\n",
-      "Prompt Tokens: 1687\n",
-      "Completion Tokens: 100\n",
-      "Total Cost (USD): $0.0009935\n"
+      "Total Tokens: 1583\n",
+      "Prompt Tokens: 1412\n",
+      "Completion Tokens: 171\n",
+      "Total Cost (USD): $0.019250000000000003\n"
      ]
     }
    ],
@@ -561,19 +298,19 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 12,
-   "id": "1837c807-136a-49d8-9c33-060e58dc16d2",
+   "execution_count": 1,
+   "id": "4a3eced5-2ff7-49a7-a48b-768af8658323",
    "metadata": {},
    "outputs": [
     {
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "Tokens Used: 96\n",
-      "\tPrompt Tokens: 26\n",
-      "\tCompletion Tokens: 70\n",
+      "Tokens Used: 0\n",
+      "\tPrompt Tokens: 0\n",
+      "\tCompletion Tokens: 0\n",
       "Successful Requests: 2\n",
-      "Total Cost (USD): $0.001888\n"
+      "Total Cost (USD): $0.0\n"
      ]
     }
    ],
@@ -627,7 +364,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.10.4"
+   "version": "3.9.1"
   }
  },
  "nbformat": 4,

docs/docs/how_to/chatbots_memory.ipynb

@@ -165,7 +165,7 @@
     }
    ],
    "source": [
-    "from langchain_community.chat_message_histories import ChatMessageHistory\n",
+    "from langchain.memory import ChatMessageHistory\n",
     "\n",
     "demo_ephemeral_chat_history = ChatMessageHistory()\n",
     "\n",

docs/docs/how_to/chatbots_tools.ipynb

@@ -336,7 +336,7 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "from langchain_community.chat_message_histories import ChatMessageHistory\n",
+    "from langchain.memory import ChatMessageHistory\n",
     "from langchain_core.runnables.history import RunnableWithMessageHistory\n",
     "\n",
     "demo_ephemeral_chat_history_for_chain = ChatMessageHistory()\n",

docs/docs/how_to/configure.ipynb

@@ -89,7 +89,7 @@
     }
    ],
    "source": [
-    "from langchain_core.prompts import PromptTemplate\n",
+    "from langchain.prompts import PromptTemplate\n",
     "from langchain_core.runnables import ConfigurableField\n",
     "from langchain_openai import ChatOpenAI\n",
     "\n",
@@ -312,8 +312,8 @@
     }
    ],
    "source": [
+    "from langchain.prompts import PromptTemplate\n",
     "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",

docs/docs/how_to/custom_callbacks.ipynb

@@ -1,141 +0,0 @@
-{
- "cells": [
-  {
-   "cell_type": "markdown",
-   "metadata": {},
-   "source": [
-    "# How to create custom callback handlers\n",
-    "\n",
-    ":::info Prerequisites\n",
-    "\n",
-    "This guide assumes familiarity with the following concepts:\n",
-    "\n",
-    "- [Callbacks](/docs/concepts/#callbacks)\n",
-    "\n",
-    ":::\n",
-    "\n",
-    "LangChain has some built-in callback handlers, but you will often want to create your own handlers with custom logic.\n",
-    "\n",
-    "To create a custom callback handler, we need to determine the [event(s)](https://api.python.langchain.com/en/latest/callbacks/langchain_core.callbacks.base.BaseCallbackHandler.html#langchain-core-callbacks-base-basecallbackhandler) we want our callback handler to handle as well as what we want our callback handler to do when the event is triggered. Then all we need to do is attach the callback handler to the object, for example via [the constructor](/docs/how_to/callbacks_constructor) or [at runtime](/docs/how_to/callbacks_runtime).\n",
-    "\n",
-    "In the example below, we'll implement streaming with a custom handler.\n",
-    "\n",
-    "In our custom callback handler `MyCustomHandler`, we implement the `on_llm_new_token` handler to print the token we have just received. We then attach our custom handler to the model object as a constructor callback."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "# | output: false\n",
-    "# | echo: false\n",
-    "\n",
-    "%pip install -qU langchain langchain_anthropic\n",
-    "\n",
-    "import getpass\n",
-    "import os\n",
-    "\n",
-    "os.environ[\"ANTHROPIC_API_KEY\"] = getpass.getpass()"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 3,
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "My custom handler, token: Here\n",
-      "My custom handler, token: 's\n",
-      "My custom handler, token:  a\n",
-      "My custom handler, token:  bear\n",
-      "My custom handler, token:  joke\n",
-      "My custom handler, token:  for\n",
-      "My custom handler, token:  you\n",
-      "My custom handler, token: :\n",
-      "My custom handler, token: \n",
-      "\n",
-      "Why\n",
-      "My custom handler, token:  di\n",
-      "My custom handler, token: d the\n",
-      "My custom handler, token:  bear\n",
-      "My custom handler, token:  dissol\n",
-      "My custom handler, token: ve\n",
-      "My custom handler, token:  in\n",
-      "My custom handler, token:  water\n",
-      "My custom handler, token: ?\n",
-      "My custom handler, token: \n",
-      "Because\n",
-      "My custom handler, token:  it\n",
-      "My custom handler, token:  was\n",
-      "My custom handler, token:  a\n",
-      "My custom handler, token:  polar\n",
-      "My custom handler, token:  bear\n",
-      "My custom handler, token: !\n"
-     ]
-    }
-   ],
-   "source": [
-    "from langchain_anthropic import ChatAnthropic\n",
-    "from langchain_core.callbacks import BaseCallbackHandler\n",
-    "from langchain_core.prompts import ChatPromptTemplate\n",
-    "\n",
-    "\n",
-    "class MyCustomHandler(BaseCallbackHandler):\n",
-    "    def on_llm_new_token(self, token: str, **kwargs) -> None:\n",
-    "        print(f\"My custom handler, token: {token}\")\n",
-    "\n",
-    "\n",
-    "prompt = ChatPromptTemplate.from_messages([\"Tell me a joke about {animal}\"])\n",
-    "\n",
-    "# To enable streaming, we pass in `streaming=True` to the ChatModel constructor\n",
-    "# Additionally, we pass in our custom handler as a list to the callbacks parameter\n",
-    "model = ChatAnthropic(\n",
-    "    model=\"claude-3-sonnet-20240229\", streaming=True, callbacks=[MyCustomHandler()]\n",
-    ")\n",
-    "\n",
-    "chain = prompt | model\n",
-    "\n",
-    "response = chain.invoke({\"animal\": \"bears\"})"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "metadata": {},
-   "source": [
-    "You can see [this reference page](https://api.python.langchain.com/en/latest/callbacks/langchain_core.callbacks.base.BaseCallbackHandler.html#langchain-core-callbacks-base-basecallbackhandler) for a list of events you can handle. Note that the `handle_chain_*` events run for most LCEL runnables.\n",
-    "\n",
-    "## Next steps\n",
-    "\n",
-    "You've now learned how to create your own custom callback handlers.\n",
-    "\n",
-    "Next, check out the other how-to guides in this section, such as [how to attach callbacks to a runnable](/docs/how_to/callbacks_attach)."
-   ]
-  }
- ],
- "metadata": {
-  "kernelspec": {
-   "display_name": "Python 3",
-   "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.5"
-  }
- },
- "nbformat": 4,
- "nbformat_minor": 2
-}

docs/docs/how_to/custom_tools.ipynb

@@ -5,29 +5,35 @@
    "id": "5436020b",
    "metadata": {},
    "source": [
-    "# How to create custom tools\n",
+    "# How to create custom Tools\n",
     "\n",
-    "When constructing an agent, you will need to provide it with a list of `Tool`s that it can use. Besides the actual function that is called, the Tool consists of several components:\n",
+    "When constructing your own agent, you will need to provide it with a list of Tools that it can use. Besides the actual function that is called, the Tool consists of several components:\n",
     "\n",
-    "| Attribute       | Type                      | Description                                                                                                      |\n",
-    "|-----------------|---------------------------|------------------------------------------------------------------------------------------------------------------|\n",
-    "| name          | str                     | Must be unique within a set of tools provided to an LLM or agent.                                           |\n",
-    "| description   | str                     | Describes what the tool does. Used as context by the LLM or agent.                                       |\n",
-    "| args_schema   | Pydantic BaseModel      | Optional but recommended, can be used to provide more information (e.g., few-shot examples) or validation for expected parameters |\n",
-    "| return_direct   | boolean      | Only relevant for agents. When True, after invoking the given tool, the agent will stop and return the result direcly to the user.  |\n",
+    "- `name` (str), is required and must be unique within a set of tools provided to an agent\n",
+    "- `description` (str), is optional but recommended, as it is used by an agent to determine tool use\n",
+    "- `args_schema` (Pydantic BaseModel), is optional but recommended, can be used to provide more information (e.g., few-shot examples) or validation for expected parameters.\n",
     "\n",
-    "LangChain provides 3 ways to create tools:\n",
     "\n",
-    "1. Using [@tool decorator](https://api.python.langchain.com/en/latest/tools/langchain_core.tools.tool.html#langchain_core.tools.tool) -- the simplest way to define a custom tool.\n",
-    "2. Using [StructuredTool.from_function](https://api.python.langchain.com/en/latest/tools/langchain_core.tools.StructuredTool.html#langchain_core.tools.StructuredTool.from_function) class method -- this is similar to the `@tool` decorator, but allows more configuration and specification of both sync and async implementations.\n",
-    "3. By sub-classing from [BaseTool](https://api.python.langchain.com/en/latest/tools/langchain_core.tools.BaseTool.html) -- This is the most flexible method, it provides the largest degree of control, at the expense of more effort and code.\n",
+    "There are multiple ways to define a tool. In this guide, we will walk through how to do for two functions:\n",
     "\n",
-    "The `@tool` or the `StructuredTool.from_function` class method should be sufficient for most use cases.\n",
+    "1. A made up search function that always returns the string \"LangChain\"\n",
+    "2. A multiplier function that will multiply two numbers by eachother\n",
     "\n",
-    ":::{.callout-tip}\n",
-    "\n",
-    "Models will perform better if the tools have well chosen names, descriptions and JSON schemas.\n",
-    ":::"
+    "The biggest difference here is that the first function only requires one input, while the second one requires multiple. Many agents only work with functions that require single inputs, so it's important to know how to work with those. For the most part, defining these custom tools is the same, but there are some differences."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 37,
+   "id": "1aaba18c",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "# Import things that are needed generically\n",
+    "from langchain.pydantic_v1 import BaseModel, Field\n",
+    "from langchain.tools import BaseTool, StructuredTool, tool"
    ]
   },
   {
@@ -42,8 +48,56 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 1,
-   "id": "cc7005cd-072f-4d37-8453-6297468e5192",
+   "execution_count": 4,
+   "id": "b0ce7de8",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "@tool\n",
+    "def search(query: str) -> str:\n",
+    "    \"\"\"Look up things online.\"\"\"\n",
+    "    return \"LangChain\""
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 7,
+   "id": "e889fa34",
+   "metadata": {},
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "search\n",
+      "search(query: str) -> str - Look up things online.\n",
+      "{'query': {'title': 'Query', 'type': 'string'}}\n"
+     ]
+    }
+   ],
+   "source": [
+    "print(search.name)\n",
+    "print(search.description)\n",
+    "print(search.args)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 8,
+   "id": "0b9694d9",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "@tool\n",
+    "def multiply(a: int, b: int) -> int:\n",
+    "    \"\"\"Multiply two numbers.\"\"\"\n",
+    "    return a * b"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 9,
+   "id": "d7f9395b",
    "metadata": {},
    "outputs": [
     {
@@ -57,45 +111,11 @@
     }
    ],
    "source": [
-    "from langchain_core.tools import tool\n",
-    "\n",
-    "\n",
-    "@tool\n",
-    "def multiply(a: int, b: int) -> int:\n",
-    "    \"\"\"Multiply two numbers.\"\"\"\n",
-    "    return a * b\n",
-    "\n",
-    "\n",
-    "# Let's inspect some of the attributes associated with the tool.\n",
     "print(multiply.name)\n",
     "print(multiply.description)\n",
     "print(multiply.args)"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "id": "96698b67-993a-4c97-b867-333132e1eb14",
-   "metadata": {},
-   "source": [
-    "Or create an **async** implementation, like this:"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 2,
-   "id": "0c0991db-b997-4611-be37-4346e660506b",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "from langchain_core.tools import tool\n",
-    "\n",
-    "\n",
-    "@tool\n",
-    "async def amultiply(a: int, b: int) -> int:\n",
-    "    \"\"\"Multiply two numbers.\"\"\"\n",
-    "    return a * b"
-   ]
-  },
   {
    "cell_type": "markdown",
    "id": "98d6eee9",
@@ -106,164 +126,72 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 3,
-   "id": "9216d03a-f6ea-4216-b7e1-0661823a4c0b",
+   "execution_count": 43,
+   "id": "dbbf4b6c",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "class SearchInput(BaseModel):\n",
+    "    query: str = Field(description=\"should be a search query\")\n",
+    "\n",
+    "\n",
+    "@tool(\"search-tool\", args_schema=SearchInput, return_direct=True)\n",
+    "def search(query: str) -> str:\n",
+    "    \"\"\"Look up things online.\"\"\"\n",
+    "    return \"LangChain\""
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 44,
+   "id": "5950ce32",
    "metadata": {},
    "outputs": [
     {
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "multiplication-tool\n",
-      "multiplication-tool(a: int, b: int) -> int - Multiply two numbers.\n",
-      "{'a': {'title': 'A', 'description': 'first number', 'type': 'integer'}, 'b': {'title': 'B', 'description': 'second number', 'type': 'integer'}}\n",
+      "search-tool\n",
+      "search-tool(query: str) -> str - Look up things online.\n",
+      "{'query': {'title': 'Query', 'description': 'should be a search query', 'type': 'string'}}\n",
       "True\n"
      ]
     }
    ],
    "source": [
-    "from langchain.pydantic_v1 import BaseModel, Field\n",
-    "\n",
-    "\n",
-    "class CalculatorInput(BaseModel):\n",
-    "    a: int = Field(description=\"first number\")\n",
-    "    b: int = Field(description=\"second number\")\n",
-    "\n",
-    "\n",
-    "@tool(\"multiplication-tool\", args_schema=CalculatorInput, return_direct=True)\n",
-    "def multiply(a: int, b: int) -> int:\n",
-    "    \"\"\"Multiply two numbers.\"\"\"\n",
-    "    return a * b\n",
-    "\n",
-    "\n",
-    "# Let's inspect some of the attributes associated with the tool.\n",
-    "print(multiply.name)\n",
-    "print(multiply.description)\n",
-    "print(multiply.args)\n",
-    "print(multiply.return_direct)"
+    "print(search.name)\n",
+    "print(search.description)\n",
+    "print(search.args)\n",
+    "print(search.return_direct)"
    ]
   },
   {
    "cell_type": "markdown",
-   "id": "b63fcc3b",
-   "metadata": {},
-   "source": [
-    "## StructuredTool\n",
-    "\n",
-    "The `StrurcturedTool.from_function` class method provides a bit more configurability than the `@tool` decorator, without requiring much additional code."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 4,
-   "id": "564fbe6f-11df-402d-b135-ef6ff25e1e63",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "6\n",
-      "10\n"
-     ]
-    }
-   ],
-   "source": [
-    "from langchain_core.tools import StructuredTool\n",
-    "\n",
-    "\n",
-    "def multiply(a: int, b: int) -> int:\n",
-    "    \"\"\"Multiply two numbers.\"\"\"\n",
-    "    return a * b\n",
-    "\n",
-    "\n",
-    "async def amultiply(a: int, b: int) -> int:\n",
-    "    \"\"\"Multiply two numbers.\"\"\"\n",
-    "    return a * b\n",
-    "\n",
-    "\n",
-    "calculator = StructuredTool.from_function(func=multiply, coroutine=amultiply)\n",
-    "\n",
-    "print(calculator.invoke({\"a\": 2, \"b\": 3}))\n",
-    "print(await calculator.ainvoke({\"a\": 2, \"b\": 5}))"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "26b3712a-b38d-4582-b6e6-bc7cfb1d6680",
-   "metadata": {},
-   "source": [
-    "To configure it:"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 5,
-   "id": "6bc055d4-1fbe-4db5-8881-9c382eba6b1b",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "6\n",
-      "Calculator\n",
-      "Calculator(a: int, b: int) -> int - multiply numbers\n",
-      "{'a': {'title': 'A', 'description': 'first number', 'type': 'integer'}, 'b': {'title': 'B', 'description': 'second number', 'type': 'integer'}}\n"
-     ]
-    }
-   ],
-   "source": [
-    "class CalculatorInput(BaseModel):\n",
-    "    a: int = Field(description=\"first number\")\n",
-    "    b: int = Field(description=\"second number\")\n",
-    "\n",
-    "\n",
-    "def multiply(a: int, b: int) -> int:\n",
-    "    \"\"\"Multiply two numbers.\"\"\"\n",
-    "    return a * b\n",
-    "\n",
-    "\n",
-    "calculator = StructuredTool.from_function(\n",
-    "    func=multiply,\n",
-    "    name=\"Calculator\",\n",
-    "    description=\"multiply numbers\",\n",
-    "    args_schema=CalculatorInput,\n",
-    "    return_direct=True,\n",
-    "    # coroutine= ... <- you can specify an async method if desired as well\n",
-    ")\n",
-    "\n",
-    "print(calculator.invoke({\"a\": 2, \"b\": 3}))\n",
-    "print(calculator.name)\n",
-    "print(calculator.description)\n",
-    "print(calculator.args)"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "b840074b-9c10-4ca0-aed8-626c52b2398f",
+   "id": "9d11e80c",
    "metadata": {},
    "source": [
     "## Subclass BaseTool\n",
     "\n",
-    "You can define a custom tool by sub-classing from `BaseTool`. This provides maximal control over the tool definition, but requires writing more code."
+    "You can also explicitly define a custom tool by subclassing the BaseTool class. This provides maximal control over the tool definition, but is a bit more work."
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 16,
+   "execution_count": 45,
    "id": "1dad8f8e",
    "metadata": {},
    "outputs": [],
    "source": [
     "from typing import Optional, Type\n",
     "\n",
-    "from langchain.pydantic_v1 import BaseModel\n",
-    "from langchain_core.callbacks import (\n",
+    "from langchain.callbacks.manager import (\n",
     "    AsyncCallbackManagerForToolRun,\n",
     "    CallbackManagerForToolRun,\n",
     ")\n",
-    "from langchain_core.tools import BaseTool\n",
+    "\n",
+    "\n",
+    "class SearchInput(BaseModel):\n",
+    "    query: str = Field(description=\"should be a search query\")\n",
     "\n",
     "\n",
     "class CalculatorInput(BaseModel):\n",
@@ -271,6 +199,24 @@
     "    b: int = Field(description=\"second number\")\n",
     "\n",
     "\n",
+    "class CustomSearchTool(BaseTool):\n",
+    "    name = \"custom_search\"\n",
+    "    description = \"useful for when you need to answer questions about current events\"\n",
+    "    args_schema: Type[BaseModel] = SearchInput\n",
+    "\n",
+    "    def _run(\n",
+    "        self, query: str, run_manager: Optional[CallbackManagerForToolRun] = None\n",
+    "    ) -> str:\n",
+    "        \"\"\"Use the tool.\"\"\"\n",
+    "        return \"LangChain\"\n",
+    "\n",
+    "    async def _arun(\n",
+    "        self, query: str, run_manager: Optional[AsyncCallbackManagerForToolRun] = None\n",
+    "    ) -> str:\n",
+    "        \"\"\"Use the tool asynchronously.\"\"\"\n",
+    "        raise NotImplementedError(\"custom_search does not support async\")\n",
+    "\n",
+    "\n",
     "class CustomCalculatorTool(BaseTool):\n",
     "    name = \"Calculator\"\n",
     "    description = \"useful for when you need to answer questions about math\"\n",
@@ -290,17 +236,35 @@
     "        run_manager: Optional[AsyncCallbackManagerForToolRun] = None,\n",
     "    ) -> str:\n",
     "        \"\"\"Use the tool asynchronously.\"\"\"\n",
-    "        # If the calculation is cheap, you can just delegate to the sync implementation\n",
-    "        # as shown below.\n",
-    "        # If the sync calculation is expensive, you should delete the entire _arun method.\n",
-    "        # LangChain will automatically provide a better implementation that will\n",
-    "        # kick off the task in a thread to make sure it doesn't block other async code.\n",
-    "        return self._run(a, b, run_manager=run_manager.get_sync())"
+    "        raise NotImplementedError(\"Calculator does not support async\")"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 7,
+   "execution_count": 46,
+   "id": "89933e27",
+   "metadata": {},
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "custom_search\n",
+      "useful for when you need to answer questions about current events\n",
+      "{'query': {'title': 'Query', 'description': 'should be a search query', 'type': 'string'}}\n"
+     ]
+    }
+   ],
+   "source": [
+    "search = CustomSearchTool()\n",
+    "print(search.name)\n",
+    "print(search.description)\n",
+    "print(search.args)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 48,
    "id": "bb551c33",
    "metadata": {},
    "outputs": [
@@ -311,9 +275,7 @@
       "Calculator\n",
       "useful for when you need to answer questions about math\n",
       "{'a': {'title': 'A', 'description': 'first number', 'type': 'integer'}, 'b': {'title': 'B', 'description': 'second number', 'type': 'integer'}}\n",
-      "True\n",
-      "6\n",
-      "6\n"
+      "True\n"
      ]
     }
    ],
@@ -322,50 +284,80 @@
     "print(multiply.name)\n",
     "print(multiply.description)\n",
     "print(multiply.args)\n",
-    "print(multiply.return_direct)\n",
-    "\n",
-    "print(multiply.invoke({\"a\": 2, \"b\": 3}))\n",
-    "print(await multiply.ainvoke({\"a\": 2, \"b\": 3}))"
+    "print(multiply.return_direct)"
    ]
   },
   {
    "cell_type": "markdown",
-   "id": "97aba6cc-4bdf-4fab-aff3-d89e7d9c3a09",
+   "id": "b63fcc3b",
    "metadata": {},
    "source": [
-    "## How to create async tools\n",
+    "## StructuredTool dataclass\n",
     "\n",
-    "LangChain Tools implement the [Runnable interface 🏃](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.base.Runnable.html).\n",
-    "\n",
-    "All Runnables expose the `invoke` and `ainvoke` methods (as well as other methods like `batch`, `abatch`, `astream` etc).\n",
-    "\n",
-    "So even if you only provide an `sync` implementation of a tool, you could still use the `ainvoke` interface, but there\n",
-    "are some important things to know:\n",
-    "\n",
-    "* LangChain's by default provides an async implementation that assumes that the function is expensive to compute, so it'll delegate execution to another thread.\n",
-    "* If you're working in an async codebase, you should create async tools rather than sync tools, to avoid incuring a small overhead due to that thread.\n",
-    "* If you need both sync and async implementations, use `StructuredTool.from_function` or sub-class from `BaseTool`.\n",
-    "* If implementing both sync and async, and the sync code is fast to run, override the default LangChain async implementation and simply call the sync code.\n",
-    "* You CANNOT and SHOULD NOT use the sync `invoke` with an `async` tool."
+    "You can also use a `StructuredTool` dataclass. This methods is a mix between the previous two. It's more convenient than inheriting from the BaseTool class, but provides more functionality than just using a decorator."
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 8,
-   "id": "6615cb77-fd4c-4676-8965-f92cc71d4944",
+   "execution_count": 35,
+   "id": "56ff7670",
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "def search_function(query: str):\n",
+    "    return \"LangChain\"\n",
+    "\n",
+    "\n",
+    "search = StructuredTool.from_function(\n",
+    "    func=search_function,\n",
+    "    name=\"Search\",\n",
+    "    description=\"useful for when you need to answer questions about current events\",\n",
+    "    # coroutine= ... <- you can specify an async method if desired as well\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 38,
+   "id": "d3fd3896",
    "metadata": {},
    "outputs": [
     {
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "6\n",
-      "10\n"
+      "Search\n",
+      "Search(query: str) - useful for when you need to answer questions about current events\n",
+      "{'query': {'title': 'Query', 'type': 'string'}}\n"
      ]
     }
    ],
    "source": [
-    "from langchain_core.tools import StructuredTool\n",
+    "print(search.name)\n",
+    "print(search.description)\n",
+    "print(search.args)"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "e9b560f7",
+   "metadata": {},
+   "source": [
+    "You can also define a custom `args_schema` to provide more information about inputs."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 41,
+   "id": "712c1967",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "class CalculatorInput(BaseModel):\n",
+    "    a: int = Field(description=\"first number\")\n",
+    "    b: int = Field(description=\"second number\")\n",
     "\n",
     "\n",
     "def multiply(a: int, b: int) -> int:\n",
@@ -373,223 +365,185 @@
     "    return a * b\n",
     "\n",
     "\n",
-    "calculator = StructuredTool.from_function(func=multiply)\n",
-    "\n",
-    "print(calculator.invoke({\"a\": 2, \"b\": 3}))\n",
-    "print(\n",
-    "    await calculator.ainvoke({\"a\": 2, \"b\": 5})\n",
-    ")  # Uses default LangChain async implementation incurs small overhead"
+    "calculator = StructuredTool.from_function(\n",
+    "    func=multiply,\n",
+    "    name=\"Calculator\",\n",
+    "    description=\"multiply numbers\",\n",
+    "    args_schema=CalculatorInput,\n",
+    "    return_direct=True,\n",
+    "    # coroutine= ... <- you can specify an async method if desired as well\n",
+    ")"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 9,
-   "id": "bb2af583-eadd-41f4-a645-bf8748bd3dcd",
+   "execution_count": 42,
+   "id": "f634081e",
    "metadata": {},
    "outputs": [
     {
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "6\n",
-      "10\n"
+      "Calculator\n",
+      "Calculator(a: int, b: int) -> int - multiply numbers\n",
+      "{'a': {'title': 'A', 'description': 'first number', 'type': 'integer'}, 'b': {'title': 'B', 'description': 'second number', 'type': 'integer'}}\n"
      ]
     }
    ],
    "source": [
-    "from langchain_core.tools import StructuredTool\n",
-    "\n",
-    "\n",
-    "def multiply(a: int, b: int) -> int:\n",
-    "    \"\"\"Multiply two numbers.\"\"\"\n",
-    "    return a * b\n",
-    "\n",
-    "\n",
-    "async def amultiply(a: int, b: int) -> int:\n",
-    "    \"\"\"Multiply two numbers.\"\"\"\n",
-    "    return a * b\n",
-    "\n",
-    "\n",
-    "calculator = StructuredTool.from_function(func=multiply, coroutine=amultiply)\n",
-    "\n",
-    "print(calculator.invoke({\"a\": 2, \"b\": 3}))\n",
-    "print(\n",
-    "    await calculator.ainvoke({\"a\": 2, \"b\": 5})\n",
-    ")  # Uses use provided amultiply without additional overhead"
+    "print(calculator.name)\n",
+    "print(calculator.description)\n",
+    "print(calculator.args)"
    ]
   },
   {
    "cell_type": "markdown",
-   "id": "c80ffdaa-e4ba-4a70-8500-32bf4f60cc1a",
-   "metadata": {},
-   "source": [
-    "You should not and cannot use `.invoke` when providing only an async definition."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 10,
-   "id": "4ad0932c-8610-4278-8c57-f9218f654c8a",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "Raised not implemented error. You should not be doing this.\n"
-     ]
-    }
-   ],
-   "source": [
-    "@tool\n",
-    "async def multiply(a: int, b: int) -> int:\n",
-    "    \"\"\"Multiply two numbers.\"\"\"\n",
-    "    return a * b\n",
-    "\n",
-    "\n",
-    "try:\n",
-    "    multiply.invoke({\"a\": 2, \"b\": 3})\n",
-    "except NotImplementedError:\n",
-    "    print(\"Raised not implemented error. You should not be doing this.\")"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "f9c746a7-88d7-4afb-bcb8-0e98b891e8b6",
+   "id": "f1da459d",
    "metadata": {},
    "source": [
     "## Handling Tool Errors \n",
+    "When a tool encounters an error and the exception is not caught, the agent will stop executing. If you want the agent to continue execution, you can raise a `ToolException` and set `handle_tool_error` accordingly. \n",
     "\n",
-    "If you're using tools with agents, you will likely need an error handling strategy, so the agent can recover from the error and continue execution.\n",
+    "When `ToolException` is thrown, the agent will not stop working, but will handle the exception according to the `handle_tool_error` variable of the tool, and the processing result will be returned to the agent as observation, and printed in red.\n",
     "\n",
-    "A simple strategy is to throw a `ToolException` from inside the tool and specify an error handler using `handle_tool_error`. \n",
-    "\n",
-    "When the error handler is specified, the exception will be caught and the error handler will decide which output to return from the tool.\n",
-    "\n",
-    "You can set `handle_tool_error` to `True`, a string value, or a function. If it's a function, the function should take a `ToolException` as a parameter and return a value.\n",
+    "You can set `handle_tool_error` to `True`, set it a unified string value, or set it as a function. If it's set as a function, the function should take a `ToolException` as a parameter and return a `str` value.\n",
     "\n",
     "Please note that only raising a `ToolException` won't be effective. You need to first set the `handle_tool_error` of the tool because its default value is `False`."
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 11,
-   "id": "7094c0e8-6192-4870-a942-aad5b5ae48fd",
+   "execution_count": null,
+   "id": "f8bf4668",
    "metadata": {},
    "outputs": [],
    "source": [
     "from langchain_core.tools import ToolException\n",
     "\n",
     "\n",
-    "def get_weather(city: str) -> int:\n",
-    "    \"\"\"Get weather for the given city.\"\"\"\n",
-    "    raise ToolException(f\"Error: There is no city by the name of {city}.\")"
+    "def search_tool1(s: str):\n",
+    "    raise ToolException(\"The search tool1 is not available.\")"
    ]
   },
   {
    "cell_type": "markdown",
-   "id": "9d93b217-1d44-4d31-8956-db9ea680ff4f",
+   "id": "7fb56757",
    "metadata": {},
    "source": [
-    "Here's an example with the default `handle_tool_error=True` behavior."
+    "First, let's see what happens if we don't set `handle_tool_error` - it will error."
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 12,
-   "id": "b4d22022-b105-4ccc-a15b-412cb9ea3097",
+   "execution_count": 58,
+   "id": "f3dfbcb0",
+   "metadata": {},
+   "outputs": [
+    {
+     "ename": "ToolException",
+     "evalue": "The search tool1 is not available.",
+     "output_type": "error",
+     "traceback": [
+      "\u001b[0;31m---------------------------------------------------------------------------\u001b[0m",
+      "\u001b[0;31mToolException\u001b[0m                             Traceback (most recent call last)",
+      "Cell \u001b[0;32mIn[58], line 7\u001b[0m\n\u001b[1;32m      1\u001b[0m search \u001b[38;5;241m=\u001b[39m StructuredTool\u001b[38;5;241m.\u001b[39mfrom_function(\n\u001b[1;32m      2\u001b[0m     func\u001b[38;5;241m=\u001b[39msearch_tool1,\n\u001b[1;32m      3\u001b[0m     name\u001b[38;5;241m=\u001b[39m\u001b[38;5;124m\"\u001b[39m\u001b[38;5;124mSearch_tool1\u001b[39m\u001b[38;5;124m\"\u001b[39m,\n\u001b[1;32m      4\u001b[0m     description\u001b[38;5;241m=\u001b[39mdescription,\n\u001b[1;32m      5\u001b[0m )\n\u001b[0;32m----> 7\u001b[0m \u001b[43msearch\u001b[49m\u001b[38;5;241;43m.\u001b[39;49m\u001b[43mrun\u001b[49m\u001b[43m(\u001b[49m\u001b[38;5;124;43m\"\u001b[39;49m\u001b[38;5;124;43mtest\u001b[39;49m\u001b[38;5;124;43m\"\u001b[39;49m\u001b[43m)\u001b[49m\n",
+      "File \u001b[0;32m~/workplace/langchain/libs/core/langchain_core/tools.py:344\u001b[0m, in \u001b[0;36mBaseTool.run\u001b[0;34m(self, tool_input, verbose, start_color, color, callbacks, tags, metadata, run_name, **kwargs)\u001b[0m\n\u001b[1;32m    342\u001b[0m \u001b[38;5;28;01mif\u001b[39;00m \u001b[38;5;129;01mnot\u001b[39;00m \u001b[38;5;28mself\u001b[39m\u001b[38;5;241m.\u001b[39mhandle_tool_error:\n\u001b[1;32m    343\u001b[0m     run_manager\u001b[38;5;241m.\u001b[39mon_tool_error(e)\n\u001b[0;32m--> 344\u001b[0m     \u001b[38;5;28;01mraise\u001b[39;00m e\n\u001b[1;32m    345\u001b[0m \u001b[38;5;28;01melif\u001b[39;00m \u001b[38;5;28misinstance\u001b[39m(\u001b[38;5;28mself\u001b[39m\u001b[38;5;241m.\u001b[39mhandle_tool_error, \u001b[38;5;28mbool\u001b[39m):\n\u001b[1;32m    346\u001b[0m     \u001b[38;5;28;01mif\u001b[39;00m e\u001b[38;5;241m.\u001b[39margs:\n",
+      "File \u001b[0;32m~/workplace/langchain/libs/core/langchain_core/tools.py:337\u001b[0m, in \u001b[0;36mBaseTool.run\u001b[0;34m(self, tool_input, verbose, start_color, color, callbacks, tags, metadata, run_name, **kwargs)\u001b[0m\n\u001b[1;32m    334\u001b[0m \u001b[38;5;28;01mtry\u001b[39;00m:\n\u001b[1;32m    335\u001b[0m     tool_args, tool_kwargs \u001b[38;5;241m=\u001b[39m \u001b[38;5;28mself\u001b[39m\u001b[38;5;241m.\u001b[39m_to_args_and_kwargs(parsed_input)\n\u001b[1;32m    336\u001b[0m     observation \u001b[38;5;241m=\u001b[39m (\n\u001b[0;32m--> 337\u001b[0m         \u001b[38;5;28;43mself\u001b[39;49m\u001b[38;5;241;43m.\u001b[39;49m\u001b[43m_run\u001b[49m\u001b[43m(\u001b[49m\u001b[38;5;241;43m*\u001b[39;49m\u001b[43mtool_args\u001b[49m\u001b[43m,\u001b[49m\u001b[43m \u001b[49m\u001b[43mrun_manager\u001b[49m\u001b[38;5;241;43m=\u001b[39;49m\u001b[43mrun_manager\u001b[49m\u001b[43m,\u001b[49m\u001b[43m \u001b[49m\u001b[38;5;241;43m*\u001b[39;49m\u001b[38;5;241;43m*\u001b[39;49m\u001b[43mtool_kwargs\u001b[49m\u001b[43m)\u001b[49m\n\u001b[1;32m    338\u001b[0m         \u001b[38;5;28;01mif\u001b[39;00m new_arg_supported\n\u001b[1;32m    339\u001b[0m         \u001b[38;5;28;01melse\u001b[39;00m \u001b[38;5;28mself\u001b[39m\u001b[38;5;241m.\u001b[39m_run(\u001b[38;5;241m*\u001b[39mtool_args, \u001b[38;5;241m*\u001b[39m\u001b[38;5;241m*\u001b[39mtool_kwargs)\n\u001b[1;32m    340\u001b[0m     )\n\u001b[1;32m    341\u001b[0m \u001b[38;5;28;01mexcept\u001b[39;00m ToolException \u001b[38;5;28;01mas\u001b[39;00m e:\n\u001b[1;32m    342\u001b[0m     \u001b[38;5;28;01mif\u001b[39;00m \u001b[38;5;129;01mnot\u001b[39;00m \u001b[38;5;28mself\u001b[39m\u001b[38;5;241m.\u001b[39mhandle_tool_error:\n",
+      "File \u001b[0;32m~/workplace/langchain/libs/core/langchain_core/tools.py:631\u001b[0m, in \u001b[0;36mStructuredTool._run\u001b[0;34m(self, run_manager, *args, **kwargs)\u001b[0m\n\u001b[1;32m    622\u001b[0m \u001b[38;5;28;01mif\u001b[39;00m \u001b[38;5;28mself\u001b[39m\u001b[38;5;241m.\u001b[39mfunc:\n\u001b[1;32m    623\u001b[0m     new_argument_supported \u001b[38;5;241m=\u001b[39m signature(\u001b[38;5;28mself\u001b[39m\u001b[38;5;241m.\u001b[39mfunc)\u001b[38;5;241m.\u001b[39mparameters\u001b[38;5;241m.\u001b[39mget(\u001b[38;5;124m\"\u001b[39m\u001b[38;5;124mcallbacks\u001b[39m\u001b[38;5;124m\"\u001b[39m)\n\u001b[1;32m    624\u001b[0m     \u001b[38;5;28;01mreturn\u001b[39;00m (\n\u001b[1;32m    625\u001b[0m         \u001b[38;5;28mself\u001b[39m\u001b[38;5;241m.\u001b[39mfunc(\n\u001b[1;32m    626\u001b[0m             \u001b[38;5;241m*\u001b[39margs,\n\u001b[1;32m    627\u001b[0m             callbacks\u001b[38;5;241m=\u001b[39mrun_manager\u001b[38;5;241m.\u001b[39mget_child() \u001b[38;5;28;01mif\u001b[39;00m run_manager \u001b[38;5;28;01melse\u001b[39;00m \u001b[38;5;28;01mNone\u001b[39;00m,\n\u001b[1;32m    628\u001b[0m             \u001b[38;5;241m*\u001b[39m\u001b[38;5;241m*\u001b[39mkwargs,\n\u001b[1;32m    629\u001b[0m         )\n\u001b[1;32m    630\u001b[0m         \u001b[38;5;28;01mif\u001b[39;00m new_argument_supported\n\u001b[0;32m--> 631\u001b[0m         \u001b[38;5;28;01melse\u001b[39;00m \u001b[38;5;28;43mself\u001b[39;49m\u001b[38;5;241;43m.\u001b[39;49m\u001b[43mfunc\u001b[49m\u001b[43m(\u001b[49m\u001b[38;5;241;43m*\u001b[39;49m\u001b[43margs\u001b[49m\u001b[43m,\u001b[49m\u001b[43m \u001b[49m\u001b[38;5;241;43m*\u001b[39;49m\u001b[38;5;241;43m*\u001b[39;49m\u001b[43mkwargs\u001b[49m\u001b[43m)\u001b[49m\n\u001b[1;32m    632\u001b[0m     )\n\u001b[1;32m    633\u001b[0m \u001b[38;5;28;01mraise\u001b[39;00m \u001b[38;5;167;01mNotImplementedError\u001b[39;00m(\u001b[38;5;124m\"\u001b[39m\u001b[38;5;124mTool does not support sync\u001b[39m\u001b[38;5;124m\"\u001b[39m)\n",
+      "Cell \u001b[0;32mIn[55], line 5\u001b[0m, in \u001b[0;36msearch_tool1\u001b[0;34m(s)\u001b[0m\n\u001b[1;32m      4\u001b[0m \u001b[38;5;28;01mdef\u001b[39;00m \u001b[38;5;21msearch_tool1\u001b[39m(s: \u001b[38;5;28mstr\u001b[39m):\n\u001b[0;32m----> 5\u001b[0m     \u001b[38;5;28;01mraise\u001b[39;00m ToolException(\u001b[38;5;124m\"\u001b[39m\u001b[38;5;124mThe search tool1 is not available.\u001b[39m\u001b[38;5;124m\"\u001b[39m)\n",
+      "\u001b[0;31mToolException\u001b[0m: The search tool1 is not available."
+     ]
+    }
+   ],
+   "source": [
+    "search = StructuredTool.from_function(\n",
+    "    func=search_tool1,\n",
+    "    name=\"Search_tool1\",\n",
+    "    description=\"A bad tool\",\n",
+    ")\n",
+    "\n",
+    "search.run(\"test\")"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "d2475acd",
+   "metadata": {},
+   "source": [
+    "Now, let's set `handle_tool_error` to be True"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 59,
+   "id": "ab81e0f0",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "'Error: There is no city by the name of foobar.'"
+       "'The search tool1 is not available.'"
       ]
      },
-     "execution_count": 12,
+     "execution_count": 59,
      "metadata": {},
      "output_type": "execute_result"
     }
    ],
    "source": [
-    "get_weather_tool = StructuredTool.from_function(\n",
-    "    func=get_weather,\n",
+    "search = StructuredTool.from_function(\n",
+    "    func=search_tool1,\n",
+    "    name=\"Search_tool1\",\n",
+    "    description=\"A bad tool\",\n",
     "    handle_tool_error=True,\n",
     ")\n",
     "\n",
-    "get_weather_tool.invoke({\"city\": \"foobar\"})"
+    "search.run(\"test\")"
    ]
   },
   {
    "cell_type": "markdown",
-   "id": "f91d6dc0-3271-4adc-a155-21f2e62ffa56",
+   "id": "dafbbcbe",
    "metadata": {},
    "source": [
-    "We can set `handle_tool_error` to a string that will always be returned."
+    "We can also define a custom way to handle the tool error"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 13,
-   "id": "3fad1728-d367-4e1b-9b54-3172981271cf",
+   "execution_count": 60,
+   "id": "ad16fbcf",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "\"There is no such city, but it's probably above 0K there!\""
+       "'The following errors occurred during tool execution:The search tool1 is not available.Please try another tool.'"
       ]
      },
-     "execution_count": 13,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
-   "source": [
-    "get_weather_tool = StructuredTool.from_function(\n",
-    "    func=get_weather,\n",
-    "    handle_tool_error=\"There is no such city, but it's probably above 0K there!\",\n",
-    ")\n",
-    "\n",
-    "get_weather_tool.invoke({\"city\": \"foobar\"})"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "b0a640c1-e08f-4413-83b6-f599f304935f",
-   "metadata": {},
-   "source": [
-    "Handling the error using a function:"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 14,
-   "id": "ebfe7c1f-318d-4e58-99e1-f31e69473c46",
-   "metadata": {},
-   "outputs": [
-    {
-     "data": {
-      "text/plain": [
-       "'The following errors occurred during tool execution: `Error: There is no city by the name of foobar.`'"
-      ]
-     },
-     "execution_count": 14,
+     "execution_count": 60,
      "metadata": {},
      "output_type": "execute_result"
     }
    ],
    "source": [
     "def _handle_error(error: ToolException) -> str:\n",
-    "    return f\"The following errors occurred during tool execution: `{error.args[0]}`\"\n",
+    "    return (\n",
+    "        \"The following errors occurred during tool execution:\"\n",
+    "        + error.args[0]\n",
+    "        + \"Please try another tool.\"\n",
+    "    )\n",
     "\n",
     "\n",
-    "get_weather_tool = StructuredTool.from_function(\n",
-    "    func=get_weather,\n",
+    "search = StructuredTool.from_function(\n",
+    "    func=search_tool1,\n",
+    "    name=\"Search_tool1\",\n",
+    "    description=\"A bad tool\",\n",
     "    handle_tool_error=_handle_error,\n",
     ")\n",
     "\n",
-    "get_weather_tool.invoke({\"city\": \"foobar\"})"
+    "search.run(\"test\")"
    ]
   }
  ],
@@ -609,7 +563,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.11.4"
+   "version": "3.10.1"
   },
   "vscode": {
    "interpreter": {

docs/docs/how_to/debugging.ipynb

@@ -12,7 +12,7 @@
     "\n",
     "- Verbose Mode: This adds print statements for \"important\" events in your chain.\n",
     "- Debug Mode: This add logging statements for ALL events in your chain.\n",
-    "- LangSmith Tracing: This logs events to [LangSmith](https://docs.smith.langchain.com/) to allow for visualization there.\n",
+    "- LangSmith Tracing: This logs events to [LangSmith](/docs/langsmith/) to allow for visualization there.\n",
     "\n",
     "|                        | Verbose Mode | Debug Mode | LangSmith Tracing |\n",
     "|------------------------|--------------|------------|-------------------|\n",

docs/docs/how_to/document_loader_pdf.ipynb

@@ -463,7 +463,7 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "from langchain_core.documents import Document\n",
+    "from langchain.docstore.document import Document\n",
     "\n",
     "cur_idx = -1\n",
     "semantic_snippets = []\n",

docs/docs/how_to/dynamic_chain.ipynb

@@ -1,190 +0,0 @@
-{
- "cells": [
-  {
-   "cell_type": "markdown",
-   "id": "50d57bf2-7104-4570-b3e5-90fd71e1bea1",
-   "metadata": {},
-   "source": [
-    "# How to create a dynamic (self-constructing) chain\n",
-    "\n",
-    ":::info Prerequisites\n",
-    "\n",
-    "This guide assumes familiarity with the following:\n",
-    "- [LangChain Expression Language (LCEL)](/docs/concepts/#langchain-expression-language)\n",
-    "- [How to turn any function into a runnable](/docs/how_to/functions)\n",
-    "\n",
-    ":::\n",
-    "\n",
-    "Sometimes we want to construct parts of a chain at runtime, depending on the chain inputs ([routing](/docs/how_to/routing/) is the most common example of this). We can create dynamic chains like this using a very useful property of RunnableLambda's, which is that if a RunnableLambda returns a Runnable, that Runnable is itself invoked. Let's see an example.\n",
-    "\n",
-    "```{=mdx}\n",
-    "import ChatModelTabs from \"@theme/ChatModelTabs\";\n",
-    "\n",
-    "<ChatModelTabs\n",
-    "  customVarName=\"llm\"\n",
-    "/>\n",
-    "```"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 4,
-   "id": "406bffc2-86d0-4cb9-9262-5c1e3442397a",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "# | echo: false\n",
-    "\n",
-    "from langchain_anthropic import ChatAnthropic\n",
-    "\n",
-    "llm = ChatAnthropic(model=\"claude-3-sonnet-20240229\")"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 10,
-   "id": "0ae6692b-983e-40b8-aa2a-6c078d945b9e",
-   "metadata": {},
-   "outputs": [
-    {
-     "data": {
-      "text/plain": [
-       "\"According to the context provided, Egypt's population in 2024 is estimated to be about 111 million.\""
-      ]
-     },
-     "execution_count": 10,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
-   "source": [
-    "from langchain_core.output_parsers import StrOutputParser\n",
-    "from langchain_core.prompts import ChatPromptTemplate\n",
-    "from langchain_core.runnables import Runnable, RunnablePassthrough, chain\n",
-    "\n",
-    "contextualize_instructions = \"\"\"Convert the latest user question into a standalone question given the chat history. Don't answer the question, return the question and nothing else (no descriptive text).\"\"\"\n",
-    "contextualize_prompt = ChatPromptTemplate.from_messages(\n",
-    "    [\n",
-    "        (\"system\", contextualize_instructions),\n",
-    "        (\"placeholder\", \"{chat_history}\"),\n",
-    "        (\"human\", \"{question}\"),\n",
-    "    ]\n",
-    ")\n",
-    "contextualize_question = contextualize_prompt | llm | StrOutputParser()\n",
-    "\n",
-    "qa_instructions = (\n",
-    "    \"\"\"Answer the user question given the following context:\\n\\n{context}.\"\"\"\n",
-    ")\n",
-    "qa_prompt = ChatPromptTemplate.from_messages(\n",
-    "    [(\"system\", qa_instructions), (\"human\", \"{question}\")]\n",
-    ")\n",
-    "\n",
-    "\n",
-    "@chain\n",
-    "def contextualize_if_needed(input_: dict) -> Runnable:\n",
-    "    if input_.get(\"chat_history\"):\n",
-    "        # NOTE: This is returning another Runnable, not an actual output.\n",
-    "        return contextualize_question\n",
-    "    else:\n",
-    "        return RunnablePassthrough()\n",
-    "\n",
-    "\n",
-    "@chain\n",
-    "def fake_retriever(input_: dict) -> str:\n",
-    "    return \"egypt's population in 2024 is about 111 million\"\n",
-    "\n",
-    "\n",
-    "full_chain = (\n",
-    "    RunnablePassthrough.assign(question=contextualize_if_needed).assign(\n",
-    "        context=fake_retriever\n",
-    "    )\n",
-    "    | qa_prompt\n",
-    "    | llm\n",
-    "    | StrOutputParser()\n",
-    ")\n",
-    "\n",
-    "full_chain.invoke(\n",
-    "    {\n",
-    "        \"question\": \"what about egypt\",\n",
-    "        \"chat_history\": [\n",
-    "            (\"human\", \"what's the population of indonesia\"),\n",
-    "            (\"ai\", \"about 276 million\"),\n",
-    "        ],\n",
-    "    }\n",
-    ")"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "5076ddb4-4a99-47ad-b549-8ac27ca3e2c6",
-   "metadata": {},
-   "source": [
-    "The key here is that `contextualize_if_needed` returns another Runnable and not an actual output. This returned Runnable is itself run when the full chain is executed.\n",
-    "\n",
-    "Looking at the trace we can see that, since we passed in chat_history, we executed the contextualize_question chain as part of the full chain: https://smith.langchain.com/public/9e0ae34c-4082-4f3f-beed-34a2a2f4c991/r"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "4fe6ca44-a643-4859-a290-be68403f51f0",
-   "metadata": {},
-   "source": [
-    "Note that the streaming, batching, etc. capabilities of the returned Runnable are all preserved"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 11,
-   "id": "6def37fa-5105-4090-9b07-77cb488ecd9c",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "What\n",
-      " is\n",
-      " the\n",
-      " population\n",
-      " of\n",
-      " Egypt\n",
-      "?\n"
-     ]
-    }
-   ],
-   "source": [
-    "for chunk in contextualize_if_needed.stream(\n",
-    "    {\n",
-    "        \"question\": \"what about egypt\",\n",
-    "        \"chat_history\": [\n",
-    "            (\"human\", \"what's the population of indonesia\"),\n",
-    "            (\"ai\", \"about 276 million\"),\n",
-    "        ],\n",
-    "    }\n",
-    "):\n",
-    "    print(chunk)"
-   ]
-  }
- ],
- "metadata": {
-  "kernelspec": {
-   "display_name": "poetry-venv-2",
-   "language": "python",
-   "name": "poetry-venv-2"
-  },
-  "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/how_to/embed_text.mdx

@@ -75,31 +75,6 @@ Otherwise you can initialize without any params:
 from langchain_cohere import CohereEmbeddings
 
 embeddings_model = CohereEmbeddings()
-```
-
-  </TabItem>
-  <TabItem value="huggingface" label="Hugging Face">
-
-To start we'll need to install the Hugging Face partner package:
-
-```bash
-pip install langchain-huggingface
-```
-
-You can then load any [Sentence Transformers model](https://huggingface.co/models?library=sentence-transformers) from the Hugging Face Hub.
-
-```python
-from langchain_huggingface import HuggingFaceEmbeddings
-
-embeddings_model = HuggingFaceEmbeddings(model_name="sentence-transformers/all-mpnet-base-v2")
-```
-
-You can also leave the `model_name` blank to use the default [sentence-transformers/all-mpnet-base-v2](https://huggingface.co/sentence-transformers/all-mpnet-base-v2) model.
-
-```python
-from langchain_huggingface import HuggingFaceEmbeddings
-
-embeddings_model = HuggingFaceEmbeddings()
 ```
 
   </TabItem>

docs/docs/how_to/ensemble_retriever.ipynb

@@ -4,17 +4,13 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "# How to combine results from multiple retrievers\n",
+    "# How to create an Ensemble Retriever\n",
     "\n",
-    "The [EnsembleRetriever](https://api.python.langchain.com/en/latest/retrievers/langchain.retrievers.ensemble.EnsembleRetriever.html) supports ensembling of results from multiple retrievers. It is initialized with a list of [BaseRetriever](https://api.python.langchain.com/en/latest/retrievers/langchain_core.retrievers.BaseRetriever.html) objects. EnsembleRetrievers rerank the results of the constituent retrievers based on the [Reciprocal Rank Fusion](https://plg.uwaterloo.ca/~gvcormac/cormacksigir09-rrf.pdf) algorithm.\n",
+    "The `EnsembleRetriever` takes a list of retrievers as input and ensemble the results of their `get_relevant_documents()` methods and rerank the results based on the [Reciprocal Rank Fusion](https://plg.uwaterloo.ca/~gvcormac/cormacksigir09-rrf.pdf) algorithm.\n",
     "\n",
     "By leveraging the strengths of different algorithms, the `EnsembleRetriever` can achieve better performance than any single algorithm. \n",
     "\n",
-    "The most common pattern is to combine a sparse retriever (like BM25) with a dense retriever (like embedding similarity), because their strengths are complementary. It is also known as \"hybrid search\". The sparse retriever is good at finding relevant documents based on keywords, while the dense retriever is good at finding relevant documents based on semantic similarity.\n",
-    "\n",
-    "## Basic usage\n",
-    "\n",
-    "Below we demonstrate ensembling of a [BM25Retriever](https://api.python.langchain.com/en/latest/retrievers/langchain_community.retrievers.bm25.BM25Retriever.html) with a retriever derived from the [FAISS vector store](https://api.python.langchain.com/en/latest/vectorstores/langchain_community.vectorstores.faiss.FAISS.html)."
+    "The most common pattern is to combine a sparse retriever (like BM25) with a dense retriever (like embedding similarity), because their strengths are complementary. It is also known as \"hybrid search\". The sparse retriever is good at finding relevant documents based on keywords, while the dense retriever is good at finding relevant documents based on semantic similarity."
    ]
   },
   {
@@ -28,15 +24,22 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 3,
+   "execution_count": 1,
    "metadata": {},
    "outputs": [],
    "source": [
     "from langchain.retrievers import EnsembleRetriever\n",
     "from langchain_community.retrievers import BM25Retriever\n",
     "from langchain_community.vectorstores import FAISS\n",
-    "from langchain_openai import OpenAIEmbeddings\n",
-    "\n",
+    "from langchain_openai import OpenAIEmbeddings"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 14,
+   "metadata": {},
+   "outputs": [],
+   "source": [
     "doc_list_1 = [\n",
     "    \"I like apples\",\n",
     "    \"I like oranges\",\n",
@@ -68,19 +71,19 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 4,
+   "execution_count": 15,
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "[Document(page_content='I like apples', metadata={'source': 1}),\n",
-       " Document(page_content='You like apples', metadata={'source': 2}),\n",
-       " Document(page_content='Apples and oranges are fruits', metadata={'source': 1}),\n",
-       " Document(page_content='You like oranges', metadata={'source': 2})]"
+       "[Document(page_content='You like apples', metadata={'source': 2}),\n",
+       " Document(page_content='I like apples', metadata={'source': 1}),\n",
+       " Document(page_content='You like oranges', metadata={'source': 2}),\n",
+       " Document(page_content='Apples and oranges are fruits', metadata={'source': 1})]"
       ]
      },
-     "execution_count": 4,
+     "execution_count": 15,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -96,17 +99,24 @@
    "source": [
     "## Runtime Configuration\n",
     "\n",
-    "We can also configure the individual retrievers at runtime using [configurable fields](/docs/how_to/configure). Below we update the \"top-k\" parameter for the FAISS retriever specifically:"
+    "We can also configure the retrievers at runtime. In order to do this, we need to mark the fields as configurable"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 5,
+   "execution_count": 16,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain_core.runnables import ConfigurableField"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 17,
    "metadata": {},
    "outputs": [],
    "source": [
-    "from langchain_core.runnables import ConfigurableField\n",
-    "\n",
     "faiss_retriever = faiss_vectorstore.as_retriever(\n",
     "    search_kwargs={\"k\": 2}\n",
     ").configurable_fields(\n",
@@ -115,8 +125,15 @@
     "        name=\"Search Kwargs\",\n",
     "        description=\"The search kwargs to use\",\n",
     "    )\n",
-    ")\n",
-    "\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 18,
+   "metadata": {},
+   "outputs": [],
+   "source": [
     "ensemble_retriever = EnsembleRetriever(\n",
     "    retrievers=[bm25_retriever, faiss_retriever], weights=[0.5, 0.5]\n",
     ")"
@@ -124,22 +141,9 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 6,
+   "execution_count": 19,
    "metadata": {},
-   "outputs": [
-    {
-     "data": {
-      "text/plain": [
-       "[Document(page_content='I like apples', metadata={'source': 1}),\n",
-       " Document(page_content='You like apples', metadata={'source': 2}),\n",
-       " Document(page_content='Apples and oranges are fruits', metadata={'source': 1})]"
-      ]
-     },
-     "execution_count": 6,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
+   "outputs": [],
    "source": [
     "config = {\"configurable\": {\"search_kwargs_faiss\": {\"k\": 1}}}\n",
     "docs = ensemble_retriever.invoke(\"apples\", config=config)\n",
@@ -177,7 +181,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.10.4"
+   "version": "3.10.1"
   }
  },
  "nbformat": 4,

docs/docs/how_to/example_selectors.ipynb

@@ -60,7 +60,7 @@
    "source": [
     "examples = [\n",
     "    {\"input\": \"hi\", \"output\": \"ciao\"},\n",
-    "    {\"input\": \"bye\", \"output\": \"arrivederci\"},\n",
+    "    {\"input\": \"bye\", \"output\": \"arrivaderci\"},\n",
     "    {\"input\": \"soccer\", \"output\": \"calcio\"},\n",
     "]"
    ]
@@ -133,7 +133,7 @@
     {
      "data": {
       "text/plain": [
-       "[{'input': 'bye', 'output': 'arrivederci'}]"
+       "[{'input': 'bye', 'output': 'arrivaderci'}]"
       ]
      },
      "execution_count": 39,
@@ -209,7 +209,7 @@
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "Translate the following words from English to Italian:\n",
+      "Translate the following words from English to Italain:\n",
       "\n",
       "Input: hand -> Output: mano\n",
       "\n",
@@ -222,7 +222,7 @@
     "    example_selector=example_selector,\n",
     "    example_prompt=example_prompt,\n",
     "    suffix=\"Input: {input} -> Output:\",\n",
-    "    prefix=\"Translate the following words from English to Italian:\",\n",
+    "    prefix=\"Translate the following words from English to Italain:\",\n",
     "    input_variables=[\"input\"],\n",
     ")\n",
     "\n",

docs/docs/how_to/example_selectors_length_based.ipynb

@@ -17,8 +17,8 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "from langchain_core.example_selectors import LengthBasedExampleSelector\n",
-    "from langchain_core.prompts import FewShotPromptTemplate, PromptTemplate\n",
+    "from langchain.prompts import FewShotPromptTemplate, PromptTemplate\n",
+    "from langchain.prompts.example_selector import LengthBasedExampleSelector\n",
     "\n",
     "# Examples of a pretend task of creating antonyms.\n",
     "examples = [\n",

docs/docs/how_to/example_selectors_mmr.ipynb

@@ -17,12 +17,12 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "from langchain_community.vectorstores import FAISS\n",
-    "from langchain_core.example_selectors import (\n",
+    "from langchain.prompts import FewShotPromptTemplate, PromptTemplate\n",
+    "from langchain.prompts.example_selector import (\n",
     "    MaxMarginalRelevanceExampleSelector,\n",
     "    SemanticSimilarityExampleSelector,\n",
     ")\n",
-    "from langchain_core.prompts import FewShotPromptTemplate, PromptTemplate\n",
+    "from langchain_community.vectorstores import FAISS\n",
     "from langchain_openai import OpenAIEmbeddings\n",
     "\n",
     "example_prompt = PromptTemplate(\n",

docs/docs/how_to/example_selectors_ngram.ipynb

@@ -19,8 +19,8 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "from langchain_community.example_selectors import NGramOverlapExampleSelector\n",
-    "from langchain_core.prompts import FewShotPromptTemplate, PromptTemplate\n",
+    "from langchain.prompts import FewShotPromptTemplate, PromptTemplate\n",
+    "from langchain.prompts.example_selector.ngram_overlap import NGramOverlapExampleSelector\n",
     "\n",
     "example_prompt = PromptTemplate(\n",
     "    input_variables=[\"input\", \"output\"],\n",

docs/docs/how_to/example_selectors_similarity.ipynb

@@ -17,9 +17,9 @@
    "metadata": {},
    "outputs": [],
    "source": [
+    "from langchain.prompts import FewShotPromptTemplate, PromptTemplate\n",
+    "from langchain.prompts.example_selector import SemanticSimilarityExampleSelector\n",
     "from langchain_chroma import Chroma\n",
-    "from langchain_core.example_selectors import SemanticSimilarityExampleSelector\n",
-    "from langchain_core.prompts import FewShotPromptTemplate, PromptTemplate\n",
     "from langchain_openai import OpenAIEmbeddings\n",
     "\n",
     "example_prompt = PromptTemplate(\n",

docs/docs/how_to/extraction_examples.ipynb

@@ -128,7 +128,7 @@
     "    # Having a good description can help improve extraction results.\n",
     "    name: Optional[str] = Field(..., description=\"The name of the person\")\n",
     "    hair_color: Optional[str] = Field(\n",
-    "        ..., description=\"The color of the person's hair if known\"\n",
+    "        ..., description=\"The color of the peron's eyes if known\"\n",
     "    )\n",
     "    height_in_meters: Optional[str] = Field(..., description=\"Height in METERs\")\n",
     "\n",

docs/docs/how_to/extraction_parse.ipynb

@@ -69,7 +69,7 @@
    "source": [
     "from typing import List, Optional\n",
     "\n",
-    "from langchain_core.output_parsers import PydanticOutputParser\n",
+    "from langchain.output_parsers import PydanticOutputParser\n",
     "from langchain_core.prompts import ChatPromptTemplate\n",
     "from langchain_core.pydantic_v1 import BaseModel, Field, validator\n",
     "\n",

docs/docs/how_to/fallbacks.ipynb

@@ -1,21 +1,11 @@
 {
  "cells": [
-  {
-   "cell_type": "raw",
-   "id": "018f3868-e60d-4db6-a1c6-c6633c66b1f4",
-   "metadata": {},
-   "source": [
-    "---\n",
-    "keywords: [LCEL, fallbacks]\n",
-    "---"
-   ]
-  },
   {
    "cell_type": "markdown",
    "id": "19c9cbd6",
    "metadata": {},
    "source": [
-    "# How to add fallbacks to a runnable\n",
+    "# Fallbacks\n",
     "\n",
     "When working with language models, you may often encounter issues from the underlying APIs, whether these be rate limiting or downtime. Therefore, as you go to move your LLM applications into production it becomes more and more important to safeguard against these. That's why we've introduced the concept of fallbacks. \n",
     "\n",
@@ -53,7 +43,7 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "from langchain_anthropic import ChatAnthropic\n",
+    "from langchain_community.chat_models import ChatAnthropic\n",
     "from langchain_openai import ChatOpenAI"
    ]
   },
@@ -90,8 +80,8 @@
    "outputs": [],
    "source": [
     "# Note that we set max_retries = 0 to avoid retrying on RateLimits, etc\n",
-    "openai_llm = ChatOpenAI(model=\"gpt-3.5-turbo-0125\", max_retries=0)\n",
-    "anthropic_llm = ChatAnthropic(model=\"claude-3-haiku-20240307\")\n",
+    "openai_llm = ChatOpenAI(max_retries=0)\n",
+    "anthropic_llm = ChatAnthropic()\n",
     "llm = openai_llm.with_fallbacks([anthropic_llm])"
    ]
   },
@@ -457,7 +447,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.9.1"
+   "version": "3.11.5"
   }
  },
  "nbformat": 4,

docs/docs/how_to/few_shot_examples.ipynb

@@ -45,7 +45,7 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "from langchain_core.prompts import PromptTemplate\n",
+    "from langchain.prompts.prompt import PromptTemplate\n",
     "\n",
     "example_prompt = PromptTemplate.from_template(\"Question: {question}\\n{answer}\")"
    ]
@@ -222,7 +222,7 @@
     }
    ],
    "source": [
-    "from langchain_core.prompts import FewShotPromptTemplate\n",
+    "from langchain.prompts.few_shot import FewShotPromptTemplate\n",
     "\n",
     "prompt = FewShotPromptTemplate(\n",
     "    examples=examples,\n",
@@ -282,8 +282,8 @@
     }
    ],
    "source": [
+    "from langchain.prompts.example_selector import SemanticSimilarityExampleSelector\n",
     "from langchain_chroma import Chroma\n",
-    "from langchain_core.example_selectors import SemanticSimilarityExampleSelector\n",
     "from langchain_openai import OpenAIEmbeddings\n",
     "\n",
     "example_selector = SemanticSimilarityExampleSelector.from_examples(\n",

docs/docs/how_to/few_shot_examples_chat.ipynb

@@ -88,7 +88,10 @@
    },
    "outputs": [],
    "source": [
-    "from langchain_core.prompts import ChatPromptTemplate, FewShotChatMessagePromptTemplate\n",
+    "from langchain.prompts import (\n",
+    "    ChatPromptTemplate,\n",
+    "    FewShotChatMessagePromptTemplate,\n",
+    ")\n",
     "\n",
     "examples = [\n",
     "    {\"input\": \"2+2\", \"output\": \"4\"},\n",
@@ -215,8 +218,8 @@
    },
    "outputs": [],
    "source": [
+    "from langchain.prompts import SemanticSimilarityExampleSelector\n",
     "from langchain_chroma import Chroma\n",
-    "from langchain_core.example_selectors import SemanticSimilarityExampleSelector\n",
     "from langchain_openai import OpenAIEmbeddings\n",
     "\n",
     "examples = [\n",
@@ -302,7 +305,10 @@
     }
    ],
    "source": [
-    "from langchain_core.prompts import ChatPromptTemplate, FewShotChatMessagePromptTemplate\n",
+    "from langchain.prompts import (\n",
+    "    ChatPromptTemplate,\n",
+    "    FewShotChatMessagePromptTemplate,\n",
+    ")\n",
     "\n",
     "# Define the few-shot prompt.\n",
     "few_shot_prompt = FewShotChatMessagePromptTemplate(\n",

docs/docs/how_to/functions.ipynb

@@ -167,7 +167,7 @@
    "source": [
     "Above, the `@chain` decorator is used to convert `custom_chain` into a runnable, which we invoke with the `.invoke()` method.\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",
+    "If you are using a tracing with [LangSmith](/docs/langsmith/), you should see a `custom_chain` trace in there, with the calls to OpenAI nested underneath.\n",
     "\n",
     "## Automatic coercion in chains\n",
     "\n",

docs/docs/how_to/graph_mapping.ipynb

@@ -300,7 +300,7 @@
     "Entities in the question map to the following database values:\n",
     "{entities_list}\n",
     "Question: {question}\n",
-    "Cypher query:\"\"\"\n",
+    "Cypher query:\"\"\"  # noqa: E501\n",
     "\n",
     "cypher_prompt = ChatPromptTemplate.from_messages(\n",
     "    [\n",
@@ -377,7 +377,7 @@
     "response_template = \"\"\"Based on the the question, Cypher query, and Cypher response, write a natural language response:\n",
     "Question: {question}\n",
     "Cypher query: {query}\n",
-    "Cypher Response: {response}\"\"\"\n",
+    "Cypher Response: {response}\"\"\"  # noqa: E501\n",
     "\n",
     "response_prompt = ChatPromptTemplate.from_messages(\n",
     "    [\n",

docs/docs/how_to/graph_semantic.ipynb

@@ -177,13 +177,14 @@
    "source": [
     "from typing import Optional, Type\n",
     "\n",
-    "# Import things that are needed generically\n",
-    "from langchain.pydantic_v1 import BaseModel, Field\n",
-    "from langchain_core.callbacks import (\n",
+    "from langchain.callbacks.manager import (\n",
     "    AsyncCallbackManagerForToolRun,\n",
     "    CallbackManagerForToolRun,\n",
     ")\n",
-    "from langchain_core.tools import BaseTool\n",
+    "\n",
+    "# Import things that are needed generically\n",
+    "from langchain.pydantic_v1 import BaseModel, Field\n",
+    "from langchain.tools import BaseTool\n",
     "\n",
     "description_query = \"\"\"\n",
     "MATCH (m:Movie|Person)\n",
@@ -226,13 +227,14 @@
    "source": [
     "from typing import Optional, Type\n",
     "\n",
-    "# Import things that are needed generically\n",
-    "from langchain.pydantic_v1 import BaseModel, Field\n",
-    "from langchain_core.callbacks import (\n",
+    "from langchain.callbacks.manager import (\n",
     "    AsyncCallbackManagerForToolRun,\n",
     "    CallbackManagerForToolRun,\n",
     ")\n",
-    "from langchain_core.tools import BaseTool\n",
+    "\n",
+    "# Import things that are needed generically\n",
+    "from langchain.pydantic_v1 import BaseModel, Field\n",
+    "from langchain.tools import BaseTool\n",
     "\n",
     "\n",
     "class InformationInput(BaseModel):\n",
@@ -285,8 +287,8 @@
     "from langchain.agents import AgentExecutor\n",
     "from langchain.agents.format_scratchpad import format_to_openai_function_messages\n",
     "from langchain.agents.output_parsers import OpenAIFunctionsAgentOutputParser\n",
+    "from langchain.prompts import ChatPromptTemplate, MessagesPlaceholder\n",
     "from langchain_core.messages import AIMessage, HumanMessage\n",
-    "from langchain_core.prompts import ChatPromptTemplate, MessagesPlaceholder\n",
     "from langchain_core.utils.function_calling import convert_to_openai_function\n",
     "from langchain_openai import ChatOpenAI\n",
     "\n",

docs/docs/how_to/index.mdx

@@ -7,42 +7,35 @@ sidebar_class_name: hidden
 
 Here you’ll find answers to “How do I….?” types of questions.
 These guides are *goal-oriented* and *concrete*; they're meant to help you complete a specific task.
-For conceptual explanations see the [Conceptual guide](/docs/concepts/).
+For conceptual explanations see [Conceptual Guides](/docs/concepts/).
 For end-to-end walkthroughs see [Tutorials](/docs/tutorials).
-For comprehensive descriptions of every class and function see the [API Reference](https://api.python.langchain.com/en/latest/).
-
-## Installation
-
-- [How to: install LangChain packages](/docs/how_to/installation/)
-- [How to: use LangChain with different Pydantic versions](/docs/how_to/pydantic_compatibility)
+For comprehensive descriptions of every class and function see [API Reference](https://api.python.langchain.com/en/latest/).
 
 ## Key features
 
 This highlights functionality that is core to using LangChain.
 
-- [How to: return structured data from a model](/docs/how_to/structured_output/)
-- [How to: use a model to call tools](/docs/how_to/tool_calling/)
+- [How to: return structured data from an LLM](/docs/how_to/structured_output/)
+- [How to: use a chat model to call tools](/docs/how_to/tool_calling/)
 - [How to: stream runnables](/docs/how_to/streaming)
 - [How to: debug your LLM apps](/docs/how_to/debugging/)
 
 ## LangChain Expression Language (LCEL)
 
-[LangChain Expression Language](/docs/concepts/#langchain-expression-language-lcel) is a way to create arbitrary custom chains. It is built on the [Runnable](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.base.Runnable.html) protocol.
-
-[**LCEL cheatsheet**](/docs/how_to/lcel_cheatsheet/): For a quick overview of how to use the main LCEL primitives.
+LangChain Expression Language is a way to create arbitrary custom chains. It is built on the Runnable protocol.
 
 - [How to: chain runnables](/docs/how_to/sequence)
 - [How to: stream runnables](/docs/how_to/streaming)
 - [How to: invoke runnables in parallel](/docs/how_to/parallel/)
-- [How to: add default invocation args to runnables](/docs/how_to/binding/)
-- [How to: turn any function into a runnable](/docs/how_to/functions)
-- [How to: pass through inputs from one chain step to the next](/docs/how_to/passthrough)
-- [How to: configure runnable behavior at runtime](/docs/how_to/configure)
-- [How to: add message history (memory) to a chain](/docs/how_to/message_history)
-- [How to: route between sub-chains](/docs/how_to/routing)
-- [How to: create a dynamic (self-constructing) chain](/docs/how_to/dynamic_chain/)
+- [How to: attach runtime arguments to a runnable](/docs/how_to/binding/)
+- [How to: run custom functions](/docs/how_to/functions)
+- [How to: pass through arguments from one step to the next](/docs/how_to/passthrough)
+- [How to: add values to a chain's state](/docs/how_to/assign)
+- [How to: configure a chain at runtime](/docs/how_to/configure)
+- [How to: add message history](/docs/how_to/message_history)
+- [How to: route execution within a chain](/docs/how_to/routing)
 - [How to: inspect runnables](/docs/how_to/inspect)
-- [How to: add fallbacks to a runnable](/docs/how_to/fallbacks)
+- [How to: add fallbacks](/docs/how_to/fallbacks)
 
 ## Components
 
@@ -50,7 +43,7 @@ These are the core building blocks you can use when building applications.
 
 ### Prompt templates
 
-[Prompt Templates](/docs/concepts/#prompt-templates) are responsible for formatting user input into a format that can be passed to a language model.
+Prompt Templates are responsible for formatting user input into a format that can be passed to a language model.
 
 - [How to: use few shot examples](/docs/how_to/few_shot_examples)
 - [How to: use few shot examples in chat models](/docs/how_to/few_shot_examples_chat/)
@@ -59,7 +52,7 @@ These are the core building blocks you can use when building applications.
 
 ### Example selectors
 
-[Example Selectors](/docs/concepts/#example-selectors) are responsible for selecting the correct few shot examples to pass to the prompt.
+Example Selectors are responsible for selecting the correct few shot examples to pass to the prompt.
 
 - [How to: use example selectors](/docs/how_to/example_selectors)
 - [How to: select examples by length](/docs/how_to/example_selectors_length_based)
@@ -69,7 +62,7 @@ These are the core building blocks you can use when building applications.
 
 ### Chat models
 
-[Chat Models](/docs/concepts/#chat-models) are newer forms of language models that take messages in and output a message.
+Chat Models are newer forms of language models that take messages in and output a message.
 
 - [How to: do function/tool calling](/docs/how_to/tool_calling)
 - [How to: get models to return structured output](/docs/how_to/structured_output)
@@ -79,11 +72,10 @@ These are the core building blocks you can use when building applications.
 - [How to: stream a response back](/docs/how_to/chat_streaming)
 - [How to: track token usage](/docs/how_to/chat_token_usage_tracking)
 - [How to: track response metadata across providers](/docs/how_to/response_metadata)
-- [How to: init any model in one line](/docs/how_to/chat_models_universal_init/)
 
 ### LLMs
 
-What LangChain calls [LLMs](/docs/concepts/#llms) are older forms of language models that take a string in and output a string.
+What LangChain calls LLMs are older forms of language models that take a string in and output a string.
 
 - [How to: cache model responses](/docs/how_to/llm_caching)
 - [How to: create a custom LLM class](/docs/how_to/custom_llm)
@@ -93,7 +85,7 @@ What LangChain calls [LLMs](/docs/concepts/#llms) are older forms of language mo
 
 ### Output parsers
 
-[Output Parsers](/docs/concepts/#output-parsers) are responsible for taking the output of an LLM and parsing into more structured format.
+Output Parsers are responsible for taking the output of an LLM and parsing into more structured format.
 
 - [How to: use output parsers to parse an LLM response into structured format](/docs/how_to/output_parser_structured)
 - [How to: parse JSON output](/docs/how_to/output_parser_json)
@@ -105,7 +97,7 @@ What LangChain calls [LLMs](/docs/concepts/#llms) are older forms of language mo
 
 ### Document loaders
 
-[Document Loaders](/docs/concepts/#document-loaders) are responsible for loading documents from a variety of sources.
+Document Loaders are responsible for loading documents from a variety of sources.
 
 - [How to: load CSV data](/docs/how_to/document_loader_csv)
 - [How to: load data from a directory](/docs/how_to/document_loader_directory)
@@ -118,7 +110,7 @@ What LangChain calls [LLMs](/docs/concepts/#llms) are older forms of language mo
 
 ### Text splitters
 
-[Text Splitters](/docs/concepts/#text-splitters) take a document and split into chunks that can be used for retrieval.
+Text Splitters take a document and split into chunks that can be used for retrieval.
 
 - [How to: recursively split text](/docs/how_to/recursive_text_splitter)
 - [How to: split by HTML headers](/docs/how_to/HTML_header_metadata_splitter)
@@ -132,20 +124,20 @@ What LangChain calls [LLMs](/docs/concepts/#llms) are older forms of language mo
 
 ### Embedding models
 
-[Embedding Models](/docs/concepts/#embedding-models) take a piece of text and create a numerical representation of it.
+Embedding Models take a piece of text and create a numerical representation of it.
 
 - [How to: embed text data](/docs/how_to/embed_text)
 - [How to: cache embedding results](/docs/how_to/caching_embeddings)
 
 ### Vector stores
 
-[Vector stores](/docs/concepts/#vector-stores) are databases that can efficiently store and retrieve embeddings.
+Vector stores are databases that can efficiently store and retrieve embeddings.
 
 - [How to: use a vector store to retrieve data](/docs/how_to/vectorstores)
 
 ### Retrievers
 
-[Retrievers](/docs/concepts/#retrievers) are responsible for taking a query and returning relevant documents.
+Retrievers are responsible for taking a query and returning relevant documents.
 
 - [How to: use a vector store to retrieve data](/docs/how_to/vectorstore_retriever)
 - [How to: generate multiple queries to retrieve data for](/docs/how_to/MultiQueryRetriever)
@@ -153,7 +145,7 @@ What LangChain calls [LLMs](/docs/concepts/#llms) are older forms of language mo
 - [How to: write a custom retriever class](/docs/how_to/custom_retriever)
 - [How to: add similarity scores to retriever results](/docs/how_to/add_scores_retriever)
 - [How to: combine the results from multiple retrievers](/docs/how_to/ensemble_retriever)
-- [How to: reorder retrieved results to mitigate the "lost in the middle" effect](/docs/how_to/long_context_reorder)
+- [How to: reorder retrieved results to put most relevant documents not in the middle](/docs/how_to/long_context_reorder)
 - [How to: generate multiple embeddings per document](/docs/how_to/multi_vector)
 - [How to: retrieve the whole document for a chunk](/docs/how_to/parent_document_retriever)
 - [How to: generate metadata filters](/docs/how_to/self_query)
@@ -168,21 +160,19 @@ Indexing is the process of keeping your vectorstore in-sync with the underlying
 
 ### Tools
 
-LangChain [Tools](/docs/concepts/#tools) contain a description of the tool (to pass to the language model) as well as the implementation of the function to call).
+LangChain Tools contain a description of the tool (to pass to the language model) as well as the implementation of the function to call).
 
-- [How to: create custom tools](/docs/how_to/custom_tools)
-- [How to: use built-in tools and built-in toolkits](/docs/how_to/tools_builtin)
+- [How to: use LangChain tools](/docs/how_to/tools)
 - [How to: use a chat model to call tools](/docs/how_to/tool_calling/)
-- [How to: add ad-hoc tool calling capability to LLMs and chat models](/docs/how_to/tools_prompting)
-- [How to: pass run time values to tools](/docs/how_to/tool_runtime)
+- [How to: use LangChain toolkits](/docs/how_to/toolkits)
+- [How to: define a custom tool](/docs/how_to/custom_tools)
+- [How to: convert LangChain tools to OpenAI functions](/docs/how_to/tools_as_openai_functions)
+- [How to: use tools without function calling](/docs/how_to/tools_prompting)
+- [How to: let the LLM choose between multiple tools](/docs/how_to/tools_multiple)
 - [How to: add a human in the loop to tool usage](/docs/how_to/tools_human)
+- [How to: do parallel tool use](/docs/how_to/tools_parallel)
 - [How to: handle errors when calling tools](/docs/how_to/tools_error)
-
-### Multimodal
-
-- [How to: pass multimodal data directly to models](/docs/how_to/multimodal_inputs/)
-- [How to: use multimodal prompts](/docs/how_to/multimodal_prompts/)
-
+- [How to: call tools using multi-modal data](/docs/how_to/tool_calls_multi_modal)
 
 ### Agents
 
@@ -195,16 +185,6 @@ For in depth how-to guides for agents, please check out [LangGraph](https://gith
 - [How to: use legacy LangChain Agents (AgentExecutor)](/docs/how_to/agent_executor)
 - [How to: migrate from legacy LangChain agents to LangGraph](/docs/how_to/migrate_agent)
 
-### Callbacks
-
-[Callbacks](/docs/concepts/#callbacks) allow you to hook into the various stages of your LLM application's execution.
-
-- [How to: pass in callbacks at runtime](/docs/how_to/callbacks_runtime)
-- [How to: attach callbacks to a module](/docs/how_to/callbacks_attach)
-- [How to: pass callbacks into a module constructor](/docs/how_to/callbacks_constructor)
-- [How to: create custom callback handlers](/docs/how_to/custom_callbacks)
-- [How to: use callbacks in async environments](/docs/how_to/callbacks_async)
-
 ### Custom
 
 All of LangChain components can easily be extended to support your own versions.
@@ -214,7 +194,6 @@ All of LangChain components can easily be extended to support your own versions.
 - [How to: write a custom retriever class](/docs/how_to/custom_retriever)
 - [How to: write a custom document loader](/docs/how_to/document_loader_custom)
 - [How to: write a custom output parser class](/docs/how_to/output_parser_custom)
-- [How to: create custom callback handlers](/docs/how_to/custom_callbacks)
 - [How to: define a custom tool](/docs/how_to/custom_tools)
 
 
@@ -225,7 +204,6 @@ These guides cover use-case specific details.
 ### Q&A with RAG
 
 Retrieval Augmented Generation (RAG) is a way to connect LLMs to external sources of data.
-For a high-level tutorial on RAG, check out [this guide](/docs/tutorials/rag/).
 
 - [How to: add chat history](/docs/how_to/qa_chat_history_how_to/)
 - [How to: stream](/docs/how_to/qa_streaming/)
@@ -237,7 +215,6 @@ For a high-level tutorial on RAG, check out [this guide](/docs/tutorials/rag/).
 ### Extraction
 
 Extraction is when you use LLMs to extract structured information from unstructured text.
-For a high level tutorial on extraction, check out [this guide](/docs/tutorials/extraction/).
 
 - [How to: use reference examples](/docs/how_to/extraction_examples/)
 - [How to: handle long text](/docs/how_to/extraction_long_text/)
@@ -246,7 +223,6 @@ For a high level tutorial on extraction, check out [this guide](/docs/tutorials/
 ### Chatbots
 
 Chatbots involve using an LLM to have a conversation.
-For a high-level tutorial on building chatbots, check out [this guide](/docs/tutorials/chatbot/).
 
 - [How to: manage memory](/docs/how_to/chatbots_memory)
 - [How to: do retrieval](/docs/how_to/chatbots_retrieval)
@@ -255,7 +231,6 @@ For a high-level tutorial on building chatbots, check out [this guide](/docs/tut
 ### Query analysis
 
 Query Analysis is the task of using an LLM to generate a query to send to a retriever.
-For a high-level tutorial on query analysis, check out [this guide](/docs/tutorials/query_analysis/).
 
 - [How to: add examples to the prompt](/docs/how_to/query_few_shot)
 - [How to: handle cases where no queries are generated](/docs/how_to/query_no_queries)
@@ -267,7 +242,6 @@ For a high-level tutorial on query analysis, check out [this guide](/docs/tutori
 ### Q&A over SQL + CSV
 
 You can use LLMs to do question answering over tabular data.
-For a high-level tutorial, check out [this guide](/docs/tutorials/sql_qa/).
 
 - [How to: use prompting to improve results](/docs/how_to/sql_prompting)
 - [How to: do query validation](/docs/how_to/sql_query_checking)
@@ -277,25 +251,8 @@ For a high-level tutorial, check out [this guide](/docs/tutorials/sql_qa/).
 ### Q&A over graph databases
 
 You can use an LLM to do question answering over graph databases.
-For a high-level tutorial, check out [this guide](/docs/tutorials/graph/).
 
 - [How to: map values to a database](/docs/how_to/graph_mapping)
 - [How to: add a semantic layer over the database](/docs/how_to/graph_semantic)
 - [How to: improve results with prompting](/docs/how_to/graph_prompting)
 - [How to: construct knowledge graphs](/docs/how_to/graph_constructing)
-
-## [LangGraph](https://langchain-ai.github.io/langgraph)
-
-LangGraph is an extension of LangChain aimed at
-building robust and stateful multi-actor applications with LLMs by modeling steps as edges and nodes in a graph.
-
-LangGraph documentation is currently hosted on a separate site.
-You can peruse [LangGraph how-to guides here](https://langchain-ai.github.io/langgraph/how-tos/).
-
-## [LangSmith](https://docs.smith.langchain.com/)
-
-LangSmith allows you to closely trace, monitor and evaluate your LLM application.
-It seamlessly integrates with LangChain, and you can use it to inspect and debug individual steps of your chains as you build.
-
-LangSmith documentation is hosted on a separate site.
-You can peruse [LangSmith how-to guides here](https://docs.smith.langchain.com/how_to_guides/).

docs/docs/how_to/indexing.ipynb

@@ -60,7 +60,7 @@
     "   * document addition by id (`add_documents` method with `ids` argument)\n",
     "   * delete by id (`delete` method with `ids` argument)\n",
     "\n",
-    "Compatible Vectorstores: `Aerospike`, `AnalyticDB`, `AstraDB`, `AwaDB`, `AzureCosmosDBNoSqlVectorSearch`, `AzureCosmosDBVectorSearch`, `Bagel`, `Cassandra`, `Chroma`, `CouchbaseVectorStore`, `DashVector`, `DatabricksVectorSearch`, `DeepLake`, `Dingo`, `ElasticVectorSearch`, `ElasticsearchStore`, `FAISS`, `HanaDB`, `Milvus`, `MyScale`, `OpenSearchVectorSearch`, `PGVector`, `Pinecone`, `Qdrant`, `Redis`, `Rockset`, `ScaNN`, `SupabaseVectorStore`, `SurrealDBStore`, `TimescaleVector`, `Vald`, `VDMS`, `Vearch`, `VespaStore`, `Weaviate`, `Yellowbrick`, `ZepVectorStore`, `TencentVectorDB`, `OpenSearchVectorSearch`.\n",
+    "Compatible Vectorstores: `AnalyticDB`, `AstraDB`, `AwaDB`, `Bagel`, `Cassandra`, `Chroma`, `CouchbaseVectorStore`, `DashVector`, `DatabricksVectorSearch`, `DeepLake`, `Dingo`, `ElasticVectorSearch`, `ElasticsearchStore`, `FAISS`, `HanaDB`, `Milvus`, `MyScale`, `OpenSearchVectorSearch`, `PGVector`, `Pinecone`, `Qdrant`, `Redis`, `Rockset`, `ScaNN`, `SupabaseVectorStore`, `SurrealDBStore`, `TimescaleVector`, `Vald`, `VDMS`, `Vearch`, `VespaStore`, `Weaviate`, `ZepVectorStore`, `TencentVectorDB`, `OpenSearchVectorSearch`.\n",
     "  \n",
     "## Caution\n",
     "\n",
@@ -786,7 +786,7 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "from langchain_core.document_loaders import BaseLoader\n",
+    "from langchain_community.document_loaders.base import BaseLoader\n",
     "\n",
     "\n",
     "class MyCustomLoader(BaseLoader):\n",

docs/docs/how_to/inspect.ipynb

@@ -39,9 +39,9 @@
    "metadata": {},
    "outputs": [],
    "source": [
+    "from langchain.prompts import ChatPromptTemplate\n",
     "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",

docs/docs/how_to/llm_caching.ipynb

@@ -119,7 +119,7 @@
    "outputs": [],
    "source": [
     "# We can do the same thing with a SQLite cache\n",
-    "from langchain_community.cache import SQLiteCache\n",
+    "from langchain.cache import SQLiteCache\n",
     "\n",
     "set_llm_cache(SQLiteCache(database_path=\".langchain.db\"))"
    ]

docs/docs/how_to/llm_token_usage_tracking.ipynb

@@ -2,105 +2,119 @@
  "cells": [
   {
    "cell_type": "markdown",
-   "id": "90dff237-bc28-4185-a2c0-d5203bbdeacd",
+   "id": "e5715368",
    "metadata": {},
    "source": [
     "# How to track token usage for LLMs\n",
     "\n",
-    "Tracking token usage to calculate cost is an important part of putting your app in production. This guide goes over how to obtain this information from your LangChain model calls.\n",
+    "This notebook goes over how to track your token usage for specific calls. It is currently only implemented for the OpenAI API.\n",
     "\n",
-    ":::info Prerequisites\n",
-    "\n",
-    "This guide assumes familiarity with the following concepts:\n",
-    "\n",
-    "- [LLMs](/docs/concepts/#llms)\n",
-    ":::\n",
-    "\n",
-    "## Using LangSmith\n",
-    "\n",
-    "You can use [LangSmith](https://www.langchain.com/langsmith) to help track token usage in your LLM application. See the [LangSmith quick start guide](https://docs.smith.langchain.com/).\n",
-    "\n",
-    "## Using callbacks\n",
-    "\n",
-    "There are some API-specific callback context managers that allow you to track token usage across multiple calls. You'll need to check whether such an integration is available for your particular model.\n",
-    "\n",
-    "If such an integration is not available for your model, you can create a custom callback manager by adapting the implementation of the [OpenAI callback manager](https://api.python.langchain.com/en/latest/_modules/langchain_community/callbacks/openai_info.html#OpenAICallbackHandler).\n",
-    "\n",
-    "### OpenAI\n",
-    "\n",
-    "Let's first look at an extremely simple example of tracking token usage for a single Chat model call.\n",
-    "\n",
-    ":::{.callout-danger}\n",
-    "\n",
-    "The callback handler does not currently support streaming token counts for legacy language models (e.g., `langchain_openai.OpenAI`). For support in a streaming context, refer to the corresponding guide for chat models [here](/docs/how_to/chat_token_usage_tracking).\n",
-    "\n",
-    ":::"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "f790edd9-823e-4bc5-befa-e9529c7237a0",
-   "metadata": {},
-   "source": [
-    "### Single call"
+    "Let's first look at an extremely simple example of tracking token usage for a single LLM call."
    ]
   },
   {
    "cell_type": "code",
    "execution_count": 1,
-   "id": "2eebbee2-6ca1-4fa8-a3aa-0376888ceefb",
+   "id": "9455db35",
    "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "\n",
-      "\n",
-      "Why don't scientists trust atoms?\n",
-      "\n",
-      "Because they make up everything.\n",
-      "---\n",
-      "\n",
-      "Total Tokens: 18\n",
-      "Prompt Tokens: 4\n",
-      "Completion Tokens: 14\n",
-      "Total Cost (USD): $3.4e-05\n"
-     ]
-    }
-   ],
+   "outputs": [],
    "source": [
     "from langchain_community.callbacks import get_openai_callback\n",
-    "from langchain_openai import OpenAI\n",
-    "\n",
-    "llm = OpenAI(model_name=\"gpt-3.5-turbo-instruct\")\n",
-    "\n",
-    "with get_openai_callback() as cb:\n",
-    "    result = llm.invoke(\"Tell me a joke\")\n",
-    "    print(result)\n",
-    "    print(\"---\")\n",
-    "print()\n",
-    "\n",
-    "print(f\"Total Tokens: {cb.total_tokens}\")\n",
-    "print(f\"Prompt Tokens: {cb.prompt_tokens}\")\n",
-    "print(f\"Completion Tokens: {cb.completion_tokens}\")\n",
-    "print(f\"Total Cost (USD): ${cb.total_cost}\")"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "7df3be35-dd97-4e3a-bd51-52434ab2249d",
-   "metadata": {},
-   "source": [
-    "### Multiple calls\n",
-    "\n",
-    "Anything inside the context manager will get tracked. Here's an example of using it to track multiple calls in sequence to a chain. This will also work for an agent which may use multiple steps."
+    "from langchain_openai import OpenAI"
    ]
   },
   {
    "cell_type": "code",
    "execution_count": 2,
-   "id": "3ec10419-294c-44bf-af85-86aabf457cb6",
+   "id": "d1c55cc9",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "llm = OpenAI(model_name=\"gpt-3.5-turbo-instruct\", n=2, best_of=2)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 3,
+   "id": "31667d54",
+   "metadata": {},
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "Tokens Used: 37\n",
+      "\tPrompt Tokens: 4\n",
+      "\tCompletion Tokens: 33\n",
+      "Successful Requests: 1\n",
+      "Total Cost (USD): $7.2e-05\n"
+     ]
+    }
+   ],
+   "source": [
+    "with get_openai_callback() as cb:\n",
+    "    result = llm.invoke(\"Tell me a joke\")\n",
+    "    print(cb)"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "c0ab6d27",
+   "metadata": {},
+   "source": [
+    "Anything inside the context manager will get tracked. Here's an example of using it to track multiple calls in sequence."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 4,
+   "id": "e09420f4",
+   "metadata": {},
+   "outputs": [
+    {
+     "name": "stdout",
+     "output_type": "stream",
+     "text": [
+      "72\n"
+     ]
+    }
+   ],
+   "source": [
+    "with get_openai_callback() as cb:\n",
+    "    result = llm.invoke(\"Tell me a joke\")\n",
+    "    result2 = llm.invoke(\"Tell me a joke\")\n",
+    "    print(cb.total_tokens)"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "d8186e7b",
+   "metadata": {},
+   "source": [
+    "If a chain or agent with multiple steps in it is used, it will track all those steps."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 5,
+   "id": "5d1125c6",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain.agents import AgentType, initialize_agent, load_tools\n",
+    "from langchain_openai import OpenAI\n",
+    "\n",
+    "llm = OpenAI(temperature=0)\n",
+    "tools = load_tools([\"serpapi\", \"llm-math\"], llm=llm)\n",
+    "agent = initialize_agent(\n",
+    "    tools, llm, agent=AgentType.ZERO_SHOT_REACT_DESCRIPTION, verbose=True\n",
+    ")"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 6,
+   "id": "2f98c536",
    "metadata": {},
    "outputs": [
     {
@@ -109,119 +123,48 @@
      "text": [
       "\n",
       "\n",
-      "Why did the chicken go to the seance?\n",
+      "\u001b[1m> Entering new AgentExecutor chain...\u001b[0m\n",
+      "\u001b[32;1m\u001b[1;3m I need to find out who Olivia Wilde's boyfriend is and then calculate his age raised to the 0.23 power.\n",
+      "Action: Search\n",
+      "Action Input: \"Olivia Wilde boyfriend\"\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3m[\"Olivia Wilde and Harry Styles took fans by surprise with their whirlwind romance, which began when they met on the set of Don't Worry Darling.\", 'Olivia Wilde started dating Harry Styles after ending her years-long engagement to Jason Sudeikis — see their relationship timeline.', 'Olivia Wilde and Harry Styles were spotted early on in their relationship walking around London. (. Image ...', \"Looks like Olivia Wilde and Jason Sudeikis are starting 2023 on good terms. Amid their highly publicized custody battle – and the actress' ...\", 'The two started dating after Wilde split up with actor Jason Sudeikisin 2020. However, their relationship came to an end last November.', \"Olivia Wilde and Harry Styles started dating during the filming of Don't Worry Darling. While the movie got a lot of backlash because of the ...\", \"Here's what we know so far about Harry Styles and Olivia Wilde's relationship.\", 'Olivia and the Grammy winner kept their romance out of the spotlight as their relationship began just two months after her split from ex-fiancé ...', \"Harry Styles and Olivia Wilde first met on the set of Don't Worry Darling and stepped out as a couple in January 2021. Relive all their biggest relationship ...\"]\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m Harry Styles is Olivia Wilde's boyfriend.\n",
+      "Action: Search\n",
+      "Action Input: \"Harry Styles age\"\u001b[0m\n",
+      "Observation: \u001b[36;1m\u001b[1;3m29 years\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I need to calculate 29 raised to the 0.23 power.\n",
+      "Action: Calculator\n",
+      "Action Input: 29^0.23\u001b[0m\n",
+      "Observation: \u001b[33;1m\u001b[1;3mAnswer: 2.169459462491557\u001b[0m\n",
+      "Thought:\u001b[32;1m\u001b[1;3m I now know the final answer.\n",
+      "Final Answer: Harry Styles is Olivia Wilde's boyfriend and his current age raised to the 0.23 power is 2.169459462491557.\u001b[0m\n",
       "\n",
-      "To talk to the other side of the road!\n",
-      "--\n",
-      "\n",
-      "\n",
-      "Why did the fish need a lawyer?\n",
-      "\n",
-      "Because it got caught in a net!\n",
-      "\n",
-      "---\n",
-      "Total Tokens: 50\n",
-      "Prompt Tokens: 12\n",
-      "Completion Tokens: 38\n",
-      "Total Cost (USD): $9.400000000000001e-05\n"
+      "\u001b[1m> Finished chain.\u001b[0m\n",
+      "Total Tokens: 2205\n",
+      "Prompt Tokens: 2053\n",
+      "Completion Tokens: 152\n",
+      "Total Cost (USD): $0.0441\n"
      ]
     }
    ],
    "source": [
-    "from langchain_community.callbacks import get_openai_callback\n",
-    "from langchain_core.prompts import PromptTemplate\n",
-    "from langchain_openai import OpenAI\n",
-    "\n",
-    "llm = OpenAI(model_name=\"gpt-3.5-turbo-instruct\")\n",
-    "\n",
-    "template = PromptTemplate.from_template(\"Tell me a joke about {topic}\")\n",
-    "chain = template | llm\n",
-    "\n",
     "with get_openai_callback() as cb:\n",
-    "    response = chain.invoke({\"topic\": \"birds\"})\n",
-    "    print(response)\n",
-    "    response = chain.invoke({\"topic\": \"fish\"})\n",
-    "    print(\"--\")\n",
-    "    print(response)\n",
-    "\n",
-    "\n",
-    "print()\n",
-    "print(\"---\")\n",
-    "print(f\"Total Tokens: {cb.total_tokens}\")\n",
-    "print(f\"Prompt Tokens: {cb.prompt_tokens}\")\n",
-    "print(f\"Completion Tokens: {cb.completion_tokens}\")\n",
-    "print(f\"Total Cost (USD): ${cb.total_cost}\")"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "ad7a3fba-9fac-4222-8f87-d1d276d27d6e",
-   "metadata": {
-    "tags": []
-   },
-   "source": [
-    "## Streaming\n",
-    "\n",
-    ":::{.callout-danger}\n",
-    "\n",
-    "`get_openai_callback` does not currently support streaming token counts for legacy language models (e.g., `langchain_openai.OpenAI`). If you want to count tokens correctly in a streaming context, there are a number of options:\n",
-    "\n",
-    "- Use chat models as described in [this guide](/docs/how_to/chat_token_usage_tracking);\n",
-    "- Implement a [custom callback handler](/docs/how_to/custom_callbacks/) that uses appropriate tokenizers to count the tokens;\n",
-    "- Use a monitoring platform such as [LangSmith](https://www.langchain.com/langsmith).\n",
-    ":::\n",
-    "\n",
-    "Note that when using legacy language models in a streaming context, token counts are not updated:"
+    "    response = agent.run(\n",
+    "        \"Who is Olivia Wilde's boyfriend? What is his current age raised to the 0.23 power?\"\n",
+    "    )\n",
+    "    print(f\"Total Tokens: {cb.total_tokens}\")\n",
+    "    print(f\"Prompt Tokens: {cb.prompt_tokens}\")\n",
+    "    print(f\"Completion Tokens: {cb.completion_tokens}\")\n",
+    "    print(f\"Total Cost (USD): ${cb.total_cost}\")"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 3,
-   "id": "cd61ed79-7858-49bb-afb5-d41291f597ba",
-   "metadata": {
-    "tags": []
-   },
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "\n",
-      "\n",
-      "Why don't scientists trust atoms?\n",
-      "\n",
-      "Because they make up everything!\n",
-      "\n",
-      "Why don't scientists trust atoms?\n",
-      "\n",
-      "Because they make up everything.\n",
-      "---\n",
-      "\n",
-      "Total Tokens: 0\n",
-      "Prompt Tokens: 0\n",
-      "Completion Tokens: 0\n",
-      "Total Cost (USD): $0.0\n"
-     ]
-    }
-   ],
-   "source": [
-    "from langchain_community.callbacks import get_openai_callback\n",
-    "from langchain_openai import OpenAI\n",
-    "\n",
-    "llm = OpenAI(model_name=\"gpt-3.5-turbo-instruct\")\n",
-    "\n",
-    "with get_openai_callback() as cb:\n",
-    "    for chunk in llm.stream(\"Tell me a joke\"):\n",
-    "        print(chunk, end=\"\", flush=True)\n",
-    "    print(result)\n",
-    "    print(\"---\")\n",
-    "print()\n",
-    "\n",
-    "print(f\"Total Tokens: {cb.total_tokens}\")\n",
-    "print(f\"Prompt Tokens: {cb.prompt_tokens}\")\n",
-    "print(f\"Completion Tokens: {cb.completion_tokens}\")\n",
-    "print(f\"Total Cost (USD): ${cb.total_cost}\")"
-   ]
+   "execution_count": null,
+   "id": "80ca77a3",
+   "metadata": {},
+   "outputs": [],
+   "source": []
   }
  ],
  "metadata": {
@@ -240,7 +183,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.10.4"
+   "version": "3.10.1"
   }
  },
  "nbformat": 4,

docs/docs/how_to/local_llms.ipynb

@@ -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",

docs/docs/how_to/long_context_reorder.ipynb

@@ -5,38 +5,28 @@
    "id": "fc0db1bc",
    "metadata": {},
    "source": [
-    "# How to reorder retrieved results to mitigate the \"lost in the middle\" effect\n",
+    "# How to reorder retrieved results to put most relevant documents not in the middle\n",
     "\n",
-    "Substantial performance degradations in [RAG](/docs/tutorials/rag) applications have been [documented](https://arxiv.org/abs/2307.03172) as the number of retrieved documents grows (e.g., beyond ten). In brief: models are liable to miss relevant information in the middle of long contexts.\n",
+    "No matter the architecture of your model, there is a substantial performance degradation when you include 10+ retrieved documents.\n",
+    "In brief: When models must access relevant information in the middle of long contexts, they tend to ignore the provided documents.\n",
+    "See: https://arxiv.org/abs/2307.03172\n",
     "\n",
-    "By contrast, queries against vector stores will typically return documents in descending order of relevance (e.g., as measured by cosine similarity of [embeddings](/docs/concepts/#embedding-models)).\n",
-    "\n",
-    "To mitigate the [\"lost in the middle\"](https://arxiv.org/abs/2307.03172) effect, you can re-order documents after retrieval such that the most relevant documents are positioned at extrema (e.g., the first and last pieces of context), and the least relevant documents are positioned in the middle. In some cases this can help surface the most relevant information to LLMs.\n",
-    "\n",
-    "The [LongContextReorder](https://api.python.langchain.com/en/latest/document_transformers/langchain_community.document_transformers.long_context_reorder.LongContextReorder.html) document transformer implements this re-ordering procedure. Below we demonstrate an example."
+    "To avoid this issue you can re-order documents after retrieval to avoid performance degradation."
    ]
   },
   {
    "cell_type": "code",
    "execution_count": null,
-   "id": "2074fdaa-edff-468a-970f-6f5f26e93d4a",
+   "id": "74d1ebe8",
    "metadata": {},
    "outputs": [],
    "source": [
     "%pip install --upgrade --quiet  sentence-transformers langchain-chroma langchain langchain-openai langchain-huggingface > /dev/null"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "id": "c97eaaf2-34b7-4770-9949-e1abc4ca5226",
-   "metadata": {},
-   "source": [
-    "First we embed some artificial documents and index them in an (in-memory) [Chroma](/docs/integrations/providers/chroma/) vector store. We will use [Hugging Face](/docs/integrations/text_embedding/huggingfacehub/) embeddings, but any LangChain vector store or embeddings model will suffice."
-   ]
-  },
   {
    "cell_type": "code",
-   "execution_count": 2,
+   "execution_count": 3,
    "id": "49cbcd8e",
    "metadata": {},
    "outputs": [
@@ -55,14 +45,20 @@
        " Document(page_content='This is just a random text.')]"
       ]
      },
-     "execution_count": 2,
+     "execution_count": 3,
      "metadata": {},
      "output_type": "execute_result"
     }
    ],
    "source": [
+    "from langchain.chains import LLMChain, StuffDocumentsChain\n",
+    "from langchain.prompts import PromptTemplate\n",
     "from langchain_chroma import Chroma\n",
+    "from langchain_community.document_transformers import (\n",
+    "    LongContextReorder,\n",
+    ")\n",
     "from langchain_huggingface import HuggingFaceEmbeddings\n",
+    "from langchain_openai import OpenAI\n",
     "\n",
     "# Get embeddings.\n",
     "embeddings = HuggingFaceEmbeddings(model_name=\"all-MiniLM-L6-v2\")\n",
@@ -87,22 +83,14 @@
     "query = \"What can you tell me about the Celtics?\"\n",
     "\n",
     "# Get relevant documents ordered by relevance score\n",
-    "docs = retriever.invoke(query)\n",
+    "docs = retriever.get_relevant_documents(query)\n",
     "docs"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "id": "175d031a-43fa-42f4-93c4-2ba52c3c3ee5",
-   "metadata": {},
-   "source": [
-    "Note that documents are returned in descending order of relevance to the query. The `LongContextReorder` document transformer will implement the re-ordering described above:"
-   ]
-  },
   {
    "cell_type": "code",
-   "execution_count": 3,
-   "id": "9a1181f2-a3dc-4614-9233-2196ab65939e",
+   "execution_count": 4,
+   "id": "34fb9d6e",
    "metadata": {},
    "outputs": [
     {
@@ -120,14 +108,12 @@
        " Document(page_content='This is a document about the Boston Celtics')]"
       ]
      },
-     "execution_count": 3,
+     "execution_count": 4,
      "metadata": {},
      "output_type": "execute_result"
     }
    ],
    "source": [
-    "from langchain_community.document_transformers import LongContextReorder\n",
-    "\n",
     "# Reorder the documents:\n",
     "# Less relevant document will be at the middle of the list and more\n",
     "# relevant elements at beginning / end.\n",
@@ -138,55 +124,59 @@
     "reordered_docs"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "id": "a8d2ef0c-c397-4d8d-8118-3f7acf86d241",
-   "metadata": {},
-   "source": [
-    "Below, we show how to incorporate the re-ordered documents into a simple question-answering chain:"
-   ]
-  },
   {
    "cell_type": "code",
    "execution_count": 5,
-   "id": "8bbea705-d5b9-4ed5-9957-e12547283622",
+   "id": "ceccab87",
    "metadata": {},
    "outputs": [
     {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "\n",
-      "The Celtics are a professional basketball team and one of the most iconic franchises in the NBA. They are highly regarded and have a large fan base. The team has had many successful seasons and is often considered one of the top teams in the league. They have a strong history and have produced many great players, such as Larry Bird and L. Kornet. The team is based in Boston and is often referred to as the Boston Celtics.\n"
-     ]
+     "data": {
+      "text/plain": [
+       "'\\n\\nThe Celtics are referenced in four of the nine text extracts. They are mentioned as the favorite team of the author, the winner of a basketball game, a team with one of the best players, and a team with a specific player. Additionally, the last extract states that the document is about the Boston Celtics. This suggests that the Celtics are a basketball team, possibly from Boston, that is well-known and has had successful players and games in the past. '"
+      ]
+     },
+     "execution_count": 5,
+     "metadata": {},
+     "output_type": "execute_result"
     }
    ],
    "source": [
-    "from langchain.chains.combine_documents import create_stuff_documents_chain\n",
-    "from langchain_core.prompts import PromptTemplate\n",
-    "from langchain_openai import OpenAI\n",
+    "# We prepare and run a custom Stuff chain with reordered docs as context.\n",
     "\n",
+    "# Override prompts\n",
+    "document_prompt = PromptTemplate(\n",
+    "    input_variables=[\"page_content\"], template=\"{page_content}\"\n",
+    ")\n",
+    "document_variable_name = \"context\"\n",
     "llm = OpenAI()\n",
-    "\n",
-    "prompt_template = \"\"\"\n",
-    "Given these texts:\n",
+    "stuff_prompt_override = \"\"\"Given this text extracts:\n",
     "-----\n",
     "{context}\n",
     "-----\n",
     "Please answer the following question:\n",
-    "{query}\n",
-    "\"\"\"\n",
-    "\n",
+    "{query}\"\"\"\n",
     "prompt = PromptTemplate(\n",
-    "    template=prompt_template,\n",
-    "    input_variables=[\"context\", \"query\"],\n",
+    "    template=stuff_prompt_override, input_variables=[\"context\", \"query\"]\n",
     ")\n",
     "\n",
-    "# Create and invoke the chain:\n",
-    "chain = create_stuff_documents_chain(llm, prompt)\n",
-    "response = chain.invoke({\"context\": reordered_docs, \"query\": query})\n",
-    "print(response)"
+    "# Instantiate the chain\n",
+    "llm_chain = LLMChain(llm=llm, prompt=prompt)\n",
+    "chain = StuffDocumentsChain(\n",
+    "    llm_chain=llm_chain,\n",
+    "    document_prompt=document_prompt,\n",
+    "    document_variable_name=document_variable_name,\n",
+    ")\n",
+    "chain.run(input_documents=reordered_docs, query=query)"
    ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "d4696a97",
+   "metadata": {},
+   "outputs": [],
+   "source": []
   }
  ],
  "metadata": {
@@ -205,7 +195,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.10.4"
+   "version": "3.10.1"
   }
  },
  "nbformat": 4,

docs/docs/how_to/migrate_agent.ipynb

@@ -18,13 +18,13 @@
   },
   {
    "cell_type": "code",
-   "execution_count": null,
+   "execution_count": 2,
    "id": "662fac50",
    "metadata": {},
    "outputs": [],
    "source": [
     "%%capture --no-stderr\n",
-    "%pip install -U langgraph langchain langchain-openai"
+    "%pip install -U langchain-openai langchain langgraph"
    ]
   },
   {
@@ -34,12 +34,12 @@
    "source": [
     "## Basic Usage\n",
     "\n",
-    "For basic creation and usage of a tool-calling ReAct-style agent, the functionality is the same. First, let's define a model and tool(s), then we'll use those to create an agent."
+    "First, let's define a model and tool."
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 1,
+   "execution_count": 6,
    "id": "1e425fea-2796-4b99-bee6-9a6ffe73f756",
    "metadata": {},
    "outputs": [],
@@ -72,7 +72,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 2,
+   "execution_count": 15,
    "id": "03ea357c-9c36-4464-b2cc-27bd150e1554",
    "metadata": {},
    "outputs": [
@@ -83,7 +83,7 @@
        " 'output': 'The value of `magic_function(3)` is 5.'}"
       ]
      },
-     "execution_count": 2,
+     "execution_count": 15,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -119,7 +119,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 3,
+   "execution_count": 16,
    "id": "53a3737a-d167-4255-89bf-20ac37f89a3e",
    "metadata": {},
    "outputs": [
@@ -130,7 +130,7 @@
        " 'output': 'The value of `magic_function(3)` is 5.'}"
       ]
      },
-     "execution_count": 3,
+     "execution_count": 16,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -150,7 +150,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 4,
+   "execution_count": 17,
    "id": "74ecebe3-512e-409c-a661-bdd5b0a2b782",
    "metadata": {},
    "outputs": [
@@ -158,10 +158,10 @@
      "data": {
       "text/plain": [
        "{'input': 'Pardon?',\n",
-       " 'output': 'The result of applying `magic_function` to the input 3 is 5.'}"
+       " 'output': 'The result of applying the `magic_function` to the input `3` is `5`.'}"
       ]
      },
-     "execution_count": 4,
+     "execution_count": 17,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -200,7 +200,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 5,
+   "execution_count": 18,
    "id": "a9a11ccd-75e2-4c11-844d-a34870b0ff91",
    "metadata": {},
    "outputs": [
@@ -211,7 +211,7 @@
        " 'output': 'El valor de `magic_function(3)` es 5.'}"
       ]
      },
-     "execution_count": 5,
+     "execution_count": 18,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -243,7 +243,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 6,
+   "execution_count": 14,
    "id": "a9486805-676a-4d19-a5c4-08b41b172989",
    "metadata": {},
    "outputs": [],
@@ -272,16 +272,20 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 7,
+   "execution_count": 21,
    "id": "d369ab45-0c82-45f4-9d3e-8efb8dd47e2c",
    "metadata": {},
    "outputs": [
     {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "{'input': 'what is the value of magic_function(3)?', 'output': 'El valor de magic_function(3) es 5. ¡Pandamonium!'}\n"
-     ]
+     "data": {
+      "text/plain": [
+       "{'input': 'what is the value of magic_function(3)?',\n",
+       " 'output': 'El valor de magic_function(3) es 5. ¡Pandamonium!'}"
+      ]
+     },
+     "execution_count": 21,
+     "metadata": {},
+     "output_type": "execute_result"
     }
    ],
    "source": [
@@ -306,278 +310,10 @@
     "\n",
     "\n",
     "messages = app.invoke({\"messages\": [(\"human\", query)]})\n",
-    "print(\n",
-    "    {\n",
-    "        \"input\": query,\n",
-    "        \"output\": messages[\"messages\"][-1].content,\n",
-    "    }\n",
-    ")"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "68df3a09",
-   "metadata": {},
-   "source": [
-    "## Memory\n",
-    "\n",
-    "With LangChain's [AgentExecutor](https://api.python.langchain.com/en/latest/agents/langchain.agents.agent.AgentExecutor.html#langchain.agents.agent.AgentExecutor.iter), you could add chat [Memory](https://api.python.langchain.com/en/latest/agents/langchain.agents.agent.AgentExecutor.html#langchain.agents.agent.AgentExecutor.memory) so it can engage in a multi-turn conversation."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 8,
-   "id": "1fb52a2c",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "Hi Polly! The output of the magic function for the input 3 is 5.\n",
-      "---\n",
-      "Yes, I remember your name, Polly! How can I assist you further?\n",
-      "---\n",
-      "The output of the magic function for the input 3 is 5.\n"
-     ]
-    }
-   ],
-   "source": [
-    "from langchain.agents import AgentExecutor, create_tool_calling_agent\n",
-    "from langchain_community.chat_message_histories import ChatMessageHistory\n",
-    "from langchain_core.prompts import ChatPromptTemplate\n",
-    "from langchain_core.runnables.history import RunnableWithMessageHistory\n",
-    "from langchain_core.tools import tool\n",
-    "from langchain_openai import ChatOpenAI\n",
-    "\n",
-    "model = ChatOpenAI(model=\"gpt-4o\")\n",
-    "memory = ChatMessageHistory(session_id=\"test-session\")\n",
-    "prompt = ChatPromptTemplate.from_messages(\n",
-    "    [\n",
-    "        (\"system\", \"You are a helpful assistant.\"),\n",
-    "        # First put the history\n",
-    "        (\"placeholder\", \"{chat_history}\"),\n",
-    "        # Then the new input\n",
-    "        (\"human\", \"{input}\"),\n",
-    "        # Finally the scratchpad\n",
-    "        (\"placeholder\", \"{agent_scratchpad}\"),\n",
-    "    ]\n",
-    ")\n",
-    "\n",
-    "\n",
-    "@tool\n",
-    "def magic_function(input: int) -> int:\n",
-    "    \"\"\"Applies a magic function to an input.\"\"\"\n",
-    "    return input + 2\n",
-    "\n",
-    "\n",
-    "tools = [magic_function]\n",
-    "\n",
-    "\n",
-    "agent = create_tool_calling_agent(model, tools, prompt)\n",
-    "agent_executor = AgentExecutor(agent=agent, tools=tools)\n",
-    "\n",
-    "agent_with_chat_history = RunnableWithMessageHistory(\n",
-    "    agent_executor,\n",
-    "    # This is needed because in most real world scenarios, a session id is needed\n",
-    "    # It isn't really used here because we are using a simple in memory ChatMessageHistory\n",
-    "    lambda session_id: memory,\n",
-    "    input_messages_key=\"input\",\n",
-    "    history_messages_key=\"chat_history\",\n",
-    ")\n",
-    "\n",
-    "config = {\"configurable\": {\"session_id\": \"test-session\"}}\n",
-    "print(\n",
-    "    agent_with_chat_history.invoke(\n",
-    "        {\"input\": \"Hi, I'm polly! What's the output of magic_function of 3?\"}, config\n",
-    "    )[\"output\"]\n",
-    ")\n",
-    "print(\"---\")\n",
-    "print(agent_with_chat_history.invoke({\"input\": \"Remember my name?\"}, config)[\"output\"])\n",
-    "print(\"---\")\n",
-    "print(\n",
-    "    agent_with_chat_history.invoke({\"input\": \"what was that output again?\"}, config)[\n",
-    "        \"output\"\n",
-    "    ]\n",
-    ")"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "c2a5a32f",
-   "metadata": {},
-   "source": [
-    "#### In LangGraph\n",
-    "\n",
-    "Memory is just [persistence](https://langchain-ai.github.io/langgraph/how-tos/persistence/), aka [checkpointing](https://langchain-ai.github.io/langgraph/reference/checkpoints/).\n",
-    "\n",
-    "Add a `checkpointer` to the agent and you get chat memory for free."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 9,
-   "id": "035e1253",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "Hi Polly! The output of the magic_function for the input 3 is 5.\n",
-      "---\n",
-      "Yes, your name is Polly!\n",
-      "---\n",
-      "The output of the magic_function for the input 3 was 5.\n"
-     ]
-    }
-   ],
-   "source": [
-    "from langchain_core.messages import SystemMessage\n",
-    "from langgraph.checkpoint import MemorySaver  # an in-memory checkpointer\n",
-    "from langgraph.prebuilt import create_react_agent\n",
-    "\n",
-    "system_message = \"You are a helpful assistant.\"\n",
-    "# This could also be a SystemMessage object\n",
-    "# system_message = SystemMessage(content=\"You are a helpful assistant. Respond only in Spanish.\")\n",
-    "\n",
-    "memory = MemorySaver()\n",
-    "app = create_react_agent(\n",
-    "    model, tools, messages_modifier=system_message, checkpointer=memory\n",
-    ")\n",
-    "\n",
-    "config = {\"configurable\": {\"thread_id\": \"test-thread\"}}\n",
-    "print(\n",
-    "    app.invoke(\n",
-    "        {\n",
-    "            \"messages\": [\n",
-    "                (\"user\", \"Hi, I'm polly! What's the output of magic_function of 3?\")\n",
-    "            ]\n",
-    "        },\n",
-    "        config,\n",
-    "    )[\"messages\"][-1].content\n",
-    ")\n",
-    "print(\"---\")\n",
-    "print(\n",
-    "    app.invoke({\"messages\": [(\"user\", \"Remember my name?\")]}, config)[\"messages\"][\n",
-    "        -1\n",
-    "    ].content\n",
-    ")\n",
-    "print(\"---\")\n",
-    "print(\n",
-    "    app.invoke({\"messages\": [(\"user\", \"what was that output again?\")]}, config)[\n",
-    "        \"messages\"\n",
-    "    ][-1].content\n",
-    ")"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "d7cf24a8",
-   "metadata": {},
-   "source": [
-    "## Iterating through steps\n",
-    "\n",
-    "With LangChain's [AgentExecutor](https://api.python.langchain.com/en/latest/agents/langchain.agents.agent.AgentExecutor.html#langchain.agents.agent.AgentExecutor.iter), you could iterate over the steps using the [stream](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.base.Runnable.html#langchain_core.runnables.base.Runnable.stream) (or async `astream`) methods or the [iter](https://api.python.langchain.com/en/latest/agents/langchain.agents.agent.AgentExecutor.html#langchain.agents.agent.AgentExecutor.iter) method. LangGraph supports stepwise iteration using [stream](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.base.Runnable.html#langchain_core.runnables.base.Runnable.stream) "
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 10,
-   "id": "d640feb3",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "{'actions': [ToolAgentAction(tool='magic_function', tool_input={'input': 3}, log=\"\\nInvoking: `magic_function` with `{'input': 3}`\\n\\n\\n\", message_log=[AIMessageChunk(content='', additional_kwargs={'tool_calls': [{'index': 0, 'id': 'call_q9MgGFjqJbV2xSUX93WqxmOt', 'function': {'arguments': '{\"input\":3}', 'name': 'magic_function'}, 'type': 'function'}]}, response_metadata={'finish_reason': 'tool_calls'}, id='run-c68fd76f-a3c3-4c3c-bfd7-748c171ed4b8', tool_calls=[{'name': 'magic_function', 'args': {'input': 3}, 'id': 'call_q9MgGFjqJbV2xSUX93WqxmOt'}], tool_call_chunks=[{'name': 'magic_function', 'args': '{\"input\":3}', 'id': 'call_q9MgGFjqJbV2xSUX93WqxmOt', 'index': 0}])], tool_call_id='call_q9MgGFjqJbV2xSUX93WqxmOt')], 'messages': [AIMessageChunk(content='', additional_kwargs={'tool_calls': [{'index': 0, 'id': 'call_q9MgGFjqJbV2xSUX93WqxmOt', 'function': {'arguments': '{\"input\":3}', 'name': 'magic_function'}, 'type': 'function'}]}, response_metadata={'finish_reason': 'tool_calls'}, id='run-c68fd76f-a3c3-4c3c-bfd7-748c171ed4b8', tool_calls=[{'name': 'magic_function', 'args': {'input': 3}, 'id': 'call_q9MgGFjqJbV2xSUX93WqxmOt'}], tool_call_chunks=[{'name': 'magic_function', 'args': '{\"input\":3}', 'id': 'call_q9MgGFjqJbV2xSUX93WqxmOt', 'index': 0}])]}\n",
-      "{'steps': [AgentStep(action=ToolAgentAction(tool='magic_function', tool_input={'input': 3}, log=\"\\nInvoking: `magic_function` with `{'input': 3}`\\n\\n\\n\", message_log=[AIMessageChunk(content='', additional_kwargs={'tool_calls': [{'index': 0, 'id': 'call_q9MgGFjqJbV2xSUX93WqxmOt', 'function': {'arguments': '{\"input\":3}', 'name': 'magic_function'}, 'type': 'function'}]}, response_metadata={'finish_reason': 'tool_calls'}, id='run-c68fd76f-a3c3-4c3c-bfd7-748c171ed4b8', tool_calls=[{'name': 'magic_function', 'args': {'input': 3}, 'id': 'call_q9MgGFjqJbV2xSUX93WqxmOt'}], tool_call_chunks=[{'name': 'magic_function', 'args': '{\"input\":3}', 'id': 'call_q9MgGFjqJbV2xSUX93WqxmOt', 'index': 0}])], tool_call_id='call_q9MgGFjqJbV2xSUX93WqxmOt'), observation=5)], 'messages': [FunctionMessage(content='5', name='magic_function')]}\n",
-      "{'output': 'The value of `magic_function(3)` is 5.', 'messages': [AIMessage(content='The value of `magic_function(3)` is 5.')]}\n"
-     ]
-    }
-   ],
-   "source": [
-    "from langchain.agents import AgentExecutor, create_tool_calling_agent\n",
-    "from langchain_core.prompts import ChatPromptTemplate\n",
-    "from langchain_core.tools import tool\n",
-    "from langchain_openai import ChatOpenAI\n",
-    "\n",
-    "model = ChatOpenAI(model=\"gpt-4o\")\n",
-    "\n",
-    "\n",
-    "prompt = ChatPromptTemplate.from_messages(\n",
-    "    [\n",
-    "        (\"system\", \"You are a helpful assistant.\"),\n",
-    "        (\"human\", \"{input}\"),\n",
-    "        # Placeholders fill up a **list** of messages\n",
-    "        (\"placeholder\", \"{agent_scratchpad}\"),\n",
-    "    ]\n",
-    ")\n",
-    "\n",
-    "\n",
-    "@tool\n",
-    "def magic_function(input: int) -> int:\n",
-    "    \"\"\"Applies a magic function to an input.\"\"\"\n",
-    "    return input + 2\n",
-    "\n",
-    "\n",
-    "tools = [magic_function]\n",
-    "\n",
-    "agent = create_tool_calling_agent(model, tools, prompt=prompt)\n",
-    "agent_executor = AgentExecutor(agent=agent, tools=tools)\n",
-    "\n",
-    "for step in agent_executor.stream({\"input\": query}):\n",
-    "    print(step)"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "46ccbcbf",
-   "metadata": {},
-   "source": [
-    "#### In LangGraph\n",
-    "\n",
-    "In LangGraph, things are handled natively using [stream](https://langchain-ai.github.io/langgraph/reference/graphs/#langgraph.graph.graph.CompiledGraph.stream) or the asynchronous `astream` method."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 11,
-   "id": "86abbe07",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "{'agent': {'messages': [AIMessage(content='', additional_kwargs={'tool_calls': [{'id': 'call_yTjXXibj76tyFyPRa1soLo0S', 'function': {'arguments': '{\"input\":3}', 'name': 'magic_function'}, 'type': 'function'}]}, response_metadata={'token_usage': {'completion_tokens': 14, 'prompt_tokens': 70, 'total_tokens': 84}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'tool_calls', 'logprobs': None}, id='run-b275f314-c42e-4e77-9dec-5c23f7dbd53b-0', tool_calls=[{'name': 'magic_function', 'args': {'input': 3}, 'id': 'call_yTjXXibj76tyFyPRa1soLo0S'}])]}}\n",
-      "{'tools': {'messages': [ToolMessage(content='5', name='magic_function', id='41c5f227-528d-4483-a313-b03b23b1d327', tool_call_id='call_yTjXXibj76tyFyPRa1soLo0S')]}}\n",
-      "{'agent': {'messages': [AIMessage(content='The value of `magic_function(3)` is 5.', response_metadata={'token_usage': {'completion_tokens': 14, 'prompt_tokens': 93, 'total_tokens': 107}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'stop', 'logprobs': None}, id='run-0ef12b6e-415d-4758-9b62-5e5e1b350072-0')]}}\n"
-     ]
-    }
-   ],
-   "source": [
-    "from langchain_core.messages import AnyMessage\n",
-    "from langgraph.prebuilt import create_react_agent\n",
-    "\n",
-    "prompt = ChatPromptTemplate.from_messages(\n",
-    "    [\n",
-    "        (\"system\", \"You are a helpful assistant.\"),\n",
-    "        (\"placeholder\", \"{messages}\"),\n",
-    "    ]\n",
-    ")\n",
-    "\n",
-    "\n",
-    "def _modify_messages(messages: list[AnyMessage]):\n",
-    "    return prompt.invoke({\"messages\": messages}).to_messages()\n",
-    "\n",
-    "\n",
-    "app = create_react_agent(model, tools, messages_modifier=_modify_messages)\n",
-    "\n",
-    "\n",
-    "for step in app.stream({\"messages\": [(\"human\", query)]}, stream_mode=\"updates\"):\n",
-    "    print(step)"
+    "{\n",
+    "    \"input\": query,\n",
+    "    \"output\": messages[\"messages\"][-1].content,\n",
+    "}"
    ]
   },
   {
@@ -592,7 +328,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 12,
+   "execution_count": 22,
    "id": "4eff44bc-a620-4c8a-97b1-268692a842bb",
    "metadata": {},
    "outputs": [
@@ -600,7 +336,7 @@
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "[(ToolAgentAction(tool='magic_function', tool_input={'input': 3}, log=\"\\nInvoking: `magic_function` with `{'input': 3}`\\n\\n\\n\", message_log=[AIMessageChunk(content='', additional_kwargs={'tool_calls': [{'index': 0, 'id': 'call_ABI4hftfEdnVgKyfF6OzZbca', 'function': {'arguments': '{\"input\":3}', 'name': 'magic_function'}, 'type': 'function'}]}, response_metadata={'finish_reason': 'tool_calls'}, id='run-837e794f-cfd8-40e0-8abc-4d98ced11b75', tool_calls=[{'name': 'magic_function', 'args': {'input': 3}, 'id': 'call_ABI4hftfEdnVgKyfF6OzZbca'}], tool_call_chunks=[{'name': 'magic_function', 'args': '{\"input\":3}', 'id': 'call_ABI4hftfEdnVgKyfF6OzZbca', 'index': 0}])], tool_call_id='call_ABI4hftfEdnVgKyfF6OzZbca'), 5)]\n"
+      "[(ToolAgentAction(tool='magic_function', tool_input={'input': 3}, log=\"\\nInvoking: `magic_function` with `{'input': 3}`\\n\\n\\n\", message_log=[AIMessageChunk(content='', additional_kwargs={'tool_calls': [{'index': 0, 'id': 'call_lIjE9voYOCFAVoUXSDPQ5bFI', 'function': {'arguments': '{\"input\":3}', 'name': 'magic_function'}, 'type': 'function'}]}, response_metadata={'finish_reason': 'tool_calls'}, id='run-7a23003a-ab50-4d7c-b14b-86129d1cacfe', tool_calls=[{'name': 'magic_function', 'args': {'input': 3}, 'id': 'call_lIjE9voYOCFAVoUXSDPQ5bFI'}], tool_call_chunks=[{'name': 'magic_function', 'args': '{\"input\":3}', 'id': 'call_lIjE9voYOCFAVoUXSDPQ5bFI', 'index': 0}])], tool_call_id='call_lIjE9voYOCFAVoUXSDPQ5bFI'), 5)]\n"
      ]
     }
    ],
@@ -620,20 +356,20 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 13,
+   "execution_count": 23,
    "id": "4f4364ea-dffe-4d25-bdce-ef7d0020b880",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "{'messages': [HumanMessage(content='what is the value of magic_function(3)?', id='0f63e437-c4d8-4da9-b6f5-b293ebfe4a64'),\n",
-       "  AIMessage(content='', additional_kwargs={'tool_calls': [{'id': 'call_S96v28LlI6hNkQrNnIio0JPh', 'function': {'arguments': '{\"input\":3}', 'name': 'magic_function'}, 'type': 'function'}]}, response_metadata={'token_usage': {'completion_tokens': 14, 'prompt_tokens': 64, 'total_tokens': 78}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'tool_calls', 'logprobs': None}, id='run-ffef7898-14b1-4537-ad90-7c000a8a5d25-0', tool_calls=[{'name': 'magic_function', 'args': {'input': 3}, 'id': 'call_S96v28LlI6hNkQrNnIio0JPh'}]),\n",
-       "  ToolMessage(content='5', name='magic_function', id='fbd9df4e-1dda-4d3e-9044-b001f7875476', tool_call_id='call_S96v28LlI6hNkQrNnIio0JPh'),\n",
-       "  AIMessage(content='The value of `magic_function(3)` is 5.', response_metadata={'token_usage': {'completion_tokens': 14, 'prompt_tokens': 87, 'total_tokens': 101}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'stop', 'logprobs': None}, id='run-e5d94c54-d9f4-45cd-be8e-a9101a8d88d6-0')]}"
+       "{'messages': [HumanMessage(content='what is the value of magic_function(3)?', id='8c252eb2-9496-4ad0-b3ae-9ecb2f6c406e'),\n",
+       "  AIMessage(content='', additional_kwargs={'tool_calls': [{'id': 'call_xmBLOw2pRqB1aRTTiwqEEftW', 'function': {'arguments': '{\"input\":3}', 'name': 'magic_function'}, 'type': 'function'}]}, response_metadata={'token_usage': {'completion_tokens': 14, 'prompt_tokens': 64, 'total_tokens': 78}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'tool_calls', 'logprobs': None}, id='run-2393b69c-7c52-4771-8bec-aca0e097fcc1-0', tool_calls=[{'name': 'magic_function', 'args': {'input': 3}, 'id': 'call_xmBLOw2pRqB1aRTTiwqEEftW'}]),\n",
+       "  ToolMessage(content='5', name='magic_function', id='bec0d0f9-bbaf-49fb-b0cb-46a658658f87', tool_call_id='call_xmBLOw2pRqB1aRTTiwqEEftW'),\n",
+       "  AIMessage(content='The value of `magic_function(3)` is 5.', response_metadata={'token_usage': {'completion_tokens': 14, 'prompt_tokens': 87, 'total_tokens': 101}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'stop', 'logprobs': None}, id='run-5904d36f-b2a4-4f55-b431-12c82992c92c-0')]}"
       ]
      },
-     "execution_count": 13,
+     "execution_count": 23,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -664,7 +400,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 14,
+   "execution_count": 24,
    "id": "16f189a7-fc78-4cb5-aa16-a94ca06401a6",
    "metadata": {},
    "outputs": [],
@@ -680,7 +416,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 15,
+   "execution_count": 26,
    "id": "c96aefd7-6f6e-4670-aca6-1ac3d4e7871f",
    "metadata": {},
    "outputs": [
@@ -695,11 +431,7 @@
       "Invoking: `magic_function` with `{'input': '3'}`\n",
       "\n",
       "\n",
-      "\u001b[0m\u001b[36;1m\u001b[1;3mSorry, there was an error. Please try again.\u001b[0m\u001b[32;1m\u001b[1;3m\n",
-      "Invoking: `magic_function` with `{'input': '3'}`\n",
-      "responded: Parece que hubo un error al intentar obtener el valor de `magic_function(3)`. Permíteme intentarlo de nuevo.\n",
-      "\n",
-      "\u001b[0m\u001b[36;1m\u001b[1;3mSorry, there was an error. Please try again.\u001b[0m\u001b[32;1m\u001b[1;3mAún no puedo obtener el valor de `magic_function(3)`. ¿Hay algo más en lo que pueda ayudarte?\u001b[0m\n",
+      "\u001b[0m\u001b[36;1m\u001b[1;3mSorry, there was an error. Please try again.\u001b[0m\u001b[32;1m\u001b[1;3mParece que hubo un error al intentar obtener el valor de `magic_function(3)`. ¿Te gustaría que lo intente de nuevo?\u001b[0m\n",
       "\n",
       "\u001b[1m> Finished chain.\u001b[0m\n"
      ]
@@ -708,10 +440,10 @@
      "data": {
       "text/plain": [
        "{'input': 'what is the value of magic_function(3)?',\n",
-       " 'output': 'Aún no puedo obtener el valor de `magic_function(3)`. ¿Hay algo más en lo que pueda ayudarte?'}"
+       " 'output': 'Parece que hubo un error al intentar obtener el valor de `magic_function(3)`. ¿Te gustaría que lo intente de nuevo?'}"
       ]
      },
-     "execution_count": 15,
+     "execution_count": 26,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -739,7 +471,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 16,
+   "execution_count": 29,
    "id": "b974a91f-6ae8-4644-83d9-73666258a6db",
    "metadata": {},
    "outputs": [
@@ -748,11 +480,14 @@
      "output_type": "stream",
      "text": [
       "('human', 'what is the value of magic_function(3)?')\n",
-      "content='' additional_kwargs={'tool_calls': [{'id': 'call_pFdKcCu5taDTtOOfX14vEDRp', 'function': {'arguments': '{\"input\":\"3\"}', 'name': 'magic_function'}, 'type': 'function'}]} response_metadata={'token_usage': {'completion_tokens': 14, 'prompt_tokens': 64, 'total_tokens': 78}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'tool_calls', 'logprobs': None} id='run-25836468-ba7e-43be-a7cf-76bba06a2a08-0' tool_calls=[{'name': 'magic_function', 'args': {'input': '3'}, 'id': 'call_pFdKcCu5taDTtOOfX14vEDRp'}]\n",
-      "content='Sorry, there was an error. Please try again.' name='magic_function' id='1a08b883-9c7b-4969-9e9b-67ce64cdcb5f' tool_call_id='call_pFdKcCu5taDTtOOfX14vEDRp'\n",
-      "content='It seems there was an error when trying to apply the magic function. Let me try again.' additional_kwargs={'tool_calls': [{'id': 'call_DA0lpDIkBFg2GHy4WsEcZG4K', 'function': {'arguments': '{\"input\":\"3\"}', 'name': 'magic_function'}, 'type': 'function'}]} response_metadata={'token_usage': {'completion_tokens': 34, 'prompt_tokens': 97, 'total_tokens': 131}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'tool_calls', 'logprobs': None} id='run-d571b774-0ea3-4e35-8b7d-f32932c3f3cc-0' tool_calls=[{'name': 'magic_function', 'args': {'input': '3'}, 'id': 'call_DA0lpDIkBFg2GHy4WsEcZG4K'}]\n",
-      "content='Sorry, there was an error. Please try again.' name='magic_function' id='0b45787b-c82a-487f-9a5a-de129c30460f' tool_call_id='call_DA0lpDIkBFg2GHy4WsEcZG4K'\n",
-      "content='It appears that there is a consistent issue when trying to apply the magic function to the input \"3.\" This could be due to various reasons, such as the input not being in the correct format or an internal error.\\n\\nIf you have any other questions or if there\\'s something else you\\'d like to try, please let me know!' response_metadata={'token_usage': {'completion_tokens': 66, 'prompt_tokens': 153, 'total_tokens': 219}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'stop', 'logprobs': None} id='run-50a962e6-21b7-4327-8dea-8e2304062627-0'\n"
+      "content='' additional_kwargs={'tool_calls': [{'id': 'call_9fMkSAUGRa2BsADwF32ct1m1', 'function': {'arguments': '{\"input\":\"3\"}', 'name': 'magic_function'}, 'type': 'function'}]} response_metadata={'token_usage': {'completion_tokens': 14, 'prompt_tokens': 64, 'total_tokens': 78}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'tool_calls', 'logprobs': None} id='run-79084bff-6e10-49bb-b7f0-f613ebcc68ac-0' tool_calls=[{'name': 'magic_function', 'args': {'input': '3'}, 'id': 'call_9fMkSAUGRa2BsADwF32ct1m1'}]\n",
+      "content='Sorry, there was an error. Please try again.' name='magic_function' id='06f997fd-5309-4d56-afa3-2fe8cbf0d04f' tool_call_id='call_9fMkSAUGRa2BsADwF32ct1m1'\n",
+      "content='' additional_kwargs={'tool_calls': [{'id': 'call_Fg92zoL8oS5q6im2jR1INRvH', 'function': {'arguments': '{\"input\":\"3\"}', 'name': 'magic_function'}, 'type': 'function'}]} response_metadata={'token_usage': {'completion_tokens': 14, 'prompt_tokens': 97, 'total_tokens': 111}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'tool_calls', 'logprobs': None} id='run-fc2e201f-6330-4330-8c4e-1a66e85c1ffa-0' tool_calls=[{'name': 'magic_function', 'args': {'input': '3'}, 'id': 'call_Fg92zoL8oS5q6im2jR1INRvH'}]\n",
+      "content='Sorry, there was an error. Please try again.' name='magic_function' id='a931dd6e-2ed7-42ea-a58c-5ffb4041d7c9' tool_call_id='call_Fg92zoL8oS5q6im2jR1INRvH'\n",
+      "content='It seems there is an issue with processing the request for the value of `magic_function(3)`. Let me try a different approach.' additional_kwargs={'tool_calls': [{'id': 'call_lbYBMptprZ6HMqNiTvoqhmwP', 'function': {'arguments': '{\"input\":\"3\"}', 'name': 'magic_function'}, 'type': 'function'}]} response_metadata={'token_usage': {'completion_tokens': 43, 'prompt_tokens': 130, 'total_tokens': 173}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'tool_calls', 'logprobs': None} id='run-2e0baab0-c4c1-42e8-b49d-a2704ae977c0-0' tool_calls=[{'name': 'magic_function', 'args': {'input': '3'}, 'id': 'call_lbYBMptprZ6HMqNiTvoqhmwP'}]\n",
+      "content='Sorry, there was an error. Please try again.' name='magic_function' id='9957435a-5de3-4662-b23c-abfa31e71208' tool_call_id='call_lbYBMptprZ6HMqNiTvoqhmwP'\n",
+      "content='It appears that the `magic_function` is currently experiencing issues when attempting to process the input \"3\". Unfortunately, I can\\'t provide the value of `magic_function(3)` at this moment.\\n\\nIf you have any other questions or need assistance with something else, please let me know!' response_metadata={'token_usage': {'completion_tokens': 58, 'prompt_tokens': 195, 'total_tokens': 253}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'stop', 'logprobs': None} id='run-bb68d7ca-da76-43ad-80ab-23737a70c391-0'\n",
+      "{'input': 'what is the value of magic_function(3)?', 'output': 'Agent stopped due to max iterations.'}\n"
      ]
     }
    ],
@@ -787,7 +522,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 17,
+   "execution_count": 30,
    "id": "4b8498fc-a7af-4164-a401-d8714f082306",
    "metadata": {},
    "outputs": [
@@ -814,7 +549,7 @@
        " 'output': 'Agent stopped due to max iterations.'}"
       ]
      },
-     "execution_count": 17,
+     "execution_count": 30,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -855,7 +590,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 18,
+   "execution_count": 31,
    "id": "a2b29113-e6be-4f91-aa4c-5c63dea3e423",
    "metadata": {},
    "outputs": [
@@ -863,7 +598,7 @@
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "{'agent': {'messages': [AIMessage(content='', additional_kwargs={'tool_calls': [{'id': 'call_HaQkeCwD5QskzJzFixCBacZ4', 'function': {'arguments': '{\"input\":\"3\"}', 'name': 'magic_function'}, 'type': 'function'}]}, response_metadata={'token_usage': {'completion_tokens': 14, 'prompt_tokens': 64, 'total_tokens': 78}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'tool_calls', 'logprobs': None}, id='run-596c9200-771f-436d-8576-72fcb81620f1-0', tool_calls=[{'name': 'magic_function', 'args': {'input': '3'}, 'id': 'call_HaQkeCwD5QskzJzFixCBacZ4'}])]}}\n",
+      "{'agent': {'messages': [AIMessage(content='', additional_kwargs={'tool_calls': [{'id': 'call_GlXWTlJ0jQc2B8jQuDVFzmnc', 'function': {'arguments': '{\"input\":\"3\"}', 'name': 'magic_function'}, 'type': 'function'}]}, response_metadata={'token_usage': {'completion_tokens': 14, 'prompt_tokens': 64, 'total_tokens': 78}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'tool_calls', 'logprobs': None}, id='run-38a0459b-a363-4181-b7a3-f25cb5c5d728-0', tool_calls=[{'name': 'magic_function', 'args': {'input': '3'}, 'id': 'call_GlXWTlJ0jQc2B8jQuDVFzmnc'}])]}}\n",
       "------\n",
       "{'input': 'what is the value of magic_function(3)?', 'output': 'Agent stopped due to max iterations.'}\n"
      ]
@@ -889,12 +624,12 @@
    "id": "32a9db70",
    "metadata": {},
    "source": [
-    "The other way to set a single max timeout for an entire run is to directly use the python stdlib [asyncio](https://docs.python.org/3/library/asyncio.html) library."
+    "The other way to set a max timeout is just via python's stdlib [asyncio](https://docs.python.org/3/library/asyncio.html)."
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 19,
+   "execution_count": 34,
    "id": "e9eb55f4-a321-4bac-b52d-9e43b411cf92",
    "metadata": {},
    "outputs": [
@@ -902,9 +637,11 @@
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "{'agent': {'messages': [AIMessage(content='', additional_kwargs={'tool_calls': [{'id': 'call_4agJXUHtmHrOOMogjF6ZuzAv', 'function': {'arguments': '{\"input\":\"3\"}', 'name': 'magic_function'}, 'type': 'function'}]}, response_metadata={'token_usage': {'completion_tokens': 14, 'prompt_tokens': 64, 'total_tokens': 78}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'tool_calls', 'logprobs': None}, id='run-a1c77db7-405f-43d9-8d57-751f2ca1a58c-0', tool_calls=[{'name': 'magic_function', 'args': {'input': '3'}, 'id': 'call_4agJXUHtmHrOOMogjF6ZuzAv'}])]}}\n",
+      "{'agent': {'messages': [AIMessage(content='', additional_kwargs={'tool_calls': [{'id': 'call_cR1oJuYcNrOmcaaIRRvh5dSr', 'function': {'arguments': '{\"input\":\"3\"}', 'name': 'magic_function'}, 'type': 'function'}]}, response_metadata={'token_usage': {'completion_tokens': 14, 'prompt_tokens': 64, 'total_tokens': 78}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'tool_calls', 'logprobs': None}, id='run-1c03c5d6-4883-4ccd-aa78-53dbafa99622-0', tool_calls=[{'name': 'magic_function', 'args': {'input': '3'}, 'id': 'call_cR1oJuYcNrOmcaaIRRvh5dSr'}])]}}\n",
       "------\n",
-      "Task Cancelled.\n"
+      "{'action': {'messages': [ToolMessage(content='Sorry, there was an error. Please try again.', name='magic_function', id='596baf13-de35-4a4f-8b78-475b387a1f40', tool_call_id='call_cR1oJuYcNrOmcaaIRRvh5dSr')]}}\n",
+      "------\n",
+      "{'input': 'what is the value of magic_function(3)?', 'output': 'Task Cancelled.'}\n"
      ]
     }
    ],
@@ -928,290 +665,6 @@
     "except TimeoutError:\n",
     "    print(\"Task Cancelled.\")"
    ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "4884ac87",
-   "metadata": {},
-   "source": [
-    "## `early_stopping_method`\n",
-    "\n",
-    "With LangChain's [AgentExecutor](https://api.python.langchain.com/en/latest/agents/langchain.agents.agent.AgentExecutor.html#langchain.agents.agent.AgentExecutor.iter), you could configure an [early_stopping_method](https://api.python.langchain.com/en/latest/agents/langchain.agents.agent.AgentExecutor.html#langchain.agents.agent.AgentExecutor.early_stopping_method) to either return a string saying \"Agent stopped due to iteration limit or time limit.\" (`\"force\"`) or prompt the LLM a final time to respond (`\"generate\"`)."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 20,
-   "id": "3f6e2cf2",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "Output with early_stopping_method='force':\n",
-      "Agent stopped due to max iterations.\n"
-     ]
-    }
-   ],
-   "source": [
-    "from langchain.agents import AgentExecutor, create_tool_calling_agent\n",
-    "from langchain_core.prompts import ChatPromptTemplate\n",
-    "from langchain_core.tools import tool\n",
-    "from langchain_openai import ChatOpenAI\n",
-    "\n",
-    "model = ChatOpenAI(model=\"gpt-4o\")\n",
-    "\n",
-    "\n",
-    "prompt = ChatPromptTemplate.from_messages(\n",
-    "    [\n",
-    "        (\"system\", \"You are a helpful assistant.\"),\n",
-    "        (\"human\", \"{input}\"),\n",
-    "        # Placeholders fill up a **list** of messages\n",
-    "        (\"placeholder\", \"{agent_scratchpad}\"),\n",
-    "    ]\n",
-    ")\n",
-    "\n",
-    "\n",
-    "@tool\n",
-    "def magic_function(input: int) -> int:\n",
-    "    \"\"\"Applies a magic function to an input.\"\"\"\n",
-    "    return \"Sorry there was an error, please try again.\"\n",
-    "\n",
-    "\n",
-    "tools = [magic_function]\n",
-    "\n",
-    "agent = create_tool_calling_agent(model, tools, prompt=prompt)\n",
-    "agent_executor = AgentExecutor(\n",
-    "    agent=agent, tools=tools, early_stopping_method=\"force\", max_iterations=1\n",
-    ")\n",
-    "\n",
-    "result = agent_executor.invoke({\"input\": query})\n",
-    "print(\"Output with early_stopping_method='force':\")\n",
-    "print(result[\"output\"])"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "706e05c4",
-   "metadata": {},
-   "source": [
-    "#### In LangGraph\n",
-    "\n",
-    "In LangGraph, you can explicitly handle the response behavior outside the agent, since the full state can be accessed."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 21,
-   "id": "73cabbc4",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "('human', 'what is the value of magic_function(3)?')\n",
-      "content='' additional_kwargs={'tool_calls': [{'id': 'call_bTURmOn9C8zslmn0kMFeykIn', 'function': {'arguments': '{\"input\":3}', 'name': 'magic_function'}, 'type': 'function'}]} response_metadata={'token_usage': {'completion_tokens': 14, 'prompt_tokens': 64, 'total_tokens': 78}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'tool_calls', 'logprobs': None} id='run-0844a504-7e6b-4ea6-a069-7017e38121ee-0' tool_calls=[{'name': 'magic_function', 'args': {'input': 3}, 'id': 'call_bTURmOn9C8zslmn0kMFeykIn'}]\n",
-      "content='Sorry there was an error, please try again.' name='magic_function' id='00d5386f-eb23-4628-9a29-d9ce6a7098cc' tool_call_id='call_bTURmOn9C8zslmn0kMFeykIn'\n",
-      "content='' additional_kwargs={'tool_calls': [{'id': 'call_JYqvvvWmXow2u012DuPoDHFV', 'function': {'arguments': '{\"input\":3}', 'name': 'magic_function'}, 'type': 'function'}]} response_metadata={'token_usage': {'completion_tokens': 14, 'prompt_tokens': 96, 'total_tokens': 110}, 'model_name': 'gpt-4o', 'system_fingerprint': 'fp_729ea513f7', 'finish_reason': 'tool_calls', 'logprobs': None} id='run-b73b1b1c-c829-4348-98cd-60b315c85448-0' tool_calls=[{'name': 'magic_function', 'args': {'input': 3}, 'id': 'call_JYqvvvWmXow2u012DuPoDHFV'}]\n",
-      "{'input': 'what is the value of magic_function(3)?', 'output': 'Agent stopped due to max iterations.'}\n"
-     ]
-    }
-   ],
-   "source": [
-    "from langgraph.errors import GraphRecursionError\n",
-    "from langgraph.prebuilt import create_react_agent\n",
-    "\n",
-    "RECURSION_LIMIT = 2 * 1 + 1\n",
-    "\n",
-    "app = create_react_agent(model, tools=tools)\n",
-    "\n",
-    "try:\n",
-    "    for chunk in app.stream(\n",
-    "        {\"messages\": [(\"human\", query)]},\n",
-    "        {\"recursion_limit\": RECURSION_LIMIT},\n",
-    "        stream_mode=\"values\",\n",
-    "    ):\n",
-    "        print(chunk[\"messages\"][-1])\n",
-    "except GraphRecursionError:\n",
-    "    print({\"input\": query, \"output\": \"Agent stopped due to max iterations.\"})"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "017fe20e",
-   "metadata": {},
-   "source": [
-    "## `trim_intermediate_steps`\n",
-    "\n",
-    "With LangChain's [AgentExecutor](https://api.python.langchain.com/en/latest/agents/langchain.agents.agent.AgentExecutor.html#langchain.agents.agent.AgentExecutor), you could trim the intermediate steps of long-running agents using [trim_intermediate_steps](https://api.python.langchain.com/en/latest/agents/langchain.agents.agent.AgentExecutor.html#langchain.agents.agent.AgentExecutor.trim_intermediate_steps), which is either an integer (indicating the agent should keep the last N steps) or a custom function.\n",
-    "\n",
-    "For instance, we could trim the value so the agent only sees the most recent intermediate step."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 22,
-   "id": "b94bb169",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "Call number: 1\n",
-      "Call number: 2\n",
-      "Call number: 3\n",
-      "Call number: 4\n",
-      "Call number: 5\n",
-      "Call number: 6\n",
-      "Call number: 7\n",
-      "Call number: 8\n",
-      "Call number: 9\n",
-      "Call number: 10\n",
-      "Call number: 11\n",
-      "Call number: 12\n",
-      "Call number: 13\n",
-      "Call number: 14\n"
-     ]
-    },
-    {
-     "name": "stderr",
-     "output_type": "stream",
-     "text": [
-      "Stopping agent prematurely due to triggering stop condition\n"
-     ]
-    },
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "Call number: 15\n"
-     ]
-    }
-   ],
-   "source": [
-    "from langchain.agents import AgentExecutor, create_tool_calling_agent\n",
-    "from langchain_core.prompts import ChatPromptTemplate\n",
-    "from langchain_core.tools import tool\n",
-    "from langchain_openai import ChatOpenAI\n",
-    "\n",
-    "model = ChatOpenAI(model=\"gpt-4o\")\n",
-    "\n",
-    "\n",
-    "prompt = ChatPromptTemplate.from_messages(\n",
-    "    [\n",
-    "        (\"system\", \"You are a helpful assistant.\"),\n",
-    "        (\"human\", \"{input}\"),\n",
-    "        # Placeholders fill up a **list** of messages\n",
-    "        (\"placeholder\", \"{agent_scratchpad}\"),\n",
-    "    ]\n",
-    ")\n",
-    "\n",
-    "\n",
-    "magic_step_num = 1\n",
-    "\n",
-    "\n",
-    "@tool\n",
-    "def magic_function(input: int) -> int:\n",
-    "    \"\"\"Applies a magic function to an input.\"\"\"\n",
-    "    global magic_step_num\n",
-    "    print(f\"Call number: {magic_step_num}\")\n",
-    "    magic_step_num += 1\n",
-    "    return input + magic_step_num\n",
-    "\n",
-    "\n",
-    "tools = [magic_function]\n",
-    "\n",
-    "agent = create_tool_calling_agent(model, tools, prompt=prompt)\n",
-    "\n",
-    "\n",
-    "def trim_steps(steps: list):\n",
-    "    # Let's give the agent amnesia\n",
-    "    return []\n",
-    "\n",
-    "\n",
-    "agent_executor = AgentExecutor(\n",
-    "    agent=agent, tools=tools, trim_intermediate_steps=trim_steps\n",
-    ")\n",
-    "\n",
-    "\n",
-    "query = \"Call the magic function 4 times in sequence with the value 3. You cannot call it multiple times at once.\"\n",
-    "\n",
-    "for step in agent_executor.stream({\"input\": query}):\n",
-    "    pass"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "3d450c5a",
-   "metadata": {},
-   "source": [
-    "#### In LangGraph\n",
-    "\n",
-    "We can use the [`messages_modifier`](https://langchain-ai.github.io/langgraph/reference/prebuilt/#create_react_agent) just as before when passing in [prompt templates](#prompt-templates)."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 23,
-   "id": "b309ba9a",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "Call number: 1\n",
-      "Call number: 2\n",
-      "Call number: 3\n",
-      "Call number: 4\n",
-      "Call number: 5\n",
-      "Call number: 6\n",
-      "Call number: 7\n",
-      "Call number: 8\n",
-      "Call number: 9\n",
-      "Call number: 10\n",
-      "Call number: 11\n",
-      "Call number: 12\n",
-      "Stopping agent prematurely due to triggering stop condition\n"
-     ]
-    }
-   ],
-   "source": [
-    "from langchain_core.messages import AnyMessage\n",
-    "from langgraph.errors import GraphRecursionError\n",
-    "from langgraph.prebuilt import create_react_agent\n",
-    "\n",
-    "magic_step_num = 1\n",
-    "\n",
-    "\n",
-    "@tool\n",
-    "def magic_function(input: int) -> int:\n",
-    "    \"\"\"Applies a magic function to an input.\"\"\"\n",
-    "    global magic_step_num\n",
-    "    print(f\"Call number: {magic_step_num}\")\n",
-    "    magic_step_num += 1\n",
-    "    return input + magic_step_num\n",
-    "\n",
-    "\n",
-    "tools = [magic_function]\n",
-    "\n",
-    "\n",
-    "def _modify_messages(messages: list[AnyMessage]):\n",
-    "    # Give the agent amnesia, only keeping the original user query\n",
-    "    return [(\"system\", \"You are a helpful assistant\"), messages[0]]\n",
-    "\n",
-    "\n",
-    "app = create_react_agent(model, tools, messages_modifier=_modify_messages)\n",
-    "\n",
-    "try:\n",
-    "    for step in app.stream({\"messages\": [(\"human\", query)]}, stream_mode=\"updates\"):\n",
-    "        pass\n",
-    "except GraphRecursionError as e:\n",
-    "    print(\"Stopping agent prematurely due to triggering stop condition\")"
-   ]
   }
  ],
  "metadata": {

docs/docs/how_to/multi_vector.ipynb

@@ -5,36 +5,33 @@
    "id": "d9172545",
    "metadata": {},
    "source": [
-    "# How to retrieve using multiple vectors per document\n",
+    "# How to use the MultiVector Retriever\n",
     "\n",
-    "It can often be useful to store multiple vectors per document. There are multiple use cases where this is beneficial. For example, we can embed multiple chunks of a document and associate those embeddings with the parent document, allowing retriever hits on the chunks to return the larger document.\n",
-    "\n",
-    "LangChain implements a base [MultiVectorRetriever](https://api.python.langchain.com/en/latest/retrievers/langchain.retrievers.multi_vector.MultiVectorRetriever.html), which simplifies this process. Much of the complexity lies in how to create the multiple vectors per document. This notebook covers some of the common ways to create those vectors and use the `MultiVectorRetriever`.\n",
+    "It can often be beneficial to store multiple vectors per document. There are multiple use cases where this is beneficial. LangChain has a base `MultiVectorRetriever` which makes querying this type of setup easy. A lot of the complexity lies in how to create the multiple vectors per document. This notebook covers some of the common ways to create those vectors and use the `MultiVectorRetriever`.\n",
     "\n",
     "The methods to create multiple vectors per document include:\n",
     "\n",
-    "- Smaller chunks: split a document into smaller chunks, and embed those (this is [ParentDocumentRetriever](https://api.python.langchain.com/en/latest/retrievers/langchain.retrievers.parent_document_retriever.ParentDocumentRetriever.html)).\n",
+    "- Smaller chunks: split a document into smaller chunks, and embed those (this is ParentDocumentRetriever).\n",
     "- Summary: create a summary for each document, embed that along with (or instead of) the document.\n",
     "- Hypothetical questions: create hypothetical questions that each document would be appropriate to answer, embed those along with (or instead of) the document.\n",
     "\n",
-    "Note that this also enables another method of adding embeddings - manually. This is useful because you can explicitly add questions or queries that should lead to a document being recovered, giving you more control.\n",
     "\n",
-    "Below we walk through an example. First we instantiate some documents. We will index them in an (in-memory) [Chroma](/docs/integrations/providers/chroma/) vector store using [OpenAI](https://python.langchain.com/v0.2/docs/integrations/text_embedding/openai/) embeddings, but any LangChain vector store or embeddings model will suffice."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "09cecd95-3499-465a-895a-944627ffb77f",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "%pip install --upgrade --quiet  langchain-chroma langchain langchain-openai > /dev/null"
+    "Note that this also enables another method of adding embeddings - manually. This is great because you can explicitly add questions or queries that should lead to a document being recovered, giving you more control."
    ]
   },
   {
    "cell_type": "code",
    "execution_count": 1,
+   "id": "eed469be",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain.retrievers.multi_vector import MultiVectorRetriever"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 2,
    "id": "18c1421a",
    "metadata": {},
    "outputs": [],
@@ -43,22 +40,25 @@
     "from langchain_chroma import Chroma\n",
     "from langchain_community.document_loaders import TextLoader\n",
     "from langchain_openai import OpenAIEmbeddings\n",
-    "from langchain_text_splitters import RecursiveCharacterTextSplitter\n",
-    "\n",
+    "from langchain_text_splitters import RecursiveCharacterTextSplitter"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 3,
+   "id": "6d869496",
+   "metadata": {},
+   "outputs": [],
+   "source": [
     "loaders = [\n",
-    "    TextLoader(\"paul_graham_essay.txt\"),\n",
+    "    TextLoader(\"../../paul_graham_essay.txt\"),\n",
     "    TextLoader(\"state_of_the_union.txt\"),\n",
     "]\n",
     "docs = []\n",
     "for loader in loaders:\n",
     "    docs.extend(loader.load())\n",
     "text_splitter = RecursiveCharacterTextSplitter(chunk_size=10000)\n",
-    "docs = text_splitter.split_documents(docs)\n",
-    "\n",
-    "# The vectorstore to use to index the child chunks\n",
-    "vectorstore = Chroma(\n",
-    "    collection_name=\"full_documents\", embedding_function=OpenAIEmbeddings()\n",
-    ")"
+    "docs = text_splitter.split_documents(docs)"
    ]
   },
   {
@@ -68,54 +68,52 @@
    "source": [
     "## Smaller chunks\n",
     "\n",
-    "Often times it can be useful to retrieve larger chunks of information, but embed smaller chunks. This allows for embeddings to capture the semantic meaning as closely as possible, but for as much context as possible to be passed downstream. Note that this is what the [ParentDocumentRetriever](https://api.python.langchain.com/en/latest/retrievers/langchain.retrievers.parent_document_retriever.ParentDocumentRetriever.html) does. Here we show what is going on under the hood.\n",
-    "\n",
-    "We will make a distinction between the vector store, which indexes embeddings of the (sub) documents, and the document store, which houses the \"parent\" documents and associates them with an identifier."
+    "Often times it can be useful to retrieve larger chunks of information, but embed smaller chunks. This allows for embeddings to capture the semantic meaning as closely as possible, but for as much context as possible to be passed downstream. Note that this is what the `ParentDocumentRetriever` does. Here we show what is going on under the hood."
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 2,
+   "execution_count": 4,
    "id": "0e7b6b45",
    "metadata": {},
    "outputs": [],
    "source": [
-    "import uuid\n",
-    "\n",
-    "from langchain.retrievers.multi_vector import MultiVectorRetriever\n",
-    "\n",
+    "# The vectorstore to use to index the child chunks\n",
+    "vectorstore = Chroma(\n",
+    "    collection_name=\"full_documents\", embedding_function=OpenAIEmbeddings()\n",
+    ")\n",
     "# The storage layer for the parent documents\n",
     "store = InMemoryByteStore()\n",
     "id_key = \"doc_id\"\n",
-    "\n",
     "# The retriever (empty to start)\n",
     "retriever = MultiVectorRetriever(\n",
     "    vectorstore=vectorstore,\n",
     "    byte_store=store,\n",
     "    id_key=id_key,\n",
     ")\n",
+    "import uuid\n",
     "\n",
     "doc_ids = [str(uuid.uuid4()) for _ in docs]"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "id": "d4feded4-856a-4282-91c3-53aabc62e6ff",
-   "metadata": {},
-   "source": [
-    "We next generate the \"sub\" documents by splitting the original documents. Note that we store the document identifier in the `metadata` of the corresponding [Document](https://api.python.langchain.com/en/latest/documents/langchain_core.documents.base.Document.html) object."
-   ]
-  },
   {
    "cell_type": "code",
-   "execution_count": 3,
-   "id": "5d23247d",
+   "execution_count": 5,
+   "id": "72a36491",
    "metadata": {},
    "outputs": [],
    "source": [
     "# The splitter to use to create smaller chunks\n",
-    "child_text_splitter = RecursiveCharacterTextSplitter(chunk_size=400)\n",
-    "\n",
+    "child_text_splitter = RecursiveCharacterTextSplitter(chunk_size=400)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 6,
+   "id": "5d23247d",
+   "metadata": {},
+   "outputs": [],
+   "source": [
     "sub_docs = []\n",
     "for i, doc in enumerate(docs):\n",
     "    _id = doc_ids[i]\n",
@@ -125,17 +123,9 @@
     "    sub_docs.extend(_sub_docs)"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "id": "8e0634f8-90d5-4250-981a-5257c8a6d455",
-   "metadata": {},
-   "source": [
-    "Finally, we index the documents in our vector store and document store:"
-   ]
-  },
   {
    "cell_type": "code",
-   "execution_count": 4,
+   "execution_count": 7,
    "id": "92ed5861",
    "metadata": {},
    "outputs": [],
@@ -144,46 +134,31 @@
     "retriever.docstore.mset(list(zip(doc_ids, docs)))"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "id": "14c48c6d-850c-4317-9b6e-1ade92f2f710",
-   "metadata": {},
-   "source": [
-    "The vector store alone will retrieve small chunks:"
-   ]
-  },
   {
    "cell_type": "code",
-   "execution_count": 5,
+   "execution_count": 8,
    "id": "8afed60c",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "Document(page_content='Tonight, I’d like to honor someone who has dedicated his life to serve this country: Justice Stephen Breyer—an Army veteran, Constitutional scholar, and retiring Justice of the United States Supreme Court. Justice Breyer, thank you for your service. \\n\\nOne of the most serious constitutional responsibilities a President has is nominating someone to serve on the United States Supreme Court.', metadata={'doc_id': '064eca46-a4c4-4789-8e3b-583f9597e54f', 'source': 'state_of_the_union.txt'})"
+       "Document(page_content='Tonight, I’d like to honor someone who has dedicated his life to serve this country: Justice Stephen Breyer—an Army veteran, Constitutional scholar, and retiring Justice of the United States Supreme Court. Justice Breyer, thank you for your service. \\n\\nOne of the most serious constitutional responsibilities a President has is nominating someone to serve on the United States Supreme Court.', metadata={'doc_id': '2fd77862-9ed5-4fad-bf76-e487b747b333', 'source': 'state_of_the_union.txt'})"
       ]
      },
-     "execution_count": 5,
+     "execution_count": 8,
      "metadata": {},
      "output_type": "execute_result"
     }
    ],
    "source": [
+    "# Vectorstore alone retrieves the small chunks\n",
     "retriever.vectorstore.similarity_search(\"justice breyer\")[0]"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "id": "717097c7-61d9-4306-8625-ef8f1940c127",
-   "metadata": {},
-   "source": [
-    "Whereas the retriever will return the larger parent document:"
-   ]
-  },
   {
    "cell_type": "code",
-   "execution_count": 6,
+   "execution_count": 9,
    "id": "3c9017f1",
    "metadata": {},
    "outputs": [
@@ -193,13 +168,14 @@
        "9875"
       ]
      },
-     "execution_count": 6,
+     "execution_count": 9,
      "metadata": {},
      "output_type": "execute_result"
     }
    ],
    "source": [
-    "len(retriever.invoke(\"justice breyer\")[0].page_content)"
+    "# Retriever returns larger chunks\n",
+    "len(retriever.get_relevant_documents(\"justice breyer\")[0].page_content)"
    ]
   },
   {
@@ -207,12 +183,12 @@
    "id": "cdef8339-f9fa-4b3b-955f-ad9dbdf2734f",
    "metadata": {},
    "source": [
-    "The default search type the retriever performs on the vector database is a similarity search. LangChain vector stores also support searching via [Max Marginal Relevance](https://api.python.langchain.com/en/latest/vectorstores/langchain_core.vectorstores.VectorStore.html#langchain_core.vectorstores.VectorStore.max_marginal_relevance_search). This can be controlled via the `search_type` parameter of the retriever:"
+    "The default search type the retriever performs on the vector database is a similarity search. LangChain Vector Stores also support searching via [Max Marginal Relevance](https://api.python.langchain.com/en/latest/vectorstores/langchain_core.vectorstores.VectorStore.html#langchain_core.vectorstores.VectorStore.max_marginal_relevance_search) so if you want this instead you can just set the `search_type` property as follows:"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 7,
+   "execution_count": 10,
    "id": "36739460-a737-4a8e-b70f-50bf8c8eaae7",
    "metadata": {},
    "outputs": [
@@ -222,7 +198,7 @@
        "9875"
       ]
      },
-     "execution_count": 7,
+     "execution_count": 10,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -232,7 +208,7 @@
     "\n",
     "retriever.search_type = SearchType.mmr\n",
     "\n",
-    "len(retriever.invoke(\"justice breyer\")[0].page_content)"
+    "len(retriever.get_relevant_documents(\"justice breyer\")[0].page_content)"
    ]
   },
   {
@@ -240,37 +216,14 @@
    "id": "d6a7ae0d",
    "metadata": {},
    "source": [
-    "## Associating summaries with a document for retrieval\n",
+    "## Summary\n",
     "\n",
-    "A summary may be able to distill more accurately what a chunk is about, leading to better retrieval. Here we show how to create summaries, and then embed those.\n",
-    "\n",
-    "We construct a simple [chain](/docs/how_to/sequence) that will receive an input [Document](https://api.python.langchain.com/en/latest/documents/langchain_core.documents.base.Document.html) object and generate a summary using a LLM.\n",
-    "\n",
-    "```{=mdx}\n",
-    "import ChatModelTabs from \"@theme/ChatModelTabs\";\n",
-    "\n",
-    "<ChatModelTabs customVarName=\"llm\" />\n",
-    "```"
+    "Oftentimes a summary may be able to distill more accurately what a chunk is about, leading to better retrieval. Here we show how to create summaries, and then embed those."
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 8,
-   "id": "6589291f-55bb-4e9a-b4ff-08f2506ed641",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "# | output: false\n",
-    "# | echo: false\n",
-    "\n",
-    "from langchain_openai import ChatOpenAI\n",
-    "\n",
-    "llm = ChatOpenAI()"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 9,
+   "execution_count": 11,
    "id": "1433dff4",
    "metadata": {},
    "outputs": [],
@@ -280,26 +233,27 @@
     "from langchain_core.documents import Document\n",
     "from langchain_core.output_parsers import StrOutputParser\n",
     "from langchain_core.prompts import ChatPromptTemplate\n",
-    "\n",
+    "from langchain_openai import ChatOpenAI"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 12,
+   "id": "35b30390",
+   "metadata": {},
+   "outputs": [],
+   "source": [
     "chain = (\n",
     "    {\"doc\": lambda x: x.page_content}\n",
     "    | ChatPromptTemplate.from_template(\"Summarize the following document:\\n\\n{doc}\")\n",
-    "    | llm\n",
+    "    | ChatOpenAI(max_retries=0)\n",
     "    | StrOutputParser()\n",
     ")"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "id": "3faa9fde-1b09-4849-a815-8b2e89c30a02",
-   "metadata": {},
-   "source": [
-    "Note that we can [batch](https://api.python.langchain.com/en/latest/runnables/langchain_core.runnables.base.Runnable.html#langchain_core.runnables.base.Runnable) the chain accross documents:"
-   ]
-  },
   {
    "cell_type": "code",
-   "execution_count": 10,
+   "execution_count": 13,
    "id": "41a2a738",
    "metadata": {},
    "outputs": [],
@@ -307,17 +261,9 @@
     "summaries = chain.batch(docs, {\"max_concurrency\": 5})"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "id": "73ef599e-140b-4905-8b62-6c52cdde1852",
-   "metadata": {},
-   "source": [
-    "We can then initialize a `MultiVectorRetriever` as before, indexing the summaries in our vector store, and retaining the original documents in our document store:"
-   ]
-  },
   {
    "cell_type": "code",
-   "execution_count": 11,
+   "execution_count": 14,
    "id": "7ac5e4b1",
    "metadata": {},
    "outputs": [],
@@ -333,13 +279,29 @@
     "    byte_store=store,\n",
     "    id_key=id_key,\n",
     ")\n",
-    "doc_ids = [str(uuid.uuid4()) for _ in docs]\n",
-    "\n",
+    "doc_ids = [str(uuid.uuid4()) for _ in docs]"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 15,
+   "id": "0d93309f",
+   "metadata": {},
+   "outputs": [],
+   "source": [
     "summary_docs = [\n",
     "    Document(page_content=s, metadata={id_key: doc_ids[i]})\n",
     "    for i, s in enumerate(summaries)\n",
-    "]\n",
-    "\n",
+    "]"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 16,
+   "id": "6d5edf0d",
+   "metadata": {},
+   "outputs": [],
+   "source": [
     "retriever.vectorstore.add_documents(summary_docs)\n",
     "retriever.docstore.mset(list(zip(doc_ids, docs)))"
    ]
@@ -358,48 +320,50 @@
    ]
   },
   {
-   "cell_type": "markdown",
-   "id": "f0274892-29c1-4616-9040-d23f9d537526",
+   "cell_type": "code",
+   "execution_count": 18,
+   "id": "299232d6",
    "metadata": {},
+   "outputs": [],
    "source": [
-    "Querying the vector store will return summaries:"
+    "sub_docs = vectorstore.similarity_search(\"justice breyer\")"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 12,
-   "id": "299232d6",
+   "execution_count": 19,
+   "id": "10e404c0",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "Document(page_content=\"President Biden recently nominated Judge Ketanji Brown Jackson to serve on the United States Supreme Court, emphasizing her qualifications and broad support. The President also outlined a plan to secure the border, fix the immigration system, protect women's rights, support LGBTQ+ Americans, and advance mental health services. He highlighted the importance of bipartisan unity in passing legislation, such as the Violence Against Women Act. The President also addressed supporting veterans, particularly those impacted by exposure to burn pits, and announced plans to expand benefits for veterans with respiratory cancers. Additionally, he proposed a plan to end cancer as we know it through the Cancer Moonshot initiative. President Biden expressed optimism about the future of America and emphasized the strength of the American people in overcoming challenges.\", metadata={'doc_id': '84015b1b-980e-400a-94d8-cf95d7e079bd'})"
+       "Document(page_content=\"The document is a speech given by President Biden addressing various issues and outlining his agenda for the nation. He highlights the importance of nominating a Supreme Court justice and introduces his nominee, Judge Ketanji Brown Jackson. He emphasizes the need to secure the border and reform the immigration system, including providing a pathway to citizenship for Dreamers and essential workers. The President also discusses the protection of women's rights, including access to healthcare and the right to choose. He calls for the passage of the Equality Act to protect LGBTQ+ rights. Additionally, President Biden discusses the need to address the opioid epidemic, improve mental health services, support veterans, and fight against cancer. He expresses optimism for the future of America and the strength of the American people.\", metadata={'doc_id': '56345bff-3ead-418c-a4ff-dff203f77474'})"
       ]
      },
-     "execution_count": 12,
+     "execution_count": 19,
      "metadata": {},
      "output_type": "execute_result"
     }
    ],
    "source": [
-    "sub_docs = retriever.vectorstore.similarity_search(\"justice breyer\")\n",
-    "\n",
     "sub_docs[0]"
    ]
   },
   {
-   "cell_type": "markdown",
-   "id": "e4f77ac5-2926-4f60-aad5-b2067900dff9",
+   "cell_type": "code",
+   "execution_count": 20,
+   "id": "e4cce5c2",
    "metadata": {},
+   "outputs": [],
    "source": [
-    "Whereas the retriever will return the larger source document:"
+    "retrieved_docs = retriever.get_relevant_documents(\"justice breyer\")"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 13,
-   "id": "e4cce5c2",
+   "execution_count": 21,
+   "id": "c8570dbb",
    "metadata": {},
    "outputs": [
     {
@@ -408,14 +372,12 @@
        "9194"
       ]
      },
-     "execution_count": 13,
+     "execution_count": 21,
      "metadata": {},
      "output_type": "execute_result"
     }
    ],
    "source": [
-    "retrieved_docs = retriever.invoke(\"justice breyer\")\n",
-    "\n",
     "len(retrieved_docs[0].page_content)"
    ]
   },
@@ -426,28 +388,42 @@
    "source": [
     "## Hypothetical Queries\n",
     "\n",
-    "An LLM can also be used to generate a list of hypothetical questions that could be asked of a particular document, which might bear close semantic similarity to relevant queries in a [RAG](/docs/tutorials/rag) application. These questions can then be embedded and associated with the documents to improve retrieval.\n",
-    "\n",
-    "Below, we use the [with_structured_output](/docs/how_to/structured_output/) method to structure the LLM output into a list of strings."
+    "An LLM can also be used to generate a list of hypothetical questions that could be asked of a particular document. These questions can then be embedded"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 16,
-   "id": "03d85234-c33a-4a43-861d-47328e1ec2ea",
+   "execution_count": 22,
+   "id": "5219b085",
    "metadata": {},
    "outputs": [],
    "source": [
-    "from typing import List\n",
-    "\n",
-    "from langchain_core.pydantic_v1 import BaseModel, Field\n",
-    "\n",
-    "\n",
-    "class HypotheticalQuestions(BaseModel):\n",
-    "    \"\"\"Generate hypothetical questions.\"\"\"\n",
-    "\n",
-    "    questions: List[str] = Field(..., description=\"List of questions\")\n",
-    "\n",
+    "functions = [\n",
+    "    {\n",
+    "        \"name\": \"hypothetical_questions\",\n",
+    "        \"description\": \"Generate hypothetical questions\",\n",
+    "        \"parameters\": {\n",
+    "            \"type\": \"object\",\n",
+    "            \"properties\": {\n",
+    "                \"questions\": {\n",
+    "                    \"type\": \"array\",\n",
+    "                    \"items\": {\"type\": \"string\"},\n",
+    "                },\n",
+    "            },\n",
+    "            \"required\": [\"questions\"],\n",
+    "        },\n",
+    "    }\n",
+    "]"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 23,
+   "id": "523deb92",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain.output_parsers.openai_functions import JsonKeyOutputFunctionsParser\n",
     "\n",
     "chain = (\n",
     "    {\"doc\": lambda x: x.page_content}\n",
@@ -455,36 +431,28 @@
     "    | ChatPromptTemplate.from_template(\n",
     "        \"Generate a list of exactly 3 hypothetical questions that the below document could be used to answer:\\n\\n{doc}\"\n",
     "    )\n",
-    "    | ChatOpenAI(max_retries=0, model=\"gpt-4o\").with_structured_output(\n",
-    "        HypotheticalQuestions\n",
+    "    | ChatOpenAI(max_retries=0, model=\"gpt-4\").bind(\n",
+    "        functions=functions, function_call={\"name\": \"hypothetical_questions\"}\n",
     "    )\n",
-    "    | (lambda x: x.questions)\n",
+    "    | JsonKeyOutputFunctionsParser(key_name=\"questions\")\n",
     ")"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "id": "6dddc40f-62af-413c-b944-f94a5e1f2f4e",
-   "metadata": {},
-   "source": [
-    "Invoking the chain on a single document demonstrates that it outputs a list of questions:"
-   ]
-  },
   {
    "cell_type": "code",
-   "execution_count": 17,
+   "execution_count": 24,
    "id": "11d30554",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "[\"What impact did the IBM 1401 have on the author's early programming experiences?\",\n",
-       " \"How did the transition from using the IBM 1401 to microcomputers influence the author's programming journey?\",\n",
-       " \"What role did Lisp play in shaping the author's understanding and approach to AI?\"]"
+       "[\"What was the author's first experience with programming like?\",\n",
+       " 'Why did the author switch their focus from AI to Lisp during their graduate studies?',\n",
+       " 'What led the author to contemplate a career in art instead of computer science?']"
       ]
      },
-     "execution_count": 17,
+     "execution_count": 24,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -494,24 +462,22 @@
    ]
   },
   {
-   "cell_type": "markdown",
-   "id": "dcffc572-7b20-4b77-857a-90ec360a8f7e",
+   "cell_type": "code",
+   "execution_count": 25,
+   "id": "3eb2e48c",
    "metadata": {},
+   "outputs": [],
    "source": [
-    "We can batch then batch the chain over all documents and assemble our vector store and document store as before:"
+    "hypothetical_questions = chain.batch(docs, {\"max_concurrency\": 5})"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 18,
+   "execution_count": 26,
    "id": "b2cd6e75",
    "metadata": {},
    "outputs": [],
    "source": [
-    "# Batch chain over documents to generate hypothetical questions\n",
-    "hypothetical_questions = chain.batch(docs, {\"max_concurrency\": 5})\n",
-    "\n",
-    "\n",
     "# The vectorstore to use to index the child chunks\n",
     "vectorstore = Chroma(\n",
     "    collection_name=\"hypo-questions\", embedding_function=OpenAIEmbeddings()\n",
@@ -525,67 +491,82 @@
     "    byte_store=store,\n",
     "    id_key=id_key,\n",
     ")\n",
-    "doc_ids = [str(uuid.uuid4()) for _ in docs]\n",
-    "\n",
-    "\n",
-    "# Generate Document objects from hypothetical questions\n",
+    "doc_ids = [str(uuid.uuid4()) for _ in docs]"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 27,
+   "id": "18831b3b",
+   "metadata": {},
+   "outputs": [],
+   "source": [
     "question_docs = []\n",
     "for i, question_list in enumerate(hypothetical_questions):\n",
     "    question_docs.extend(\n",
     "        [Document(page_content=s, metadata={id_key: doc_ids[i]}) for s in question_list]\n",
-    "    )\n",
-    "\n",
-    "\n",
+    "    )"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 28,
+   "id": "224b24c5",
+   "metadata": {},
+   "outputs": [],
+   "source": [
     "retriever.vectorstore.add_documents(question_docs)\n",
     "retriever.docstore.mset(list(zip(doc_ids, docs)))"
    ]
   },
   {
-   "cell_type": "markdown",
-   "id": "75cba8ab-a06f-4545-85fc-cf49d0204b5e",
+   "cell_type": "code",
+   "execution_count": 29,
+   "id": "7b442b90",
    "metadata": {},
+   "outputs": [],
    "source": [
-    "Note that querying the underlying vector store will retrieve hypothetical questions that are semantically similar to the input query:"
+    "sub_docs = vectorstore.similarity_search(\"justice breyer\")"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 19,
-   "id": "7b442b90",
+   "execution_count": 30,
+   "id": "089b5ad0",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "[Document(page_content='What might be the potential benefits of nominating Circuit Court of Appeals Judge Ketanji Brown Jackson to the United States Supreme Court?', metadata={'doc_id': '43292b74-d1b8-4200-8a8b-ea0cb57fbcdb'}),\n",
-       " Document(page_content='How might the Bipartisan Infrastructure Law impact the economic competition between the U.S. and China?', metadata={'doc_id': '66174780-d00c-4166-9791-f0069846e734'}),\n",
-       " Document(page_content='What factors led to the creation of Y Combinator?', metadata={'doc_id': '72003c4e-4cc9-4f09-a787-0b541a65b38c'}),\n",
-       " Document(page_content='How did the ability to publish essays online change the landscape for writers and thinkers?', metadata={'doc_id': 'e8d2c648-f245-4bcc-b8d3-14e64a164b64'})]"
+       "[Document(page_content='Who has been nominated to serve on the United States Supreme Court?', metadata={'doc_id': '0b3a349e-c936-4e77-9c40-0a39fc3e07f0'}),\n",
+       " Document(page_content=\"What was the context and content of Robert Morris' advice to the document's author in 2010?\", metadata={'doc_id': 'b2b2cdca-988a-4af1-ba47-46170770bc8c'}),\n",
+       " Document(page_content='How did personal circumstances influence the decision to pass on the leadership of Y Combinator?', metadata={'doc_id': 'b2b2cdca-988a-4af1-ba47-46170770bc8c'}),\n",
+       " Document(page_content='What were the reasons for the author leaving Yahoo in the summer of 1999?', metadata={'doc_id': 'ce4f4981-ca60-4f56-86f0-89466de62325'})]"
       ]
      },
-     "execution_count": 19,
+     "execution_count": 30,
      "metadata": {},
      "output_type": "execute_result"
     }
    ],
    "source": [
-    "sub_docs = retriever.vectorstore.similarity_search(\"justice breyer\")\n",
-    "\n",
     "sub_docs"
    ]
   },
   {
-   "cell_type": "markdown",
-   "id": "63c32e43-5f4a-463b-a0c2-2101986f70e6",
+   "cell_type": "code",
+   "execution_count": 31,
+   "id": "7594b24e",
    "metadata": {},
+   "outputs": [],
    "source": [
-    "And invoking the retriever will return the corresponding document:"
+    "retrieved_docs = retriever.get_relevant_documents(\"justice breyer\")"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 20,
-   "id": "7594b24e",
+   "execution_count": 32,
+   "id": "4c120c65",
    "metadata": {},
    "outputs": [
     {
@@ -594,15 +575,22 @@
        "9194"
       ]
      },
-     "execution_count": 20,
+     "execution_count": 32,
      "metadata": {},
      "output_type": "execute_result"
     }
    ],
    "source": [
-    "retrieved_docs = retriever.invoke(\"justice breyer\")\n",
     "len(retrieved_docs[0].page_content)"
    ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "005072b8",
+   "metadata": {},
+   "outputs": [],
+   "source": []
   }
  ],
  "metadata": {
@@ -621,7 +609,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.10.4"
+   "version": "3.10.1"
   }
  },
  "nbformat": 4,

docs/docs/how_to/multimodal_inputs.ipynb

@@ -1,228 +0,0 @@
-{
- "cells": [
-  {
-   "cell_type": "markdown",
-   "id": "4facdf7f-680e-4d28-908b-2b8408e2a741",
-   "metadata": {},
-   "source": [
-    "# How to pass multimodal data directly to models\n",
-    "\n",
-    "Here we demonstrate how to pass multimodal input directly to models. \n",
-    "We currently expect all input to be passed in the same format as [OpenAI expects](https://platform.openai.com/docs/guides/vision).\n",
-    "For other model providers that support multimodal input, we have added logic inside the class to convert to the expected format.\n",
-    "\n",
-    "In this example we will ask a model to describe an image."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 1,
-   "id": "0d9fd81a-b7f0-445a-8e3d-cfc2d31fdd59",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "image_url = \"https://upload.wikimedia.org/wikipedia/commons/thumb/d/dd/Gfp-wisconsin-madison-the-nature-boardwalk.jpg/2560px-Gfp-wisconsin-madison-the-nature-boardwalk.jpg\""
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 2,
-   "id": "fb896ce9",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "from langchain_core.messages import HumanMessage\n",
-    "from langchain_openai import ChatOpenAI\n",
-    "\n",
-    "model = ChatOpenAI(model=\"gpt-4o\")"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "4fca4da7",
-   "metadata": {},
-   "source": [
-    "The most commonly supported way to pass in images is to pass it in as a byte string.\n",
-    "This should work for most model integrations."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 3,
-   "id": "9ca1040c",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "import base64\n",
-    "\n",
-    "import httpx\n",
-    "\n",
-    "image_data = base64.b64encode(httpx.get(image_url).content).decode(\"utf-8\")"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 4,
-   "id": "ec680b6b",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "The weather in the image appears to be clear and pleasant. The sky is mostly blue with scattered, light clouds, suggesting a sunny day with minimal cloud cover. There is no indication of rain or strong winds, and the overall scene looks bright and calm. The lush green grass and clear visibility further indicate good weather conditions.\n"
-     ]
-    }
-   ],
-   "source": [
-    "message = HumanMessage(\n",
-    "    content=[\n",
-    "        {\"type\": \"text\", \"text\": \"describe the weather in this image\"},\n",
-    "        {\n",
-    "            \"type\": \"image_url\",\n",
-    "            \"image_url\": {\"url\": f\"data:image/jpeg;base64,{image_data}\"},\n",
-    "        },\n",
-    "    ],\n",
-    ")\n",
-    "response = model.invoke([message])\n",
-    "print(response.content)"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "8656018e-c56d-47d2-b2be-71e87827f90a",
-   "metadata": {},
-   "source": [
-    "We can feed the image URL directly in a content block of type \"image_url\". Note that only some model providers support this."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 5,
-   "id": "a8819cf3-5ddc-44f0-889a-19ca7b7fe77e",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "The weather in the image appears to be clear and sunny. The sky is mostly blue with a few scattered clouds, suggesting good visibility and a likely pleasant temperature. The bright sunlight is casting distinct shadows on the grass and vegetation, indicating it is likely daytime, possibly late morning or early afternoon. The overall ambiance suggests a warm and inviting day, suitable for outdoor activities.\n"
-     ]
-    }
-   ],
-   "source": [
-    "message = HumanMessage(\n",
-    "    content=[\n",
-    "        {\"type\": \"text\", \"text\": \"describe the weather in this image\"},\n",
-    "        {\"type\": \"image_url\", \"image_url\": {\"url\": image_url}},\n",
-    "    ],\n",
-    ")\n",
-    "response = model.invoke([message])\n",
-    "print(response.content)"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "1c470309",
-   "metadata": {},
-   "source": [
-    "We can also pass in multiple images."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 6,
-   "id": "325fb4ca",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "Yes, the two images are the same. They both depict a wooden boardwalk extending through a grassy field under a blue sky with light clouds. The scenery, lighting, and composition are identical.\n"
-     ]
-    }
-   ],
-   "source": [
-    "message = HumanMessage(\n",
-    "    content=[\n",
-    "        {\"type\": \"text\", \"text\": \"are these two images the same?\"},\n",
-    "        {\"type\": \"image_url\", \"image_url\": {\"url\": image_url}},\n",
-    "        {\"type\": \"image_url\", \"image_url\": {\"url\": image_url}},\n",
-    "    ],\n",
-    ")\n",
-    "response = model.invoke([message])\n",
-    "print(response.content)"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "71bd28cf-d76c-44e2-a55e-c5f265db986e",
-   "metadata": {},
-   "source": [
-    "## Tool calls\n",
-    "\n",
-    "Some multimodal models support [tool calling](/docs/concepts/#functiontool-calling) features as well. To call tools using such models, simply bind tools to them in the [usual way](/docs/how_to/tool_calling), and invoke the model using content blocks of the desired type (e.g., containing image data)."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 8,
-   "id": "cd22ea82-2f93-46f9-9f7a-6aaf479fcaa9",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "[{'name': 'weather_tool', 'args': {'weather': 'sunny'}, 'id': 'call_BSX4oq4SKnLlp2WlzDhToHBr'}]\n"
-     ]
-    }
-   ],
-   "source": [
-    "from typing import Literal\n",
-    "\n",
-    "from langchain_core.tools import tool\n",
-    "\n",
-    "\n",
-    "@tool\n",
-    "def weather_tool(weather: Literal[\"sunny\", \"cloudy\", \"rainy\"]) -> None:\n",
-    "    \"\"\"Describe the weather\"\"\"\n",
-    "    pass\n",
-    "\n",
-    "\n",
-    "model_with_tools = model.bind_tools([weather_tool])\n",
-    "\n",
-    "message = HumanMessage(\n",
-    "    content=[\n",
-    "        {\"type\": \"text\", \"text\": \"describe the weather in this image\"},\n",
-    "        {\"type\": \"image_url\", \"image_url\": {\"url\": image_url}},\n",
-    "    ],\n",
-    ")\n",
-    "response = model_with_tools.invoke([message])\n",
-    "print(response.tool_calls)"
-   ]
-  }
- ],
- "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/how_to/multimodal_prompts.ipynb

@@ -1,184 +0,0 @@
-{
- "cells": [
-  {
-   "cell_type": "markdown",
-   "id": "4facdf7f-680e-4d28-908b-2b8408e2a741",
-   "metadata": {},
-   "source": [
-    "# How to use multimodal prompts\n",
-    "\n",
-    "Here we demonstrate how to use prompt templates to format multimodal inputs to models. \n",
-    "\n",
-    "In this example we will ask a model to describe an image."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 7,
-   "id": "0d9fd81a-b7f0-445a-8e3d-cfc2d31fdd59",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "import base64\n",
-    "\n",
-    "import httpx\n",
-    "\n",
-    "image_url = \"https://upload.wikimedia.org/wikipedia/commons/thumb/d/dd/Gfp-wisconsin-madison-the-nature-boardwalk.jpg/2560px-Gfp-wisconsin-madison-the-nature-boardwalk.jpg\"\n",
-    "image_data = base64.b64encode(httpx.get(image_url).content).decode(\"utf-8\")"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 6,
-   "id": "2671f995",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "from langchain_core.prompts import ChatPromptTemplate\n",
-    "from langchain_openai import ChatOpenAI\n",
-    "\n",
-    "model = ChatOpenAI(model=\"gpt-4o\")"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 10,
-   "id": "4ee35e4f",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "prompt = ChatPromptTemplate.from_messages(\n",
-    "    [\n",
-    "        (\"system\", \"Describe the image provided\"),\n",
-    "        (\n",
-    "            \"user\",\n",
-    "            [{\"type\": \"image_url\", \"image_url\": \"data:image/jpeg;base64,{image_data}\"}],\n",
-    "        ),\n",
-    "    ]\n",
-    ")"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 11,
-   "id": "089f75c2",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "chain = prompt | model"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 13,
-   "id": "02744b06",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "The image depicts a sunny day with a beautiful blue sky filled with scattered white clouds. The sky has varying shades of blue, ranging from a deeper hue near the horizon to a lighter, almost pale blue higher up. The white clouds are fluffy and scattered across the expanse of the sky, creating a peaceful and serene atmosphere. The lighting and cloud patterns suggest pleasant weather conditions, likely during the daytime hours on a mild, sunny day in an outdoor natural setting.\n"
-     ]
-    }
-   ],
-   "source": [
-    "response = chain.invoke({\"image_data\": image_data})\n",
-    "print(response.content)"
-   ]
-  },
-  {
-   "cell_type": "markdown",
-   "id": "e9b9ebf6",
-   "metadata": {},
-   "source": [
-    "We can also pass in multiple images."
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 14,
-   "id": "02190ee3",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "prompt = ChatPromptTemplate.from_messages(\n",
-    "    [\n",
-    "        (\"system\", \"compare the two pictures provided\"),\n",
-    "        (\n",
-    "            \"user\",\n",
-    "            [\n",
-    "                {\n",
-    "                    \"type\": \"image_url\",\n",
-    "                    \"image_url\": \"data:image/jpeg;base64,{image_data1}\",\n",
-    "                },\n",
-    "                {\n",
-    "                    \"type\": \"image_url\",\n",
-    "                    \"image_url\": \"data:image/jpeg;base64,{image_data2}\",\n",
-    "                },\n",
-    "            ],\n",
-    "        ),\n",
-    "    ]\n",
-    ")"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 15,
-   "id": "42af057b",
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "chain = prompt | model"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": 16,
-   "id": "513abe00",
-   "metadata": {},
-   "outputs": [
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "The two images provided are identical. Both images feature a wooden boardwalk path extending through a lush green field under a bright blue sky with some clouds. The perspective, colors, and elements in both images are exactly the same.\n"
-     ]
-    }
-   ],
-   "source": [
-    "response = chain.invoke({\"image_data1\": image_data, \"image_data2\": image_data})\n",
-    "print(response.content)"
-   ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "ea8152c3",
-   "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/how_to/output_parser_fixing.ipynb

@@ -23,7 +23,7 @@
    "source": [
     "from typing import List\n",
     "\n",
-    "from langchain_core.output_parsers import PydanticOutputParser\n",
+    "from langchain.output_parsers import PydanticOutputParser\n",
     "from langchain_core.pydantic_v1 import BaseModel, Field\n",
     "from langchain_openai import ChatOpenAI"
    ]

docs/docs/how_to/output_parser_retry.ipynb

@@ -17,9 +17,13 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "from langchain.output_parsers import OutputFixingParser\n",
-    "from langchain_core.output_parsers import PydanticOutputParser\n",
-    "from langchain_core.prompts import PromptTemplate\n",
+    "from langchain.output_parsers import (\n",
+    "    OutputFixingParser,\n",
+    "    PydanticOutputParser,\n",
+    ")\n",
+    "from langchain.prompts import (\n",
+    "    PromptTemplate,\n",
+    ")\n",
     "from langchain_core.pydantic_v1 import BaseModel, Field\n",
     "from langchain_openai import ChatOpenAI, OpenAI"
    ]

docs/docs/how_to/output_parser_structured.ipynb

@@ -94,7 +94,7 @@
    "source": [
     "## LCEL\n",
     "\n",
-    "Output parsers implement the [Runnable interface](/docs/concepts#interface), the basic building block of the [LangChain Expression Language (LCEL)](/docs/concepts#langchain-expression-language-lcel). This means they support `invoke`, `ainvoke`, `stream`, `astream`, `batch`, `abatch`, `astream_log` calls.\n",
+    "Output parsers implement the [Runnable interface](/docs/concepts#interface), the basic building block of the [LangChain Expression Language (LCEL)](/docs/concepts#langchain-expression-language). This means they support `invoke`, `ainvoke`, `stream`, `astream`, `batch`, `abatch`, `astream_log` calls.\n",
     "\n",
     "Output parsers accept a string or `BaseMessage` as input and can return an arbitrary type."
    ]

docs/docs/how_to/parent_document_retriever.ipynb

@@ -57,7 +57,7 @@
    "outputs": [],
    "source": [
     "loaders = [\n",
-    "    TextLoader(\"paul_graham_essay.txt\"),\n",
+    "    TextLoader(\"../../paul_graham_essay.txt\"),\n",
     "    TextLoader(\"state_of_the_union.txt\"),\n",
     "]\n",
     "docs = []\n",
@@ -124,8 +124,8 @@
     {
      "data": {
       "text/plain": [
-       "['9a63376c-58cc-42c9-b0f7-61f0e1a3a688',\n",
-       " '40091598-e918-4a18-9be0-f46413a95ae4']"
+       "['cfdf4af7-51f2-4ea3-8166-5be208efa040',\n",
+       " 'bf213c21-cc66-4208-8a72-733d030187e6']"
       ]
      },
      "execution_count": 6,
@@ -190,7 +190,7 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "retrieved_docs = retriever.invoke(\"justice breyer\")"
+    "retrieved_docs = retriever.get_relevant_documents(\"justice breyer\")"
    ]
   },
   {
@@ -338,17 +338,17 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 18,
+   "execution_count": 17,
    "id": "3a3202df",
    "metadata": {},
    "outputs": [],
    "source": [
-    "retrieved_docs = retriever.invoke(\"justice breyer\")"
+    "retrieved_docs = retriever.get_relevant_documents(\"justice breyer\")"
    ]
   },
   {
    "cell_type": "code",
-   "execution_count": 19,
+   "execution_count": 18,
    "id": "684fdb2c",
    "metadata": {},
    "outputs": [
@@ -358,7 +358,7 @@
        "1849"
       ]
      },
-     "execution_count": 19,
+     "execution_count": 18,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -369,7 +369,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 20,
+   "execution_count": 19,
    "id": "9f17f662",
    "metadata": {},
    "outputs": [
@@ -424,7 +424,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.10.4"
+   "version": "3.10.1"
   }
  },
  "nbformat": 4,

docs/docs/how_to/paul_graham_essay.txt

@@ -1,351 +0,0 @@
-What I Worked On
-
-February 2021
-
-Before college the two main things I worked on, outside of school, were writing and programming. I didn't write essays. I wrote what beginning writers were supposed to write then, and probably still are: short stories. My stories were awful. They had hardly any plot, just characters with strong feelings, which I imagined made them deep.
-
-The first programs I tried writing were on the IBM 1401 that our school district used for what was then called "data processing." This was in 9th grade, so I was 13 or 14. The school district's 1401 happened to be in the basement of our junior high school, and my friend Rich Draves and I got permission to use it. It was like a mini Bond villain's lair down there, with all these alien-looking machines — CPU, disk drives, printer, card reader — sitting up on a raised floor under bright fluorescent lights.
-
-The language we used was an early version of Fortran. You had to type programs on punch cards, then stack them in the card reader and press a button to load the program into memory and run it. The result would ordinarily be to print something on the spectacularly loud printer.
-
-I was puzzled by the 1401. I couldn't figure out what to do with it. And in retrospect there's not much I could have done with it. The only form of input to programs was data stored on punched cards, and I didn't have any data stored on punched cards. The only other option was to do things that didn't rely on any input, like calculate approximations of pi, but I didn't know enough math to do anything interesting of that type. So I'm not surprised I can't remember any programs I wrote, because they can't have done much. My clearest memory is of the moment I learned it was possible for programs not to terminate, when one of mine didn't. On a machine without time-sharing, this was a social as well as a technical error, as the data center manager's expression made clear.
-
-With microcomputers, everything changed. Now you could have a computer sitting right in front of you, on a desk, that could respond to your keystrokes as it was running instead of just churning through a stack of punch cards and then stopping. [1]
-
-The first of my friends to get a microcomputer built it himself. It was sold as a kit by Heathkit. I remember vividly how impressed and envious I felt watching him sitting in front of it, typing programs right into the computer.
-
-Computers were expensive in those days and it took me years of nagging before I convinced my father to buy one, a TRS-80, in about 1980. The gold standard then was the Apple II, but a TRS-80 was good enough. This was when I really started programming. I wrote simple games, a program to predict how high my model rockets would fly, and a word processor that my father used to write at least one book. There was only room in memory for about 2 pages of text, so he'd write 2 pages at a time and then print them out, but it was a lot better than a typewriter.
-
-Though I liked programming, I didn't plan to study it in college. In college I was going to study philosophy, which sounded much more powerful. It seemed, to my naive high school self, to be the study of the ultimate truths, compared to which the things studied in other fields would be mere domain knowledge. What I discovered when I got to college was that the other fields took up so much of the space of ideas that there wasn't much left for these supposed ultimate truths. All that seemed left for philosophy were edge cases that people in other fields felt could safely be ignored.
-
-I couldn't have put this into words when I was 18. All I knew at the time was that I kept taking philosophy courses and they kept being boring. So I decided to switch to AI.
-
-AI was in the air in the mid 1980s, but there were two things especially that made me want to work on it: a novel by Heinlein called The Moon is a Harsh Mistress, which featured an intelligent computer called Mike, and a PBS documentary that showed Terry Winograd using SHRDLU. I haven't tried rereading The Moon is a Harsh Mistress, so I don't know how well it has aged, but when I read it I was drawn entirely into its world. It seemed only a matter of time before we'd have Mike, and when I saw Winograd using SHRDLU, it seemed like that time would be a few years at most. All you had to do was teach SHRDLU more words.
-
-There weren't any classes in AI at Cornell then, not even graduate classes, so I started trying to teach myself. Which meant learning Lisp, since in those days Lisp was regarded as the language of AI. The commonly used programming languages then were pretty primitive, and programmers' ideas correspondingly so. The default language at Cornell was a Pascal-like language called PL/I, and the situation was similar elsewhere. Learning Lisp expanded my concept of a program so fast that it was years before I started to have a sense of where the new limits were. This was more like it; this was what I had expected college to do. It wasn't happening in a class, like it was supposed to, but that was ok. For the next couple years I was on a roll. I knew what I was going to do.
-
-For my undergraduate thesis, I reverse-engineered SHRDLU. My God did I love working on that program. It was a pleasing bit of code, but what made it even more exciting was my belief — hard to imagine now, but not unique in 1985 — that it was already climbing the lower slopes of intelligence.
-
-I had gotten into a program at Cornell that didn't make you choose a major. You could take whatever classes you liked, and choose whatever you liked to put on your degree. I of course chose "Artificial Intelligence." When I got the actual physical diploma, I was dismayed to find that the quotes had been included, which made them read as scare-quotes. At the time this bothered me, but now it seems amusingly accurate, for reasons I was about to discover.
-
-I applied to 3 grad schools: MIT and Yale, which were renowned for AI at the time, and Harvard, which I'd visited because Rich Draves went there, and was also home to Bill Woods, who'd invented the type of parser I used in my SHRDLU clone. Only Harvard accepted me, so that was where I went.
-
-I don't remember the moment it happened, or if there even was a specific moment, but during the first year of grad school I realized that AI, as practiced at the time, was a hoax. By which I mean the sort of AI in which a program that's told "the dog is sitting on the chair" translates this into some formal representation and adds it to the list of things it knows.
-
-What these programs really showed was that there's a subset of natural language that's a formal language. But a very proper subset. It was clear that there was an unbridgeable gap between what they could do and actually understanding natural language. It was not, in fact, simply a matter of teaching SHRDLU more words. That whole way of doing AI, with explicit data structures representing concepts, was not going to work. Its brokenness did, as so often happens, generate a lot of opportunities to write papers about various band-aids that could be applied to it, but it was never going to get us Mike.
-
-So I looked around to see what I could salvage from the wreckage of my plans, and there was Lisp. I knew from experience that Lisp was interesting for its own sake and not just for its association with AI, even though that was the main reason people cared about it at the time. So I decided to focus on Lisp. In fact, I decided to write a book about Lisp hacking. It's scary to think how little I knew about Lisp hacking when I started writing that book. But there's nothing like writing a book about something to help you learn it. The book, On Lisp, wasn't published till 1993, but I wrote much of it in grad school.
-
-Computer Science is an uneasy alliance between two halves, theory and systems. The theory people prove things, and the systems people build things. I wanted to build things. I had plenty of respect for theory — indeed, a sneaking suspicion that it was the more admirable of the two halves — but building things seemed so much more exciting.
-
-The problem with systems work, though, was that it didn't last. Any program you wrote today, no matter how good, would be obsolete in a couple decades at best. People might mention your software in footnotes, but no one would actually use it. And indeed, it would seem very feeble work. Only people with a sense of the history of the field would even realize that, in its time, it had been good.
-
-There were some surplus Xerox Dandelions floating around the computer lab at one point. Anyone who wanted one to play around with could have one. I was briefly tempted, but they were so slow by present standards; what was the point? No one else wanted one either, so off they went. That was what happened to systems work.
-
-I wanted not just to build things, but to build things that would last.
-
-In this dissatisfied state I went in 1988 to visit Rich Draves at CMU, where he was in grad school. One day I went to visit the Carnegie Institute, where I'd spent a lot of time as a kid. While looking at a painting there I realized something that might seem obvious, but was a big surprise to me. There, right on the wall, was something you could make that would last. Paintings didn't become obsolete. Some of the best ones were hundreds of years old.
-
-And moreover this was something you could make a living doing. Not as easily as you could by writing software, of course, but I thought if you were really industrious and lived really cheaply, it had to be possible to make enough to survive. And as an artist you could be truly independent. You wouldn't have a boss, or even need to get research funding.
-
-I had always liked looking at paintings. Could I make them? I had no idea. I'd never imagined it was even possible. I knew intellectually that people made art — that it didn't just appear spontaneously — but it was as if the people who made it were a different species. They either lived long ago or were mysterious geniuses doing strange things in profiles in Life magazine. The idea of actually being able to make art, to put that verb before that noun, seemed almost miraculous.
-
-That fall I started taking art classes at Harvard. Grad students could take classes in any department, and my advisor, Tom Cheatham, was very easy going. If he even knew about the strange classes I was taking, he never said anything.
-
-So now I was in a PhD program in computer science, yet planning to be an artist, yet also genuinely in love with Lisp hacking and working away at On Lisp. In other words, like many a grad student, I was working energetically on multiple projects that were not my thesis.
-
-I didn't see a way out of this situation. I didn't want to drop out of grad school, but how else was I going to get out? I remember when my friend Robert Morris got kicked out of Cornell for writing the internet worm of 1988, I was envious that he'd found such a spectacular way to get out of grad school.
-
-Then one day in April 1990 a crack appeared in the wall. I ran into professor Cheatham and he asked if I was far enough along to graduate that June. I didn't have a word of my dissertation written, but in what must have been the quickest bit of thinking in my life, I decided to take a shot at writing one in the 5 weeks or so that remained before the deadline, reusing parts of On Lisp where I could, and I was able to respond, with no perceptible delay "Yes, I think so. I'll give you something to read in a few days."
-
-I picked applications of continuations as the topic. In retrospect I should have written about macros and embedded languages. There's a whole world there that's barely been explored. But all I wanted was to get out of grad school, and my rapidly written dissertation sufficed, just barely.
-
-Meanwhile I was applying to art schools. I applied to two: RISD in the US, and the Accademia di Belli Arti in Florence, which, because it was the oldest art school, I imagined would be good. RISD accepted me, and I never heard back from the Accademia, so off to Providence I went.
-
-I'd applied for the BFA program at RISD, which meant in effect that I had to go to college again. This was not as strange as it sounds, because I was only 25, and art schools are full of people of different ages. RISD counted me as a transfer sophomore and said I had to do the foundation that summer. The foundation means the classes that everyone has to take in fundamental subjects like drawing, color, and design.
-
-Toward the end of the summer I got a big surprise: a letter from the Accademia, which had been delayed because they'd sent it to Cambridge England instead of Cambridge Massachusetts, inviting me to take the entrance exam in Florence that fall. This was now only weeks away. My nice landlady let me leave my stuff in her attic. I had some money saved from consulting work I'd done in grad school; there was probably enough to last a year if I lived cheaply. Now all I had to do was learn Italian.
-
-Only stranieri (foreigners) had to take this entrance exam. In retrospect it may well have been a way of excluding them, because there were so many stranieri attracted by the idea of studying art in Florence that the Italian students would otherwise have been outnumbered. I was in decent shape at painting and drawing from the RISD foundation that summer, but I still don't know how I managed to pass the written exam. I remember that I answered the essay question by writing about Cezanne, and that I cranked up the intellectual level as high as I could to make the most of my limited vocabulary. [2]
-
-I'm only up to age 25 and already there are such conspicuous patterns. Here I was, yet again about to attend some august institution in the hopes of learning about some prestigious subject, and yet again about to be disappointed. The students and faculty in the painting department at the Accademia were the nicest people you could imagine, but they had long since arrived at an arrangement whereby the students wouldn't require the faculty to teach anything, and in return the faculty wouldn't require the students to learn anything. And at the same time all involved would adhere outwardly to the conventions of a 19th century atelier. We actually had one of those little stoves, fed with kindling, that you see in 19th century studio paintings, and a nude model sitting as close to it as possible without getting burned. Except hardly anyone else painted her besides me. The rest of the students spent their time chatting or occasionally trying to imitate things they'd seen in American art magazines.
-
-Our model turned out to live just down the street from me. She made a living from a combination of modelling and making fakes for a local antique dealer. She'd copy an obscure old painting out of a book, and then he'd take the copy and maltreat it to make it look old. [3]
-
-While I was a student at the Accademia I started painting still lives in my bedroom at night. These paintings were tiny, because the room was, and because I painted them on leftover scraps of canvas, which was all I could afford at the time. Painting still lives is different from painting people, because the subject, as its name suggests, can't move. People can't sit for more than about 15 minutes at a time, and when they do they don't sit very still. So the traditional m.o. for painting people is to know how to paint a generic person, which you then modify to match the specific person you're painting. Whereas a still life you can, if you want, copy pixel by pixel from what you're seeing. You don't want to stop there, of course, or you get merely photographic accuracy, and what makes a still life interesting is that it's been through a head. You want to emphasize the visual cues that tell you, for example, that the reason the color changes suddenly at a certain point is that it's the edge of an object. By subtly emphasizing such things you can make paintings that are more realistic than photographs not just in some metaphorical sense, but in the strict information-theoretic sense. [4]
-
-I liked painting still lives because I was curious about what I was seeing. In everyday life, we aren't consciously aware of much we're seeing. Most visual perception is handled by low-level processes that merely tell your brain "that's a water droplet" without telling you details like where the lightest and darkest points are, or "that's a bush" without telling you the shape and position of every leaf. This is a feature of brains, not a bug. In everyday life it would be distracting to notice every leaf on every bush. But when you have to paint something, you have to look more closely, and when you do there's a lot to see. You can still be noticing new things after days of trying to paint something people usually take for granted, just as you can after days of trying to write an essay about something people usually take for granted.
-
-This is not the only way to paint. I'm not 100% sure it's even a good way to paint. But it seemed a good enough bet to be worth trying.
-
-Our teacher, professor Ulivi, was a nice guy. He could see I worked hard, and gave me a good grade, which he wrote down in a sort of passport each student had. But the Accademia wasn't teaching me anything except Italian, and my money was running out, so at the end of the first year I went back to the US.
-
-I wanted to go back to RISD, but I was now broke and RISD was very expensive, so I decided to get a job for a year and then return to RISD the next fall. I got one at a company called Interleaf, which made software for creating documents. You mean like Microsoft Word? Exactly. That was how I learned that low end software tends to eat high end software. But Interleaf still had a few years to live yet. [5]
-
-Interleaf had done something pretty bold. Inspired by Emacs, they'd added a scripting language, and even made the scripting language a dialect of Lisp. Now they wanted a Lisp hacker to write things in it. This was the closest thing I've had to a normal job, and I hereby apologize to my boss and coworkers, because I was a bad employee. Their Lisp was the thinnest icing on a giant C cake, and since I didn't know C and didn't want to learn it, I never understood most of the software. Plus I was terribly irresponsible. This was back when a programming job meant showing up every day during certain working hours. That seemed unnatural to me, and on this point the rest of the world is coming around to my way of thinking, but at the time it caused a lot of friction. Toward the end of the year I spent much of my time surreptitiously working on On Lisp, which I had by this time gotten a contract to publish.
-
-The good part was that I got paid huge amounts of money, especially by art student standards. In Florence, after paying my part of the rent, my budget for everything else had been $7 a day. Now I was getting paid more than 4 times that every hour, even when I was just sitting in a meeting. By living cheaply I not only managed to save enough to go back to RISD, but also paid off my college loans.
-
-I learned some useful things at Interleaf, though they were mostly about what not to do. I learned that it's better for technology companies to be run by product people than sales people (though sales is a real skill and people who are good at it are really good at it), that it leads to bugs when code is edited by too many people, that cheap office space is no bargain if it's depressing, that planned meetings are inferior to corridor conversations, that big, bureaucratic customers are a dangerous source of money, and that there's not much overlap between conventional office hours and the optimal time for hacking, or conventional offices and the optimal place for it.
-
-But the most important thing I learned, and which I used in both Viaweb and Y Combinator, is that the low end eats the high end: that it's good to be the "entry level" option, even though that will be less prestigious, because if you're not, someone else will be, and will squash you against the ceiling. Which in turn means that prestige is a danger sign.
-
-When I left to go back to RISD the next fall, I arranged to do freelance work for the group that did projects for customers, and this was how I survived for the next several years. When I came back to visit for a project later on, someone told me about a new thing called HTML, which was, as he described it, a derivative of SGML. Markup language enthusiasts were an occupational hazard at Interleaf and I ignored him, but this HTML thing later became a big part of my life.
-
-In the fall of 1992 I moved back to Providence to continue at RISD. The foundation had merely been intro stuff, and the Accademia had been a (very civilized) joke. Now I was going to see what real art school was like. But alas it was more like the Accademia than not. Better organized, certainly, and a lot more expensive, but it was now becoming clear that art school did not bear the same relationship to art that medical school bore to medicine. At least not the painting department. The textile department, which my next door neighbor belonged to, seemed to be pretty rigorous. No doubt illustration and architecture were too. But painting was post-rigorous. Painting students were supposed to express themselves, which to the more worldly ones meant to try to cook up some sort of distinctive signature style.
-
-A signature style is the visual equivalent of what in show business is known as a "schtick": something that immediately identifies the work as yours and no one else's. For example, when you see a painting that looks like a certain kind of cartoon, you know it's by Roy Lichtenstein. So if you see a big painting of this type hanging in the apartment of a hedge fund manager, you know he paid millions of dollars for it. That's not always why artists have a signature style, but it's usually why buyers pay a lot for such work. [6]
-
-There were plenty of earnest students too: kids who "could draw" in high school, and now had come to what was supposed to be the best art school in the country, to learn to draw even better. They tended to be confused and demoralized by what they found at RISD, but they kept going, because painting was what they did. I was not one of the kids who could draw in high school, but at RISD I was definitely closer to their tribe than the tribe of signature style seekers.
-
-I learned a lot in the color class I took at RISD, but otherwise I was basically teaching myself to paint, and I could do that for free. So in 1993 I dropped out. I hung around Providence for a bit, and then my college friend Nancy Parmet did me a big favor. A rent-controlled apartment in a building her mother owned in New York was becoming vacant. Did I want it? It wasn't much more than my current place, and New York was supposed to be where the artists were. So yes, I wanted it! [7]
-
-Asterix comics begin by zooming in on a tiny corner of Roman Gaul that turns out not to be controlled by the Romans. You can do something similar on a map of New York City: if you zoom in on the Upper East Side, there's a tiny corner that's not rich, or at least wasn't in 1993. It's called Yorkville, and that was my new home. Now I was a New York artist — in the strictly technical sense of making paintings and living in New York.
-
-I was nervous about money, because I could sense that Interleaf was on the way down. Freelance Lisp hacking work was very rare, and I didn't want to have to program in another language, which in those days would have meant C++ if I was lucky. So with my unerring nose for financial opportunity, I decided to write another book on Lisp. This would be a popular book, the sort of book that could be used as a textbook. I imagined myself living frugally off the royalties and spending all my time painting. (The painting on the cover of this book, ANSI Common Lisp, is one that I painted around this time.)
-
-The best thing about New York for me was the presence of Idelle and Julian Weber. Idelle Weber was a painter, one of the early photorealists, and I'd taken her painting class at Harvard. I've never known a teacher more beloved by her students. Large numbers of former students kept in touch with her, including me. After I moved to New York I became her de facto studio assistant.
-
-She liked to paint on big, square canvases, 4 to 5 feet on a side. One day in late 1994 as I was stretching one of these monsters there was something on the radio about a famous fund manager. He wasn't that much older than me, and was super rich. The thought suddenly occurred to me: why don't I become rich? Then I'll be able to work on whatever I want.
-
-Meanwhile I'd been hearing more and more about this new thing called the World Wide Web. Robert Morris showed it to me when I visited him in Cambridge, where he was now in grad school at Harvard. It seemed to me that the web would be a big deal. I'd seen what graphical user interfaces had done for the popularity of microcomputers. It seemed like the web would do the same for the internet.
-
-If I wanted to get rich, here was the next train leaving the station. I was right about that part. What I got wrong was the idea. I decided we should start a company to put art galleries online. I can't honestly say, after reading so many Y Combinator applications, that this was the worst startup idea ever, but it was up there. Art galleries didn't want to be online, and still don't, not the fancy ones. That's not how they sell. I wrote some software to generate web sites for galleries, and Robert wrote some to resize images and set up an http server to serve the pages. Then we tried to sign up galleries. To call this a difficult sale would be an understatement. It was difficult to give away. A few galleries let us make sites for them for free, but none paid us.
-
-Then some online stores started to appear, and I realized that except for the order buttons they were identical to the sites we'd been generating for galleries. This impressive-sounding thing called an "internet storefront" was something we already knew how to build.
-
-So in the summer of 1995, after I submitted the camera-ready copy of ANSI Common Lisp to the publishers, we started trying to write software to build online stores. At first this was going to be normal desktop software, which in those days meant Windows software. That was an alarming prospect, because neither of us knew how to write Windows software or wanted to learn. We lived in the Unix world. But we decided we'd at least try writing a prototype store builder on Unix. Robert wrote a shopping cart, and I wrote a new site generator for stores — in Lisp, of course.
-
-We were working out of Robert's apartment in Cambridge. His roommate was away for big chunks of time, during which I got to sleep in his room. For some reason there was no bed frame or sheets, just a mattress on the floor. One morning as I was lying on this mattress I had an idea that made me sit up like a capital L. What if we ran the software on the server, and let users control it by clicking on links? Then we'd never have to write anything to run on users' computers. We could generate the sites on the same server we'd serve them from. Users wouldn't need anything more than a browser.
-
-This kind of software, known as a web app, is common now, but at the time it wasn't clear that it was even possible. To find out, we decided to try making a version of our store builder that you could control through the browser. A couple days later, on August 12, we had one that worked. The UI was horrible, but it proved you could build a whole store through the browser, without any client software or typing anything into the command line on the server.
-
-Now we felt like we were really onto something. I had visions of a whole new generation of software working this way. You wouldn't need versions, or ports, or any of that crap. At Interleaf there had been a whole group called Release Engineering that seemed to be at least as big as the group that actually wrote the software. Now you could just update the software right on the server.
-
-We started a new company we called Viaweb, after the fact that our software worked via the web, and we got $10,000 in seed funding from Idelle's husband Julian. In return for that and doing the initial legal work and giving us business advice, we gave him 10% of the company. Ten years later this deal became the model for Y Combinator's. We knew founders needed something like this, because we'd needed it ourselves.
-
-At this stage I had a negative net worth, because the thousand dollars or so I had in the bank was more than counterbalanced by what I owed the government in taxes. (Had I diligently set aside the proper proportion of the money I'd made consulting for Interleaf? No, I had not.) So although Robert had his graduate student stipend, I needed that seed funding to live on.
-
-We originally hoped to launch in September, but we got more ambitious about the software as we worked on it. Eventually we managed to build a WYSIWYG site builder, in the sense that as you were creating pages, they looked exactly like the static ones that would be generated later, except that instead of leading to static pages, the links all referred to closures stored in a hash table on the server.
-
-It helped to have studied art, because the main goal of an online store builder is to make users look legit, and the key to looking legit is high production values. If you get page layouts and fonts and colors right, you can make a guy running a store out of his bedroom look more legit than a big company.
-
-(If you're curious why my site looks so old-fashioned, it's because it's still made with this software. It may look clunky today, but in 1996 it was the last word in slick.)
-
-In September, Robert rebelled. "We've been working on this for a month," he said, "and it's still not done." This is funny in retrospect, because he would still be working on it almost 3 years later. But I decided it might be prudent to recruit more programmers, and I asked Robert who else in grad school with him was really good. He recommended Trevor Blackwell, which surprised me at first, because at that point I knew Trevor mainly for his plan to reduce everything in his life to a stack of notecards, which he carried around with him. But Rtm was right, as usual. Trevor turned out to be a frighteningly effective hacker.
-
-It was a lot of fun working with Robert and Trevor. They're the two most independent-minded people I know, and in completely different ways. If you could see inside Rtm's brain it would look like a colonial New England church, and if you could see inside Trevor's it would look like the worst excesses of Austrian Rococo.
-
-We opened for business, with 6 stores, in January 1996. It was just as well we waited a few months, because although we worried we were late, we were actually almost fatally early. There was a lot of talk in the press then about ecommerce, but not many people actually wanted online stores. [8]
-
-There were three main parts to the software: the editor, which people used to build sites and which I wrote, the shopping cart, which Robert wrote, and the manager, which kept track of orders and statistics, and which Trevor wrote. In its time, the editor was one of the best general-purpose site builders. I kept the code tight and didn't have to integrate with any other software except Robert's and Trevor's, so it was quite fun to work on. If all I'd had to do was work on this software, the next 3 years would have been the easiest of my life. Unfortunately I had to do a lot more, all of it stuff I was worse at than programming, and the next 3 years were instead the most stressful.
-
-There were a lot of startups making ecommerce software in the second half of the 90s. We were determined to be the Microsoft Word, not the Interleaf. Which meant being easy to use and inexpensive. It was lucky for us that we were poor, because that caused us to make Viaweb even more inexpensive than we realized. We charged $100 a month for a small store and $300 a month for a big one. This low price was a big attraction, and a constant thorn in the sides of competitors, but it wasn't because of some clever insight that we set the price low. We had no idea what businesses paid for things. $300 a month seemed like a lot of money to us.
-
-We did a lot of things right by accident like that. For example, we did what's now called "doing things that don't scale," although at the time we would have described it as "being so lame that we're driven to the most desperate measures to get users." The most common of which was building stores for them. This seemed particularly humiliating, since the whole reason d'etre of our software was that people could use it to make their own stores. But anything to get users.
-
-We learned a lot more about retail than we wanted to know. For example, that if you could only have a small image of a man's shirt (and all images were small then by present standards), it was better to have a closeup of the collar than a picture of the whole shirt. The reason I remember learning this was that it meant I had to rescan about 30 images of men's shirts. My first set of scans were so beautiful too.
-
-Though this felt wrong, it was exactly the right thing to be doing. Building stores for users taught us about retail, and about how it felt to use our software. I was initially both mystified and repelled by "business" and thought we needed a "business person" to be in charge of it, but once we started to get users, I was converted, in much the same way I was converted to fatherhood once I had kids. Whatever users wanted, I was all theirs. Maybe one day we'd have so many users that I couldn't scan their images for them, but in the meantime there was nothing more important to do.
-
-Another thing I didn't get at the time is that growth rate is the ultimate test of a startup. Our growth rate was fine. We had about 70 stores at the end of 1996 and about 500 at the end of 1997. I mistakenly thought the thing that mattered was the absolute number of users. And that is the thing that matters in the sense that that's how much money you're making, and if you're not making enough, you might go out of business. But in the long term the growth rate takes care of the absolute number. If we'd been a startup I was advising at Y Combinator, I would have said: Stop being so stressed out, because you're doing fine. You're growing 7x a year. Just don't hire too many more people and you'll soon be profitable, and then you'll control your own destiny.
-
-Alas I hired lots more people, partly because our investors wanted me to, and partly because that's what startups did during the Internet Bubble. A company with just a handful of employees would have seemed amateurish. So we didn't reach breakeven until about when Yahoo bought us in the summer of 1998. Which in turn meant we were at the mercy of investors for the entire life of the company. And since both we and our investors were noobs at startups, the result was a mess even by startup standards.
-
-It was a huge relief when Yahoo bought us. In principle our Viaweb stock was valuable. It was a share in a business that was profitable and growing rapidly. But it didn't feel very valuable to me; I had no idea how to value a business, but I was all too keenly aware of the near-death experiences we seemed to have every few months. Nor had I changed my grad student lifestyle significantly since we started. So when Yahoo bought us it felt like going from rags to riches. Since we were going to California, I bought a car, a yellow 1998 VW GTI. I remember thinking that its leather seats alone were by far the most luxurious thing I owned.
-
-The next year, from the summer of 1998 to the summer of 1999, must have been the least productive of my life. I didn't realize it at the time, but I was worn out from the effort and stress of running Viaweb. For a while after I got to California I tried to continue my usual m.o. of programming till 3 in the morning, but fatigue combined with Yahoo's prematurely aged culture and grim cube farm in Santa Clara gradually dragged me down. After a few months it felt disconcertingly like working at Interleaf.
-
-Yahoo had given us a lot of options when they bought us. At the time I thought Yahoo was so overvalued that they'd never be worth anything, but to my astonishment the stock went up 5x in the next year. I hung on till the first chunk of options vested, then in the summer of 1999 I left. It had been so long since I'd painted anything that I'd half forgotten why I was doing this. My brain had been entirely full of software and men's shirts for 4 years. But I had done this to get rich so I could paint, I reminded myself, and now I was rich, so I should go paint.
-
-When I said I was leaving, my boss at Yahoo had a long conversation with me about my plans. I told him all about the kinds of pictures I wanted to paint. At the time I was touched that he took such an interest in me. Now I realize it was because he thought I was lying. My options at that point were worth about $2 million a month. If I was leaving that kind of money on the table, it could only be to go and start some new startup, and if I did, I might take people with me. This was the height of the Internet Bubble, and Yahoo was ground zero of it. My boss was at that moment a billionaire. Leaving then to start a new startup must have seemed to him an insanely, and yet also plausibly, ambitious plan.
-
-But I really was quitting to paint, and I started immediately. There was no time to lose. I'd already burned 4 years getting rich. Now when I talk to founders who are leaving after selling their companies, my advice is always the same: take a vacation. That's what I should have done, just gone off somewhere and done nothing for a month or two, but the idea never occurred to me.
-
-So I tried to paint, but I just didn't seem to have any energy or ambition. Part of the problem was that I didn't know many people in California. I'd compounded this problem by buying a house up in the Santa Cruz Mountains, with a beautiful view but miles from anywhere. I stuck it out for a few more months, then in desperation I went back to New York, where unless you understand about rent control you'll be surprised to hear I still had my apartment, sealed up like a tomb of my old life. Idelle was in New York at least, and there were other people trying to paint there, even though I didn't know any of them.
-
-When I got back to New York I resumed my old life, except now I was rich. It was as weird as it sounds. I resumed all my old patterns, except now there were doors where there hadn't been. Now when I was tired of walking, all I had to do was raise my hand, and (unless it was raining) a taxi would stop to pick me up. Now when I walked past charming little restaurants I could go in and order lunch. It was exciting for a while. Painting started to go better. I experimented with a new kind of still life where I'd paint one painting in the old way, then photograph it and print it, blown up, on canvas, and then use that as the underpainting for a second still life, painted from the same objects (which hopefully hadn't rotted yet).
-
-Meanwhile I looked for an apartment to buy. Now I could actually choose what neighborhood to live in. Where, I asked myself and various real estate agents, is the Cambridge of New York? Aided by occasional visits to actual Cambridge, I gradually realized there wasn't one. Huh.
-
-Around this time, in the spring of 2000, I had an idea. It was clear from our experience with Viaweb that web apps were the future. Why not build a web app for making web apps? Why not let people edit code on our server through the browser, and then host the resulting applications for them? [9] You could run all sorts of services on the servers that these applications could use just by making an API call: making and receiving phone calls, manipulating images, taking credit card payments, etc.
-
-I got so excited about this idea that I couldn't think about anything else. It seemed obvious that this was the future. I didn't particularly want to start another company, but it was clear that this idea would have to be embodied as one, so I decided to move to Cambridge and start it. I hoped to lure Robert into working on it with me, but there I ran into a hitch. Robert was now a postdoc at MIT, and though he'd made a lot of money the last time I'd lured him into working on one of my schemes, it had also been a huge time sink. So while he agreed that it sounded like a plausible idea, he firmly refused to work on it.
-
-Hmph. Well, I'd do it myself then. I recruited Dan Giffin, who had worked for Viaweb, and two undergrads who wanted summer jobs, and we got to work trying to build what it's now clear is about twenty companies and several open-source projects worth of software. The language for defining applications would of course be a dialect of Lisp. But I wasn't so naive as to assume I could spring an overt Lisp on a general audience; we'd hide the parentheses, like Dylan did.
-
-By then there was a name for the kind of company Viaweb was, an "application service provider," or ASP. This name didn't last long before it was replaced by "software as a service," but it was current for long enough that I named this new company after it: it was going to be called Aspra.
-
-I started working on the application builder, Dan worked on network infrastructure, and the two undergrads worked on the first two services (images and phone calls). But about halfway through the summer I realized I really didn't want to run a company — especially not a big one, which it was looking like this would have to be. I'd only started Viaweb because I needed the money. Now that I didn't need money anymore, why was I doing this? If this vision had to be realized as a company, then screw the vision. I'd build a subset that could be done as an open-source project.
-
-Much to my surprise, the time I spent working on this stuff was not wasted after all. After we started Y Combinator, I would often encounter startups working on parts of this new architecture, and it was very useful to have spent so much time thinking about it and even trying to write some of it.
-
-The subset I would build as an open-source project was the new Lisp, whose parentheses I now wouldn't even have to hide. A lot of Lisp hackers dream of building a new Lisp, partly because one of the distinctive features of the language is that it has dialects, and partly, I think, because we have in our minds a Platonic form of Lisp that all existing dialects fall short of. I certainly did. So at the end of the summer Dan and I switched to working on this new dialect of Lisp, which I called Arc, in a house I bought in Cambridge.
-
-The following spring, lightning struck. I was invited to give a talk at a Lisp conference, so I gave one about how we'd used Lisp at Viaweb. Afterward I put a postscript file of this talk online, on paulgraham.com, which I'd created years before using Viaweb but had never used for anything. In one day it got 30,000 page views. What on earth had happened? The referring urls showed that someone had posted it on Slashdot. [10]
-
-Wow, I thought, there's an audience. If I write something and put it on the web, anyone can read it. That may seem obvious now, but it was surprising then. In the print era there was a narrow channel to readers, guarded by fierce monsters known as editors. The only way to get an audience for anything you wrote was to get it published as a book, or in a newspaper or magazine. Now anyone could publish anything.
-
-This had been possible in principle since 1993, but not many people had realized it yet. I had been intimately involved with building the infrastructure of the web for most of that time, and a writer as well, and it had taken me 8 years to realize it. Even then it took me several years to understand the implications. It meant there would be a whole new generation of essays. [11]
-
-In the print era, the channel for publishing essays had been vanishingly small. Except for a few officially anointed thinkers who went to the right parties in New York, the only people allowed to publish essays were specialists writing about their specialties. There were so many essays that had never been written, because there had been no way to publish them. Now they could be, and I was going to write them. [12]
-
-I've worked on several different things, but to the extent there was a turning point where I figured out what to work on, it was when I started publishing essays online. From then on I knew that whatever else I did, I'd always write essays too.
-
-I knew that online essays would be a marginal medium at first. Socially they'd seem more like rants posted by nutjobs on their GeoCities sites than the genteel and beautifully typeset compositions published in The New Yorker. But by this point I knew enough to find that encouraging instead of discouraging.
-
-One of the most conspicuous patterns I've noticed in my life is how well it has worked, for me at least, to work on things that weren't prestigious. Still life has always been the least prestigious form of painting. Viaweb and Y Combinator both seemed lame when we started them. I still get the glassy eye from strangers when they ask what I'm writing, and I explain that it's an essay I'm going to publish on my web site. Even Lisp, though prestigious intellectually in something like the way Latin is, also seems about as hip.
-
-It's not that unprestigious types of work are good per se. But when you find yourself drawn to some kind of work despite its current lack of prestige, it's a sign both that there's something real to be discovered there, and that you have the right kind of motives. Impure motives are a big danger for the ambitious. If anything is going to lead you astray, it will be the desire to impress people. So while working on things that aren't prestigious doesn't guarantee you're on the right track, it at least guarantees you're not on the most common type of wrong one.
-
-Over the next several years I wrote lots of essays about all kinds of different topics. O'Reilly reprinted a collection of them as a book, called Hackers & Painters after one of the essays in it. I also worked on spam filters, and did some more painting. I used to have dinners for a group of friends every thursday night, which taught me how to cook for groups. And I bought another building in Cambridge, a former candy factory (and later, twas said, porn studio), to use as an office.
-
-One night in October 2003 there was a big party at my house. It was a clever idea of my friend Maria Daniels, who was one of the thursday diners. Three separate hosts would all invite their friends to one party. So for every guest, two thirds of the other guests would be people they didn't know but would probably like. One of the guests was someone I didn't know but would turn out to like a lot: a woman called Jessica Livingston. A couple days later I asked her out.
-
-Jessica was in charge of marketing at a Boston investment bank. This bank thought it understood startups, but over the next year, as she met friends of mine from the startup world, she was surprised how different reality was. And how colorful their stories were. So she decided to compile a book of interviews with startup founders.
-
-When the bank had financial problems and she had to fire half her staff, she started looking for a new job. In early 2005 she interviewed for a marketing job at a Boston VC firm. It took them weeks to make up their minds, and during this time I started telling her about all the things that needed to be fixed about venture capital. They should make a larger number of smaller investments instead of a handful of giant ones, they should be funding younger, more technical founders instead of MBAs, they should let the founders remain as CEO, and so on.
-
-One of my tricks for writing essays had always been to give talks. The prospect of having to stand up in front of a group of people and tell them something that won't waste their time is a great spur to the imagination. When the Harvard Computer Society, the undergrad computer club, asked me to give a talk, I decided I would tell them how to start a startup. Maybe they'd be able to avoid the worst of the mistakes we'd made.
-
-So I gave this talk, in the course of which I told them that the best sources of seed funding were successful startup founders, because then they'd be sources of advice too. Whereupon it seemed they were all looking expectantly at me. Horrified at the prospect of having my inbox flooded by business plans (if I'd only known), I blurted out "But not me!" and went on with the talk. But afterward it occurred to me that I should really stop procrastinating about angel investing. I'd been meaning to since Yahoo bought us, and now it was 7 years later and I still hadn't done one angel investment.
-
-Meanwhile I had been scheming with Robert and Trevor about projects we could work on together. I missed working with them, and it seemed like there had to be something we could collaborate on.
-
-As Jessica and I were walking home from dinner on March 11, at the corner of Garden and Walker streets, these three threads converged. Screw the VCs who were taking so long to make up their minds. We'd start our own investment firm and actually implement the ideas we'd been talking about. I'd fund it, and Jessica could quit her job and work for it, and we'd get Robert and Trevor as partners too. [13]
-
-Once again, ignorance worked in our favor. We had no idea how to be angel investors, and in Boston in 2005 there were no Ron Conways to learn from. So we just made what seemed like the obvious choices, and some of the things we did turned out to be novel.
-
-There are multiple components to Y Combinator, and we didn't figure them all out at once. The part we got first was to be an angel firm. In those days, those two words didn't go together. There were VC firms, which were organized companies with people whose job it was to make investments, but they only did big, million dollar investments. And there were angels, who did smaller investments, but these were individuals who were usually focused on other things and made investments on the side. And neither of them helped founders enough in the beginning. We knew how helpless founders were in some respects, because we remembered how helpless we'd been. For example, one thing Julian had done for us that seemed to us like magic was to get us set up as a company. We were fine writing fairly difficult software, but actually getting incorporated, with bylaws and stock and all that stuff, how on earth did you do that? Our plan was not only to make seed investments, but to do for startups everything Julian had done for us.
-
-YC was not organized as a fund. It was cheap enough to run that we funded it with our own money. That went right by 99% of readers, but professional investors are thinking "Wow, that means they got all the returns." But once again, this was not due to any particular insight on our part. We didn't know how VC firms were organized. It never occurred to us to try to raise a fund, and if it had, we wouldn't have known where to start. [14]
-
-The most distinctive thing about YC is the batch model: to fund a bunch of startups all at once, twice a year, and then to spend three months focusing intensively on trying to help them. That part we discovered by accident, not merely implicitly but explicitly due to our ignorance about investing. We needed to get experience as investors. What better way, we thought, than to fund a whole bunch of startups at once? We knew undergrads got temporary jobs at tech companies during the summer. Why not organize a summer program where they'd start startups instead? We wouldn't feel guilty for being in a sense fake investors, because they would in a similar sense be fake founders. So while we probably wouldn't make much money out of it, we'd at least get to practice being investors on them, and they for their part would probably have a more interesting summer than they would working at Microsoft.
-
-We'd use the building I owned in Cambridge as our headquarters. We'd all have dinner there once a week — on tuesdays, since I was already cooking for the thursday diners on thursdays — and after dinner we'd bring in experts on startups to give talks.
-
-We knew undergrads were deciding then about summer jobs, so in a matter of days we cooked up something we called the Summer Founders Program, and I posted an announcement on my site, inviting undergrads to apply. I had never imagined that writing essays would be a way to get "deal flow," as investors call it, but it turned out to be the perfect source. [15] We got 225 applications for the Summer Founders Program, and we were surprised to find that a lot of them were from people who'd already graduated, or were about to that spring. Already this SFP thing was starting to feel more serious than we'd intended.
-
-We invited about 20 of the 225 groups to interview in person, and from those we picked 8 to fund. They were an impressive group. That first batch included reddit, Justin Kan and Emmett Shear, who went on to found Twitch, Aaron Swartz, who had already helped write the RSS spec and would a few years later become a martyr for open access, and Sam Altman, who would later become the second president of YC. I don't think it was entirely luck that the first batch was so good. You had to be pretty bold to sign up for a weird thing like the Summer Founders Program instead of a summer job at a legit place like Microsoft or Goldman Sachs.
-
-The deal for startups was based on a combination of the deal we did with Julian ($10k for 10%) and what Robert said MIT grad students got for the summer ($6k). We invested $6k per founder, which in the typical two-founder case was $12k, in return for 6%. That had to be fair, because it was twice as good as the deal we ourselves had taken. Plus that first summer, which was really hot, Jessica brought the founders free air conditioners. [16]
-
-Fairly quickly I realized that we had stumbled upon the way to scale startup funding. Funding startups in batches was more convenient for us, because it meant we could do things for a lot of startups at once, but being part of a batch was better for the startups too. It solved one of the biggest problems faced by founders: the isolation. Now you not only had colleagues, but colleagues who understood the problems you were facing and could tell you how they were solving them.
-
-As YC grew, we started to notice other advantages of scale. The alumni became a tight community, dedicated to helping one another, and especially the current batch, whose shoes they remembered being in. We also noticed that the startups were becoming one another's customers. We used to refer jokingly to the "YC GDP," but as YC grows this becomes less and less of a joke. Now lots of startups get their initial set of customers almost entirely from among their batchmates.
-
-I had not originally intended YC to be a full-time job. I was going to do three things: hack, write essays, and work on YC. As YC grew, and I grew more excited about it, it started to take up a lot more than a third of my attention. But for the first few years I was still able to work on other things.
-
-In the summer of 2006, Robert and I started working on a new version of Arc. This one was reasonably fast, because it was compiled into Scheme. To test this new Arc, I wrote Hacker News in it. It was originally meant to be a news aggregator for startup founders and was called Startup News, but after a few months I got tired of reading about nothing but startups. Plus it wasn't startup founders we wanted to reach. It was future startup founders. So I changed the name to Hacker News and the topic to whatever engaged one's intellectual curiosity.
-
-HN was no doubt good for YC, but it was also by far the biggest source of stress for me. If all I'd had to do was select and help founders, life would have been so easy. And that implies that HN was a mistake. Surely the biggest source of stress in one's work should at least be something close to the core of the work. Whereas I was like someone who was in pain while running a marathon not from the exertion of running, but because I had a blister from an ill-fitting shoe. When I was dealing with some urgent problem during YC, there was about a 60% chance it had to do with HN, and a 40% chance it had do with everything else combined. [17]
-
-As well as HN, I wrote all of YC's internal software in Arc. But while I continued to work a good deal in Arc, I gradually stopped working on Arc, partly because I didn't have time to, and partly because it was a lot less attractive to mess around with the language now that we had all this infrastructure depending on it. So now my three projects were reduced to two: writing essays and working on YC.
-
-YC was different from other kinds of work I've done. Instead of deciding for myself what to work on, the problems came to me. Every 6 months there was a new batch of startups, and their problems, whatever they were, became our problems. It was very engaging work, because their problems were quite varied, and the good founders were very effective. If you were trying to learn the most you could about startups in the shortest possible time, you couldn't have picked a better way to do it.
-
-There were parts of the job I didn't like. Disputes between cofounders, figuring out when people were lying to us, fighting with people who maltreated the startups, and so on. But I worked hard even at the parts I didn't like. I was haunted by something Kevin Hale once said about companies: "No one works harder than the boss." He meant it both descriptively and prescriptively, and it was the second part that scared me. I wanted YC to be good, so if how hard I worked set the upper bound on how hard everyone else worked, I'd better work very hard.
-
-One day in 2010, when he was visiting California for interviews, Robert Morris did something astonishing: he offered me unsolicited advice. I can only remember him doing that once before. One day at Viaweb, when I was bent over double from a kidney stone, he suggested that it would be a good idea for him to take me to the hospital. That was what it took for Rtm to offer unsolicited advice. So I remember his exact words very clearly. "You know," he said, "you should make sure Y Combinator isn't the last cool thing you do."
-
-At the time I didn't understand what he meant, but gradually it dawned on me that he was saying I should quit. This seemed strange advice, because YC was doing great. But if there was one thing rarer than Rtm offering advice, it was Rtm being wrong. So this set me thinking. It was true that on my current trajectory, YC would be the last thing I did, because it was only taking up more of my attention. It had already eaten Arc, and was in the process of eating essays too. Either YC was my life's work or I'd have to leave eventually. And it wasn't, so I would.
-
-In the summer of 2012 my mother had a stroke, and the cause turned out to be a blood clot caused by colon cancer. The stroke destroyed her balance, and she was put in a nursing home, but she really wanted to get out of it and back to her house, and my sister and I were determined to help her do it. I used to fly up to Oregon to visit her regularly, and I had a lot of time to think on those flights. On one of them I realized I was ready to hand YC over to someone else.
-
-I asked Jessica if she wanted to be president, but she didn't, so we decided we'd try to recruit Sam Altman. We talked to Robert and Trevor and we agreed to make it a complete changing of the guard. Up till that point YC had been controlled by the original LLC we four had started. But we wanted YC to last for a long time, and to do that it couldn't be controlled by the founders. So if Sam said yes, we'd let him reorganize YC. Robert and I would retire, and Jessica and Trevor would become ordinary partners.
-
-When we asked Sam if he wanted to be president of YC, initially he said no. He wanted to start a startup to make nuclear reactors. But I kept at it, and in October 2013 he finally agreed. We decided he'd take over starting with the winter 2014 batch. For the rest of 2013 I left running YC more and more to Sam, partly so he could learn the job, and partly because I was focused on my mother, whose cancer had returned.
-
-She died on January 15, 2014. We knew this was coming, but it was still hard when it did.
-
-I kept working on YC till March, to help get that batch of startups through Demo Day, then I checked out pretty completely. (I still talk to alumni and to new startups working on things I'm interested in, but that only takes a few hours a week.)
-
-What should I do next? Rtm's advice hadn't included anything about that. I wanted to do something completely different, so I decided I'd paint. I wanted to see how good I could get if I really focused on it. So the day after I stopped working on YC, I started painting. I was rusty and it took a while to get back into shape, but it was at least completely engaging. [18]
-
-I spent most of the rest of 2014 painting. I'd never been able to work so uninterruptedly before, and I got to be better than I had been. Not good enough, but better. Then in November, right in the middle of a painting, I ran out of steam. Up till that point I'd always been curious to see how the painting I was working on would turn out, but suddenly finishing this one seemed like a chore. So I stopped working on it and cleaned my brushes and haven't painted since. So far anyway.
-
-I realize that sounds rather wimpy. But attention is a zero sum game. If you can choose what to work on, and you choose a project that's not the best one (or at least a good one) for you, then it's getting in the way of another project that is. And at 50 there was some opportunity cost to screwing around.
-
-I started writing essays again, and wrote a bunch of new ones over the next few months. I even wrote a couple that weren't about startups. Then in March 2015 I started working on Lisp again.
-
-The distinctive thing about Lisp is that its core is a language defined by writing an interpreter in itself. It wasn't originally intended as a programming language in the ordinary sense. It was meant to be a formal model of computation, an alternative to the Turing machine. If you want to write an interpreter for a language in itself, what's the minimum set of predefined operators you need? The Lisp that John McCarthy invented, or more accurately discovered, is an answer to that question. [19]
-
-McCarthy didn't realize this Lisp could even be used to program computers till his grad student Steve Russell suggested it. Russell translated McCarthy's interpreter into IBM 704 machine language, and from that point Lisp started also to be a programming language in the ordinary sense. But its origins as a model of computation gave it a power and elegance that other languages couldn't match. It was this that attracted me in college, though I didn't understand why at the time.
-
-McCarthy's 1960 Lisp did nothing more than interpret Lisp expressions. It was missing a lot of things you'd want in a programming language. So these had to be added, and when they were, they weren't defined using McCarthy's original axiomatic approach. That wouldn't have been feasible at the time. McCarthy tested his interpreter by hand-simulating the execution of programs. But it was already getting close to the limit of interpreters you could test that way — indeed, there was a bug in it that McCarthy had overlooked. To test a more complicated interpreter, you'd have had to run it, and computers then weren't powerful enough.
-
-Now they are, though. Now you could continue using McCarthy's axiomatic approach till you'd defined a complete programming language. And as long as every change you made to McCarthy's Lisp was a discoveredness-preserving transformation, you could, in principle, end up with a complete language that had this quality. Harder to do than to talk about, of course, but if it was possible in principle, why not try? So I decided to take a shot at it. It took 4 years, from March 26, 2015 to October 12, 2019. It was fortunate that I had a precisely defined goal, or it would have been hard to keep at it for so long.
-
-I wrote this new Lisp, called Bel, in itself in Arc. That may sound like a contradiction, but it's an indication of the sort of trickery I had to engage in to make this work. By means of an egregious collection of hacks I managed to make something close enough to an interpreter written in itself that could actually run. Not fast, but fast enough to test.
-
-I had to ban myself from writing essays during most of this time, or I'd never have finished. In late 2015 I spent 3 months writing essays, and when I went back to working on Bel I could barely understand the code. Not so much because it was badly written as because the problem is so convoluted. When you're working on an interpreter written in itself, it's hard to keep track of what's happening at what level, and errors can be practically encrypted by the time you get them.
-
-So I said no more essays till Bel was done. But I told few people about Bel while I was working on it. So for years it must have seemed that I was doing nothing, when in fact I was working harder than I'd ever worked on anything. Occasionally after wrestling for hours with some gruesome bug I'd check Twitter or HN and see someone asking "Does Paul Graham still code?"
-
-Working on Bel was hard but satisfying. I worked on it so intensively that at any given time I had a decent chunk of the code in my head and could write more there. I remember taking the boys to the coast on a sunny day in 2015 and figuring out how to deal with some problem involving continuations while I watched them play in the tide pools. It felt like I was doing life right. I remember that because I was slightly dismayed at how novel it felt. The good news is that I had more moments like this over the next few years.
-
-In the summer of 2016 we moved to England. We wanted our kids to see what it was like living in another country, and since I was a British citizen by birth, that seemed the obvious choice. We only meant to stay for a year, but we liked it so much that we still live there. So most of Bel was written in England.
-
-In the fall of 2019, Bel was finally finished. Like McCarthy's original Lisp, it's a spec rather than an implementation, although like McCarthy's Lisp it's a spec expressed as code.
-
-Now that I could write essays again, I wrote a bunch about topics I'd had stacked up. I kept writing essays through 2020, but I also started to think about other things I could work on. How should I choose what to do? Well, how had I chosen what to work on in the past? I wrote an essay for myself to answer that question, and I was surprised how long and messy the answer turned out to be. If this surprised me, who'd lived it, then I thought perhaps it would be interesting to other people, and encouraging to those with similarly messy lives. So I wrote a more detailed version for others to read, and this is the last sentence of it.
-
-
-
-
-
-
-
-
-
-Notes
-
-[1] My experience skipped a step in the evolution of computers: time-sharing machines with interactive OSes. I went straight from batch processing to microcomputers, which made microcomputers seem all the more exciting.
-
-[2] Italian words for abstract concepts can nearly always be predicted from their English cognates (except for occasional traps like polluzione). It's the everyday words that differ. So if you string together a lot of abstract concepts with a few simple verbs, you can make a little Italian go a long way.
-
-[3] I lived at Piazza San Felice 4, so my walk to the Accademia went straight down the spine of old Florence: past the Pitti, across the bridge, past Orsanmichele, between the Duomo and the Baptistery, and then up Via Ricasoli to Piazza San Marco. I saw Florence at street level in every possible condition, from empty dark winter evenings to sweltering summer days when the streets were packed with tourists.
-
-[4] You can of course paint people like still lives if you want to, and they're willing. That sort of portrait is arguably the apex of still life painting, though the long sitting does tend to produce pained expressions in the sitters.
-
-[5] Interleaf was one of many companies that had smart people and built impressive technology, and yet got crushed by Moore's Law. In the 1990s the exponential growth in the power of commodity (i.e. Intel) processors rolled up high-end, special-purpose hardware and software companies like a bulldozer.
-
-[6] The signature style seekers at RISD weren't specifically mercenary. In the art world, money and coolness are tightly coupled. Anything expensive comes to be seen as cool, and anything seen as cool will soon become equally expensive.
-
-[7] Technically the apartment wasn't rent-controlled but rent-stabilized, but this is a refinement only New Yorkers would know or care about. The point is that it was really cheap, less than half market price.
-
-[8] Most software you can launch as soon as it's done. But when the software is an online store builder and you're hosting the stores, if you don't have any users yet, that fact will be painfully obvious. So before we could launch publicly we had to launch privately, in the sense of recruiting an initial set of users and making sure they had decent-looking stores.
-
-[9] We'd had a code editor in Viaweb for users to define their own page styles. They didn't know it, but they were editing Lisp expressions underneath. But this wasn't an app editor, because the code ran when the merchants' sites were generated, not when shoppers visited them.
-
-[10] This was the first instance of what is now a familiar experience, and so was what happened next, when I read the comments and found they were full of angry people. How could I claim that Lisp was better than other languages? Weren't they all Turing complete? People who see the responses to essays I write sometimes tell me how sorry they feel for me, but I'm not exaggerating when I reply that it has always been like this, since the very beginning. It comes with the territory. An essay must tell readers things they don't already know, and some people dislike being told such things.
-
-[11] People put plenty of stuff on the internet in the 90s of course, but putting something online is not the same as publishing it online. Publishing online means you treat the online version as the (or at least a) primary version.
-
-[12] There is a general lesson here that our experience with Y Combinator also teaches: Customs continue to constrain you long after the restrictions that caused them have disappeared. Customary VC practice had once, like the customs about publishing essays, been based on real constraints. Startups had once been much more expensive to start, and proportionally rare. Now they could be cheap and common, but the VCs' customs still reflected the old world, just as customs about writing essays still reflected the constraints of the print era.
-
-Which in turn implies that people who are independent-minded (i.e. less influenced by custom) will have an advantage in fields affected by rapid change (where customs are more likely to be obsolete).
-
-Here's an interesting point, though: you can't always predict which fields will be affected by rapid change. Obviously software and venture capital will be, but who would have predicted that essay writing would be?
-
-[13] Y Combinator was not the original name. At first we were called Cambridge Seed. But we didn't want a regional name, in case someone copied us in Silicon Valley, so we renamed ourselves after one of the coolest tricks in the lambda calculus, the Y combinator.
-
-I picked orange as our color partly because it's the warmest, and partly because no VC used it. In 2005 all the VCs used staid colors like maroon, navy blue, and forest green, because they were trying to appeal to LPs, not founders. The YC logo itself is an inside joke: the Viaweb logo had been a white V on a red circle, so I made the YC logo a white Y on an orange square.
-
-[14] YC did become a fund for a couple years starting in 2009, because it was getting so big I could no longer afford to fund it personally. But after Heroku got bought we had enough money to go back to being self-funded.
-
-[15] I've never liked the term "deal flow," because it implies that the number of new startups at any given time is fixed. This is not only false, but it's the purpose of YC to falsify it, by causing startups to be founded that would not otherwise have existed.
-
-[16] She reports that they were all different shapes and sizes, because there was a run on air conditioners and she had to get whatever she could, but that they were all heavier than she could carry now.
-
-[17] Another problem with HN was a bizarre edge case that occurs when you both write essays and run a forum. When you run a forum, you're assumed to see if not every conversation, at least every conversation involving you. And when you write essays, people post highly imaginative misinterpretations of them on forums. Individually these two phenomena are tedious but bearable, but the combination is disastrous. You actually have to respond to the misinterpretations, because the assumption that you're present in the conversation means that not responding to any sufficiently upvoted misinterpretation reads as a tacit admission that it's correct. But that in turn encourages more; anyone who wants to pick a fight with you senses that now is their chance.
-
-[18] The worst thing about leaving YC was not working with Jessica anymore. We'd been working on YC almost the whole time we'd known each other, and we'd neither tried nor wanted to separate it from our personal lives, so leaving was like pulling up a deeply rooted tree.
-
-[19] One way to get more precise about the concept of invented vs discovered is to talk about space aliens. Any sufficiently advanced alien civilization would certainly know about the Pythagorean theorem, for example. I believe, though with less certainty, that they would also know about the Lisp in McCarthy's 1960 paper.
-
-But if so there's no reason to suppose that this is the limit of the language that might be known to them. Presumably aliens need numbers and errors and I/O too. So it seems likely there exists at least one path out of McCarthy's Lisp along which discoveredness is preserved.
-
-
-
-Thanks to Trevor Blackwell, John Collison, Patrick Collison, Daniel Gackle, Ralph Hazell, Jessica Livingston, Robert Morris, and Harj Taggar for reading drafts of this.

docs/docs/how_to/pydantic_compatibility.md

@@ -1,105 +0,0 @@
-# How to use LangChain with different Pydantic versions
-
-- 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/)
-- Pydantic v2 and v1 are under the same package name, so both versions cannot be installed at the same time
-
-## LangChain Pydantic migration plan
-
-As of `langchain>=0.0.267`, LangChain will allow users to install either Pydantic V1 or V2. 
-   * Internally LangChain will continue to [use V1](https://docs.pydantic.dev/latest/migration/#continue-using-pydantic-v1-features).
-   * During this time, users can pin their pydantic version to v1 to avoid breaking changes, or start a partial
-   migration using pydantic v2 throughout their code, but avoiding mixing v1 and v2 code for LangChain (see below).
-
-User can either pin to pydantic v1, and upgrade their code in one go once LangChain has migrated to v2 internally, or they can start a partial migration to v2, but must avoid mixing v1 and v2 code for LangChain.
-
-Below are two examples of showing how to avoid mixing pydantic v1 and v2 code in
-the case of inheritance and in the case of passing objects to LangChain.
-
-**Example 1: Extending via inheritance**
-
-**YES** 
-
-```python
-from pydantic.v1 import root_validator, validator
-
-class CustomTool(BaseTool): # BaseTool is v1 code
-    x: int = Field(default=1)
-
-    def _run(*args, **kwargs):
-        return "hello"
-
-    @validator('x') # v1 code
-    @classmethod
-    def validate_x(cls, x: int) -> int:
-        return 1
-    
-
-CustomTool(
-    name='custom_tool',
-    description="hello",
-    x=1,
-)
-```
-
-Mixing Pydantic v2 primitives with Pydantic v1 primitives can raise cryptic errors
-
-**NO** 
-
-```python
-from pydantic import Field, field_validator # pydantic v2
-
-class CustomTool(BaseTool): # BaseTool is v1 code
-    x: int = Field(default=1)
-
-    def _run(*args, **kwargs):
-        return "hello"
-
-    @field_validator('x') # v2 code
-    @classmethod
-    def validate_x(cls, x: int) -> int:
-        return 1
-    
-
-CustomTool( 
-    name='custom_tool',
-    description="hello",
-    x=1,
-)
-```
-
-**Example 2: Passing objects to LangChain**
-
-**YES**
-
-```python
-from langchain_core.tools import Tool
-from pydantic.v1 import BaseModel, Field # <-- Uses v1 namespace
-
-class CalculatorInput(BaseModel):
-    question: str = Field()
-
-Tool.from_function( # <-- tool uses v1 namespace
-    func=lambda question: 'hello',
-    name="Calculator",
-    description="useful for when you need to answer questions about math",
-    args_schema=CalculatorInput
-)
-```
-
-**NO**
-
-```python
-from langchain_core.tools import Tool
-from pydantic import BaseModel, Field # <-- Uses v2 namespace
-
-class CalculatorInput(BaseModel):
-    question: str = Field()
-
-Tool.from_function( # <-- tool uses v1 namespace
-    func=lambda question: 'hello',
-    name="Calculator",
-    description="useful for when you need to answer questions about math",
-    args_schema=CalculatorInput
-)
-```

docs/docs/how_to/qa_chat_history_how_to.ipynb

@@ -36,13 +36,12 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 1,
+   "execution_count": null,
    "id": "ede7fdc0-ef31-483d-bd67-32e4b5c5d527",
    "metadata": {},
    "outputs": [],
    "source": [
-    "%%capture --no-stderr\n",
-    "%pip install --upgrade --quiet  langchain langchain-community langchain-chroma bs4"
+    "%pip install --upgrade --quiet  langchain langchain-community langchainhub langchain-chroma bs4"
    ]
   },
   {
@@ -55,7 +54,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 2,
+   "execution_count": null,
    "id": "143787ca-d8e6-4dc9-8281-4374f4d71720",
    "metadata": {},
    "outputs": [],
@@ -63,8 +62,7 @@
     "import getpass\n",
     "import os\n",
     "\n",
-    "if not os.environ.get(\"OPENAI_API_KEY\"):\n",
-    "    os.environ[\"OPENAI_API_KEY\"] = getpass.getpass()\n",
+    "os.environ[\"OPENAI_API_KEY\"] = getpass.getpass()\n",
     "\n",
     "# import dotenv\n",
     "\n",
@@ -85,14 +83,13 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 3,
+   "execution_count": 2,
    "id": "07411adb-3722-4f65-ab7f-8f6f57663d11",
    "metadata": {},
    "outputs": [],
    "source": [
     "os.environ[\"LANGCHAIN_TRACING_V2\"] = \"true\"\n",
-    "if not os.environ.get(\"LANGCHAIN_API_KEY\"):\n",
-    "    os.environ[\"LANGCHAIN_API_KEY\"] = getpass.getpass()"
+    "os.environ[\"LANGCHAIN_API_KEY\"] = getpass.getpass()"
    ]
   },
   {
@@ -129,7 +126,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 4,
+   "execution_count": 1,
    "id": "cb58f273-2111-4a9b-8932-9b64c95030c8",
    "metadata": {},
    "outputs": [],
@@ -160,12 +157,13 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 5,
+   "execution_count": 2,
    "id": "820244ae-74b4-4593-b392-822979dd91b8",
    "metadata": {},
    "outputs": [],
    "source": [
     "import bs4\n",
+    "from langchain import hub\n",
     "from langchain.chains import create_retrieval_chain\n",
     "from langchain.chains.combine_documents import create_stuff_documents_chain\n",
     "from langchain_chroma import Chroma\n",
@@ -204,7 +202,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 6,
+   "execution_count": 3,
    "id": "2b685428-8b82-4af1-be4f-7232c5d55b73",
    "metadata": {},
    "outputs": [],
@@ -241,7 +239,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 7,
+   "execution_count": 4,
    "id": "4c4b1695-6217-4ee8-abaf-7cc26366d988",
    "metadata": {},
    "outputs": [],
@@ -267,7 +265,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 8,
+   "execution_count": 5,
    "id": "afef4385-f571-4874-8f52-3d475642f579",
    "metadata": {},
    "outputs": [],
@@ -316,7 +314,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 9,
+   "execution_count": 6,
    "id": "9c3fb176-8d6a-4dc7-8408-6a22c5f7cc72",
    "metadata": {},
    "outputs": [],
@@ -345,17 +343,17 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 10,
+   "execution_count": 7,
    "id": "1046c92f-21b3-4214-907d-92878d8cba23",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "'Task decomposition involves breaking down a complex task into smaller and simpler steps to make it more manageable and easier to accomplish. This process can be done using techniques like Chain of Thought (CoT) or Tree of Thoughts to guide the model in breaking down tasks effectively. Task decomposition can be facilitated by providing simple prompts to a language model, task-specific instructions, or human inputs.'"
+       "'Task decomposition involves breaking down a complex task into smaller and simpler steps to make it more manageable and easier to accomplish. This process can be done using techniques like Chain of Thought (CoT) or Tree of Thoughts to guide the model in thinking step by step or exploring multiple reasoning possibilities at each step. Task decomposition can be facilitated by providing simple prompts to a language model, task-specific instructions, or human inputs.'"
       ]
      },
-     "execution_count": 10,
+     "execution_count": 7,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -371,17 +369,17 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 11,
+   "execution_count": 8,
    "id": "0e89c75f-7ad7-4331-a2fe-57579eb8f840",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "'Task decomposition can be achieved through various methods, including using techniques like Chain of Thought (CoT) or Tree of Thoughts to guide the model in breaking down tasks effectively. Common ways of task decomposition include providing simple prompts to a language model, task-specific instructions, or human inputs to break down complex tasks into smaller and more manageable steps. Additionally, task decomposition can involve utilizing resources like internet access for information gathering, long-term memory management, and GPT-3.5 powered agents for delegation of simple tasks.'"
+       "'Task decomposition can be achieved through various methods, including using techniques like Chain of Thought (CoT) or Tree of Thoughts to guide the model in breaking down complex tasks into smaller steps. Common ways of task decomposition include providing simple prompts to a language model, task-specific instructions tailored to the specific task at hand, or incorporating human inputs to guide the decomposition process effectively.'"
       ]
      },
-     "execution_count": 11,
+     "execution_count": 8,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -403,7 +401,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 12,
+   "execution_count": 10,
    "id": "7686b874-3a85-499f-82b5-28a85c4c768c",
    "metadata": {},
    "outputs": [
@@ -413,11 +411,11 @@
      "text": [
       "User: What is Task Decomposition?\n",
       "\n",
-      "AI: Task decomposition involves breaking down a complex task into smaller and simpler steps to make it more manageable and easier to accomplish. This process can be done using techniques like Chain of Thought (CoT) or Tree of Thoughts to guide the model in breaking down tasks effectively. Task decomposition can be facilitated by providing simple prompts to a language model, task-specific instructions, or human inputs.\n",
+      "AI: Task decomposition involves breaking down a complex task into smaller and simpler steps to make it more manageable and easier to accomplish. This process can be done using techniques like Chain of Thought (CoT) or Tree of Thoughts to guide the model in thinking step by step or exploring multiple reasoning possibilities at each step. Task decomposition can be facilitated by providing simple prompts to a language model, task-specific instructions, or human inputs.\n",
       "\n",
       "User: What are common ways of doing it?\n",
       "\n",
-      "AI: Task decomposition can be achieved through various methods, including using techniques like Chain of Thought (CoT) or Tree of Thoughts to guide the model in breaking down tasks effectively. Common ways of task decomposition include providing simple prompts to a language model, task-specific instructions, or human inputs to break down complex tasks into smaller and more manageable steps. Additionally, task decomposition can involve utilizing resources like internet access for information gathering, long-term memory management, and GPT-3.5 powered agents for delegation of simple tasks.\n",
+      "AI: Task decomposition can be achieved through various methods, including using techniques like Chain of Thought (CoT) or Tree of Thoughts to guide the model in breaking down complex tasks into smaller steps. Common ways of task decomposition include providing simple prompts to a language model, task-specific instructions tailored to the specific task at hand, or incorporating human inputs to guide the decomposition process effectively.\n",
       "\n"
      ]
     }
@@ -454,7 +452,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 13,
+   "execution_count": 1,
    "id": "71c32048-1a41-465f-a9e2-c4affc332fd9",
    "metadata": {},
    "outputs": [],
@@ -554,17 +552,17 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 14,
+   "execution_count": 2,
    "id": "6d0a7a73-d151-47d9-9e99-b4f3291c0322",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "'Task decomposition involves breaking down a complex task into smaller and simpler steps to make it more manageable. Techniques like Chain of Thought (CoT) and Tree of Thoughts help in decomposing hard tasks into multiple manageable tasks by instructing models to think step by step and explore multiple reasoning possibilities at each step. Task decomposition can be achieved through various methods such as using prompting techniques, task-specific instructions, or human inputs.'"
+       "'Task decomposition involves breaking down a complex task into smaller and simpler steps to make it more manageable. This process helps agents or models tackle difficult tasks by dividing them into more easily achievable subgoals. Task decomposition can be done through techniques like Chain of Thought or Tree of Thoughts, which guide the model in thinking step by step or exploring multiple reasoning possibilities at each step.'"
       ]
      },
-     "execution_count": 14,
+     "execution_count": 2,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -580,17 +578,17 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 15,
+   "execution_count": 3,
    "id": "17021822-896a-4513-a17d-1d20b1c5381c",
    "metadata": {},
    "outputs": [
     {
      "data": {
       "text/plain": [
-       "'Task decomposition can be done in common ways such as using prompting techniques like Chain of Thought (CoT) or Tree of Thoughts, which instruct models to think step by step and explore multiple reasoning possibilities at each step. Another way is to provide task-specific instructions, such as asking to \"Write a story outline\" for writing a novel, to guide the decomposition process. Additionally, task decomposition can also involve human inputs to break down complex tasks into smaller and simpler steps.'"
+       "\"Common ways of task decomposition include using techniques like Chain of Thought (CoT) or Tree of Thoughts to guide models in breaking down complex tasks into smaller steps. This can be achieved through simple prompting with LLMs, task-specific instructions, or human inputs to help the model understand and navigate the task effectively. Task decomposition aims to enhance model performance on complex tasks by utilizing more test-time computation and shedding light on the model's thinking process.\""
       ]
      },
-     "execution_count": 15,
+     "execution_count": 3,
      "metadata": {},
      "output_type": "execute_result"
     }
@@ -620,7 +618,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 16,
+   "execution_count": 2,
    "id": "809cc747-2135-40a2-8e73-e4556343ee64",
    "metadata": {},
    "outputs": [],
@@ -648,14 +646,14 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 17,
+   "execution_count": 3,
    "id": "1726d151-4653-4c72-a187-a14840add526",
    "metadata": {},
    "outputs": [],
    "source": [
-    "from langgraph.prebuilt import create_react_agent\n",
+    "from langgraph.prebuilt import chat_agent_executor\n",
     "\n",
-    "agent_executor = create_react_agent(llm, tools)"
+    "agent_executor = chat_agent_executor.create_tool_calling_executor(llm, tools)"
    ]
   },
   {
@@ -668,26 +666,19 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 18,
+   "execution_count": 5,
    "id": "52ae46d9-43f7-481b-96d5-df750be3ad65",
    "metadata": {},
    "outputs": [
-    {
-     "name": "stderr",
-     "output_type": "stream",
-     "text": [
-      "Error in LangChainTracer.on_tool_end callback: TracerException(\"Found chain run at ID 5cd28d13-88dd-4eac-a465-3770ac27eff6, but expected {'tool'} run.\")\n"
-     ]
-    },
     {
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "{'agent': {'messages': [AIMessage(content='', additional_kwargs={'tool_calls': [{'id': 'call_TbhPPPN05GKi36HLeaN4QM90', 'function': {'arguments': '{\"query\":\"Task Decomposition\"}', 'name': 'blog_post_retriever'}, 'type': 'function'}]}, response_metadata={'token_usage': {'completion_tokens': 19, 'prompt_tokens': 68, 'total_tokens': 87}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': None, 'finish_reason': 'tool_calls', 'logprobs': None}, id='run-2e60d910-879a-4a2a-b1e9-6a6c5c7d7ebc-0', tool_calls=[{'name': 'blog_post_retriever', 'args': {'query': 'Task Decomposition'}, 'id': 'call_TbhPPPN05GKi36HLeaN4QM90'}])]}}\n",
+      "{'agent': {'messages': [AIMessage(content='', additional_kwargs={'tool_calls': [{'id': 'call_wxRrUmNbaNny8wh9JIb5uCRB', 'function': {'arguments': '{\"query\":\"Task Decomposition\"}', 'name': 'blog_post_retriever'}, 'type': 'function'}]}, response_metadata={'token_usage': {'completion_tokens': 19, 'prompt_tokens': 68, 'total_tokens': 87}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_3b956da36b', 'finish_reason': 'tool_calls', 'logprobs': None}, id='run-57ee0d12-6142-4957-a002-cce0093efe07-0', tool_calls=[{'name': 'blog_post_retriever', 'args': {'query': 'Task Decomposition'}, 'id': 'call_wxRrUmNbaNny8wh9JIb5uCRB'}])]}}\n",
       "----\n",
-      "{'tools': {'messages': [ToolMessage(content='Fig. 1. Overview of a LLM-powered autonomous agent system.\\nComponent One: Planning#\\nA complicated task usually involves many steps. An agent needs to know what they are and plan ahead.\\nTask Decomposition#\\nChain of thought (CoT; Wei et al. 2022) has become a standard prompting technique for enhancing model performance on complex tasks. The model is instructed to “think step by step” to utilize more test-time computation to decompose hard tasks into smaller and simpler steps. CoT transforms big tasks into multiple manageable tasks and shed lights into an interpretation of the model’s thinking process.\\n\\nFig. 1. Overview of a LLM-powered autonomous agent system.\\nComponent One: Planning#\\nA complicated task usually involves many steps. An agent needs to know what they are and plan ahead.\\nTask Decomposition#\\nChain of thought (CoT; Wei et al. 2022) has become a standard prompting technique for enhancing model performance on complex tasks. The model is instructed to “think step by step” to utilize more test-time computation to decompose hard tasks into smaller and simpler steps. CoT transforms big tasks into multiple manageable tasks and shed lights into an interpretation of the model’s thinking process.\\n\\nTree of Thoughts (Yao et al. 2023) extends CoT by exploring multiple reasoning possibilities at each step. It first decomposes the problem into multiple thought steps and generates multiple thoughts per step, creating a tree structure. The search process can be BFS (breadth-first search) or DFS (depth-first search) with each state evaluated by a classifier (via a prompt) or majority vote.\\nTask decomposition can be done (1) by LLM with simple prompting like \"Steps for XYZ.\\\\n1.\", \"What are the subgoals for achieving XYZ?\", (2) by using task-specific instructions; e.g. \"Write a story outline.\" for writing a novel, or (3) with human inputs.\\n\\nTree of Thoughts (Yao et al. 2023) extends CoT by exploring multiple reasoning possibilities at each step. It first decomposes the problem into multiple thought steps and generates multiple thoughts per step, creating a tree structure. The search process can be BFS (breadth-first search) or DFS (depth-first search) with each state evaluated by a classifier (via a prompt) or majority vote.\\nTask decomposition can be done (1) by LLM with simple prompting like \"Steps for XYZ.\\\\n1.\", \"What are the subgoals for achieving XYZ?\", (2) by using task-specific instructions; e.g. \"Write a story outline.\" for writing a novel, or (3) with human inputs.', name='blog_post_retriever', tool_call_id='call_TbhPPPN05GKi36HLeaN4QM90')]}}\n",
+      "{'action': {'messages': [ToolMessage(content='Fig. 1. Overview of a LLM-powered autonomous agent system.\\nComponent One: Planning#\\nA complicated task usually involves many steps. An agent needs to know what they are and plan ahead.\\nTask Decomposition#\\nChain of thought (CoT; Wei et al. 2022) has become a standard prompting technique for enhancing model performance on complex tasks. The model is instructed to “think step by step” to utilize more test-time computation to decompose hard tasks into smaller and simpler steps. CoT transforms big tasks into multiple manageable tasks and shed lights into an interpretation of the model’s thinking process.\\n\\nTree of Thoughts (Yao et al. 2023) extends CoT by exploring multiple reasoning possibilities at each step. It first decomposes the problem into multiple thought steps and generates multiple thoughts per step, creating a tree structure. The search process can be BFS (breadth-first search) or DFS (depth-first search) with each state evaluated by a classifier (via a prompt) or majority vote.\\nTask decomposition can be done (1) by LLM with simple prompting like \"Steps for XYZ.\\\\n1.\", \"What are the subgoals for achieving XYZ?\", (2) by using task-specific instructions; e.g. \"Write a story outline.\" for writing a novel, or (3) with human inputs.\\n\\n(3) Task execution: Expert models execute on the specific tasks and log results.\\nInstruction:\\n\\nWith the input and the inference results, the AI assistant needs to describe the process and results. The previous stages can be formed as - User Input: {{ User Input }}, Task Planning: {{ Tasks }}, Model Selection: {{ Model Assignment }}, Task Execution: {{ Predictions }}. You must first answer the user\\'s request in a straightforward manner. Then describe the task process and show your analysis and model inference results to the user in the first person. If inference results contain a file path, must tell the user the complete file path.\\n\\nFig. 11. Illustration of how HuggingGPT works. (Image source: Shen et al. 2023)\\nThe system comprises of 4 stages:\\n(1) Task planning: LLM works as the brain and parses the user requests into multiple tasks. There are four attributes associated with each task: task type, ID, dependencies, and arguments. They use few-shot examples to guide LLM to do task parsing and planning.\\nInstruction:', name='blog_post_retriever', id='9c3a17f7-653c-47fa-b4e4-fa3d8d24c85d', tool_call_id='call_wxRrUmNbaNny8wh9JIb5uCRB')]}}\n",
       "----\n",
-      "{'agent': {'messages': [AIMessage(content='Task decomposition is a technique used to break down complex tasks into smaller and simpler steps. This approach helps in transforming big tasks into multiple manageable tasks, making it easier for autonomous agents to handle and interpret the thinking process. One common method for task decomposition is the Chain of Thought (CoT) technique, where models are instructed to \"think step by step\" to decompose hard tasks. Another extension of CoT is the Tree of Thoughts, which explores multiple reasoning possibilities at each step by creating a tree structure of multiple thoughts per step. Task decomposition can be facilitated through various methods such as using simple prompts, task-specific instructions, or human inputs.', response_metadata={'token_usage': {'completion_tokens': 130, 'prompt_tokens': 636, 'total_tokens': 766}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': None, 'finish_reason': 'stop', 'logprobs': None}, id='run-3ef17638-65df-4030-a7fe-795e6da91c69-0')]}}\n",
+      "{'agent': {'messages': [AIMessage(content='Task decomposition is a technique used to break down complex tasks into smaller and simpler steps. This approach helps agents in planning and executing tasks more effectively. One common method for task decomposition is the Chain of Thought (CoT) technique, where models are instructed to think step by step to decompose hard tasks into manageable steps. Another extension of CoT is the Tree of Thoughts, which explores multiple reasoning possibilities at each step by creating a tree structure of thought steps.\\n\\nTask decomposition can be achieved through various methods, such as using language models with simple prompting, task-specific instructions, or human inputs. By breaking down tasks into smaller components, agents can better plan and execute tasks efficiently.\\n\\nIf you would like more detailed information or examples on task decomposition, feel free to ask!', response_metadata={'token_usage': {'completion_tokens': 154, 'prompt_tokens': 588, 'total_tokens': 742}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_3b956da36b', 'finish_reason': 'stop', 'logprobs': None}, id='run-8991fa20-c527-4f9e-a058-fc6264fe6259-0')]}}\n",
       "----\n"
      ]
     }
@@ -716,7 +707,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 19,
+   "execution_count": null,
    "id": "837a401e-9757-4d0e-a0da-24fa097d887e",
    "metadata": {},
    "outputs": [],
@@ -725,7 +716,9 @@
     "\n",
     "memory = SqliteSaver.from_conn_string(\":memory:\")\n",
     "\n",
-    "agent_executor = create_react_agent(llm, tools, checkpointer=memory)"
+    "agent_executor = chat_agent_executor.create_tool_calling_executor(\n",
+    "    llm, tools, checkpointer=memory\n",
+    ")"
    ]
   },
   {
@@ -740,7 +733,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 20,
+   "execution_count": 22,
    "id": "d6d70833-b958-4cd7-9e27-29c1c08bb1b8",
    "metadata": {},
    "outputs": [
@@ -748,7 +741,7 @@
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "{'agent': {'messages': [AIMessage(content='Hello Bob! How can I assist you today?', response_metadata={'token_usage': {'completion_tokens': 11, 'prompt_tokens': 67, 'total_tokens': 78}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': None, 'finish_reason': 'stop', 'logprobs': None}, id='run-1cd17562-18aa-4839-b41b-403b17a0fc20-0')]}}\n",
+      "{'agent': {'messages': [AIMessage(content='Hello Bob! How can I assist you today?', response_metadata={'token_usage': {'completion_tokens': 11, 'prompt_tokens': 67, 'total_tokens': 78}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_3b956da36b', 'finish_reason': 'stop', 'logprobs': None}, id='run-1451e59b-b135-4776-985d-4759338ffee5-0')]}}\n",
       "----\n"
      ]
     }
@@ -773,26 +766,19 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 21,
+   "execution_count": 23,
    "id": "e2c570ae-dd91-402c-8693-ae746de63b16",
    "metadata": {},
    "outputs": [
-    {
-     "name": "stderr",
-     "output_type": "stream",
-     "text": [
-      "Error in LangChainTracer.on_tool_end callback: TracerException(\"Found chain run at ID c54381c0-c5d9-495a-91a0-aca4ae755663, but expected {'tool'} run.\")\n"
-     ]
-    },
     {
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "{'agent': {'messages': [AIMessage(content='', additional_kwargs={'tool_calls': [{'id': 'call_rg7zKTE5e0ICxVSslJ1u9LMg', 'function': {'arguments': '{\"query\":\"Task Decomposition\"}', 'name': 'blog_post_retriever'}, 'type': 'function'}]}, response_metadata={'token_usage': {'completion_tokens': 19, 'prompt_tokens': 91, 'total_tokens': 110}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': None, 'finish_reason': 'tool_calls', 'logprobs': None}, id='run-122bf097-7ff1-49aa-b430-e362b51354ad-0', tool_calls=[{'name': 'blog_post_retriever', 'args': {'query': 'Task Decomposition'}, 'id': 'call_rg7zKTE5e0ICxVSslJ1u9LMg'}])]}}\n",
+      "{'agent': {'messages': [AIMessage(content='', additional_kwargs={'tool_calls': [{'id': 'call_ab2x4iUPSWDAHS5txL7PspSK', 'function': {'arguments': '{\"query\":\"Task Decomposition\"}', 'name': 'blog_post_retriever'}, 'type': 'function'}]}, response_metadata={'token_usage': {'completion_tokens': 19, 'prompt_tokens': 91, 'total_tokens': 110}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_3b956da36b', 'finish_reason': 'tool_calls', 'logprobs': None}, id='run-f76b5813-b41c-4d0d-9ed2-667b988d885e-0', tool_calls=[{'name': 'blog_post_retriever', 'args': {'query': 'Task Decomposition'}, 'id': 'call_ab2x4iUPSWDAHS5txL7PspSK'}])]}}\n",
       "----\n",
-      "{'tools': {'messages': [ToolMessage(content='Fig. 1. Overview of a LLM-powered autonomous agent system.\\nComponent One: Planning#\\nA complicated task usually involves many steps. An agent needs to know what they are and plan ahead.\\nTask Decomposition#\\nChain of thought (CoT; Wei et al. 2022) has become a standard prompting technique for enhancing model performance on complex tasks. The model is instructed to “think step by step” to utilize more test-time computation to decompose hard tasks into smaller and simpler steps. CoT transforms big tasks into multiple manageable tasks and shed lights into an interpretation of the model’s thinking process.\\n\\nFig. 1. Overview of a LLM-powered autonomous agent system.\\nComponent One: Planning#\\nA complicated task usually involves many steps. An agent needs to know what they are and plan ahead.\\nTask Decomposition#\\nChain of thought (CoT; Wei et al. 2022) has become a standard prompting technique for enhancing model performance on complex tasks. The model is instructed to “think step by step” to utilize more test-time computation to decompose hard tasks into smaller and simpler steps. CoT transforms big tasks into multiple manageable tasks and shed lights into an interpretation of the model’s thinking process.\\n\\nTree of Thoughts (Yao et al. 2023) extends CoT by exploring multiple reasoning possibilities at each step. It first decomposes the problem into multiple thought steps and generates multiple thoughts per step, creating a tree structure. The search process can be BFS (breadth-first search) or DFS (depth-first search) with each state evaluated by a classifier (via a prompt) or majority vote.\\nTask decomposition can be done (1) by LLM with simple prompting like \"Steps for XYZ.\\\\n1.\", \"What are the subgoals for achieving XYZ?\", (2) by using task-specific instructions; e.g. \"Write a story outline.\" for writing a novel, or (3) with human inputs.\\n\\nTree of Thoughts (Yao et al. 2023) extends CoT by exploring multiple reasoning possibilities at each step. It first decomposes the problem into multiple thought steps and generates multiple thoughts per step, creating a tree structure. The search process can be BFS (breadth-first search) or DFS (depth-first search) with each state evaluated by a classifier (via a prompt) or majority vote.\\nTask decomposition can be done (1) by LLM with simple prompting like \"Steps for XYZ.\\\\n1.\", \"What are the subgoals for achieving XYZ?\", (2) by using task-specific instructions; e.g. \"Write a story outline.\" for writing a novel, or (3) with human inputs.', name='blog_post_retriever', tool_call_id='call_rg7zKTE5e0ICxVSslJ1u9LMg')]}}\n",
+      "{'action': {'messages': [ToolMessage(content='Fig. 1. Overview of a LLM-powered autonomous agent system.\\nComponent One: Planning#\\nA complicated task usually involves many steps. An agent needs to know what they are and plan ahead.\\nTask Decomposition#\\nChain of thought (CoT; Wei et al. 2022) has become a standard prompting technique for enhancing model performance on complex tasks. The model is instructed to “think step by step” to utilize more test-time computation to decompose hard tasks into smaller and simpler steps. CoT transforms big tasks into multiple manageable tasks and shed lights into an interpretation of the model’s thinking process.\\n\\nTree of Thoughts (Yao et al. 2023) extends CoT by exploring multiple reasoning possibilities at each step. It first decomposes the problem into multiple thought steps and generates multiple thoughts per step, creating a tree structure. The search process can be BFS (breadth-first search) or DFS (depth-first search) with each state evaluated by a classifier (via a prompt) or majority vote.\\nTask decomposition can be done (1) by LLM with simple prompting like \"Steps for XYZ.\\\\n1.\", \"What are the subgoals for achieving XYZ?\", (2) by using task-specific instructions; e.g. \"Write a story outline.\" for writing a novel, or (3) with human inputs.\\n\\n(3) Task execution: Expert models execute on the specific tasks and log results.\\nInstruction:\\n\\nWith the input and the inference results, the AI assistant needs to describe the process and results. The previous stages can be formed as - User Input: {{ User Input }}, Task Planning: {{ Tasks }}, Model Selection: {{ Model Assignment }}, Task Execution: {{ Predictions }}. You must first answer the user\\'s request in a straightforward manner. Then describe the task process and show your analysis and model inference results to the user in the first person. If inference results contain a file path, must tell the user the complete file path.\\n\\nFig. 11. Illustration of how HuggingGPT works. (Image source: Shen et al. 2023)\\nThe system comprises of 4 stages:\\n(1) Task planning: LLM works as the brain and parses the user requests into multiple tasks. There are four attributes associated with each task: task type, ID, dependencies, and arguments. They use few-shot examples to guide LLM to do task parsing and planning.\\nInstruction:', name='blog_post_retriever', id='e0895fa5-5d41-4be0-98db-10a83d42fc2f', tool_call_id='call_ab2x4iUPSWDAHS5txL7PspSK')]}}\n",
       "----\n",
-      "{'agent': {'messages': [AIMessage(content='Task decomposition is a technique used to break down complex tasks into smaller and simpler steps. This approach helps in managing and solving intricate problems by dividing them into more manageable components. By decomposing tasks, agents or models can better understand the steps involved and plan their actions accordingly. Techniques like Chain of Thought (CoT) and Tree of Thoughts are examples of methods that enhance model performance on complex tasks by breaking them down into smaller steps.', response_metadata={'token_usage': {'completion_tokens': 87, 'prompt_tokens': 659, 'total_tokens': 746}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': None, 'finish_reason': 'stop', 'logprobs': None}, id='run-b9166386-83e5-4b82-9a4b-590e5fa76671-0')]}}\n",
+      "{'agent': {'messages': [AIMessage(content='Task decomposition is a technique used in complex tasks where the task is broken down into smaller and simpler steps. This approach helps in managing and solving difficult tasks by dividing them into more manageable components. One common method for task decomposition is the Chain of Thought (CoT) technique, which prompts the model to think step by step and decompose hard tasks into smaller steps. Another extension of CoT is the Tree of Thoughts, which explores multiple reasoning possibilities at each step by creating a tree structure of thought steps.\\n\\nTask decomposition can be achieved through various methods, such as using language models with simple prompting, task-specific instructions, or human inputs. By breaking down tasks into smaller components, agents can better plan and execute complex tasks effectively.\\n\\nIf you would like more detailed information or examples related to task decomposition, feel free to ask!', response_metadata={'token_usage': {'completion_tokens': 165, 'prompt_tokens': 611, 'total_tokens': 776}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_3b956da36b', 'finish_reason': 'stop', 'logprobs': None}, id='run-13296566-8577-4d65-982b-a39718988ca3-0')]}}\n",
       "----\n"
      ]
     }
@@ -819,7 +805,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 22,
+   "execution_count": 25,
    "id": "570d8c68-136e-4ba5-969a-03ba195f6118",
    "metadata": {},
    "outputs": [
@@ -827,24 +813,11 @@
      "name": "stdout",
      "output_type": "stream",
      "text": [
-      "{'agent': {'messages': [AIMessage(content='', additional_kwargs={'tool_calls': [{'id': 'call_6kbxTU5CDWLmF9mrvR7bWSkI', 'function': {'arguments': '{\"query\":\"Common ways of task decomposition\"}', 'name': 'blog_post_retriever'}, 'type': 'function'}]}, response_metadata={'token_usage': {'completion_tokens': 21, 'prompt_tokens': 769, 'total_tokens': 790}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': None, 'finish_reason': 'tool_calls', 'logprobs': None}, id='run-2d2c8327-35cd-484a-b8fd-52436657c2d8-0', tool_calls=[{'name': 'blog_post_retriever', 'args': {'query': 'Common ways of task decomposition'}, 'id': 'call_6kbxTU5CDWLmF9mrvR7bWSkI'}])]}}\n",
-      "----\n"
-     ]
-    },
-    {
-     "name": "stderr",
-     "output_type": "stream",
-     "text": [
-      "Error in LangChainTracer.on_tool_end callback: TracerException(\"Found chain run at ID 29553415-e0f4-41a9-8921-ba489e377f68, but expected {'tool'} run.\")\n"
-     ]
-    },
-    {
-     "name": "stdout",
-     "output_type": "stream",
-     "text": [
-      "{'tools': {'messages': [ToolMessage(content='Fig. 1. Overview of a LLM-powered autonomous agent system.\\nComponent One: Planning#\\nA complicated task usually involves many steps. An agent needs to know what they are and plan ahead.\\nTask Decomposition#\\nChain of thought (CoT; Wei et al. 2022) has become a standard prompting technique for enhancing model performance on complex tasks. The model is instructed to “think step by step” to utilize more test-time computation to decompose hard tasks into smaller and simpler steps. CoT transforms big tasks into multiple manageable tasks and shed lights into an interpretation of the model’s thinking process.\\n\\nFig. 1. Overview of a LLM-powered autonomous agent system.\\nComponent One: Planning#\\nA complicated task usually involves many steps. An agent needs to know what they are and plan ahead.\\nTask Decomposition#\\nChain of thought (CoT; Wei et al. 2022) has become a standard prompting technique for enhancing model performance on complex tasks. The model is instructed to “think step by step” to utilize more test-time computation to decompose hard tasks into smaller and simpler steps. CoT transforms big tasks into multiple manageable tasks and shed lights into an interpretation of the model’s thinking process.\\n\\nTree of Thoughts (Yao et al. 2023) extends CoT by exploring multiple reasoning possibilities at each step. It first decomposes the problem into multiple thought steps and generates multiple thoughts per step, creating a tree structure. The search process can be BFS (breadth-first search) or DFS (depth-first search) with each state evaluated by a classifier (via a prompt) or majority vote.\\nTask decomposition can be done (1) by LLM with simple prompting like \"Steps for XYZ.\\\\n1.\", \"What are the subgoals for achieving XYZ?\", (2) by using task-specific instructions; e.g. \"Write a story outline.\" for writing a novel, or (3) with human inputs.\\n\\nTree of Thoughts (Yao et al. 2023) extends CoT by exploring multiple reasoning possibilities at each step. It first decomposes the problem into multiple thought steps and generates multiple thoughts per step, creating a tree structure. The search process can be BFS (breadth-first search) or DFS (depth-first search) with each state evaluated by a classifier (via a prompt) or majority vote.\\nTask decomposition can be done (1) by LLM with simple prompting like \"Steps for XYZ.\\\\n1.\", \"What are the subgoals for achieving XYZ?\", (2) by using task-specific instructions; e.g. \"Write a story outline.\" for writing a novel, or (3) with human inputs.', name='blog_post_retriever', tool_call_id='call_6kbxTU5CDWLmF9mrvR7bWSkI')]}}\n",
+      "{'agent': {'messages': [AIMessage(content='', additional_kwargs={'tool_calls': [{'id': 'call_KvoiamnLfGEzMeEMlV3u0TJ7', 'function': {'arguments': '{\"query\":\"common ways of task decomposition\"}', 'name': 'blog_post_retriever'}, 'type': 'function'}]}, response_metadata={'token_usage': {'completion_tokens': 21, 'prompt_tokens': 930, 'total_tokens': 951}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_3b956da36b', 'finish_reason': 'tool_calls', 'logprobs': None}, id='run-dd842071-6dbd-4b68-8657-892eaca58638-0', tool_calls=[{'name': 'blog_post_retriever', 'args': {'query': 'common ways of task decomposition'}, 'id': 'call_KvoiamnLfGEzMeEMlV3u0TJ7'}])]}}\n",
       "----\n",
-      "{'agent': {'messages': [AIMessage(content='Common ways of task decomposition include:\\n1. Using LLM with simple prompting like \"Steps for XYZ\" or \"What are the subgoals for achieving XYZ?\"\\n2. Using task-specific instructions, for example, \"Write a story outline\" for writing a novel.\\n3. Involving human inputs in the task decomposition process.', response_metadata={'token_usage': {'completion_tokens': 67, 'prompt_tokens': 1339, 'total_tokens': 1406}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': None, 'finish_reason': 'stop', 'logprobs': None}, id='run-9ad14cde-ca75-4238-a868-f865e0fc50dd-0')]}}\n",
+      "{'action': {'messages': [ToolMessage(content='Tree of Thoughts (Yao et al. 2023) extends CoT by exploring multiple reasoning possibilities at each step. It first decomposes the problem into multiple thought steps and generates multiple thoughts per step, creating a tree structure. The search process can be BFS (breadth-first search) or DFS (depth-first search) with each state evaluated by a classifier (via a prompt) or majority vote.\\nTask decomposition can be done (1) by LLM with simple prompting like \"Steps for XYZ.\\\\n1.\", \"What are the subgoals for achieving XYZ?\", (2) by using task-specific instructions; e.g. \"Write a story outline.\" for writing a novel, or (3) with human inputs.\\n\\nFig. 1. Overview of a LLM-powered autonomous agent system.\\nComponent One: Planning#\\nA complicated task usually involves many steps. An agent needs to know what they are and plan ahead.\\nTask Decomposition#\\nChain of thought (CoT; Wei et al. 2022) has become a standard prompting technique for enhancing model performance on complex tasks. The model is instructed to “think step by step” to utilize more test-time computation to decompose hard tasks into smaller and simpler steps. CoT transforms big tasks into multiple manageable tasks and shed lights into an interpretation of the model’s thinking process.\\n\\nResources:\\n1. Internet access for searches and information gathering.\\n2. Long Term memory management.\\n3. GPT-3.5 powered Agents for delegation of simple tasks.\\n4. File output.\\n\\nPerformance Evaluation:\\n1. Continuously review and analyze your actions to ensure you are performing to the best of your abilities.\\n2. Constructively self-criticize your big-picture behavior constantly.\\n3. Reflect on past decisions and strategies to refine your approach.\\n4. Every command has a cost, so be smart and efficient. Aim to complete tasks in the least number of steps.\\n\\n(3) Task execution: Expert models execute on the specific tasks and log results.\\nInstruction:\\n\\nWith the input and the inference results, the AI assistant needs to describe the process and results. The previous stages can be formed as - User Input: {{ User Input }}, Task Planning: {{ Tasks }}, Model Selection: {{ Model Assignment }}, Task Execution: {{ Predictions }}. You must first answer the user\\'s request in a straightforward manner. Then describe the task process and show your analysis and model inference results to the user in the first person. If inference results contain a file path, must tell the user the complete file path.', name='blog_post_retriever', id='c749bb8e-c8e0-4fa3-bc11-3e2e0651880b', tool_call_id='call_KvoiamnLfGEzMeEMlV3u0TJ7')]}}\n",
+      "----\n",
+      "{'agent': {'messages': [AIMessage(content='According to the blog post, common ways of task decomposition include:\\n\\n1. Using language models with simple prompting like \"Steps for XYZ\" or \"What are the subgoals for achieving XYZ?\"\\n2. Utilizing task-specific instructions, for example, using \"Write a story outline\" for writing a novel.\\n3. Involving human inputs in the task decomposition process.\\n\\nThese methods help in breaking down complex tasks into smaller and more manageable steps, facilitating better planning and execution of the overall task.', response_metadata={'token_usage': {'completion_tokens': 100, 'prompt_tokens': 1475, 'total_tokens': 1575}, 'model_name': 'gpt-3.5-turbo', 'system_fingerprint': 'fp_3b956da36b', 'finish_reason': 'stop', 'logprobs': None}, id='run-98b765b3-f1a6-4c9a-ad0f-2db7950b900f-0')]}}\n",
       "----\n"
      ]
     }
@@ -879,15 +852,20 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 23,
+   "execution_count": 26,
    "id": "b1d2b4d4-e604-497d-873d-d345b808578e",
    "metadata": {},
    "outputs": [],
    "source": [
     "import bs4\n",
+    "from langchain.agents import AgentExecutor, create_tool_calling_agent\n",
     "from langchain.tools.retriever import create_retriever_tool\n",
     "from langchain_chroma import Chroma\n",
+    "from langchain_community.chat_message_histories import ChatMessageHistory\n",
     "from langchain_community.document_loaders import WebBaseLoader\n",
+    "from langchain_core.chat_history import BaseChatMessageHistory\n",
+    "from langchain_core.prompts import ChatPromptTemplate, MessagesPlaceholder\n",
+    "from langchain_core.runnables.history import RunnableWithMessageHistory\n",
     "from langchain_openai import ChatOpenAI, OpenAIEmbeddings\n",
     "from langchain_text_splitters import RecursiveCharacterTextSplitter\n",
     "from langgraph.checkpoint.sqlite import SqliteSaver\n",
@@ -922,7 +900,9 @@
     "tools = [tool]\n",
     "\n",
     "\n",
-    "agent_executor = create_react_agent(llm, tools, checkpointer=memory)"
+    "agent_executor = chat_agent_executor.create_tool_calling_executor(\n",
+    "    llm, tools, checkpointer=memory\n",
+    ")"
    ]
   },
   {
@@ -961,7 +941,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.11.2"
+   "version": "3.10.4"
   }
  },
  "nbformat": 4,

docs/docs/how_to/qa_sources.ipynb

@@ -14,7 +14,7 @@
     "We will cover two approaches:\n",
     "\n",
     "1. Using the built-in [create_retrieval_chain](https://api.python.langchain.com/en/latest/chains/langchain.chains.retrieval.create_retrieval_chain.html), which returns sources by default;\n",
-    "2. Using a simple [LCEL](/docs/concepts#langchain-expression-language-lcel) implementation, to show the operating principle."
+    "2. Using a simple [LCEL](/docs/concepts#langchain-expression-language) implementation, to show the operating principle."
    ]
   },
   {

docs/docs/how_to/query_multiple_queries.ipynb

@@ -83,9 +83,9 @@
    "metadata": {},
    "outputs": [],
    "source": [
+    "from langchain.text_splitter import RecursiveCharacterTextSplitter\n",
     "from langchain_chroma import Chroma\n",
     "from langchain_openai import OpenAIEmbeddings\n",
-    "from langchain_text_splitters import RecursiveCharacterTextSplitter\n",
     "\n",
     "texts = [\"Harrison worked at Kensho\", \"Ankush worked at Facebook\"]\n",
     "embeddings = OpenAIEmbeddings(model=\"text-embedding-3-small\")\n",