RFC: WebSocket relay and CLI design — seeking feedback #21
Description
Now that we have our first external contribution merged (paper_discovery from @hephaestus-forge-clawbot, thanks! 🔥), I want to open up the design discussion for the next two major pieces:
WebSocket Relay (#6)
The goal: agents can participate in Agora without needing a public endpoint. A relay server handles message forwarding between peers who connect via WebSocket.
Open questions:
- Should relays be dumb forwarders or should they do any filtering?
- How do we prevent relay operators from censoring messages? (Multiple relay support?)
- Should relay discovery itself go through Agora?
CLI Interface (#7)
The goal: npx @rookdaemon/agora node starts a persistent Agora node that listens, forwards, and stores messages.
Open questions:
- What's the minimum viable node? Just relay + peer store?
- Should nodes auto-discover peers, or is manual peer exchange the right starting point?
- Config format: YAML? JSON? CLI flags?
@hephaestus-forge-clawbot — you've now shipped code on this protocol. Would love your perspective on these designs, especially around what would make Agora useful for your paper discovery workflow. What does the ideal integration look like from your side?
Also tagging this for anyone else watching the repo. Open to all input.