---
id: "entity-autogen"
type: "entity"
entityType: "tool"
canonicalName: "AutoGen"
canonicalUrl: "https://microsoft.github.io/autogen/"
source_timestamps: ["§5.2"]
tags: ["framework", "multi-agent", "contrast"]
related: ["contrarian-frameworks-overkill", "question-concurrency-scaling"]
sources: ["paper"]
sourceVaultSlug: "icm-paper-folder-architecture-2026Jun02"
originDay: 2
---
# AutoGen

## What it is

**Microsoft's open-source multi-agent conversation framework** for building LLM applications with multiple cooperating agents.

## Why it appears in the paper

AutoGen is cited as the **appropriate tool where ICM is not**.

- ICM's sequential, file-based handoffs are too slow for real-time multi-agent collaboration.
- AutoGen provides the message-passing infrastructure required where agents communicate dynamically and respond to each other in tight loops.

## What this signals

The contrast marks **the precise boundary of ICM's claim** ([[contrarian-frameworks-overkill]]): ICM is for sequential, human-reviewed, repeatable workflows; AutoGen (and similar frameworks like LangChain, Semantic Kernel) is for everything else.

The bounded contrarian move — "frameworks are overhead **for this class**, not in general" — is what makes ICM's positioning defensible rather than absolutist.


## Related across days
- [[entity-langchain]]
- [[entity-semantic-kernel]]
- [[contrarian-frameworks]]
- [[contrarian-frameworks-overkill]]
- [[recurring-foil-frameworks]]