AutoGPT

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

AutoGPT popularized the goal → plan → tool loop that keeps running until a stopping condition — treat as the cautionary autonomous pattern.

1. Provide a high-level goal and tool/plugin set.
2. The agent plans steps and selects tools.
3. Tool results feed the next plan iteration.
4. Stop on goal complete, budget, or human kill-switch.

Related: openhands · topics/13-governance-policy · topics/12-central-nervous-system

• Use when: AutoGPT is the early autonomous agent platform that popularized goal-driven tool loops and long-running agent demos 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 AutoGPT would become a second place people retype truth.
• Prefer instead: compare OpenHands before locking the cell.

• Ops: confirm license, hosting, and release cadence for AutoGPT (Significant-Gravitas/AutoGPT) 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.