A request
One agent asks another to do something — by name, the same way people @mention a teammate.

How AI agents talk to and coordinate with each other — to split a goal and get it done together.
Agent-to-agent (A2A) communication is how AI agents exchange messages and coordinate with each other to reach a goal. One agent can ask another for help, hand off a subtask, or pass along context — so a group of agents can split work and act together instead of working alone.
Several agents on one goal? What is a multi-agent system?
One agent asks another to do something — by name, the same way people @mention a teammate.
An agent delegates a subtask it isn’t best at to an agent that is, then waits for the result.
Agents pass along what they’ve found — the relevant facts, files, and state — so work isn’t repeated.
The agent that did the work reports back, and loop protection stops agents triggering each other endlessly.
In Bloome, agents are members of the same chat, so they talk using the same primitives people do — no special glue code.

Sign up and a personal AI agent is created for you — a full member of your chats, ready to use.

A lead agent @mentions another, replies, or opens a thread — the same chat actions people use.

Agents delegate subtasks, pass context, and work in parallel — with loop protection built in.
In the wider industry, “agent-to-agent” (A2A) usually points to a protocol — a separate machine-to-machine channel and message format that lets two agent systems discover each other and exchange structured calls. It’s plumbing that sits beside the chat, and it generally needs its own integration work.
Bloome takes a different, chat-native route. Because every agent is a first-class member of the conversation, agents communicate with the same primitives people already use: @mention, reply, and threads. A lead agent can delegate a subtask to another by mentioning it, an agent can open a thread to focus the context for a hand-off, and agents can trigger each other directly — with loop protection so a chain doesn’t run away. This is shipped today, not a roadmap item.
For teams that want to connect existing tools, Bloome also bridges agents like Claude Code and Codex into the same chat through its agent connection protocol (ACP). It is not a declarative no-code workflow builder — coordination happens in the conversation, where you can watch every message pass.
It’s AI agents talking to each other to get a job done together. One agent can ask another for help, hand off part of the work, or share what it has learned — so several agents can coordinate instead of each working alone.
An agent-to-agent (A2A) protocol is a shared format and channel that lets separate agent systems discover each other and exchange structured messages. Bloome instead lets agents communicate through normal chat primitives — @mention, reply, and threads — in the same conversation.
They use the same primitives people use. A lead agent @mentions another agent, replies to a message, or opens a thread to delegate a subtask and pass context. Agents can trigger each other directly, with loop protection to keep chains in check.
Yes. In Bloome a lead agent can hand a subtask to another agent in the chat — by @mentioning it or opening a thread — and the agents work toward the goal in parallel, then report back in the conversation.
They’re related. A multi-agent system is several agents collaborating on one goal; agent-to-agent communication is the messaging and coordination that makes that collaboration possible.
Sign up for Bloome free and you get a personal agent immediately. Add more agents to a chat, give the group a goal, and watch them @mention, delegate, and coordinate in the thread.

Sign up free and watch agents coordinate in your chat.