Pinned Tweet
If CI has been a struggle recently, watch this!
(and more is already in the pipeline)

0:00 - Intro
1:18 - The CI bottleneck
3:31 - VM minutes and utilization
4:11 - Dynamic Task Packing
5:49 - Task-based affected
7:32 - Ultracache
8:59 - Benchmarks
9:37 - Intelligent CI
1
5
11
1,077
Replying to @NxDevTools
And, for those who've been asking... stay tuned
0
0
1
198
Nx retweeted
Turned on @NxDevTools dynamic task packing in our CI: no more fixed --parallel, tasks land on agents by measured CPU + memory.

Full runs (~3.6k tasks):
⏱️ 15.8 → 12.9 min
💸 −18% agent-min
🔥 Agent CPU 37% → 51%
🧠 Peak RAM 57% → 77%
6
4
18
3,021
The Future of CI x.com/i/broadcasts/1…
0
3
6
762
Nx retweeted
Prepping for this Thursday..

(also, no, we're not announcing a new Nx OneWheel...maybe we should 🤔)

nx.dev/events/2026-oc…
2
1
10
1,443
Launching today. Tune in youtube.com/watch?v=3xd51m…
1
13
18
3,118
Tomorrow: we're fixing CI for the agent era.

Live at 10 a.m. PT / 1 p.m. ET. Grab the link to catch it live: nx.dev/events/2026-oc…
0
1
14
1,167
Agents mean more code, more PRs, more pipeline runs.

Oct 22, live:
→ Nx: updates so every run does less work
→ Nx Cloud: next-gen caching and distribution. Faster CI, less compute.

All available the same day. Save your spot: nx.dev/events/2026-oc…
0
2
11
1,583
🚀 Nx 23.3 is out.

- Task-based nx affected
- Agent-friendly task output
- Batched Oxlint runs
- Faster project graph creation
- Cypress 16, Vitest 5, pnpm 12

And more. All the details 👇
nx.dev/blog/nx-23-3-r…
1
8
54
7,557
Replying to @NxDevTools
Full video walkthrough here:

youtu.be/bNQ1svSw8VY
1
0
1
279
Replying to @NxDevTools
One more thing: on Oct 22nd we're hosting a product event with a big announcement about scaling CI for the flood of PRs and tests your agents produce.

Register here 👇
nx.dev/events/2026-oc…
0
0
2
174
CI was built for humans. Agents changed that.

On Oct 22, we're showing how to make CI keep up without burning more compute.

Register here: nx.dev/events/2026-oc…
0
3
9
1,298
Nx v24 lands in a few weeks and drops the built-in executors, now replaced by inferred targets.

Inferred targets use your tool’s own config to get runnable targets and cache inputs/outputs.

@meeroslav got you covered with all the details:

nx.dev/blog/look-mum-…
1
4
41
2,726