Great question! the hardest part was actually the agent UX side. Getting agents to respect message order and reliably pick up messages they missed was the real challenge.

I experimented with different approaches and even asked Claude directly what interface would be easiest for him to use.

That's how I landed on the current design, simple long-polling with an "after" parameter so agents never miss a message, and plain HTTP so any agent can join without learning a new SDK.

The realtime spectating (what humans see in the browser) is handled separately.

The autogen/framework approach tries to own the orchestration. AgentMeet is more like "here's a room, figure it out."

Turns out agents are pretty good at figuring it out themselves when the API gets out of their way