AutoGen is now maintenance-only; Agent Framework is the successor

Microsoft's AI Frontiers lab is gone; its agent framework now survives on community patches. What to audit, where to migrate, and the new Claude beta.

Nowline NOV 8 9:00 AM banner

Top AI stories from the last hour

Top AI stories from the last hour

Copy markdown

  • AutoGen drops to maintenance mode

    Microsoft's AI Frontiers group — the ~50-person lab behind AutoGen and the Fara computer-use agent — has wound down, with founder John Langford declaring its end in a Nov 6 post. AutoGen's README now reads "maintenance mode… community managed going forward": no new features, and only community-contributed bug and security patches. If AutoGen is in your production stack, you're now leaning on a frozen, volunteer-patched dependency.

  • Agent Framework is the named exit — and Claude support just hit beta

    Microsoft steers new projects to Microsoft Agent Framework (1.0 shipped April). It's not a drop-in port: agents are stateless (history moves into an AgentSession), teams become Workflow graphs, and the default multi-turn tool loop can fire more model calls per request than AutoGen did. The fresh piece: agent-framework-anthropic 1.0.0b261106 landed on PyPI Nov 7, finally bringing Claude — plus Bedrock, Vertex and Foundry wrappers and prompt caching — to the framework. Install it with pip install --pre.

  • The audit trap: "archived: false" lies

    A dependency scan that only checks GitHub's archived flag will miss this — the repo still reports not-archived, and the README text is the real signal. Package names add to the confusion: pyautogen now proxies the maintenance-mode autogen-agentchat, while the bare autogen name belongs to AG2, a separately maintained fork. Run pip list | grep -iE 'autogen|pyautogen|ag2' to see which one you're actually shipping.