Skip to main content
agno create my-os
agno create clones a starter template into a new directory, strips its git history, and prints the next steps: 
cd my-os
cp example.env .env   # then fill in your secrets
agno up               # start it with docker compose
agno connect          # make it available in your coding agents

​
Starter Templates

Pick a starter with --template: 
agno create my-os --template agentos-aws
TemplateTargetRepository
agentos-docker (default)Local dev and any Docker hostagno-agi/agentos-docker
agentos-awsAWSagno-agi/agentos-aws
agentos-flyFly.ioagno-agi/agentos-fly
agentos-gcpGoogle Cloudagno-agi/agentos-gcp
agentos-railwayRailwayagno-agi/agentos-railway
Every starter ships an AgentOS application, an example.env, and a compose file that agno up picks up. See Templates for the full catalog, including pre-built agent systems.

​
Custom Templates

Scaffold from any git repository, such as your team’s internal starter: 
agno create my-os --url https://github.com/acme/agentos-internal

​
How It Works

  1. Validates the name. It becomes a directory under the current directory, so it must be a single path segment of letters, digits, -, and _.
  2. Runs git clone --depth 1 on the template repository (git must be installed).
  3. Removes the cloned .git directory, giving you a clean tree to init your own repo in.
The command fails if the target directory already exists. The CLI doesn’t keep a registry of projects; up, down, and restart operate on whatever directory you run them from.

​
Next Steps

TaskGuide
Start the projectagno up
Connect coding agentsagno connect
Deploy to productionTemplates