What is AgentOS?

AgentOS is a FastAPI-powered runtime for serving multi-agent systems. The smallest AgentOS looks like this:

agno_assist.py

from agno.agent import Agent
from agno.db.sqlite import SqliteDb
from agno.models.anthropic import Claude
from agno.os import AgentOS

agent = Agent(
    name="Agno Assist",
    model=Claude(id="claude-sonnet-4-5"),
    db=SqliteDb(db_file="agno.db"),
)

agent_os = AgentOS(agents=[agent])
app = agent_os.get_app()

This registers one agent, stores its sessions in a local SQLite database, and returns a FastAPI app that you can run locally or deploy to your cloud provider. Engineering teams use AgentOS to serve agents, teams, and workflows through one backend. It provides REST endpoints for runs, sessions, memory, knowledge, evaluations, approvals, and schedules. Add MCP, messaging interfaces, tracing, and JWT authorization as your deployment needs them. Build components with the Agno SDK or supported adapters for the Claude Agent SDK, LangGraph, DSPy, and Antigravity. Register them with AgentOS to power product features, automations, and internal tools.

What AgentOS Provides

Capability	What It Does
API	Exposes 80+ REST endpoints with SSE streaming for runs
Persistence	Stores sessions and enabled memory, knowledge, evaluation, approval, schedule, and trace data in configured databases
Request isolation	Deep-copies native Agno components on core REST, MCP, and A2A run endpoints
Authorization	Supports JWT validation, endpoint permissions, service accounts, and opt-in per-user data isolation
Observability	Writes OpenTelemetry traces to a configured database when tracing is enabled
Interfaces	Serves MCP, A2A, AG-UI, Slack, WhatsApp, and Telegram when configured
Multi-framework	Runs native Agno components alongside Claude Agent SDK, LangGraph, DSPy, and Antigravity adapters

Architecture

AgentOS has two parts:

Layer	Role
Runtime	Runs agents, teams, and workflows as a FastAPI service
Control Plane	Provides the web interface for testing, inspecting, and operating connected runtimes

The runtime exposes the same APIs to your product and the AgentOS Control Plane.

Products and the AgentOS Control Plane connecting to an AgentOS runtime

Where Data Flows

Your AgentOS runtime and configured databases run in infrastructure you control. The Control Plane sends requests directly from your browser to the selected runtime.

Layer	Data Path
Runtime	Runs in your infrastructure
Stored application state	Written to the databases you configure
Control Plane requests	Travel from the browser to the selected runtime
Models, tools, and interfaces	Call the external services you configure
Agno telemetry	Sends usage metadata according to your telemetry configuration

See Telemetry for the collected fields and configuration options. See Security & Auth for runtime authentication and authorization.

Get Started

AgentOS

Example Usage

What is AgentOS?

What AgentOS Provides

Architecture

Where Data Flows

Next Steps

Run AgentOS Locally

Connect the Control Plane

Use the Control Plane

Security & Auth

Developer Resources

​What AgentOS Provides

​Architecture

​Where Data Flows

​Next Steps

Run AgentOS Locally

Connect the Control Plane

Use the Control Plane

Security & Auth

​Developer Resources

What AgentOS Provides

Architecture

Where Data Flows

Next Steps

Developer Resources