Drupal AI Context RC1 Focuses on Reliability Ahead of 1.0

Following five beta releases, Drupal AI Context, also known as Context Control Center, entered its release-candidate phase with 1.0.0-rc1 on 25 September 2026. Kristen Pol, project lead for AI Context and a program manager for the Drupal AI Initiative, detailed the release in a 5 October post published by Salsa Digital. The project currently has no supported stable release.

Context Control Center provides a shared layer for information that Drupal AI features need to use consistently. Sites can centrally manage material such as brand voice, editorial standards, organisational knowledge and governance rules instead of maintaining separate instructions for each AI integration.

RC1 covers 62 credited issues and shifts the emphasis toward release readiness. Drupal.org says the release focuses on making the administrative interface and context selection reliable enough for production trials, following a broader QA pass across context items, scopes, settings, agents, automators, AI CKEditor, Drupal 10 and upgrades.

Admin and Context Selection Get More Attention

Administration changes target sites with larger context libraries. Searches on the Context items and Consumers listings now match individual words separately, while the Consumers listing adds filters for type and automatic context push. Consumer types can inherit the site's selection mode by default, and context-item listings keep parent and child rows together across pages.

RC1 also changes how context is resolved and stored. Situational scopes now work correctly for API-proxy consumers such as AI CKEditor, while Tag and Taxonomy scope values are stored as entity UUIDs to make configuration more portable between environments. Subscribed-scope prefiltering was also changed so it no longer scans every published context item ID.

QA Covers Upgrades and Edge Cases

The release includes fixes found during a pre-RC QA pass. Drupal.org lists issues involving agent editing, upgrades from earlier releases, Markdown document loading, configuration validation, conditional subcontexts and Drupal 10 compatibility among the areas addressed.

The release also removes an unused revision setting because context items always create revisions, and it fixes several administrative errors that could produce white screens or broken status reports in particular upgrade and editing scenarios.

Integrations Continue Beyond AI Agents

The broader consumer model introduced during the beta cycle is intended to let the same governed context reach more Drupal AI features. AI CKEditor already supports Context Control Center, allowing shared guidance to be used during AI-assisted editing.

Integrations with AI Translate and AI Validations are still developing. Salsa Digital says the aim is to let those features reuse centrally managed guidance such as glossaries, protected terminology and validation-specific context rather than maintaining separate instructions for each tool.

The project team is asking users to test upgrades, context selection, configuration import and export, document loading and larger context libraries before the stable release. AI CKEditor testing in editorial workflows is also encouraged.

Pol said the team is planning Drupal AI Context 1.0 for about a month after the October 5 update, depending on what emerges from RC testing. A second release candidate may be issued before the stable release.