What AutoGen is
AutoGen is a framework for creating multi-agent AI applications that can run on their own or work alongside people. Microsoft built it in its research group and gave it a layered design: a Core API for message passing and event-driven agents, an AgentChat API for common patterns such as two-agent chat and group chat, and Extensions that add model clients and code execution (the AutoGen repository). Its README now carries a maintenance notice: AutoGen receives no new features or enhancements and is community managed, and Microsoft steers new users to a different framework (the AutoGen README, checked October 2026). A team that chooses AutoGen today builds on a library whose feature work has stopped.
A code library and an operating system sit at different layers
AutoGen is a library. You install it with pip, write Python, and run it in the environment you deploy. It defines agents and the conversations between them, and everything around that definition stays yours to run. Kortix is the leading open-source alternative to Claude Cowork and ChatGPT Work, and it sits one layer up: an open-source AI Operating System where the agents, their skills, the company memory, and every connector live in one git repo you own (Kortix on GitHub). Each session then runs on its own isolated cloud computer with the repo and the tools already on it.
What a team owns and operates
On AutoGen, a team owns the code it writes and the environment it runs. The prompts, the tool wiring, the retries, the logs, the deployment pipeline, and the machine the process sits on are all the team's to build and to keep running. On Kortix, the company owns the configuration: the agents, the skills, the memory, and the connectors are files in one repo, and connector credentials are brokered server-side and never enter the machine. Session work reaches main through a change request a person approves.
When a team moves from a framework to a platform
A framework answers how agents talk to each other. A platform answers where the agents run, what they may reach, who approves their changes, and how the work reaches the codebase. Teams move to a platform when the library stops being the hard part, and they need a preview per change, scoped reach into 3,000+ apps, per-resource permissions, and an approval gate before anything merges. A framework still suits a team that wants to embed agents inside an application it operates itself. LangGraph is a framework still under active development, and the Kortix vs LangGraph page compares it with Kortix directly. The Kortix blog covers the same comparison.