Components
Save and load Agents, Teams, and Workflows to and from a database, with a Registry for restoring tools, models, and schemas.
| Example | Description |
|---|---|
| Save Agent to Database | Demonstrates creating an agent and saving it to the database. |
| Load Agent from Database | Demonstrates loading an agent from the database by ID and running it. |
| Save Team to Database | Demonstrates creating a team with member agents and saving it to the database. |
| Load Team from Database | Demonstrates loading a team from the database by ID and running it. |
| Save Workflow to Database | Persist a two-step content workflow to PostgresDb with workflow.save(db=db), which versions the workflow on each save. |
| Load Workflow from Database | Demonstrates loading a workflow from the database by ID and running it. |
| Registry for Non-Serializable Components | Demonstrates using Registry to restore tools, models, and schemas when loading. |
| AgentOS Registry App | Demonstrates configuring AgentOS with a Registry and serving the app. |
| AgentOS Registry Demo | Register tools, custom functions, Pydantic schemas, models, and a PgVector vector DB in an AgentOS Registry. |
| Workflows | Examples for saving and loading workflows with advanced step types. |
| Auto-Populating the Registry from Agents, Teams, and Workflows | AgentOS automatically discovers the components (models, tools, databases, and vector databases) used anywhere inside its agents, teams, and workflows and adds them to the registry. |
| Serving an AgentOS with an Auto-Populated Registry | Serve an AgentOS with no explicit registry and read the auto-discovered models, tools, and dbs from the GET /registry endpoint. |