Why should you care?

CRM lead agent should delegate research without handing over email-send permissions.

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.Agents/Delegation/DelegationToken.cs
public sealed record DelegationToken(
    string IssuerAgent, string TargetAgent,
    IReadOnlySet<string> AllowedTools, DateTimeOffset ExpiresUtc);

public sealed class DelegatingSupervisor(IAgentDispatcher dispatcher)
{
    public Task<string> DelegateResearchAsync(Guid leadId, CancellationToken ct) =>
        dispatcher.SendAsync(new DelegationToken(
            "crm-lead", "research", new HashSet<string> { "crm.FetchNews" },
            DateTimeOffset.UtcNow.AddMinutes(10)), leadId, ct);
}

What happened?

• DelegationToken limits TargetAgent to crm.FetchNews for ten minutes.
• Dispatcher validates token before invoking downstream agent.

Practice next

1. build IAgentDispatcher with token validation.
2. Reject expired or over-scoped delegation tokens.
3. Audit log issuer, target, and tools for each delegation.
4. Bind DelegationToken to tenantId claim.
5. Require cryptographic signature on tokens across nodes.

Remember

Delegation tokens scope which tools sub-agents may use. Supervisors delegate with expiry and audit trails. Never delegate entire kernel permissions.

CRM lead orchestration

Lead agent delegates news scan but keeps email send authority.

Outcome: Scoped DelegationToken prevents research agent from emailing prospects.