FoundationAgents/MetaGPT

Choose this fork only if you specifically want an older MetaGPT base for AFlow/MathAI experimentation. For production or broad agent-workflow use, upstream MetaGPT is the safer default.

This is not a good adoption target for most users. It is a stale fork with no visible added functionality and is far behind an actively maintained upstream, so the main value is as an archival snapshot rather than a better or safer product choice.

Prefer this fork if you want a small, focused extension for queue/session/plan-oriented workflows and want to stay close to upstream. Prefer upstream if you want the broader, better-supported base without relying on experimental contrib code.

Prefer upstream unless you specifically need to stay on this older snapshot. This fork does not show added capabilities, while it does lag upstream by 20 commits and likely misses recent fixes and compatibility improvements.

Prefer upstream unless you specifically need an old snapshot. This fork does not show added capabilities and is far behind current MetaGPT, so it is mainly a stale baseline rather than a better adoption target.

Choose this fork only if the Gradio web UI is the main requirement and you are comfortable inheriting a very old MetaGPT base. For most adopters, upstream is the better choice because this fork is stale and far behind current framework work.

Choose this fork only if the issue-solver workflow is the specific capability you need. For general MetaGPT use, upstream is the better choice because this fork is extremely stale and adds little beyond one CI workflow.

Prefer upstream unless you explicitly need this older snapshot. The fork adds no visible capabilities, is far behind main, and looks inactive, so it is mainly useful as a frozen reference rather than a production choice.