The self-managing agent platform
Introduction
Agno is a self-managing agent platform. Build agents for your company, product, or customers. Run them as durable services on AgentOS. Put them to work automating company operations.
- Build agents with the Agno, Claude Agent, or Codex SDKs. Combine agents into teams and workflows.
- Run agents as durable services with built-in API and MCP. AgentOS handles authentication, role-based access, resume/replay, human approvals, scheduling, and durable execution.
- Automate company operations with Company OS. Give agents responsibilities, organize work into projects and tasks, and configure recurring routines. People set direction and review results; agents own and execute.
Agno provides the orchestration and service layer around your agents, making them available in:
- Your product: using the REST API.
- Claude and ChatGPT: using the MCP server.
- Chat apps like Slack: using Agno Interfaces.
Run your platform in your own cloud and keep your data in your control. Review conversations, inspect traces, manage knowledge, and track your agent activity using the AgentOS UI.
Get started
Agno is built for coding agents. Start with a pre-built template and give this prompt to your coding agent:
Help me set up my agent platform and build my first agent.
Clone https://github.com/agno-agi/agentos-railway into a folder called agent-platform, cd into it, and follow .agents/skills/setup-platform/SKILL.md.
The setup skill runs your platform locally and helps you build your first agent. You get:
- An API server and MCP server.
- PostgreSQL storage for conversations, memory, and platform activity.
- OS Manager to help build and manage your platform.
- Claude and Codex engineers to work on your code.
- Skills for building, evaluating, and improving agents.
- A Company workspace for organizing ongoing work, with a daily maintenance routine that reviews your codebase and Agno releases and proposes platform improvements.
Connect your platform to os.agno.com to start using it. Build agents with code, use the no-code UI, or chat with the OS Manager.
Start improving your agents and platform with the /improve skill. Keep useful changes and regression tests so each round builds on the last. When you're ready, configure scheduled improvement runs in a sandbox that return pull requests for review.
Templates for every cloud
Choose a template for your cloud: Docker · Railway · AWS · GCP · Azure · Fly.io · Render · Modal · Helm
What's included
| Capability | What you can do |
|---|---|
| Agents and teams | Build agents that use tools, delegate work, and collaborate. |
| Workflows | Control execution with routing, conditions, loops, and parallel steps. |
| Memory and knowledge | Remember users across sessions and retrieve answers from your data. |
| Tools and integrations | Connect agents to APIs, databases, and MCP servers. |
| Durable execution | Persist background jobs and track their status across restarts. |
| Human approval | Review sensitive actions before they run, then approve and continue. |
| Observability | Trace runs, inspect tool calls, and diagnose failures. |
| Scheduling | Run agents, teams, and workflows on recurring schedules. |
| Security | Control access with authentication, roles, and per-user data isolation. |
| Coding agents | Run Claude and Codex in sandboxes to implement and test changes. |
| Company OS | Organize work into products, projects, tasks, and recurring routines. |
Tutorials
First, add Agno to your coding agent so it can read the tutorials as you build. Then, learn how to:
- Build your agent platform
- Serve agents as an API
- Serve agents over MCP
- Run Claude and Codex as services
- Read the documentation
Community
Follow Agno on X for releases and demos, or subscribe to The Agno Loop.
See the contributing guide to contribute.
License
Agno is distributed under the Apache 2.0 license.
Telemetry
Agno sends a telemetry event per agent so we know which model providers to prioritize. Prompts, messages, and outputs are never sent. Disable by setting AGNO_TELEMETRY=false.
Metadata
Release files for agno 3.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| agno-3.2.0.tar.gz | 4.6 MB | With provenance | Details for agno-3.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agno-3.2.0-py3-none-any.whl | Python 3 | none | any | Details for agno-3.2.0-py3-none-any.whl |
Total release size: 9.7 MB
Release files / agno-3.2.0.tar.gz
| Download URL | agno-3.2.0.tar.gz |
|---|---|
| Size | 4.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7bc159b9a8a673c0e1b6215c91c9d579e11a3c0d516562cd2005a2eb00c6edeb
|
|
BLAKE2b-256 checksum How to use checksums |
29713c20c6d948f7aa3b9c36a31f66f44b4e080298324d843e0c32429bfe5d8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / agno-3.2.0-py3-none-any.whl
| Download URL | agno-3.2.0-py3-none-any.whl |
|---|---|
| Size | 5.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
91f72b47433fc3e80f02e507a2d78373f19901ddedd5a484712ec301b896ba7a
|
|
BLAKE2b-256 checksum How to use checksums |
dadc3a19c3dd532822a1d36c5b85b8140427591020deb5703b35e25a79d8c38c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logSecurity for agno 3.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for agno-3.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
