Why should you care?

Advanced customers want researcher + writer + reviewer teams like internal AgentNest engineering patterns, configurable in UI.

See it live — copy this example

Paste into an ASP.NET Core 8+ / AgentNest project, then run with dotnet run (set your API keys in user-secrets).

// AgentNest.MultiAgent/ConfiguredSupervisorHost.cs
public sealed class ConfiguredSupervisorHost(IAgentTeamLoader teams, IAgentDispatcher dispatcher)
{
    public async Task<TeamResult> RunTeamAsync(string teamId, AgentRequest request, CancellationToken ct)
    {
        var team = teams.Load(teamId);
        object? handoff = request;
        foreach (var member in team.Members)
        {
            handoff = await dispatcher.InvokeAsync(member.AgentName, member.AllowedTools, handoff!, ct);
        }
        return new TeamResult(teamId, handoff);
    }
}

What happened?

• ConfiguredSupervisorHost loads team JSON definition and chains agents via dispatcher with per-member tool scopes — platformized multi-agent pattern.
• Follow the steps below — typing the code yourself is the fastest way to learn.

Practice next

1. Define agent team schema in SQL with ordered members.
2. Build admin UI to assign CrmResearch + CrmWriter + CrmReviewer chain.
3. Meter TeamResult runs separately from single-agent calls.
4. Parallel member stage when team graph defines fork join.
5. Team template marketplace for common CRM and ERP patterns.

Remember

Multi-agent platform runs configured agent chains with scoped tools. Load team definitions from SQL admin UI. Reuse dispatcher and delegation infrastructure.

Proposal quality team

Customer configures research, draft, compliance review agent chain for RFP responses.

Outcome: ConfiguredSupervisorHost runs nightly; compliance agent blocks unsourced pricing claims.