Drupal AI Context Beta 4 Adds Selection and Governance Controls

Drupal editorial graphic titled "How Beta 4 Gives AI Better Context" with the supporting text "New controls help Drupal teams decide what AI agents can see rank and use." A context management interface ranks "Policy overview" at priority 90 "Funding guide" at priority 60 and "Expert insight" at priority 30 while a token meter shows "Context tokens 752 of 2000" to illustrate how Drupal teams can control which sources AI receives.

Beta 4 of Drupal AI Context, also known as Context Control Center (CCC), is now available with new controls for selecting, ranking, and governing context supplied to AI workflows. In a 17 August 2026 blog post published by Salsa Digital, Kristen Pol, project lead for AI Context and program manager for the Drupal AI Initiative, said the project is moving towards its first release candidate. Drupal.org release notes list 70 credited issues in 1.0.0-beta4, including eight new features and nine bug fixes.

The update adds a Taxonomy scope plugin that associates context items with taxonomy terms on Drupal content, while a High, Medium, or Low Priority field influences selection order when several items are eligible. Agents can be configured to opt out of automatic context injection while retaining tool-based retrieval, and the previous maximum-items setting has been removed; selection is now governed by the token budget and global-item limit. Context items now have a dedicated Draft, Published, and Archived editorial workflow, separate from other site content. The administration interface also stores estimated token counts and shows how context items and agent subscriptions relate to configured token budgets.

Beta 4 promotes the Document Loader: Context File Importer submodule from experimental to stable and restores Drupal 10 and PHP 8.1 compatibility after problems introduced in beta 3. The Drupal.org release notes list support for Drupal ^10.5 or ^11.2. Salsa Digital says Drupal 10 sites that upgraded to beta 3 should treat beta 4 as a required update and advises teams to run database updates and test upgrades in a non-production environment, particularly when using Document Loader, custom integrations, or configuration exported from an earlier beta.

In a separate interview with The DropTimes, conducted when beta 3 was the current release, Kristen said CCC gives teams greater control and traceability over the context supplied to a model but does not guarantee improved output. Salsa Digital also advises against using CCC in production while it remains in beta, and Drupal.org currently lists no supported stable release.

Disclosure: This content is produced with the assistance of AI.

Disclaimer: The opinions expressed in this story do not necessarily represent that of TheDropTimes. We regularly share third-party blog posts that feature Drupal in good faith. TDT recommends Reader's discretion while consuming such content, as the veracity/authenticity of the story depends on the blogger and their motives. 

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.

Related Organizations

Related People

Upcoming Events

Latest Opportunities