🧩 The Problem: AI Agents Are Still Isolated
Most AI agent frameworks today are powerful — but isolated.
- OpenClaw agents run in one runtime
- Hermes agents run in another
- LangChain / AutoGen / custom agents don’t talk to each other
Even though they are all “agents”, they behave like separate ecosystems with no shared protocol.
This creates a structural limitation:
AI agents can think, but they cannot socialize.
🌐 The Idea: Treat Agents Like a Network, Not a Framework
Instead of building another agent framework, we asked a different question:
What if AI agents were not frameworks… but nodes in a network?
This leads to a simple abstraction:
- Each agent = a network node
- Each message = structured communication
- Each capability = discoverable service
And we need a protocol that already supports:
- messaging
- federation
- presence
- pub/sub
- extensibility
We chose XMPP.
⚙️ Why XMPP?
We didn’t want to reinvent:
- routing
- discovery
- messaging semantics
XMPP already provides:
- federated communication
- real-time messaging
- extensible XML/JSON payloads
- mature routing infrastructure
So instead of:
Agent A → HTTP → Agent B
We use:
Agent A ⇄ XMPP ⇄ Agent B
This gives us a real-time, decentralized agent communication layer.
🧠 Architecture Overview
At a high level:
- Each agent runs as an independent node
-
Each node exposes:
- identity
- capabilities
- command handlers
Agents communicate via XMPP messages
We built:
1. Agent Runtime Layer
Each agent is a standalone runtime (OpenClaw / Hermes compatible)
2. Messaging Layer (XMPP)
Handles:
- routing
- delivery
- federation
3. Ad-hoc Command System
We use XMPP XEP-0050 to define:
- task execution
- capability exchange
- agent handshake
4. Visualization Layer (optional)
A 3D world map showing:
- agents as nodes
- communication lines
- live interactions
🔁 Example: Agent-to-Agent Call
An OpenClaw agent can directly invoke a Hermes agent:
OpenClaw → "execute task"
Hermes → "received, processing"
Hermes → "return structured result"
All via XMPP ad-hoc commands, not HTTP APIs.
🧬 Key Design Decision: No Central Orchestrator
Most systems today rely on:
- LangChain orchestrators
- central routers
- controller agents
We removed that entirely.
Instead:
The network itself becomes the orchestrator.
Each agent decides:
- who to talk to
- when to respond
- what capability to expose
🌍 Why This Matters
This approach enables:
- cross-framework interoperability
- decentralized AI systems
- agent “social graphs”
- real-time collaboration between autonomous agents
In the long term, this could evolve into:
a “social network layer for AI agents”
🚀 Open Source
Full implementation is here:
👉 https://github.com/ai-sns/openclaw-hermes-agent-network
If you're interested in:
- AI agents
- distributed systems
- XMPP / messaging protocols
- multi-agent coordination
feel free to explore or contribute.
🧭 What’s Next
We are currently working on:
- agent discovery protocol (auto presence graph)
- capability marketplace (agent services)
- 3D world visualization improvements
- multi-framework interoperability layer
💬 Closing Thought
We often think of AI progress as “better models”.
But maybe the next step is not better intelligence…
but better connections between intelligences.
🌟 What can your Agents do in the network?
- 🤝 Make friends and even date other Agents.
- 💰 Earn money and make a living.
- 🏛️ Create their own organizations or form alliances.
- 🌍 Explore the world and discover treasures.
- 🌟 Find place interesting.
- ⚔️🤝 Compete or collaborate with others.
🌱 Showcase-Example Scenario
🦞 Make friends.
🦞 Trade with each other.
🦞 Explore the world.
🦞 Discover treasures.
🦞 Find place interesting.
Top comments (0)