AutoGen's Name Changed — A Multi-Agent Experiment That Went Off to Become AG2

|qwen3.6-plus Human|reviews|AG2,AutoGen,multi-agent,agent framework,GroupChat,A2A,MCP,open-source,user reviews,real user reviews
AutoGen's original creators left Microsoft's official repo and carried on under the name AG2. The background to the split between the side keeping v0.2 compatible and the side rewriting fully at v0.4, plus what users recorded about the strengths and the cost of unpredictability in conversational multi-agent on top of it.
Markdown source·Anything to add or correct?

AutoGen's Name Changed — A Multi-Agent Experiment That Went Off to Become AG2

A summary post went up on r/AutoGenAI in 2025: "There's been a lot of confusion in the AutoGen community, so I gathered as much as I could. The early contributors and creators of AutoGen left Microsoft's official repo and renamed their version AG2. This isn't a new framework — it's effectively a continuation of AutoGen 0.2.34. Meanwhile, Microsoft is keeping 0.2 while undertaking a complete rewrite at 0.4."

That one thread is the map for everything that followed. Two paths split off from the same concept, and production users had to figure out which side to stand on. This post carries both that fork and, layered on top of it, the assessment of conversational multi-agent itself.

1. Scope of sources

I read the r/AutoGenAI fork summary (2025), the AG2 official docs, an alternatives comparison (2025-10), and a comprehensive AutoGen evaluation.

2. What the fork means for users

A table from the official docs explains the practical situation.

AG2 ClassicAG2 (new)
Importimport autogenimport ag2
Core agentConversableAgentAgent
Multi-agentGroupChat / swarm / nestedNetwork (hub + channels)

Existing code doesn't stop working. You just pin the Classic package. But v1.0 is not a drop-in upgrade — the agent model, orchestration, and imports all changed. Teams staying on Microsoft's 0.2 have to plan a migration when 0.4 lands. One comparison piece summarized the options teams faced at the time: want stability and backward compatibility, go AG2; want to chase Microsoft's rewrite line, go 0.4; both feel burdensome, leave for another framework.

3. The value of conversational multi-agent

Separate from the fork, the assessment of what the AutoGen lineage delivers is remarkably consistent.

Collaborative workflows. The evaluations converge on strength in scenarios where agents critique, review, and iterate to refine a result, in tool-heavy work, and in governance that needs human approval steps.

AutoGen Studio. Visual orchestration is cited as a big speed-up for prototyping, and the ability to export to code is an advantage.

Guardrails and autonomy control. The pattern of setting autonomy levels per agent and inserting human approval at specific steps was maintained and strengthened on the AG2 side.

4. The price of being unpredictable

It's the shadow side of the same conversational models.

Workflow predictability. "A freeform approach sometimes yields unpredictable workflows. If an agent falls into a loop or starts rambling, it's self-harm level." That's one comparison piece's phrasing. For teams that want exact graphs and state machines, LangGraph is the more honest choice, the evaluations continue.

Cost and tokens. Multi-agent conversation burns tokens fast. The warning to set your own budget policies and caching is repeated.

Project stability. The chaos from the rewrite and the fork was itself a cost. The real production question wasn't "which side is right" but "which codebase will the team stay on."

5. Conclusion — continuity of concept, separation of name

The user record on AG2 and AutoGen sorts into two layers.

The name layer: the original creators' line (AG2) split from Microsoft's rewrite (0.4). For existing users, AG2 functioned as "a safe harbor of the familiar orchestration." Moving between Classic and the new v1.0 is a choice, not an obligation.

The concept layer: the idea of multi-agents collaborating through conversation has a relatively stable evaluation. Strong at negotiation, critique, and HITL; weak at deterministic state machines and cost control.

So the question for evaluating this framework isn't "is AutoGen alive" — it's "is our work in the form of conversational collaboration, or in the form of a deterministic graph." And if it's the former, the name changed but the concept stayed where it was. That's what the user record says.

Related posts: Google ADK user reviews · OpenAI Agents SDK user reviews · AG2 agent hub entry

Sources