AutoGen README clarifies community maintenance and points new projects to Microsoft Agent Framework

Microsoft’s AutoGen repository has made its maintenance status harder to miss. A README change merged on October 6 adds a maintenance-mode badge and says AutoGen will receive no new features or enhancements; it is now community-managed, with contributions focused on bug fixes, security patches and documentation.

This is a documentation update that clarifies AutoGen’s direction, not a new shutdown announcement. The repository still describes AutoGen as a framework for building autonomous and human-assisted multi-agent applications. Existing users can keep using it, but the maintainers warn that community support may be limited.

For new projects, Microsoft points developers to Microsoft Agent Framework, its successor project. Microsoft’s migration guide maps familiar concepts and APIs, including model clients, tools and multi-agent workflows, while calling out design changes. For example, Agent Framework centers orchestration on typed, graph-based workflows; its guide says distributed execution is planned, while AutoGen has experimental distributed runtimes. Teams should review the migration details before assuming a drop-in replacement.

The practical takeaway: existing AutoGen deployments do not need to stop, but teams planning new capabilities should evaluate Agent Framework and budget migration work. AutoGen’s README links a migration path, yet differences in runtime and orchestration mean projects should validate their own workflows.

Sources: AutoGen README change, merged Oct. 6; AutoGen repository; Microsoft’s AutoGen migration guide.