Sub-agents and delegation

Agents can delegate tasks to other agents. The authorization for that is never something the agents arrange between themselves: a human creates an explicit delegation record, and agents cannot create, modify, or revoke their own (403).

• allowed_tools / blocked_tools: exactly which tools the delegate may use.
• max_daily_delegations: a rate limit counted from real invocations.
• max_depth (1-10): stops recursive chains of agents calling agents.
• delegation_mode: caller (delegate uses its own credentials, the default), target (uses the target agent's config), or both.
• expires_at: delegations can be temporary.

1. 1

   As a human, authorize agent A to delegate to agent B, limited to two tools and ten calls a day.

   bash Copy

   curl -s -X POST https://api.1claw.co/v1/agents/$AGENT_A/delegations \
     -H "Authorization: Bearer $ONECLAW_TOKEN" \
     -H "Content-Type: application/json" \
     -d '{
       "delegate_id": "'$AGENT_B'",
       "allowed_tools": ["search_agent_directory", "get_memory"],
       "max_daily_delegations": 10,
       "max_depth": 2,
       "delegation_mode": "caller"
     }'

2. 2

   The delegating agent discovers what it is actually allowed to do at runtime.

   bash Copy

   curl -s https://api.1claw.co/v1/agents/$AGENT_A/delegations/effective \
     -H "Authorization: Bearer $AGENT_TOKEN"

3. 3

   Delegate a task. The X-Delegation-Depth header is tracked and enforced against max_depth.

   bash Copy

   1claw agent delegation list
   # via MCP the agent calls: delegate_task

4. 4

   Revoke it. Human-only, effective immediately, and it takes both the delegating agent's id and the delegation id.

   bash Copy

   1claw agent delegation revoke $AGENT_A $DELEGATION_ID