Run details

NxWorkspace

CI Pipeline Executions
- Current executionFailed
  feat/nxc-4694-4698-agent-output
- Runs and Agents
- Timeline
- Configuration
- Self-Healing CI
- Project Graph
- Resource Usage
- Analysis
- Conformance
Runs
- Current runSucceeded
- Tasks
- Resource Usage

Insights

Compare tasks
Analytics

Sign in

feat(core): add an output style that addresses task logs instead of printing them An agent driving nx gets the static renderer and reads thousands of lines of passing output to find the one failure. Since NXC-4694 every task leaves its output at `<cacheDir>/terminalOutputs/<hash>`, so the run itself no longer has to carry that text. `--output-style=summary` prints run counts and one line per failing task naming the file holding its output: NX 34 tasks: 31 succeeded, 29 cached, 1 failed, 2 skipped x nx run js:test (exit 3) full log: /repo/.nx/cache/terminalOutputs/9f2c... Re-run with --output-style=static to inline logs. Nothing is printed for a task that succeeded, and no task output is inlined at all, so the size of a run's output depends on how many tasks failed and never on how much they logged. Inlining a fixed tail was considered and dropped: every consumer of this style can read the file - it is chosen for agents or asked for explicitly - and a fixed slice is as likely to catch a runner's footer as its error. The style that inlines logs is named in the closing line. It is the default when `isAiAgent()` and no style was given. That resolution sits in the existing yargs middleware chain, after NX_DEFAULT_OUTPUT_STYLE and before the TUI check, so an explicitly requested style always wins and the TUI correctly declines. Deciding it at life cycle selection instead would have skipped NX_DEFAULT_OUTPUT_STYLE and landed after `--output-style` was normalized. `terminalOutputPathForHash` is shared from `tasks-runner/cache` so the renderer can address a log without holding a cache instance; it mirrors the native layout, which the legacy cache already agreed with.

nx run-many -t check-imports check-lock-files check-codeowners --parallel=1 --no-dte

Succeeded

4 CPU cores

read-write access token used

d53b0cc636703

Get faster results

Learn how to enable distribution.

Atomizer enabled

1 group of tasks optimized.

© 2026 - Nx Cloud

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