Run details

NxWorkspace

CI Pipeline Executions
- Current executionCanceled
  chore/issue-triage-tooling
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

Sign in

chore(repo): record the traps in driving nx's TUI unattended Reproducing #36520 needed 160 unattended runs per version, and each of these cost an iteration before it was understood. - `tui.autoExit: 0` is a duration, so it means never auto-exit, not exit immediately. A loop set that way waits forever for a keypress. - 22.7.x keeps the TUI open after a task fails and `--tuiAutoExit=true` does not override it, so an unattended run hangs on exactly the case being measured. Feed it a quit. - `--tui` and `--outputStyle` are mutually exclusive; passing both prints help and exits 1, which reads as the reproduction failing. Also: size the pty, or the capability check refuses the TUI and the run measures the non-TUI path again.

nx build workspace-plugin

Succeeded

100%

Cache hits

2 of 2 tasks used cache.

Resource usage is collected per agent

Run-level metrics are not available for distributed runs. View CPU and memory in this CI pipeline execution’s Analysis page.

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

NxWorkspace