aljaz/Auto-GPT
1
0
Fork 0
mirror of https://github.com/aljazceru/Auto-GPT.git synced 2025-12-17 14:04:27 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
39c46ef6be4e7772bc2a39e8b5b72066391ec689
Auto-GPT/docs/content/AutoGPT/components/introduction.md
Nicholas Tindle 5e89b8c6d1 Add all the new component docs to the site and do a tidy up of docs (#7098) 
* feat: add all the new component docs to the site

* fix(docs): relative links and markdown warnings

* feat(docs): How to contribute to the docs as a docs section

* fix(docs): missed docs page for developer setup

* fix(docs): re-add configurations options

* fix(docs): bad link to components fixed

* fix(docs): bad link to components fixed

* ref(docs): reorder some items to make more sense

* fix(docs): bad indentation and duplicate block

* fix(docs): warning about out of date markdown extension

* fix(docs): broken links fixed

* fix(docs): markdown formatter complaints
2024-04-23 08:49:07 -05:00

1.9 KiB
Raw Blame History

Component Agents

This guide explains the component-based architecture of AutoGPT agents. It's a new way of building agents that is more flexible and easier to extend. Components replace some agent's logic and plugins with a more modular and composable system.

Agent is composed of components, and each component implements a range of protocols (interfaces), each one providing a specific functionality, e.g. additional commands or messages. Each protocol is handled in a specific order, defined by the agent. This allows for a clear separation of concerns and a more modular design.

This system is simple, flexible, requires basically no configuration, and doesn't hide any data - anything can still be passed or accessed directly from or between components.

Definitions & Guides

See Creating Components to get started! Or you can explore the following topics in detail:

  • 🧩 Component: a class that implements one or more protocols. It can be added to an agent to provide additional functionality. See what's already provided in Built-in Components.
  • ⚙️ Protocol: an interface that defines a set of methods that a component must implement. Protocols are used to group related functionality.
  • 🛠️ Command: enable agent to interact with user and tools.
  • 🤖 Agent: a class that is composed of components. It's responsible for executing pipelines and managing the components.
  • Pipeline: a sequence of method calls on components. Pipelines are used to execute a series of actions in a specific order. As of now there's no formal class for a pipeline, it's just a sequence of method calls on components. There are two default pipelines implemented in the default agent: propose_action and execute. See 🤖 Agent to learn more.