Skip to main content

N-to-N Topology

Most multi-agent systems are hub-and-spoke: one leader, many workers. connector.json supports full mesh — any agent talks to any agent.

Topologies

Why Full Mesh Matters

In a hub-and-spoke system:
In full mesh:

The Spec

Four agents. No leader. Each owns a domain. They coordinate directly.

How N2N Works

No orchestrator needed for routine communication. Agents self-organize around the task.

Broadcast Channel

Any agent can send to all:

Observer Mode

The main session (you) can observe the entire mesh without participating:
You see everything. You can inject commands to any agent or broadcast to all. But you don’t have to — the mesh self-organizes.

Mesh + Hierarchy

Full mesh doesn’t mean no structure. Agents can have specializations and natural leadership:
Everyone talks to everyone. But when there’s disagreement, it escalates to the lead. Natural hierarchy emerges from rules, not from wiring.

N2N + Cross-Machine

Full mesh across multiple machines:
Frontend and QA on laptop. Backend and DevOps on server. Full mesh communication across machines via gateway relay. Every agent can message every other agent regardless of location.

The Topology Spectrum

connector.json supports all topologies: