── CLI REFERENCE ──
exo clean
Remove all files and directories generated by Exo from the current project.
## Synopsis
bash
exo clean [--yes]## Description
Reads .exo.yaml and removes all infrastructure assets that Exo would have generated — Dockerfiles, Terraform directories, Kubernetes manifests, CI pipelines, Helm charts, monitoring configs, and project files.
By default, prompts for confirmation before deleting anything. Pass --yes to skip the prompt (useful in CI). The .exo.yaml config file itself is not removed.
## Flags
| Flag | Description |
|---|---|
--yes | Skip the confirmation prompt and delete immediately |
## What Gets Removed
| Asset | Path |
|---|---|
| Dockerfile | Dockerfile |
| Docker Compose | docker-compose.*.yml |
| Terraform | infra/<provider>/ |
| Kubernetes | k8s/ |
| Helm Chart | charts/<name>/ |
| CI/CD | .github/workflows/ci.yml, .gitlab-ci.yml |
| Monitoring | monitoring/, grafana_dashboard.json, alerts.yml |
| Project files | Makefile, .env.example, .gitignore |
## Examples
Interactive (with confirmation)
bash
$ exo cleanThe following will be deleted: Dockerfile, k8s/, infra/aws/, .github/workflows/ci.ymlProceed? [y/N]: yCleaned 4 items.Non-interactive (CI/CD)
bash
exo clean --yesClean and regenerate with new config
bash
# Switch from AWS to GCPexo clean --yes# Edit .exo.yaml: provider: gcpexo init --non-interactive## Notes
!
.exo.yaml is preserved — it is never deleted by clean!Your application source code is never touched
→Use
exo status first to see exactly what exists before cleaning→Use
exo diff to preview new output before regenerating