# Exit Codes & Error Taxonomy

> Understand CLI exit codes and platform stage failure codes.

- **Category**: Platform & Reference
- **Last Verified**: 2026-07-14

To enable automation and reliable agent interaction, Kubeletto uses explicit exit code definitions and domain-specific stage errors.

## CLI Exit Codes

| Code | Taxonomy | Trigger |
| --- | --- | --- |
| 0 | Success | Finished successfully. |
| 2 | Misuse / Validation | Invalid flags or parameters. |
| 3 | Unauthenticated | Expired session or invalid key. |
| 4 | Forbidden | Insufficient permissions. |
| 5 | Not Found | Resource does not exist. |
| 7 | Quota Exceeded | Exceeded allocated limits. |
| 8 | User Build Error | Code compile failed. |
| 9 | Platform Error | Internal cluster error. |
| 10 | Timeout | Deploy watch timed out. |

## Platform Failure Stage Codes

- `IMAGE_NOT_FOUND`: Container reference does not exist in registry.
- `UNSUPPORTED_ARCH`: Target image is not x86-64 (amd64).
- `GIT_CLONE_FAILED`: Cannot fetch files from remote repository.
- `PORT_MISMATCH`: Application failed to listen on port $PORT.
- `CONTAINER_CRASH_LOOP`: Runtime crashed repeatedly at launch.
- `OOM_KILLED`: Exceeded container memory threshold limits.