Skip to main content
The Agno SDK gives engineering teams Python primitives for agents, multi-agent teams, and explicit workflows, plus composable models, tools, memory, knowledge, learning, and guardrails. Each configured primitive remains a regular Python object that can run directly or be served through AgentOS.
workbench is a component: an agent primitive configured with a model, tools, storage, and session history. AgentOS serves the same object as a runtime component.

Primitives

Capabilities

Model and tools

Memory and context

Control and safety

Operations

Components

Agents, teams, and workflows become runnable components once you add their models, tools, state, and configuration. Code-defined components stay in Python. Components created in Studio or through the /components API use draft and published versions, with a current version that you can promote or roll back.

Versioned components

When components are created via the API, they carry a versioned configuration. Published versions are immutable, and run requests accept a version parameter so you can pin clients to a specific version. A current pointer decides which version your production API serves: set it to a newer version to promote, or an earlier one to roll back. Tune a component’s instructions, model, or tools and publish the change as a new version. Promote the new version or roll back to an earlier version based on its results.

Learn more

SDK Introduction

Agents, teams, and workflows in pure Python.

Build Agents

Create agents with models, tools, and instructions.

Build Agent Platform

Assemble a full platform on the AgentOS runtime.