# OpenWOP vs AutoGen, Microsoft Agent Framework and AG2

> Source: https://openwop.dev/comparisons/autogen/ · OpenWOP, the open-source protocol for multi-agent workflow orchestration.

AutoGen, its successor Microsoft Agent Framework, and the community fork AG2 are frameworks you write agent conversations in; OpenWOP is an open protocol that defines how a host exposes a durable run of whatever agents it hosts. If you build on .NET or Azure, Microsoft Agent Framework is the better choice for writing agents.

Checked 4 October 2026. Figures come from each project's own README, docs and package registries.

## Which project is which

- **Microsoft AutoGen** is in maintenance mode. Its README says it "will not receive new features or enhancements" and points new users to Microsoft Agent Framework ([README](https://github.com/microsoft/autogen/blob/main/README.md)).
- **Microsoft Agent Framework** is the successor to both AutoGen and Semantic Kernel, for .NET and Python; 1.0 shipped in April 2026 ([overview](https://learn.microsoft.com/en-us/agent-framework/overview/)).
- **AG2** is a community fork of AutoGen 0.2, Apache 2.0; its v1.0 (July 2026) was a rewrite ([repository](https://github.com/ag2ai/ag2)).

## At a glance

| Property | OpenWOP | Microsoft Agent Framework |
|---|---|---|
| What it is | A wire protocol plus a conformance suite | An SDK with an in-process workflow runtime ([overview](https://learn.microsoft.com/en-us/agent-framework/overview/)) |
| Licence | Spec CC BY 4.0, code Apache 2.0 | MIT (AG2: Apache 2.0) |
| Languages | Any language that speaks HTTP; SDKs for TypeScript, Python and Go | .NET and Python; Go in preview (AG2: Python) |
| Where state lives | An append-only event log per run ([events](https://openwop.dev/spec/v2/core/events.html)) | Checkpoints after each step; restoring needs the same workflow shape ([checkpoints](https://learn.microsoft.com/en-us/agent-framework/workflows/checkpoints)) |
| Human approval | Interrupts resumed by token ([interrupt](https://openwop.dev/spec/v2/core/interrupt.html)) | Request ports and tool-approval requests ([docs](https://learn.microsoft.com/en-us/agent-framework/workflows/human-in-the-loop)) |
| Replay and fork | Fork any run from any event; replay must not repeat side effects on hosts that advertise it ([replay](https://openwop.dev/spec/v2/core/replay.html)) | Resume from a checkpoint |
| Interop | A public wire spec and conformance suite | A2A, MCP and AG-UI; no wire spec of its own ([integrations](https://learn.microsoft.com/en-us/agent-framework/integrations/)) |
| Hosting | Reference app at [app.openwop.dev](https://app.openwop.dev/) | Microsoft Foundry hosted agents |
| Maturity | New: the spec repo started in May 2026 | Generally available since April 2026, about 13,900 GitHub stars |

## When to choose Agent Framework or AG2

- You want Microsoft backing, .NET as a first-class language, and Azure hosting (Agent Framework).
- You want an actively developed community project with broad protocol support in Python (AG2).
- You are writing the agents themselves; OpenWOP gives you nothing to write agents in.

## When OpenWOP fits

- You need a run's lifecycle, approvals and replay to be the same across independent hosts, checked by a conformance suite.
- You are building a host or platform and want clients to work with it without custom integration.

OpenWOP is months old, has one steward, and no independent organisation has implemented a host yet.

## Using them together

An OpenWOP host could call an Agent Framework or AG2 agent over A2A, which all three support, or run one inside a workflow step. Neither has been built or tested yet.

## Common questions

### Is AutoGen still maintained?

Microsoft's AutoGen is in maintenance mode and Microsoft points new users to Agent Framework. AG2 is a separate, community-run fork that is still actively developed.

### Why not just use Agent Framework checkpoints?

If you run one Agent Framework application, they are enough. They are tied to its internal format and workflow shape, whereas OpenWOP's run surface is meant to be the same across independent hosts.

## Sources

- [AutoGen README](https://github.com/microsoft/autogen/blob/main/README.md), [Agent Framework overview](https://learn.microsoft.com/en-us/agent-framework/overview/), [checkpoints](https://learn.microsoft.com/en-us/agent-framework/workflows/checkpoints), [human-in-the-loop](https://learn.microsoft.com/en-us/agent-framework/workflows/human-in-the-loop), [integrations](https://learn.microsoft.com/en-us/agent-framework/integrations/), [1.0 announcement](https://devblogs.microsoft.com/agent-framework/microsoft-agent-framework-version-1-0/)
- [AG2 repository](https://github.com/ag2ai/ag2), [AG2 v1.0 release](https://github.com/ag2ai/ag2/releases/tag/v1.0.0)
- OpenWOP: [events](https://openwop.dev/spec/v2/core/events.html), [interrupt](https://openwop.dev/spec/v2/core/interrupt.html), [replay](https://openwop.dev/spec/v2/core/replay.html), [conformance](https://openwop.dev/conformance/)