Three posts makes this a trilogy, and we all know how risky the third one is.
The last post ended with "Now I've started, I can't stop!" and then, evidently, I stopped. It's been a busy four months at Serene! Anyway. I promised to cover sequential execution and per-turn agents, and I will. But rather than stretch this into a series with a fourth part I'd have to promise and then deliver late again, I'm closing it off here. You get the promised bit, what held up, what I'd change, and where the framework has gone since we built on it.
If you're joining late, the earlier posts are on infrastructure and Aspire and building on the Microsoft Agent Framework.
Two agents, one queue
There's a question at the heart of any multi-agent system: do your agents run at the same time, or one after another?
The obvious answer is at the same time. Faster, more efficient, why make anything wait?
We went the other way. Every turn in MySerene runs two agents in a fixed order, every time. A
Discussion
Be the first to comment
Add your perspective to get the discussion started.