What's the difference between the OpenAI Agents SDK and AutoGen?

The OpenAI Agents SDK moves work by handoff: one agent delegates a task to another named agent, and that’s the whole exchange. Microsoft’s AutoGen signature pattern is a group chat instead, several agents reading the same thread while a manager decides who speaks next each round.

AutoGen rebuilt itself between v0.2 and v0.4 into what its own migration guide calls “an asynchronous, event-driven architecture.” The current AgentChat layer offers RoundRobinGroupChat and SelectorGroupChat for picking a next speaker, plus a Swarm preset that drops the central manager: each agent hands off by name through a tool call instead of a manager choosing, but every agent in a Swarm still reads and writes the same shared thread. The Agents SDK never runs a shared thread: a handoff hands the task and context to one named agent, and nothing else reads that exchange unless it’s handed off again.

Both patterns carry the same risk at the boundary: what looks fine in one agent’s own output can still be the failure, if the fact it needed never crossed to the next agent. A group chat just has more boundaries for that to happen at than a single handoff does.

sources

keep reading

More on this.

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y