From 425c437cd375a77dbb288a4eebacf609b456a0d3 Mon Sep 17 00:00:00 2001 From: Harrison Chase Date: Wed, 12 Apr 2023 13:46:58 -0700 Subject: [PATCH] cr --- docs/use_cases/agents/custom_agent_with_plugin_retrieval.ipynb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use_cases/agents/custom_agent_with_plugin_retrieval.ipynb b/docs/use_cases/agents/custom_agent_with_plugin_retrieval.ipynb index 0f72d882..cba8f69f 100644 --- a/docs/use_cases/agents/custom_agent_with_plugin_retrieval.ipynb +++ b/docs/use_cases/agents/custom_agent_with_plugin_retrieval.ipynb @@ -9,7 +9,7 @@ "\n", "This notebook combines two concepts in order to build a custom agent that can interact with AI Plugins:\n", "\n", - "1. [Custom Agent with Retrieval](../../modules/agents/agents/custom_agent_with_plugin_retrieval.html): This introduces the concept of retrieving many tools, which is useful when trying to work with arbitrarily many plugins.\n", + "1. [Custom Agent with Retrieval](../../modules/agents/agents/custom_agent_with_plugin_retrieval.ipynb): This introduces the concept of retrieving many tools, which is useful when trying to work with arbitrarily many plugins.\n", "2. [Natural Language API Chains](../../modules/chains/examples/openapi.ipynb): This creates Natural Language wrappers around OpenAPI endpoints. This is useful because (1) plugins use OpenAPI endpoints under the hood, (2) wrapping them in an NLAChain allows the router agent to call it more easily.\n", "\n", "The novel idea introduced in this notebook is the idea of using retrieval to select not the tools explicitly, but the set of OpenAPI specs to use. We can then generate tools from those OpenAPI specs. The use case for this is when trying to get agents to use plugins. It may be more efficient to choose plugins first, then the endpoints, rather than the endpoints directly. This is because the plugins may contain more useful information for selection."