In the last year Nx has grown. Monthly NPM downloads hit 36 million (up 63% from a year ago). We shipped first-party plugins for Docker, .NET, Maven, Angular rspack, and rsbuild. We released an entirely new Terminal UI with better support for Continuous Tasks, and the Nx MCP server.
On the platform side we released new analytics, optimized task distribution, resource tracking, and launched Self-Healing CI.
2026 is the year Nx becomes infrastructure for autonomous AI agents.
We're embedding AI agents directly into the Nx Platform that understand your entire codebase, optimize your builds without human intervention, and make architectural decisions alongside your team. Not AI features bolted onto existing tools - autonomous capabilities built on full codebase intelligence.
Why Nx Matters for AI Agents
Monorepo architecture makes this possible because agents perform better when they can see more. A monorepo puts all relevant code in one place. An agent can read frontend, backend, and shared libraries together, deduce best practices, and make a single PR touching dozens of projects.
But monorepos at scale are hard. Without the right tooling, CI becomes slow and the agent's context gets overwhelmed. Think of it like bandwidth. A 56k modem and fiber optic can both load a webpage, but only fiber lets you stream 4K video. Nx is bandwidth for agent context.
Here's the chain:
- Staying competitive requires effective use of AI agents
- Effective agents require autonomy
- Autonomy requires seeing and updating code across projects and incorporating CI into the agent's loop
- Cross project integration requires either a monorepo or infrastructure connecting multiple repositories together (synthetic monorepo)
- Making either work requires CI that's fast, reliable, and integrated with the agent
Nx is building the infrastructure to make this chain work end-to-end.
Self-Healing CI Evolution: Erasing the Divide Between Local and CI
Self-Healing CI fixes failures automatically. Nx analyzes what went wrong, generates a fix, validates it, and applies it if confident. For many clients, over 50% of generated fixes are useful, and developers save more time from self-healing than from caching and distributed task execution combined.
Additional self-healing features coming in 2026:
- Optimized LLM-based flaky task detection
- Composing multiple unrelated fixes
- Ability to tweak fixes that are almost right
But, what we're most excited about this year is Local-to-CI integration. When a CI failure occurs, context flows back to your local agent automatically. Instead of you context-switching to diagnose the problem, the agent sees what failed and why. It iterates on a fix and pushes again. The agent stays in flow.
We have an early version of this integration in this video.
Org-Wide Agentic Intelligence: Erasing The Repo Divide
Most AI agents have a blind spot: they only see one repository at a time. When a change in Repo A affects Repo B, the agent has no visibility. Only senior engineers with deep system knowledge can safely execute large cross-repo changes.
Monorepos, Polyrepos, and Synthetic Monorepos
Monorepo: A single repository containing multiple projects, enabling shared tooling and cross-project visibility.
Polyrepo: Multiple separate repositories, each containing one or more projects, with boundaries between them.
Synthetic Monorepo: Code remains stored in multiple repositories like a polyrepo, but Nx bridges the boundaries between repos, enabling cross-repo visibility and intelligence as an alternative to a full monorepo. It's monorepo benefits for people with a polyrepo setup.
Synthetic monorepos solve this by extending Nx's project graph across repository boundaries. Think of it like a team of engineers, one from each repo, sitting in the same room. Each brings knowledge of their repo, and together they can coordinate. That's what synthetic monorepos enable for agents: the benefit of monorepos without having a full monorepo.
Expanding the scope of agent autonomy: Agent capabilities have evolved in stages: first they could edit a line, then a block, then a file, then an entire repo. Synthetic monorepos take this to the organizational level. An agent can now reason about and modify code across your entire codebase, regardless of how it's split across repositories. This drastically reduces unnecessary human coordination. Changes that used to require meetings, Slack threads, and manual PR coordination can now happen in a single agent session.
This is how it works: A parent/orchestrator agent coordinates with cloud agents to make coherent changes across repos, then automatically submits pull requests. The Nx Platform tracks those PRs and their CI executions. If one fails, the parent agent receives context and re-evaluates its approach.
Agentic Migrations
nx migrate has been one of Nx's most loved features for years, automatically updating configuration and deprecated APIs when you upgrade. But complex upgrades still require manual intervention, and coordinating across repositories takes weeks.
Agentic migrations remove these limits. AI agents handle nuanced code changes that rule-based migrations can't. Combined with Self-Healing CI, migrations become self-verifying. Combined with synthetic monorepos, they scale across repositories.
Improved Task Distribution Efficiency
Distributed Task Execution is getting smarter. In 2025, we added resource tracking that records CPU and RAM usage for every task. Now we're putting that data to work.
Instead of batching tasks upfront, Nx will continuously feed tasks to agents, keeping CPU and RAM utilization high. The system knows each task's resource profile and can determine in real time whether an agent can take on another task or is at capacity.
This means less idle time, better hardware utilization, and faster CI runs without more machines.
Task Sandboxing
Nx plugins automatically configure caching for the tools they support. This means caching in Nx tends to be set up more correctly than in build tools that require manual configuration. But there's still opportunity for misconfiguration or mistakes, especially in complex repositories with custom build steps.
When caching goes wrong, you can get false negatives (cache misses when you should have hit) or, more dangerously, false positives (cache hits that return stale results). False positives are subtle and hard to detect. They've led several organizations to disable caching entirely on their main branch, sacrificing significant performance gains for safety.
Sandboxing eliminates this concern. During CI execution, Nx traces every file operation. If a task reads from or writes to files outside its declared inputs and outputs, the build fails with an error.
Think of it like a security camera for your build. If something accesses files it shouldn't, you'll know immediately.
Enterprise Observability
Nx collects significant data about your CI, but much of it isn't easily accessible externally. Enterprises using Datadog or other observability platforms have had to build their own tooling to extract and upload data.
What's coming:
- Prometheus integration and direct integration with observability platforms
- Richer insights in the Nx Platform UI for understanding build performance
Polyglot Expansion
Many organizations work across languages but have little to integrate them. We're doubling down on polyglot support.
What's coming:
- Python language and tooling support
- Further C#/.NET improvements (building on
@nx/dotnet) - Improved Gradle and Maven support
- mise integration for managing native toolchains
What languages we support next depends on what you need. Let us know.
Incremental Project Graph Hydration
In polyglot monorepos, building the full project graph requires tooling for every language in the repo. A JavaScript developer needs Java and .NET installed just to compute the graph, even if they never touch those projects.
We're introducing lazy graph hydration: a minimal project graph that only expands nodes when needed. Work on your JS projects without installing tooling for languages you don't use.
We're keeping up with the next wave of JavaScript tooling. We're watching the ox ecosystem (oxlint, oxfmt) and Biome closely. These tools are fast, and we're bringing them into Nx workspaces.
We're also ensuring Nx stays aligned with ESM as more tools become ESM-only.
What's Next
We'll share more details as features land. In the meantime, let us know what you're building and what you need. You can find multiple ways to stay in touch on our community page.