MetaGPT

In this catalog it is the Frameworks option when you need to compose multi-step agent loops and tool handoffs. Keep MetaGPT on the observe/propose side of the loop: useful signals and drafts, with human or policy authority still required before anything irreversible runs.

MetaGPT models a virtual software company: role agents follow SOP-like procedures to collaborate on engineering-shaped tasks.

1. Assign company roles (PM, architect, engineer, …).
2. Publish a requirement; roles produce artifacts per SOP.
3. Downstream roles consume prior artifacts.
4. Emit specs/code/docs as the run output.

Related: camel · openhands · topics/05-collective-intelligence · topics/12-central-nervous-system

• Use when: MetaGPT is a research-driven multi-agent framework that models a software company with roles and SOPs so agents collaborate on complex engineering-shaped tasks matches the bottleneck and you specifically need to compose multi-step agent loops and tool handoffs.
• Skip when: another pack already covers the need with less ops surface, or MetaGPT would become a second place people retype truth.
• Prefer instead: compare CAMEL, OpenHands before locking the cell.

• Ops: confirm license, hosting, and release cadence for MetaGPT (FoundationAgents/MetaGPT) before relying on it in a live corridor.
• Integration: bad credentials, scopes, or schema drift produce empty retrievals or runaway tool/model spend without an obvious UI alarm.
• Scope: Frameworks components support agents; they are not the company ledger or the approval authority.