Skip to main content
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 the docker compose commands without running them
FlagCommandsDescription
--file, -fallCompose file to use
--pull, -pup, restartAlways pull newer images
--volumes, -vdownAlso remove named volumes. Destroys data.
--dry-run, -drallPrint the command without running it
--jsonallEmit a single JSON document
restart runs down, waits two seconds, then runs up.

​
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, or jwt
  • MCP auth, when the MCP endpoint carries its own OAuth protection
  • Each supported coding agent: not detected, detected but not connected, or configured (with the config location)
FlagDefaultDescription
--urlautodiscoverAgentOS base URL
--server-namederived from the AgentOS nameMCP server entry name to look for in client configs
--jsonoffEmit a single JSON document

​
Next Steps

TaskGuide
Connect coding agentsagno connect
Manage tokensagno tokens
Full flag and JSON referenceagnoctl reference