monitor-ci

To monitor Nx Cloud CI pipelines, you can use a self-healing workflow that spawns a subagent to poll CI status, report progress, and apply fixes via MCP or local verification across branches and CI attempts.

CI self-healing is an automated workflow that detects pipeline failures and applies corrective actions, such as updating lockfiles or triggering environment reruns, coordinating subagents to resolve issues across branches with minimal manual intervention.

Yes, automating CI workflow recovery requires a connected Nx Cloud workspace, the ability to spawn and monitor a ci-monitor-subagent, and permissions to apply fixes via MCP to orchestrate self-healing across branches.

Yes, automated CI monitoring supports human-in-the-loop pushes by providing clear cycle accounting and offering a wait-mode for CI events, allowing developers to interject manual fixes while the subagent continues tracking pipeline progress.

The best way to handle environment reruns and new CI attempts is orchestrating a self-healing CI workflow that applies fixes across branches, coordinates subagents, and accounts for fixed results while waiting for new CI events.

Local verification is required after applying lockfile fixes to validate that the self-healing actions successfully resolved the pipeline issue before the subagent reports the fixed results back to the Nx Cloud workspace.