/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

microsoft/autogen

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T11:58:07.338Z

3mo ago

microsoft/autogen

microsoft/autogen is a large, active open source framework for building multi-agent AI applications that can work autonomously or with humans. It is Python-first, has a .NET area and protos in the repo, and includes documentation and an AutoGen Studio no-code GUI. The repo is currently maintained, with recent commits in March 2026 and a note that new users should consider Microsoft Agent Framework while AutoGen continues to receive bug fixes and critical security patches.

Loading tags...

Stars56,439

Forks8,481

Default branchmain

Last pushed2026-03-29T13:31:03Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

6 of 6 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork if you value bundled examples, notebooks, and downstream experimentation more than staying current with upstream AutoGen. Prefer upstream if you need the latest fixes, security hardening, and the most reliable maintenance path.

Choose this fork only if its local-model and custom orchestration changes are the point. If you want the current AutoGen platform, upstream is the safer choice because this fork is far behind and likely missing recent fixes and tooling improvements.

Choose this fork only if you specifically want the older, customized codebase and its extra examples. If you want a current, actively maintained AutoGen, upstream is the better default.

Prefer upstream unless you specifically need this fork’s older snapshot and custom notebook/UI work. This fork looks like a substantial divergence with useful demos, but it is too stale for most new deployments.

Choose this fork only if you need its older, customized AutoGen snapshot. If you want current fixes, security patches, MCP/Studio improvements, or the latest supported behaviors, upstream is the better default.

Choose this fork only if its 2024-era customizations are the goal. For most adopters, upstream is the safer choice because it is actively maintained and materially ahead on fixes, security, and MCP/Studio work.

Fork comparison

autogenhub/autogen

38/100

stale

significant_divergence

Prefer this fork if you value bundled examples, notebooks, and downstream experimentation more than staying current with upstream AutoGen. Prefer upstream if you need the latest fixes, security hardening, and the most reliable maintenance path.

Likely purpose

To serve as a downstream, opinionated AutoGen distribution for experimentation, demos, and community-driven agent workflows, especially around notebooks, sample apps, and org-specific integrations.

Best for

Teams that want a demo-heavy AutoGen fork for internal workshops or proof-of-concept work.; Developers maintaining existing downstream examples or compatibility patches.; Users who prefer a more opinionated, community-oriented fork over tracking upstream closely.

Additional features

Adds substantial notebook-based walkthroughs and demos, including Microsoft Fabric and retrieval-oriented agent examples.
Adds or expands sample and evaluation assets such as group chat tests, agent builder library content, and OpenAI Swarm-style multi-agent examples.
Appears to package more community and presentation material, including talks, style updates, and maintainers-related documentation.
Includes downstream tweaks to agent behavior and compatibility, such as GPTAssistantAgent role mapping and OpenAI API compatibility fixes.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

Lags upstream by about 200 commits and was last pushed in February 2025, so it likely misses newer upstream fixes, hardening, and release-line improvements.
Likely lacks recent upstream security and MCP-related updates, including importlib provider loading restrictions and AutoGen Studio/MCP hardening.
May be missing newer upstream guidance and maintenance-state updates pointing new users toward Microsoft Agent Framework.
The large divergence makes it harder to assume parity with upstream documentation, packaging, and tested installation paths.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Useful if you want a fork centered on demos, notebooks, and hands-on examples.
May be better suited for community experimentation than the mainline repo.
Contains downstream compatibility and workflow-specific adjustments that can help with older or niche integrations.

Risks

Materially stale relative to upstream, so bug fixes and security hardening may be absent.
Large diff size increases the chance of drift in tests, packaging, and dependency management.
Some upstream capabilities may behave differently or require extra integration work because this is not a narrow patch fork.