Portal Community

AgentTeam Model

public class AgentTeam
{
    public Guid Id { get; init; }
    public string Name { get; set; }               // "Enterprise Support Team"
    public string TenantId { get; init; }
    public Guid OrchestratorAgentId { get; set; }  // the routing agent
    public Guid DefaultAgentId { get; set; }        // fallback when routing fails
    public RoutingConfig RoutingConfig { get; set; }
    public List<TeamMember> Members { get; set; }
}

public class TeamMember
{
    public Guid AgentId { get; set; }
    public AgentCapabilityDeclaration Capabilities { get; set; }
    public float[] IntentEmbedding { get; set; }    // pre-computed embedding of intent examples
    public int RoutingPriority { get; set; }         // lower = higher priority when scores are tied
}

public class RoutingConfig
{
    public RoutingStrategy Strategy { get; set; }
    public float ConfidenceThreshold { get; set; }   // below this, go to DefaultAgent
    public int MaxHandoffHistoryMessages { get; set; }
    public bool AllowParallelExecution { get; set; }
    public bool ShowHandoffIndicatorInUI { get; set; }
}

Creating a Team in agents-app

1

Create Specialist Agents

Create each specialist agent (HR, Finance, IT, etc.) with their system prompts, tools, and knowledge bases. Set capability declarations for each.

2

Create Orchestrator Agent

Create the orchestrator agent with a routing-focused system prompt. This agent will receive all initial user messages.

3

Create the Team

In agents-app → Teams → New Team. Set the orchestrator, default agent, and routing strategy.

4

Add Team Members

Add each specialist as a team member. Set routing priority and verify intent examples are populated.

5

Test Routing

Use the Team Routing Test panel in agents-app to send test messages and verify each routes to the correct specialist.

Team-Level Permissions

Team membership controls which users see the team's orchestrator in their chat. Users with access to the team's orchestrator agent get the full multi-agent experience. Users can be granted access to individual specialists directly (bypassing the orchestrator) if they are power users who know which agent to use.