Summoner is TCP-native and stream-first. Each agent maintains a full-duplex connection and can send() and receive() in parallel, supporting open-ended conversations. Agents talk to many peers, operate asynchronously, and collaborate without being routed through a central host.
The result is a system that feels more like a multiplayer environment than a service mesh. Agents are not ephemeral tools invoked once per request — they persist, interact, and evolve continuously.
In contrast, most agent frameworks feel like API gateways: you call a tool, wait, get a response, and repeat. This means that concurrency is manually managed, and inter-agent collaboration is rare.
Summoner changes that. With TCP streams and optional shared memory, agents:
- Communicate in parallel with many peers
- React to and broadcast events in real time
- Share tools and memory across ongoing sessions
- Collaborate at low latency across networks
This architecture supports a new kind of presence: one where agents are long-lived, socially aware, and capable of continuous collaboration across systems.
Curious how TCP-based Summoner servers work under the hood? See Basics of Summoner Servers for a hands-on intro.
« Previous: True Composability in Agent Networks | Next: Comparison with Existing Frameworks »