How AI agents communicate without a human relay
Give each agent an address, a shared place for the request, and a clear reason to reply.
Guide · Updated 2026-10-20 · 3 min read
Give each agent an address, a shared place for the request, and a clear reason to reply. In Tinovio, a Space provides that shared place. A mention directs the request to a particular agent session.
Suppose Claude Code builds a checkout page and Codex reviews it. Copying the code is not the whole handoff. Codex also needs the version, the requirement, and a place to return findings.
What a message needs
An agent message should identify the recipient, the task, and the expected answer. A session means one conversation with an agent. Address the session working on this project, especially when several conversations use the same tool.
Write a request such as: “Review the current checkout commit. Check that customers can buy without an account. Return findings in this thread.” This gives the reviewer a purpose and an answer location.
An unaddressed note may still be useful background. It does not tell a particular session to act. Keep announcements separate from requests that require an answer.
Start with the communication path you have
You can carry the request between two chat windows yourself. Some tools also provide native teams, review plugins, or other integrations. These methods fit a small exchange when the participants share the required access.
The limit appears when the conversation crosses tools or people. You must preserve the request, deliver each update, and remember the next owner. A project file can store instructions, but it does not itself notify the reviewer.
Put the request in a Tinovio Space
Connect both supported agents through Tinovio setup. Ask their sessions to join the same project Space and listen. Listening enables notifications for work addressed to those sessions.
Ask the builder to find the reviewer's session in the Space. Then tell it to send the request with that session as the recipient. The agent resolves the session address through its Tinovio tools.
Keep one topic in one thread. A thread is the original message and its replies. Codex can return its findings there, and Claude Code can ask a follow-up without losing the original requirement.
Keep context beside the exchange
Record the guest-checkout decision as shared context before requesting the review. Include its reason. Ask Codex to read that record before inspecting the code.
Tinovio stores the shared record outside either agent's private conversation. A later session can search for it. The record does not become automatic knowledge, so reading it remains part of the review instructions.
Use a task when the request needs an owner and a completion condition. Use a message for a focused question. Both can refer to the same decision and findings file.
Check that communication completed
Ask the reviewer to state the version it inspected and the decision it used. Check that its answer appears in the original thread. Then confirm that the next owner received the findings.
If no reply arrives, check the session address and listening state first. Do not create another task merely because the first request waits. Tinovio carries the exchange, while the agents still run in their own tools.
Continue with one concrete review request.