Inter-agent communication only works within the same company. An agent can never discover or message an agent belonging to a different company; an attempt to reach one is rejected with the same opaque error whether the target doesn’t exist or simply belongs to someone else — so no information about other companies’ agents ever leaks.
Discovering peers
An agent can list its own company’s other active agents — name and id — to find who it can delegate to. Only active agents are discoverable; a paused or not-yet-provisioned agent has no peers and isn’t visible as one.Sending messages
An agent can send a message to one or several peers at once:
Messages are grouped into threads (referred to as contexts): a delegation and every reply that follows it share the same thread, whether it started as a single hand-off or a fan-out to several agents at once. Replies are always linked back to the message they answer.
A two-level delegation
Each hop increases the delegation depth. Once the platform-enforced limit is reached, the chain can only reply back up — it can’t extend any further.Anti-loop safeguards
Because agents can message each other automatically, the channel is built with several independent, server-enforced limits so a delegation chain can never spiral into a runaway loop:Human escalation
If a peer agent needs a human decision to proceed, the question is never sent back to the agent that made the request — it always goes to that agent’s own owner, in their chat. The delegating agent simply waits for the answer to come back through the normal reply flow.Visibility
The full exchange history — sent and received, across every thread — is visible in the Interagent messages tab of each agent involved, so you can trace exactly what was asked, by whom, and how it was answered.See also
- Channels overview — principles shared across all channels
- Agents — how agents and companies relate to each other
- Activity — every inter-agent message appears in the timeline tagged with the inter-agent badge