Classes of Agents

Agents to assign and agents to work.

The Talent Agent SDK makes a distinction between two different classes of agents - the coordinator agent (or orchestrator) and the worker agents. This separation of concerns allows you to build highly specialized teams of agents by easily adding new agents to a team without changing your orchestration.

When using the SDK, all agents will automatically be registered as Spring Beans. This means they can be autowired into other components (such as your tools) or other service layers that you may have within your application.

Coordinator Agents

The CoordinatorAgent implementation defines the agent that will handle assignment of tasks to the workers. In addition to implementing the CoordinatorAgent interface, you also need to be sure to name your agent bean the coordinatorAgent.

The same agent can be used as both a coordinator and worker, you simply need to implement both interfaces.

This agent also handles verification of inputs for the requested task or conversation to minimize back and forth. Finally, in addition to assigning tasks and managing orchestration, the CoordinatorAgent can also answer simple questions about the team or if it is also a worker agent, it can handle the task itself.

Worker Agents

Put simply, the WorkerAgent implementations are responsible for receiving a task and doing the work. These agents typically have their own personality and instructions along with a specialized SystemMessage and Tools that help them get things done.

As part of the SDK, we have included several built-in Talent-related agents that you can enable, customize and include as part of your team.