── CLI REFERENCE ──

exo status

Display a grouped tree view of all generated infrastructure assets and their status.

## Synopsis

bash
exo status

## Description

Reads .exo.yaml and scans for the full set of expected generated assets. Output is a tree grouped into 7 categories with file sizes, modification times, and a summary progress bar at the bottom.

Uses ✓ for files/directories present and ✗ for missing items. Tree connectors (├── / └──) give a clear visual hierarchy.

## Example Output

text
$ exo status
EXO Project Status ─ my-service
Containers
├── ✓ Dockerfile 1.2 KB • 2h ago
└── ✓ docker-compose 0.8 KB • 2h ago
CI/CD
├── ✓ GitHub Actions dir • 2h ago
└── ✗ GitLab CI missing
Infrastructure
├── ✓ Terraform (AWS) dir • 2h ago
└── ✗ Terraform (GCP) missing
Kubernetes
├── ✓ K8s Manifests dir • 2h ago
└── ✓ Helm Chart dir • 2h ago
Monitoring
├── ✓ Monitoring Stack dir • 2h ago
├── ✓ Grafana Dashboard 4.1 KB • 2h ago
└── ✓ Alert Rules 0.9 KB • 2h ago
Database
└── ✓ PostgreSQL 0.5 KB • 2h ago
Project
├── ✓ .exo.yaml 0.1 KB • 2h ago
├── ✓ Makefile 0.8 KB • 2h ago
├── ✓ .env.example 0.2 KB • 2h ago
└── ✓ .gitignore 0.4 KB • 2h ago
████████████████░░ 14 / 16 assets present

## Asset Categories

CategoryAssets Checked
ContainersDockerfile, docker-compose.yml
CI/CD.github/workflows/, .gitlab-ci.yml
Infrastructureinfra/aws/, infra/gcp/, infra/azure/
Kubernetesk8s/, charts/<name>/
Monitoringmonitoring/, grafana_dashboard.json, alerts.yml
Databasedocker-compose.<db>.yml
Project.exo.yaml, Makefile, .env.example, .gitignore

## Tips

→Run after exo init to verify all assets were generated
→Use alongside exo diff to preview what would change before regenerating
→Combine with exo clean to remove all assets when starting fresh