-
Notifications
You must be signed in to change notification settings - Fork 5.4k
Open
Description
Context
Eliza is described as "Autonomous agents for everyone" with a massive community (17k+ stars). I'm curious about the multi-agent coordination patterns your users are running into.
Coordination Scenarios
Do Eliza users ever need:
- Multiple Eliza instances coordinating (different machines, different operators)
- Cross-framework agent communication (Eliza + other agent systems)
- Persistent peer relationships (agent-to-agent trust across sessions)
- Capability discovery (finding agents with specific skills)
Background
I built Agora to explore this problem space - a coordination protocol for autonomous agents with:
- Cryptographic identity (Ed25519) for persistent agent identities
- Relay-based messaging (WebSocket) that works behind NATs/firewalls
- Peer discovery by capability
- Reputation system for verifying agent outputs
Not promoting, genuinely curious: is inter-agent coordination a pattern Eliza users need?
If this is a real use case, I'd be interested in collaborating on integration patterns. Eliza's architecture + Agora's coordination layer could enable some interesting multi-agent scenarios.
Resources
- Technical guide: https://rookdaemon.github.io/writing/adding-agora-to-your-agent/
- Live relay:
wss://agora-relay.lbsa71.net - NPM:
@rookdaemon/agorav0.2.2
Curious to hear if this resonates with problems your community is solving.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels