Type
agent_communicationVariants
Read Only, Limited, Full Orchestration
Common Use Cases
Delegating to specialist agentsRoute tasks to agents with specific expertise or capabilities
Orchestrating multi-agent workflowsCoordinate complex workflows across multiple specialized agents
Calling team-based executionsExecute tasks using team agents with shared capabilities
Session continuationResume or extend existing agent sessions
Variants Overview
Configuration
Example Configuration:π Full Configuration Reference
π Full Configuration Reference
βοΈ Variant-Specific Defaults
βοΈ Variant-Specific Defaults
Read Only:
allowed_operations: [βget_execution_statusβ] (locked)- No execution capability
max_execution_depth: 2 (recommended)- Requires whitelist configuration
max_concurrent_calls: 3
allowed_operations: [β*β] (all operations)allowed_agents: [β*β] (all agents)max_execution_depth: 5max_concurrent_calls: 10
Quick Start
View Complete Examples
See full orchestration patterns, deployment workflows, and multi-agent coordination examples
Agent Execution Examples
Single Agent Call
Orchestrator Request:Sequential Execution
Orchestrator Request:Team Execution
Orchestrator Request:Security Features
Circular Call DetectionPrevents infinite loops where agents call each other recursively
Execution Depth LimitingLimits how deep agent call chains can go
Whitelist-based AccessOnly allows calling explicitly permitted agents and teams
Concurrent LimitsPrevents resource exhaustion by limiting parallel calls
Best Practices
Use Whitelisting
Use Whitelisting
Always specify
allowed_agents rather than using β*β wildcards.Set Reasonable Depth Limits
Set Reasonable Depth Limits
Keep
max_execution_depth low (2-3) to prevent complex call chains.Limit Concurrent Calls
Limit Concurrent Calls
Configure
max_concurrent_calls to prevent resource exhaustion.Troubleshooting & Related Skills
Agent Execution Blocked
Agent Execution Blocked
Solutions:
- Verify agent ID is in
allowed_agentslist - Check
execute_agentis inallowed_operations - Confirm target agent exists and is enabled
Execution Depth Exceeded
Execution Depth Exceeded
Solutions:
- Increase
max_execution_depthif appropriate - Restructure orchestration to reduce call chain depth
- Consider using workflow executor for complex chains
Circular Dependency Detected
Circular Dependency Detected
Solutions:
- Review agent call chain for circular references
- Restructure orchestration logic to avoid loops
- Use different agents for different stages
Related Skills
Workflow Executor
Alternative for complex multi-step workflows
Contextual Awareness
Share context between orchestrated agents
Knowledge API
Agents can share knowledge base access
View All Skills
Return to built-in skills overview