nx-ci-monitor

Automate Nx Cloud CI monitoring by invoking the nx-ci-monitor tool on your current branch, which watches pipeline status and automatically applies self-healing fixes to reduce recovery toil.

Self-healing works by orchestrating a ci-watcher subagent to poll Nx Cloud CI pipeline status, diagnose failures, and trigger automated actions like applying fixes or waiting for new CI attempts.

Yes, you need an active Nx Cloud connection to monitor CI pipelines automatically. The tool performs connection checks to ensure safe operations before watching and applying self-healing fixes.

Yes, you can configure defaults for Nx CI monitoring including max cycles, timeouts, and verbosity levels to control how long the pipeline watcher polls and reports CI status.

The best way to watch CI status across Nx workspaces is using an automated monitoring tool that reports pipeline failures and applies auto-fix options, supporting local verification workflows.

Automated CI monitoring waits for new CI attempts after applying a fix to verify the self-healing action succeeded, ensuring the Nx Cloud pipeline recovers before exiting the monitoring cycle.