peer-collab

Configure direct peer-to-peer messaging by adding each agent's ID to the other's config.json peers list. Both agents must run in the same mission to exchange messages directly via the file bus.

Direct peer-to-peer messaging bypasses the orchestrator by using the zeus bus send-message command. This enables fast back-and-forth coordination between two roles, such as frontend and backend during API contract negotiations.

Use direct peer messaging for tight back-and-forth coordination between two roles, like design reviews or cross-role handoffs. It provides low-latency communication by skipping the orchestrator round-trip via the file bus.

Yes, ZEUS_PEERS must be configured. You declare peers in each agent's config.json, which surfaces them as ZEUS_PEERS and enables targeted private conversations over the Zeus file bus.

Peer-to-peer messages are sent using zeus bus send-message and are received by the target agent on its next inbox check. This polling mechanism allows asynchronous communication between agents.

Yes, peer collaboration is designed for workflow scenarios within a single mission. It supports cross-role handoffs and tight coordination between two configured agents operating in that mission.