Self-Healing CI has had auto-apply for a while. You tell it which tasks are safe to fix automatically, and when CI fails on one of those, Self-Healing pushes the fix straight to your PR branch without waiting on you. The tricky part has always been figuring out which tasks in your workspace are actually good candidates.
We just shipped a feature to help with that: auto-apply suggestions. Nx Cloud now monitors your Self-Healing activity and recommends tasks that look safe to auto-apply, based on your actual CI history.
Quick recap: Self-Healing and auto-apply
Self-Healing CI detects failing tasks on your PR, generates a fix with an agent, verifies it by re-running the broken task, and pushes the suggested fix back to your PR for review.
Auto-apply is a setting on top of that. Instead of waiting for you to review, Self-Healing commits the verified fix directly to your PR branch. You can configure it in your Nx Cloud dashboard (Settings > Self-Healing CI > Auto-apply verified code changes). Common presets cover Nx sync checks, conformance checks, and format checks, and you can add custom targets for your workspace.
Previously you could also configure auto-apply via flags in your CI configuration. That still works, but the dashboard approach is faster to set up and easier to manage across your team.
Auto-apply suggestions tailored to your pipeline
In an ideal world, you'd always just auto-apply. The fact that Nx's Self-Healing only does it when its verification step passes already gives you some level of confidence, but as we all know, it is not always as straightforward. Sometimes AI agents still make things up to get that test case to pass.
That said, there are some tasks almost everyone has in their repo for which using auto-apply is a no-brainer. Things like linting, formatting, or the Nx sync command. If these fail, auto-applying is pretty straightforward. For some of them, triggering the CLI command directly is enough, like --fix for linting (which Self-Healing does).
But you might have other, custom tasks which could be good candidates for being auto-applied and thus speed up your CI cycle time (time to green, or TTG).
To help find those, Nx Cloud now tracks which tasks Self-Healing has been fixing successfully and nudges you when there's an opportunity to enable auto-apply.
When you open a PR and Self-Healing has been active, you might see a notification in the GitHub comment about pending recommendations.
Clicking that link takes you to the Self-Healing CI settings page, where a new suggestions panel appears at the top.
The suggestions panel shows:
- Which tasks could be added to auto-apply
- How many times Self-Healing has fixed that task
- Verification rate: how often the fix passed on re-run
- Confidence level: an overall indicator of how safe it is to auto-apply
For example, if your workspace has a check-links task that has been fixed five times by Self-Healing with a high verification rate, the suggestion panel will recommend enabling auto-apply for it.
Why auto-apply?
The whole point of Self-Healing CI is to improve the time to green (TTG) on your CI pipeline and remove the burden from the developer. As such, the more tasks you auto-apply the more value you get out of it. Every task you add to auto-apply is one less interruption.
Also, there's nothing more satisfying than coming back to a PR to check its state, seeing that there was a failure, it got fixed, added to your PR and another CI run already succeeded.
With this new auto-apply suggestions feature we aim to help you figure out candidates easily, which would otherwise be tricky and require quite a bit of analysis of your runs and applied fixes.
Next time you open a PR and see a pending recommendations link in the Nx Cloud comment, give it a look. And if you haven't set up Self-Healing CI yet, here's how to enable it for your workspace.
