I have a repository here with similar examples across all those frameworks: https://github.com/Azure-Samples/python-ai-agent-frameworks-...
I started comparing their features in more details in a gist, but it's WIP: https://gist.github.com/pamelafox/c6318cb5d367731ce7ec01340e...
I can flesh that out if it's helpful. I find it fascinating to see where agent frameworks converge and diverge. Generally, the frameworks are converging, which is great for developers, since we can learn a concept in one framework and apply it to another, but there are definitely differences as you get into the edge cases and production-level sophistication.
> It brings together and extends ideas from Semantic Kernel and AutoGen projects, combining their strengths while adding new capabilities
… and giving a hint what will happen to the aforementioned projects.
—
It’s a shame when someone’s promotion is tied to how many new things they ship.
—
> To learn more about migrating from either Semantic Kernel or AutoGen, see the Migration Guide from Semantic Kernel and Migration Guide from AutoGen.
It seems the motto of Microsoft for the last 15 years: “You won’t have time for new features — all you’ll do is migrations.”
You can also expose the agents as MCP, AGUI and so it can be a tool you integrate with other AI platforms.
If you use it with OpenAI responses api, there’s not even any need to store input items in your own DB
> AI agents: Individual agents that use LLMs to process user inputs, call tools and MCP servers to perform actions, and generate responses. Agents support model providers including Azure OpenAI, OpenAI, and Azure AI.
> Workflows: Graph-based workflows that connect multiple agents and functions to perform complex, multi-step tasks. Workflows support type-based routing, nesting, checkpointing, and request/response patterns for human-in-the-loop scenarios.
Said nobody?
The site above only runs local in browser models and uses a local user account. So it’s easy for infinite people to play with and costs me nothing to host.
It’s still a ways away from a Show HN post, and is more capable with remote frontier models, or with gguf over onnx (maybe?) whenever I get the local app out.
Got part way through their tutorial, seemed okay. Haven't used it in prod, though.
It’s a modern cross platform open source language with very good performance
I prefer Go's approach on preferring interfaces instead of inheritance. But what I like is Clojure and Lisp where the semantics of algorithms and data structure is not so diffuse.
The bitter irony is, Microsoft has since embrace-extend-extinguished Bonzi Buddy spyware tech, building it right into Windows 11. So... they're moving onward to the future I guess?
Unfortunately, the API died in Windows Vista, and was only widely available in Windows XP at the latest.
API documentation seems rather sparse too, though it looks like an LLM somewhere found a pirated book or something with example code because generated code seems to understand the API and its restrictions decently well. Writing the kind of C++ that still compiles on old versions of Windows is what broke my will to finish the project, though.
Reimplementations exist too: https://mklab.eu.org/clippy/
I remember Microsoft Agents as the enforcement arm of the Business Software Association.
They'd perform copyright raids on small biz, typically after some disgruntled employee phoned in an infringement tip.