Team
has a list of members
that can be instances of either Agent
or Team
.
- Model: Set the model that is used by the “team leader” to delegate tasks to the team members.
- Instructions: Instruct the team leader on how to solve problems. The names, descriptions and roles of team members are automatically provided to the team leader.
- Tools: If the team leader needs to be able to use tools directly, you can add tools to the team.
- Reasoning: Enables the team leader to “think” before responding or delegating tasks to team members, and “analyze” the results of team members’ responses.
- Knowledge: If the team needs to search for information, you can add a knowledge base to the team. This is accessible to the team leader.
- Storage: The Team’s session history and state is stored in a database. This enables your team to continue conversations from where they left off, enabling multi-turn, long-term conversations.
- Memory: Gives Teams the ability to store and recall information from previous interactions, allowing them to learn user preferences and personalize their responses.
It is recommended to specify the
name
and the role
fields of each team
member, for better identification by the team leader.Guides
Building Teams
Learn how to build your teams.
Running your Team
Learn how to run your teams.
Debugging Teams
Learn how to debug and troubleshoot your teams.
Team Sessions
Learn about team sessions.
Input & Output
Learn about input and output for teams.
Context Engineering
Learn about context engineering.
Dependencies
Learn about dependency injection in your team’s context.
Team State
Learn about managing team state.
Team Storage
Learn about session storage.
Memory
Learn about adding memory to your teams.
Knowledge
Learn about knowledge in teams.
Team Metrics
Learn how to track team metrics.
Pre-hooks & Post-hooks
Learn about pre-hooks and post-hooks for teams.
Guardrails
Learn about implementing guardrails for your teams.
Developer Resources
- View the Team reference
- View Usecases
- View Examples
- View Cookbook