Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/src/content/docs/agents/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -20,12 +20,12 @@ A well-crafted agent description:

The more detailed and precise these descriptions are, the more accurately the Classifier can route requests to the right agent. This is especially important in complex systems with multiple specialized agents.

For a more detailed explanation of the agent selection process, please refer to the [How it works section](/agent-squad/general/how-it-works) section in our documentation.
For a more detailed explanation of the agent selection process, please refer to the [How it works](/agent-squad/general/how-it-works) section in our documentation.

To optimize agent selection:
- Invest time in crafting thorough, specific agent descriptions
- Regularly review and refine these descriptions
- Use the framework's [agent overlap analysis](/agent-squad/advanced-features/agent-overlap) to ensure clear differentiation between agents
- Use the framework's [agent overlap analysis](/agent-squad/cookbook/monitoring/agent-overlap) to ensure clear differentiation between agents

By prioritizing detailed agent descriptions and fine-tuning the selection process, you can significantly enhance the efficiency and accuracy of your Agent Squad implementation.

Expand Down
2 changes: 1 addition & 1 deletion docs/src/content/docs/classifiers/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -193,4 +193,4 @@ Best for:

---

For more detailed information on each classifier, refer to the [BedrockClassifier](/agent-squad/classifiers/built-in/bedrock-classifier) and [AnthropicClassifier](/classifiers/built-in/anthropic-classifier) documentation pages.
For more detailed information on each classifier, refer to the [BedrockClassifier](/agent-squad/classifiers/built-in/bedrock-classifier) and [AnthropicClassifier](/agent-squad/classifiers/built-in/anthropic-classifier) documentation pages.
8 changes: 4 additions & 4 deletions docs/src/content/docs/general/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ Yes, the framework includes a built-in DynamoDB storage option. For detailed ins

##### Can I deploy the Agent Squad on AWS Lambda?

Yes, the system is designed for seamless deployment as an AWS Lambda function. For step-by-step guidance on integrating the orchestrator with Lambda, processing incoming requests, and handling responses, please consult the [AWS Lambda Integration](/agent-squad/deployment/aws-lambda) section in our documentation.
Yes, the system is designed for seamless deployment as an AWS Lambda function. For step-by-step guidance on integrating the orchestrator with Lambda, processing incoming requests, and handling responses, please consult the [AWS Lambda Integration](/agent-squad/cookbook/lambda/aws-lambda-python/) section in our documentation.

<br />

Expand Down Expand Up @@ -115,8 +115,8 @@ Yes, [Bedrock LLM Agent](/agent-squad/agents/built-in/bedrock-llm-agent) support

For practical examples of implementing tools with agents, refer to our documentation on:

- [Creating a Weather Agent with Custom Tools](/agent-squad/advanced-features/weather-tool-use)
- [Building a Math Agent using Tools](/agent-squad/advanced-features/math-tool-use)
- [Creating a Weather Agent with Custom Tools](/agent-squad/cookbook/tools/weather-api)
- [Building a Math Agent using Tools](/agent-squad/cookbook/tools/math-operations)

These guides demonstrate how to define tool specifications, implement handlers, and integrate tools into BedrockLLMAgent instances, helping you create powerful, domain-specific AI assistants.

Expand All @@ -139,7 +139,7 @@ This custom implementation was chosen because we wanted to have complete control

Yes, logging can be fully customized. While the orchestrator uses `console.log` by default, you can provide your own logger when initializing the orchestrator.

For detailed instructions on customizing logging, see our [Logging documentation](/agent-squad/advanced-features/logging).
For detailed instructions on customizing logging, see our [Logging documentation](/agent-squad/cookbook/monitoring/logging).


##### For a user intent, is there the possibility to execute multiple processing (so like multiple agents)?
Expand Down
2 changes: 1 addition & 1 deletion docs/src/content/docs/orchestrator/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -423,7 +423,7 @@ By understanding and customizing these behaviors, you can fine-tune your Agent S

- The `storage` option allows you to specify a custom storage mechanism. By default, it uses in-memory storage (`InMemoryChatStorage`), but you can implement your own storage solution or use built-in options like DynamoDB storage. For more information, see the [Storage section](/agent-squad/storage/overview).

- The `logger` option lets you provide a custom logger. If not specified, a default logger will be used. To learn how to implement a custom logger, check out [the logging section](/agent-squad/advanced-features/custom-logging).
- The `logger` option lets you provide a custom logger. If not specified, a default logger will be used. To learn how to implement a custom logger, check out [the logging section](/agent-squad/cookbook/monitoring/logging).

- The `classifier` option allows you to use a custom classifier for intent classification. If not provided, a `BedrockClassifier` will be used by default. For details on implementing a custom classifier, see the [Custom Classifiers](/agent-squad/classifiers/custom-classifier) documentation.

Expand Down