What people actually say about AutoGen
65 mentions across 5 sources · 51% positive · researched Oct 9, 2026
Hacker News, YouTube, Stack Overflow, GitHub, Lemmy
What users praise
- • MIT-licensed and free to self-host, with 61k+ GitHub stars and active development
- • Three-layer architecture (Studio, AgentChat, Core) lets developers pick the abstraction they need
- • Native MCP support via McpWorkbench keeps it current with the protocol everyone is adopting
What frustrates them
- • ChatCompletionCache silently omits tool_choice from its cache key — a genuine correctness bug
- • BaseTool still lacks an approval function, so guarding destructive tool calls is manual
- • AutoGen Studio had a code-execution flaw — agent runtimes require real sandboxing
This is a summary. The full report adds every quote we found, a per-source breakdown, recurring themes, hidden costs and the learning curve — run a free scan below, or see the full AutoGen review.
What comes up again and again about AutoGen
Recurring themes across everything we collected, with where each one showed up.
AutoGen is consistently grouped with LangGraph and CrewAI as a default agent-framework trio
praised · seen on Hacker News, YouTube
Framework comparison content is everywhere, reflecting decision fatigue more than excitement
mixed · seen on YouTube
Reliability gaps in tool-level plumbing (tool_choice caching, BaseTool approval)
criticised · seen on GitHub
Onboarding and version-migration friction trip up new and existing users
criticised · seen on Stack Overflow
Agent runtime security (code execution via Studio) is a live concern
criticised · seen on Lemmy
Open-source pricing misconceptions about AutoGen vs hosted competitors
mixed · seen on YouTube
How hard is AutoGen to learn?
Users describe it as intermediate · typically A few hours for a basic AgentChat agent; days to get a Core-level distributed setup working to get going
Where people get stuck
- • Choosing between Studio, AgentChat, and Core before you've shipped anything
- • API churn between 0.2 and 0.7 breaks tutorials and older examples
- • Group chat speaker-transition config errors are non-obvious to diagnose
- • Tool-call safety requires understanding base abstractions, not just config
Who AutoGen actually suits
Works well for
- • Python developers building multi-agent systems who want programmatic control
- • Research teams prototyping conversational and event-driven agent topologies
- • Engineers who need MCP integration, Docker sandboxing, or gRPC-distributed agents out of the box
- • Shops already standardized on Microsoft/Azure AI tooling
Not the right fit for
- • Non-developers looking for a no-code assistant builder
- • Teams that want a managed, batteries-included agent platform with SLAs
- • Simple single-prompt LLM apps where LangChain or a direct API call is enough
- • Production setups requiring airtight, out-of-the-box tool-call approval gates
What people are discussing right now
Discussion volume is medium and trending stable
- AutoGen vs CrewAI vs LangGraph framework selection
- Multi-agent orchestration patterns and group chat design
- Tool-call safety, approval hooks, and guardrails
- MCP integration and distributed agent architectures
- Version 0.2 to 0.7 migration friction
What people really think about AutoGen
A real-time sweep of the open web — social media, forums, review sites, video reviews and live community discussions — distilled into one honest verdict with the actual mentions behind it.
What's inside your AutoGen report
Everything you need to decide — distilled from real, current user opinion.
Live mentions
The actual posts, reviews & complaints about AutoGen — with links and dates.
Honest verdict
A straight answer on whether it lives up to the hype — and who it’s really for.
Praise & gripes
What users genuinely love and the frustrations that keep coming up.
Real quotes
Representative voices from real users, not marketing copy.
Recurring themes
The patterns across hundreds of opinions, surfaced at a glance.
Red flags
Hidden costs and dealbreakers people only discover after signing up.
How it works
Sign up free
Create an account in seconds — get 5 free scans, no card.
We sweep the web
Live social media, forums, reviews & video opinions — in ~30–60s.
Get your report
An honest, downloadable verdict with the real mentions behind it.
Ready to see the real verdict on AutoGen?
Your scan is ready in under a minute · $1.
Compare AutoGen head-to-head
See how it stacks up against the tools people weigh it against.
Top alternatives to AutoGen
Researching options? Explore the closest alternatives.
Semantic Kernel
Microsoft's open-source SDK for building AI agents and copilots with plugins, memory, and multi-agent orchestration.
AutoGPT
AutoGPT gives you a team of named AI Experts — for SEO content, sales outreach, and ops — briefed in plain English and coordinated by Otto.
LangChain
Open-source agent frameworks (langchain, langgraph, deepagents) plus LangSmith for tracing, evals, deployment and governance.
LangGraph
LangGraph is an MIT-licensed, low-level agent orchestration framework for building stateful, controllable AI agents as graphs of states and transitions.
CrewAI
CrewAI is an enterprise agent build and runtime platform: a visual multi-agent builder plus a governed control plane for production workflows.
Google Agent Development Kit
Google Agent Development Kit (ADK) is the MIT-licensed open-source framework for building production AI agents with graph workflows in
Check sentiment on these too
Run a live scan on the alternatives before you decide.
AutoGen — questions buyers ask
What do people complain about most with AutoGen?
The complaints that recur most often are ChatCompletionCache silently omits tool_choice from its cache key — a genuine correctness bug, BaseTool still lacks an approval function, so guarding destructive tool calls is manual and AutoGen Studio had a code-execution flaw — agent runtimes require real sandboxing. Drawn from 65 mentions across 5 sources.
What do users like about AutoGen?
Users consistently praise MIT-licensed and free to self-host, with 61k+ GitHub stars and active development, three-layer architecture (Studio, AgentChat, Core) lets developers pick the abstraction they need and native MCP support via McpWorkbench keeps it current with the protocol everyone is adopting.
Is AutoGen hard to learn?
Users describe it as intermediate; most people are up and running in a few hours for a basic AgentChat agent, days to get a Core-level distributed setup working; the usual sticking points are choosing between Studio, AgentChat, and Core before you've shipped anything and API churn between 0.2 and 0.7 breaks tutorials and older examples.
Who should not use AutoGen?
Based on what users report, it is a poor fit for non-developers looking for a no-code assistant builder, teams that want a managed, batteries-included agent platform with SLAs and simple single-prompt LLM apps where LangChain or a direct API call is enough.
What are people saying about AutoGen right now?
Discussion volume is medium and trending stable. Current topics: AutoGen vs CrewAI vs LangGraph framework selection, multi-agent orchestration patterns and group chat design and tool-call safety, approval hooks, and guardrails.
How current is this report?
Each scan runs live the moment you click — it reflects what people are saying now, and every report lists the dated mentions behind it.
Can I download it?
Yes — download the full report as a polished, shareable PDF.