Operate Your AgentOS

agno up        # docker compose up -d --build
agno down      # docker compose down
agno restart   # down, then up
agno status    # what is running, how it is secured, what is connected

up, down, and restart shell out to docker compose against your project's compose file. Run them from a project directory created with agno create, or point them at a compose file with --file.

Compose File Detection

Without --file, the CLI looks for the first match in the current directory, then in ./infra:

docker-compose.yml, docker-compose.yaml, compose.yml, compose.yaml

up, down, restart

agno up --pull            # pull newer images before starting
agno down --volumes       # also remove named volumes (destroys data)
agno restart --dry-run    # print only the up command; run neither command

A real restart runs down, waits two seconds, then runs up. A dry run skips the wait and runs neither command. In human-readable mode, restart --dry-run prints only the up command. With --json, its response contains both command payloads.

Typer handles usage errors before the command runs. Unknown commands, unknown flags, missing arguments, and invalid option values exit with code 2 and write diagnostics to stderr. They do not emit JSON, even when --json is present.

status

agno status

status discovers the AgentOS (see discovery order) and reports:

• Base URL and agno version
• MCP endpoint, or disabled when the MCP server is off
• Auth mode: none, security_key, jwt, or unknown when legacy probing cannot determine the mode
• MCP auth, when the MCP endpoint carries its own OAuth protection
• Each supported client: not detected, detected but not connected, or configured (with the config location)

Next Steps