Comparisons / AutoGen vs Flue

AutoGen vs Flue: Which Agent Framework to Use?

AutoGen vs Flue, head to head

AutoGen and Flue both let you build an agent, but they sit in different parts of the stack and they assume different things about who's writing the code.

AutoGen by Microsoft models agents as ConversableAgents that chat with each other.

Flue is a declarative TypeScript agent framework from Fred K.

Underneath, both wrap the same thing: a model call, a tool dispatch, a loop. The decision is about which abstraction your team wants to think in day to day, and which ecosystem you're willing to inherit along with it. There's an honest, framework-free version of the same pattern in about 60 lines of Python in the lesson at the bottom of this page — useful as a baseline regardless of which framework wins.

Pick AutoGen if

Pick AutoGen if autoGen excels at complex multi-agent workflows where agents need to debate or collaborate. For single-agent use cases or simple tool-calling agents, the plain Python version is significantly simpler. The tradeoffs in its intro should match how your team already thinks about agents; Flue will feel like translation if they don't.

Full AutoGencomparison →

Pick Flue if

Pick Flue if flue is the natural choice when the deploy target is Cloudflare and you want a TypeScript-first, declarative agent framework tuned for Durable Objects. Its cross-runtime story (Cloudflare + Node + CI) is genuinely useful if agents run in more than one place. For a single-agent loop that doesn't need persistence, plain TypeScript is simpler. The tradeoffs in its intro should match how your team already thinks about agents; AutoGen will feel like translation if they don't.

Full Fluecomparison →

What both add

Whichever you pick, you're inheriting a dependency tree and a vocabulary your team has to learn before they ship anything. AutoGen has its own class hierarchy and tool registration conventions; Flue has its. Either way, when something misbehaves you'll be reading framework source before you reach the actual HTTP call.

If the real workload is one model and a handful of tools, both can feel like a workbench for driving a nail. The lesson below builds the same pattern in plain Python — useful as a comparison point even if you ultimately keep the framework.

By the numbers

By the numbers

AutoGen

GitHub Stars

56.7k

Forks

8.5k

Language

Python

License

CC-BY-4.0

Created

2023-08-18

Created by

Microsoft Research

github.com/microsoft/autogen

Flue

GitHub Stars

2.4k

Forks

140

Language

TypeScript

License

MIT

Created

2026-05-01

Created by

Fred K. Schott + Astro team (at Cloudflare)

Backed by

Cloudflare

Cloud/SaaS

Cloudflare Durable Objects; also deploys to Node, GitHub Actions, GitLab CI

Production ready

Yes

github.com/withastro/flue

GitHub stats as of April 2026. Stars indicate community interest, not necessarily quality or fit for your use case.

ConceptAutoGenFlue
Agent`ConversableAgent` with `system_message`, `llm_config``createAgent({ model, instructions, tools })` — declarative config, framework runs the loop
Tools`register_for_llm()` and `register_for_execution()`Registered with valibot schemas: `{ name, description, schema, execute }`
ConversationTwo-agent chat with `initiate_chat()`, message history
Multi-Agent`GroupChat` with `GroupChatManager`, speaker selection
Nested Chats`register_nested_chats()` for sub-task handling
Termination`is_termination_msg` callback, `max_consecutive_auto_reply`
StateDurable Streams — replayable, checkpointed event log stored in Cloudflare Durable Objects
DeploymentOne config controls deploys to Cloudflare, Node, GitHub Actions, or GitLab CI
RuntimeThe Pi harness — same runtime as OpenClaw, so agents share tooling with that ecosystem
Cloudflare-nativeDurable Objects give per-agent persistence and locking without an external DB

Or build your own in 60 lines

Both AutoGen and Flue implement the same 8 patterns. An agent is a function. Tools are a dict. The loop is a while loop. The whole thing composes in ~60 lines of Python.

No framework. No dependencies. No opinions. Just the code.

Build it from scratch →