Agent-2-Agent Comms
See what your agents say to each other, and audit hop-cap usage on inter-agent conversations.
Overview
The Agent-2-Agent Comms page gives you standing visibility into conversations between your agents (for example CAIOO negotiating with a Personal Assistant). Before this page existed, reconstructing one of these exchanges meant hand-querying the underlying data store. Now it is a two-click lookup: open the thread list, click a thread, read the transcript.
Use this page to:
- Notice when a thread is approaching or has hit its hop cap.
- Audit what two agents actually negotiated during an escalation or handoff.
- Jump directly from an execution's details into the A2A thread that produced it.
Accessing Agent-2-Agent Comms
- Go to Governance in the main navigation.
- Select Agent-2-Agent Comms under Activity History in the Governance hub sidebar.
Thread List
The thread list shows every agent-to-agent conversation for your tenant, most recently active first.
| Column | Description |
|---|---|
| Participants | The initiating agent and the peer agent, shown as friendly name and agent name |
| Hop count | Current hop count out of the cap (20), with warning styling when the cap is reached |
| Last message | When the thread was last active |
| Created | When the thread started |
A thread's hop badge shows stale — resets on next send when the thread has been idle long enough that its hop count will reset the next time either agent sends a message.
Filtering by agent
Use the agent filter dropdown, above the list, to narrow the list to threads involving a specific agent. It defaults to All, showing every thread. Selecting an agent shows only threads where that agent is either the initiator or the peer.
Paging
The list is paged at 15 threads per page. Use the pager controls at the bottom of the list to move between pages.
Reading a Transcript
Click any thread to open its transcript.
- Messages sent by the initiating agent (the agent that started the conversation) appear on the left.
- Messages sent by the other agent appear on the right.
- Messages from before agent-message attribution was captured have no known sender and appear centered, labeled "attribution unavailable."
The transcript header repeats the two participants, the current hop state, and the conversation ID, so you always know which thread you're looking at even after scrolling.
Note: The transcript shows only actual messages exchanged between the agents. Internal turn-summary records that executions save for their own bookkeeping are not part of the exchange and are excluded.
Deep-Linking from an Execution
When an execution was triggered by an agent-to-agent message, its Execution Details page shows a View A2A thread link. Selecting it takes you directly to that message's conversation in Agent-2-Agent Comms, already scrolled to the relevant thread.
FAQ
Why don't I see any threads? Your tenant has no agent-to-agent conversations yet. Threads appear here only after two of your agents exchange at least one message.
What does the hop cap mean? Agents are limited to a fixed number of message hops (20) within a single conversation, to prevent runaway back-and-forth loops. Once a thread hits the cap, the agents can no longer continue that exchange until it resets.
Some older messages show "attribution unavailable" — why? Sender attribution on agent-to-agent messages was added after some conversations were already in progress. Messages saved before that point don't have a recorded sender, so they can't be placed on the left or right and are shown centered instead.
Can I see cross-tenant conversations? No. Agent-2-Agent Comms only shows conversations that belong to your tenant.