What problem does it solve?
It prevents wasted GPU time by detecting early training quality failures such as loss divergence, NaNs/Infs, and degrading evaluation metrics.
Core Features & Use Cases
- Periodic WandB metric health checks: Continuously evaluates loss trends and evaluation metric movement while training is still running.
- Clear decision rules with escalation: Stops for clearly bad signals, continues when clearly healthy, and escalates ambiguous cases to a Codex judgment step.
- Fallback when WandB is unreachable: If WandB cannot be accessed, it checks the training log via SSH to avoid false assumptions about failure.
Use case example: During multi-hour model training on expensive hardware, run this check every 10–60 minutes to stop promptly if loss diverges or metrics collapse, instead of discovering the issue only after training completes.
Quick Start
Set up a recurring CronCreate job to run training-check against the WandB run path so it can automatically monitor the run and decide whether to stop, continue, or wait.