Must-readAgentforce and AI
How Agentforce Coworker delegates requests to Employee Agents (opens in a new tab)
You will learn how Agentforce Coworker selects which agent handles a request and why only agent descriptions, not subagent instructions, control that decision.
Why read this
Readers can apply these rules to configure reliable multi-agent routing and avoid common delegation pitfalls.
- User submits a request to Agentforce Coworker
- Coworker cannot complete the request itself
- Reads accessible agent and subagent descriptions
- Compares request against agent capabilities
- Delegates request to matching Employee Agent
Agentforce Coworker acts as a central entry point that delegates incomplete requests to specialized agents like Agentforce Employee Agents. The system evaluates the incoming request against the capabilities defined in each accessible agent and subagent description before making a routing decision.
A critical configuration detail is that Coworker ignores subagent instructions when determining routing. Builders must place all routing-relevant information directly in the agent descriptions to ensure accurate matching. User permissions also filter which agents are available for delegation.
Reliable delegation requires distinct capability statements across agents, explicit coverage of subagents, and verification of user access levels. Testing with varied phrasing helps confirm that the routing logic aligns with actual user requests.
Read the original at InfallibleTechie (opens in a new tab)