run-status

You can check the status of a long-running pipeline by reading the run state from state.yaml. It formats current progress, checkpoints, and recent activity into a concise output, eliminating guesswork for faster decision making.

Run status output includes the run-id, title, intent, mode, started time, duration, checkpoints, and recent activity. It provides visibility into ongoing work by displaying current progress and status markers from state.yaml.

To track progress and checkpoints for manual sessions or CI/CD workflows, read the active run state from state.yaml. It displays status markers, recent activity, and timestamps to provide visibility into ongoing executions.

Yes, this run status tool requires a state.yaml file to function. It reads the current run state, including run-id, title, intent, and timestamps, directly from this YAML file to generate its status output.

You need to query run status for active work items during long-running executions such as data pipelines, CI/CD workflows, or manual sessions. It provides visibility into started time, duration, and checkpoints to enable faster decision making.