Local AI for Drupal update planning means running a large language model on your own server, alongside deterministic Drupal tools, to help interpret what a module scan finds before you commit to a major version upgrade. The model never decides compatibility by itself — it reads the output of real checks and explains what the result means, while the checks themselves still run entirely offline.
That distinction matters because Drupal's update tooling already does the hard, factual work without any AI involved. The contributed Upgrade Status module scans a site's installed custom and contributed modules, running PHPStan-based deprecation checks against the next major core version and reporting the results on a Reports page or through `drush upgrade_status:analyze`. Adding local AI on top is about making those findings easier to act on, not about replacing them.
Table of Contents
- What "testing advice against installed modules" actually means
- Why the AI commentary needs its own skepticism
- Running the model locally instead of sending code to a cloud API
- Why update planning can't wait for perfect tooling
- Tracking fixed versions across branches, not just "the latest"
- Frequently Asked Questions
What "testing advice against installed modules" actually means
Upgrade Status answers one narrow question: does a specific module's code use anything that the next major Drupal core version removes or changes? It does this with static analysis, not guesswork, which is why its findings are treated as ground truth rather than suggestions. A newer contributed tool, AI Drush Tools, adds a Drush command, `ai:module-check`, that checks one installed module's upgrade path to the next major core version.
Its deterministic checks work without AI at all — the AI layer is optional and only appends commentary on migration risk, pitfalls, and next steps. The practical workflow is to run the deterministic scan first, get a list of flagged modules, and then ask a local model to summarize what each flag likely means for your specific site — translating a PHPStan error into a sentence a project manager or client can read. The model is doing explanation, not detection.
Why the AI commentary needs its own skepticism
AI Drush Tools' own project page states plainly that the module sits outside Drupal's security advisory coverage and should be used at your own risk, and it reports adoption on only one or two sites so far, according to the module's Drupal.org listing. That's a small sample, and it means the AI-generated advice has not been stress-tested across a wide range of real codebases. Treat anything the AI layer says about "migration risk" or "next steps" as a second opinion, not a verdict.
If the deterministic check says a module is incompatible, that's the fact to act on. If the AI commentary disagrees with, softens, or elaborates on that fact in a way that doesn't match what you see in the actual deprecation report, trust the report. This is the core discipline of the whole approach: deterministic Drupal.org tooling tells you what's true about your code; AI commentary tells you how to think about what's true. Reversing that order — letting a model's narrative override a static-analysis result — is where this kind of workflow goes wrong.
Running the model locally instead of sending code to a cloud API
Drupal's official ai_provider_ollama module connects Drupal's core AI module to a self-hosted Ollama server, so inference happens offline rather than through a third-party API. It needs only the core AI module as a dependency, and connection details go in at `/admin/config/ai/providers/ollama`, with credentials stored through the Key module. For teams that don't want module names, custom code excerpts, or client site details leaving their own infrastructure, this is the main appeal.
The commentary AI Drush Tools generates about a module's upgrade risk never has to reach an external vendor's servers — it's processed by whatever model you've loaded into Ollama, on hardware you control. The tradeoff is that local models are generally smaller and less capable than the largest cloud-hosted ones, so the commentary should be read as a helpful first pass rather than an expert migration plan. Pair it with the deterministic scan results and your own read of the Drupal core change records for anything flagged as high-risk.
Why update planning can't wait for perfect tooling
Drupal update planning has urgency beyond routine maintenance. The Drupal Security Team's PSA-2026-10-12 announced a critical core security release for all supported branches on 14 October 2026, rated 19 out of 25 on the project's risk calculator, and told site owners to update to their branch's latest patch release beforehand, according to Drupal.org's security advisories page. That release became SA-CORE-2026-014 (CVE-2026-108097), a critical remote-code-execution flaw in core's Field UI module affecting versions from 8.9 onward, fixed in 10.6.19, 11.3.19, and 11.4.10, as reported in adevweb.com's security brief.
Core alone isn't directly exploitable, but installed contributed modules or custom code can expose the vulnerable path — which is exactly the kind of interaction a module-level compatibility scan is built to catch. The same October 2026 batch included a critical access-bypass and RCE advisory for the contributed Entity List module (CVE-2026-108099, also rated 19 out of 25), with the Security Team recommending an upgrade to Entity List 3.0.10 for any site running it, according to TheDropTimes. Two unrelated critical advisories landing in the same window is a reminder that update planning tools need to track every installed module, not just core.
Tracking fixed versions across branches, not just "the latest"
A single "latest version" number isn't enough to plan around, because Drupal fixes get backported across active branches at different patch levels. Earlier in 2026, SA-CORE-2026-004 (CVE-2026-9082) fixed a highly critical SQL injection in Drupal core 11.3.10, a fix that applied specifically to the 11.3.x branch rather than a single universal release number, as reported by TheDropTimes.
Any update-planning workflow — AI-assisted or not — has to check which branch a site is actually running and confirm the specific patch release for that branch, rather than comparing against a generic "current version" figure. A module-check command that reports compatibility with "the next major version" is answering a different question than "is this site on a patched release," and both checks belong in the same planning pass. Running Upgrade Status or AI Drush Tools' deterministic check alongside a branch-specific security audit gives a fuller picture: one tells you whether your code will survive the jump to the next major version, the other tells you whether the version you're on right now is already exposed.
Frequently Asked Questions
Does the AI commentary in AI Drush Tools replace the deterministic compatibility check?
No. The module's deterministic checks run without AI and produce the actual compatibility result; the AI commentary is an optional add-on that explains risk and next steps.
Is AI Drush Tools covered by Drupal's security advisory policy?
No. The module's own project page states it falls outside that coverage and should be used at your own risk, per its Drupal.org listing.
What does ai_provider_ollama require to run locally?
Only Drupal's core AI module as a dependency, with the Ollama server's connection details entered at `/admin/config/ai/providers/ollama` and credentials stored via the Key module, per its project page.
Why does a security advisory matter for update planning if core itself isn't directly exploitable?
Because installed contributed modules or custom code can still expose the vulnerable path core introduces, as noted in adevweb.com's brief on SA-CORE-2026-014.




