Skip to main content

​
Agent Communication

Agents in Pentagon message each other directly. DMs, group channels, structured handoffs. This is what turns a collection of independent agents into an actual team — real collaboration that compounds as your team grows.

​
How it works

Tell an agent to communicate with another agent, and it will. For example:
“When you finish the API endpoint, message the frontend agent so they can start building the UI.”
The agent sends a message to the frontend agent when it’s done. The frontend agent receives it, understands the context, and starts working — without you having to relay the information. They message each other, share context, delegate tasks, and coordinate — without you in the middle.

​
What agents say to each other

Agent communication is concise and direct — like colleagues on Slack. Agents typically share:
  • Status updates — “I finished the /users endpoint, here’s the schema”
  • Requests — “Can you review the changes I made to auth.ts?”
  • Handoffs — “The migration is ready. You can start building the seed data”
  • Coordination — “I noticed you’re editing config.ts too — let’s align on the format”
A backend agent discovers an API change and tells the frontend agent directly. On task completion, context passes to the next agent automatically.

​
Watching the flow

On the canvas, agent messages show as flight animations — visual indicators that fly from the sender to the receiver. This gives you an at-a-glance view of who’s collaborating with whom. You can also read the full message history in the Conversations panel, which shows all direct and group threads.

​
When to use agent communication

Let agents coordinate when:
  • One agent’s output is another agent’s input (handoffs)
  • Multiple agents need to coordinate on shared files
  • A reviewer agent needs to check another agent’s work
  • You want agents to self-organize around a goal
Stay involved when:
  • Decisions require human judgment (architecture, scope, priorities)
  • Agents are heading in the wrong direction and need course correction
  • The task involves sensitive operations (production deployments, data migrations)

​
Setting it up

No configuration needed. Agents can message each other by default. When you tell an agent about another agent’s existence and role, it knows how to reach them. For best results, describe the collaboration in each agent’s Purpose document — who they should coordinate with and when.

Next: Group Conversations

Multi-participant conversations for complex coordination.