From 85c0103ebb13463ffbefcef96b3ee75758ac603a Mon Sep 17 00:00:00 2001 From: Eugene Yurtsev Date: Thu, 6 Jun 2024 12:08:39 -0400 Subject: [PATCH] docs: another attempt to fix nav bar (#612) --- docs/_scripts/copy_notebooks.py | 1 + docs/docs/how-tos/index.md | 2 +- docs/mkdocs.yml | 4 ++-- ...ues-to-tools.ipynb => pass-run-time-values-to-tools.ipynb} | 0 4 files changed, 4 insertions(+), 3 deletions(-) rename examples/{passing-run-time-values-to-tools.ipynb => pass-run-time-values-to-tools.ipynb} (100%) diff --git a/docs/_scripts/copy_notebooks.py b/docs/_scripts/copy_notebooks.py index 8918d047e..4b9b42a34 100644 --- a/docs/_scripts/copy_notebooks.py +++ b/docs/_scripts/copy_notebooks.py @@ -20,6 +20,7 @@ _MANUAL = { "state-model.ipynb", "subgraph.ipynb", "force-calling-a-tool-first.ipynb", + "pass-run-time-values-to-tools.ipynb", "dynamic-returning-direct.ipynb", "managing-agent-steps.ipynb", "respond-in-format.ipynb", diff --git a/docs/docs/how-tos/index.md b/docs/docs/how-tos/index.md index 99413f785..e74b9cc17 100644 --- a/docs/docs/how-tos/index.md +++ b/docs/docs/how-tos/index.md @@ -25,7 +25,7 @@ Recipes showing how to apply common design patterns in your workflows: The following examples are useful especially if you are used to LangChain's AgentExecutor configurations. - [Force calling a tool first](force-calling-a-tool-first.ipynb): Define a fixed workflow before ceding control to the ReAct agent -- [Passing run time values to tools](passing-run-time-values-to-tools.ipynb): Pass values that are only known at run time to tools (e.g., the ID of the user who made the request) +- [Pass run time values to tools](pass-run-time-values-to-tools.ipynb): Pass values that are only known at run time to tools (e.g., the ID of the user who made the request) - [Dynamic direct return](dynamically-returning-directly.ipynb): Let the LLM decide whether the graph should finish after a tool is run or whether the LLM should be able to review the output and keep going - [Respond in structured format](respond-in-format.ipynb): Let the LLM use tools or populate schema to provide the user. Useful if your agent should generate structured content - [Managing agent steps](managing-agent-steps.ipynb): How to format the intermediate steps of your workflow for the agent diff --git a/docs/mkdocs.yml b/docs/mkdocs.yml index 121bbabd1..e8870acbd 100644 --- a/docs/mkdocs.yml +++ b/docs/mkdocs.yml @@ -147,7 +147,7 @@ nav: - "Map-reduce": how-tos/map-reduce.ipynb - "Human-in-the-Loop": how-tos/human-in-the-loop.ipynb - "Force Calling a Tool First": how-tos/force-calling-a-tool-first.ipynb - - "Passing Run-Time Values to Tools": how-tos/passing-run-time-values-to-tools.ipynb + - "Pass Run-Time Values to Tools": how-tos/pass-run-time-values-to-tools.ipynb - "Dynamic Direct Return": how-tos/dynamically-returning-directly.ipynb - "Respond in Structured Format": how-tos/respond-in-format.ipynb - "Managing Agent Steps": how-tos/managing-agent-steps.ipynb @@ -236,4 +236,4 @@ extra: name: This page could be improved data: 0 note: >- - Thanks for your feedback! Please help us improve this page by adding to the discussion below. \ No newline at end of file + Thanks for your feedback! Please help us improve this page by adding to the discussion below. diff --git a/examples/passing-run-time-values-to-tools.ipynb b/examples/pass-run-time-values-to-tools.ipynb similarity index 100% rename from examples/passing-run-time-values-to-tools.ipynb rename to examples/pass-run-time-values-to-tools.ipynb