communicate

Agent cross-repo coordination routes requests by sending in-mesh channel messages and cross-repo GitHub issue briefs with consistent context. This prevents coordination breakdowns by letting you send self-contained requests to other agents for tracked async hand-offs or real-time pings.

Inbound state reading fetches issue bodies and comments to inline current state before writing briefs or plans. This GitHub issue fetching for planning and triage avoids ambiguity by ensuring the receiving agent gets full context instead of a reference to issue numbers.

Cross-repo hand-offs use tracked GitHub issue threads to create an audit trail between sibling-repo agents. Posting new issues and replying to existing ones with full acceptance criteria ensures the receiving agent can act immediately with durable, signed context.

In-mesh coordination uses channel messages for quick status pings and fast questions where a tracked artifact isn't needed. Use GitHub issues for durable async hand-offs requiring an audit trail, and use mesh messages for ephemeral coordination that needs no persistent record.

Yes, agent communication requires the culture channel message for mesh routing and agtag issue post, reply, and fetch operations for GitHub. These dependencies enforce safe argument parsing and signature conventions to maintain consistent context across cross-repo coordination.