Skip to main content
agno create my-os
cd my-os
cp example.env .env   # fill in your secrets
agno up
agno connect
The agno command scaffolds AgentOS projects, runs them with Docker Compose, connects your coding agents over MCP, and manages service-account tokens. Every command takes --json and emits a single JSON document on stdout, so coding agents and scripts can drive it.

​
Install

The CLI ships with the SDK, so installing agno 2.7 or later puts the agno command on your PATH. 
pip install -U agno
The CLI is also published standalone as agnoctl. It depends on typer, rich, and httpx only, so it runs on machines without the SDK: 
uvx agnoctl connect
agno and agnoctl are the same CLI under two names.

​
Commands

CommandWhat it doesGuide
agno create <name>Scaffold a project from a starter templateCreate a project
agno connectConnect coding agents to a running AgentOS over MCPConnect your clients
agno disconnectRemove AgentOS MCP entries from client configsConnect your clients
agno up / down / restartRun the project with Docker ComposeOperate your AgentOS
agno statusShow the discovered AgentOS and connected clientsOperate your AgentOS
agno tokens create / list / revokeManage service-account tokensManage tokens

​
How the CLI Finds Your AgentOS

connect, status, and tokens need a running AgentOS. They resolve its URL in this order:
PrioritySourceExample
1--url flagagno connect --url https://os.example.com
2AGENTOS_URL environment variableexport AGENTOS_URL=https://os.example.com
3AGENTOS_URL in a project env fileAGENTOS_URL=https://os.example.com in .env.production, then .env
4Localhost probePorts 7777, 7778, 7779, 8000
The probe covers AgentOS.serve()’s default port (7777), common bump-up ports, and a bare uvicorn setup (8000). If your AgentOS runs on any other host or port, point the CLI at it with --url or AGENTOS_URL.

​
Developer Resources