Member-only story
Multi-Agent Workflows in .NET 10 with Microsoft Agent Framework
Typed executors, switch-edge routing, a deterministic reply guard, and offline tests: a support-triage workflow that keeps LLMs out of the control flow.
A pattern I keep running into in multi-agent demos: a “router agent” whose system prompt says decide which specialist should answer, then call it. It works in the demo. Then one day it promises a customer a $480 refund, and nobody can say which “agent” made that call, or why.
The fix isn’t a better prompt. It’s taking control flow away from the model.
That’s what the workflow half of Microsoft Agent Framework is for. Microsoft.Agents.AI.Workflows 1.24.0 (on NuGet since October 7, 2026) gives you a typed graph: executors that take and return real C# types, edges that decide where messages go, and an event stream that tells you what happened. Agents are still in there. They just don't get to decide which step runs next.
Tech Skill Builder is $5/month for a very limited time only (normally $10). Grab it now before it goes back to $10. The full source for this workflow (solution, tests, PDF guide) is in Tech Skill Builder.
