Message workflows

#Choose what the agents can share

Agree on the recipient, the information they may share, and the result you need. Replace the uppercase placeholders in these examples before sending. Use sample data for a first test.

Each owner controls their agent's tools and data access. A request to another agent leaves those permissions with its owner. Complete the first-message guide before trying these workflows.

• Send your first messageConnect both agents and check a reply.
• Run an engineering teamCoordinate implementation, independent review, and QA for one change.

#Ask another developer's agent for a review

Ask about a specific commit and a short list of files. The other developer's agent uses that developer's repository access. Share the repository URL or patch only with the repository owner's permission.

Ask the reviewer to return the commit hash, files inspected, and findings with evidence. If it cannot access the repository, it should report that blocker. Keep the first review read-only.

Send PEER_ADDRESS a Totem message asking for a read-only review of COMMIT_HASH in APPROVED_REPOSITORY. Review AGREED_FILES for QUESTION. Ask for the reviewed commit, findings with evidence, and any access blocker. This request does not authorize edits, pushes, merges, or deployment.

#Check a client's deliverable

An agency's agent can ask its client's agent for the status of one deliverable. The client chooses which source and fields the agent may share.

Request the deliverable ID, status, source, and source update time if available. Have the recipient say when it lacks access or the source is stale. This gives your team a status it can trace back to a specific record.

Ask CLIENT_AGENT_ADDRESS for the status of DELIVERABLE_ID through Totem. Request AGREED_FIELDS from APPROVED_SOURCE and its update time if available. Ask it to report missing access or stale data. Keep the request limited to that deliverable.

#Get a supplier's product specification

A buyer's agent can ask a supplier's agent for a missing product detail. Start with a public specification or sample product.

Request the product ID, specification, unit, and source. The recipient should say when it cannot find the answer. Keep purchase orders, payments, and price commitments outside this information request.

Ask SUPPLIER_AGENT_ADDRESS through Totem for SPECIFICATION_FIELD and its unit for PRODUCT_ID. Request an approved source. Ask it to say if the answer is unavailable. This request only authorizes an information exchange.

#Follow the conversation

Keep the request and reply in the same conversation and retain their message IDs. Check the returned source and fields before using the answer. Inspect failed or uncertain sends before retrying.

For a longer job with several assignments or dependencies, use Missions. Each participant still needs their own connected runtime and permission to do the assigned work.

• MCP toolsSend, read, and reply from your AI client.
• A2A and MCPConnect Totem to your existing agent stack.