Daily Digest

Daily Digest – 29 June 2026

2026 Capabilities Progress

  1. Page generation — The AI agent can now work with block components and their properties, expanding the range of building blocks available for page generation [66][115]. Fixes were merged to resolve preview errors that disrupted AI-driven page creation [80][118].
  2. Context management — Work advanced on scope override functionality allowing sub-contexts to override parent settings, giving administrators finer control over how brand voice and style guides apply [120][127]. Work is in progress on a full-page view layout for context items [121][128], and accessibility issues affecting the interface are being addressed [124][125][129][130].
  3. Background agents — Two new agent skills were proposed to enable autonomous configuration of AI settings and guardrails [7][8], expanding agents' ability to operate without manual intervention. The meta issue tracking background agents remains active [23].
  4. Design system integration — A fix was in progress to properly compile JSX for AI-created code components, resolving rendering failures that prevented AI-generated components from displaying correctly [55][98]. The CLI tool now merges global asset library updates more efficiently [56][99].
  5. Content creation and discovery — Batch embeddings support progressed across multiple vector database providers, enabling faster indexing for AI-powered search [10][30][46][48][131][134][135]. The tone-of-voice CKEditor plugin now respects translated taxonomy terms [25][32], and improvements to the AI Writer interface are under review [16].
  6. Advanced governance — Client-side publishing now prevents users from overwriting changes when conflicts are detected [117], complementing backend conflict detection work. Guardrail capabilities expanded with semantic topic matching [14][31] and a new sensitive content stream guardrail for mid-stream evaluation [3].
  7. Intelligent website improvements — No direct progress today.
  8. Multi-channel campaigns — No direct progress today.

Shipped

  1. AI module deprecated field widget actions removed — Work is in progress to remove the bundled field_widget_actions sub-module and require the standalone project to eliminate namespace conflicts [4][26].
  2. AI module streaming HTML preservation being worked on — Work is in progress to preserve HTML tags during streamed translation workflows [5][27].
  3. AI module JSON schema element now works in off-canvas dialogs — Work is in progress to support the ai_json_schema form element in off-canvas dialogs, which will enable more flexible configuration interfaces [9][29].
  4. AI module tone-of-voice plugin now supports translated taxonomy — Work is in progress to make the CKEditor tone-of-voice plugin correctly use translated versions of linked taxonomy terms [25][32].
  5. AI Context module accessibility improvements in progress — Work is in progress to address multiple issues affecting screen reader access to tooltips, icons, and links [124][125][129][130].

Ongoing

  1. AI module batch embeddings architecture under review — A new first-class operation type for batch embeddings is being evaluated to enable faster vector database indexing [10][30].
  2. AI module semantic topic matching for guardrails in development — The RestrictToTopic guardrail is being enhanced to match topics by meaning rather than exact strings [14][31].
  3. Canvas AI chat message persistence issue under review — A fix to prevent in-progress chat messages from disappearing when page metadata is edited mid-run is awaiting merge [53][90].
  4. Canvas AI code component server-side compilation bug being addressed — AI-created code components currently fail to compile server-side and render incorrectly, with a fix in review [55][98].
  5. Reading Room Gold partner onboarding nearing completion — Most onboarding tasks are complete, with final audit and public listing steps remaining [33][34][35].

AI (Artificial Intelligence)

Development continues on the AI module with progress across user interface improvements, architectural enhancements, and tooling for agent-driven configuration. Several items moved forward during the period.

Work on batch embeddings for improved indexing performance advanced with a new merge request that introduces batch embeddings as a first-class operation type, preserving backward compatibility while enabling faster vector database indexing. This change enables multiple chunks to be processed simultaneously rather than sequentially, addressing performance bottlenecks in search indexing workflows.

Two new agent skills were proposed to allow AI-driven site configuration: setup-guardrails and configure-ai-settings. These would enable agents to configure operational settings and guardrails via command-line tools rather than requiring manual admin UI interaction, expanding autonomous agent capabilities. Both issues have been assigned for development.

A fix for preserving HTML in streamed output is under review, addressing an issue where HTML tags were being malformed during translation workflows. A merge request to support translated taxonomy terms in the CKEditor tone-of-voice plugin was also opened. Work continued on adding semantic topic matching to the RestrictToTopic guardrail, allowing topic matching by meaning rather than exact string comparison.

The bundled field_widget_actions sub-module, already deprecated, is now being fully removed to eliminate namespace conflicts with the standalone project. A merge request removing 34 files and adding the standalone package as a dependency was opened. Issue tracking for dark-theme rendering bugs in the Tool Explorer and MDX Editor, off-canvas dialog support for the JSON schema form element, and functional testing for AI CKEditor are all in progress.

How can I help on this project?

  • Prioritize review and sign-off on the batch embeddings architecture change to unblock indexing performance improvements for production sites.
  • Clarify acceptance criteria for autonomous agent configuration skills to ensure they align with broader automation and security strategy.

Contributors: Ahmad Khader (Ahmad-Khader), Ahmad Khalil (ahmad-khalil-imagex), Joshua Fernandes (joshua1234511), Pravesh Poonia (Pravesh_Poonia), Rob Loach (robloach), Thomas Werthmüller (weri)


Drupal AI Initiative

The Drupal AI Initiative completed foundational work on the AI CMS Demo System during this period. Four related work items were closed, covering repository setup and access configuration for partner organizations, the technical architecture defining how the system will be structured and maintained, the creation of a baseline demonstration instance, and the development of a hosting-specific implementation. This system will showcase AI capabilities integrated into Drupal CMS and provide a reference model for partners.

Onboarding continues for Reading Room, a new Gold partner. Most onboarding steps have been completed, with outstanding items including adding the partner to public-facing pages and conducting a follow-up audit to verify successful integration. Additionally, work is underway to convert partner onboarding templates to native GitLab formats to streamline future partner integrations.

Two infrastructure tasks were opened to configure domain name settings for the GitLab control server and module finder tool, which will support the initiative's technical operations.

How can I help on this project?

  • Ensure legal and invoicing contacts for Reading Room are provided to the Drupal Association to complete partner onboarding.
  • Review and approve marketing content for the Reading Room partner announcement on public-facing pages.
  • Confirm infrastructure resources are available to complete DNS configuration for initiative tools.

AI Integration - ECA

This module connects the AI Integration framework with Drupal's Event-Condition-Action (ECA) system, allowing automated workflows to incorporate AI capabilities.

Development work focused on expanding the range of AI operations available to automation workflows. A new task was opened to add support for text translation workflows, which would enable automated content translation using AI providers. This addresses a gap in the current offering, which already supports chat, embedding, content moderation, and speech conversion, but lacks translation capabilities. The addition would allow organizations to automate multilingual content workflows without custom development.

No code changes were merged during this period. The module remains in active development toward its 1.0.0 release. As an evolving integration project, open feature requests like this are a normal part of building out comprehensive coverage of AI operations.

How can I help on this project?

  • Clarify organizational priorities for which AI operations are most valuable to automate, to help the team sequence remaining feature work toward the stable release.
  • Consider allocating dedicated testing resources to validate AI workflow integrations as new operation types are added.

AI Agents Test

The AI Agents Test module saw limited activity in the past 24 hours. One research initiative examining the potential consolidation of testing infrastructure was closed. The Research: merging ai_agents_test with ai_eval (and AiLlm test harness) issue was resolved, which had been exploring whether multiple overlapping testing approaches in the Drupal AI ecosystem should be unified. This research is part of broader work to streamline how AI configurations are validated across different tools and modules.

No code changes were merged or committed during this period. The module remains in an exploratory phase as architectural decisions around testing infrastructure are being finalized.

How can I help on this project?

  • Clarify strategic priorities for testing infrastructure consolidation, ensuring the team has clear direction on whether to pursue integration or maintain separate tools.
  • Allocate resources to move from research to implementation once architectural decisions are confirmed.

OpenAI Provider

A new merge request has been opened to add support for batch embeddings. This enhancement will allow the module to process multiple embedding requests together, which can improve efficiency and reduce costs when working with OpenAI's services. Batch processing is particularly valuable for organizations handling large volumes of content or data that needs to be analyzed or indexed. The work is currently under review.

No other activity was recorded during this period.

How can I help on this project?

  • Prioritize review resources to evaluate the batch embeddings feature, ensuring it meets business requirements before merging.
  • Consider allocating budget for testing with realistic data volumes to validate cost savings from batch processing.

Contributors: Paul Sheldrake (paulsheldrake)


Anthropic Provider

A merge request was opened to address a compatibility issue affecting conversational AI features. When multiple AI agents pass control to one another, the conversation can end with a message from the system or assistant rather than the user. The Anthropic service rejects these conversations, causing failures in tools like Drupal Canvas AI. The proposed fix ensures conversations always end with a user message, preventing rejections and allowing multi-agent workflows to function smoothly. This work supports more sophisticated AI-powered features in Drupal.

How can I help on this project?

  • Prioritize testing and review of the conversational fix to ensure multi-agent AI features can ship reliably.
  • Assess whether additional integration testing resources are needed to validate complex AI workflow scenarios before release.
Contributors: Rajab Natshah (RajabNatshah)

Milvus VDB Provider

This module enables Drupal to work with Milvus, a vector database used for AI-powered search and content recommendations. It remains in active development as the team works to improve performance and scalability.

During this period, a new merge request was opened to add support for batching on indexing operations. This work will allow the system to process multiple pieces of content at once when building search indexes, rather than handling them one at a time. For sites with large content libraries, this should significantly reduce the time required to index content and improve system efficiency during content updates.

The merge request is under review. No bugs or blocking issues were reported during this period.

How can I help on this project?

  • Ensure the team has dedicated review capacity to evaluate and merge the batching functionality, which could deliver measurable performance improvements for content-heavy sites.
  • Clarify whether production deployment timelines require expedited testing resources for this indexing enhancement.

Contributors: Artem Dmitriiev (a.dmitriiev)


AI Image Alt Text

A merge request was opened to add support for newer versions of the Drupal AI module, which the AI Image Alt Text module depends on. This compatibility work ensures the module can continue functioning as its underlying dependencies evolve, maintaining access to AI-powered alternative text generation for images across newer Drupal environments.

The merge request is currently under review. Once integrated, this will allow sites using more recent versions of the AI module to adopt or continue using automated image accessibility features without compatibility constraints.

How can I help on this project?

  • Prioritize code review resources to evaluate and merge the compatibility update, reducing time to deployment.
  • Consider funding automated compatibility testing to catch dependency issues earlier in future development cycles.

Contributors: Peter Philipp (daspeter)


AI Agents

A bug was identified and addressed during this period that was causing warning messages to appear each time an AI agent ran. The issue, Array to string conversion in Token::doReplace() when a dynamical token value is an array (applyTokens), resulted from certain data values being incompatible with the text replacement system used by agents. This caused disruptive warnings to appear in the editing interface, affecting the user experience for anyone building or testing AI agent workflows.

A fix has been prepared and is under review. Once merged, this will eliminate the warnings and provide a cleaner, more professional interface for users working with AI agents in the Drupal Canvas editor.

The module remains in active development with normal iteration on quality and usability improvements as issues are discovered and resolved.

How can I help on this project?

  • Prioritize code review resources to merge the pending fix, ensuring a smoother user experience for teams testing AI agent functionality.
  • Consider expanding testing coverage or user feedback cycles to catch interface issues earlier in the workflow.

Contributors: Rajab Natshah (RajabNatshah)


Tool API

No development activity was recorded during this period. One issue remains under discussion: MapDefinitionNormalizer and ContextDefinitionNormalizer break REST serialization (same as #3568588), which affects how content is delivered through REST endpoints when the Tool module is enabled. This issue could prevent integrations that rely on REST APIs from functioning correctly. The problem is assigned and flagged for attention by the AI Initiative Sprint team, but no solution has been merged yet.

The module is currently in beta, and active work on compatibility issues like this is a normal part of maturing toward a stable release.

How can I help on this project?

  • Confirm whether REST API compatibility is a priority for planned integrations, and communicate urgency to the development team if needed.
  • Ensure the team has sufficient testing resources to validate fixes across different API configurations before the stable release.

Drupal Canvas

Over the past 24 hours, the project delivered several foundational improvements to AI functionality, conflict handling, and tooling quality. The AI agent's ability to work with block components was completed, enabling richer page-building capabilities. A longstanding issue causing unexpected errors during AI-driven page generation was resolved by consolidating how the system updates page fields during preview, improving reliability and user experience.

On the conflict-resolution front, the client-side publishing flow now prevents users from publishing changes when conflicts are detected, reducing the risk of overwriting edits made outside their session. This complements earlier backend work and moves the conflict-detection feature closer to full integration.

Guidelines for AI-assisted development were refined based on recent contributor experience, helping maintain code quality as the project scales. The CLI tool's output was cleaned up for consistency and better usability by both humans and AI agents. A test workaround was removed following an upstream fix, and several issues related to translation, auto-save behaviour, and component metadata were opened with merge requests already in progress.

Two bugs remain under investigation: a rendering issue affecting AI-created code components (which fail to compile server-side and display as [object Object]), and a problem where in-progress chat messages disappear when editing page metadata during an active AI run. Both have open merge requests.

How can I help on this project?

  • Prioritise review and merge of the two AI user-experience issues (chat messages disappearing mid-run, and code component rendering failures) to unblock quality improvements in the AI agent workflow.
  • Evaluate whether conflict-resolution UI work should be resourced for faster integration, as the backend and client-side pieces are now largely in place.

Contributors: **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Abhishek Dhariwal (adaptative), AKHIL BABU (AkhilBabu) [2], Andrew Belcher (andrewbelcher), Bálint Kléri (balintbrews) [1], Chandan Singh (chandu7929), Christian López Espínola (penyaskito), Feliksas Mazeikis (f.mazeikis), Gábor Hojtsy (goba), Kunal Sachdev (kunal.sachdev) [1], Narendra Singh Rathore (NarendraR), Rajab Natshah (RajabNatshah), Ravi Maniyar (ravi.maniyar.123) [1], Ted Bowman (tedbow), utkarsh_33 (Utkarsh_33), Wim Leers (wimleers) [2]


Context Control Center (CCC)

The project is nearing its first release candidate and work over the last 24 hours has concentrated on refining user experience and accessibility ahead of that milestone. Two key areas of functionality progressed: a new full-page view layout for context items that improves readability and navigation, and a feature that allows sub-contexts to override their parent's scope settings, giving users more control over how context is applied. Both have open merge requests undergoing final review and testing.

Separately, work began on improving accessibility across the module's interface. Issues related to tooltip and icon-only content and interactive and external links both saw new merge requests opened to address best-practice findings. A third merge request corrected a minor configuration inconsistency and outdated documentation. These changes ensure the interface is usable by screen readers and assistive technology.

A broader tracking issue, Fix CCC issues based on AI Best Practices results, has been opened to coordinate outstanding items flagged by automated review. Most are non-blocking enhancements, with only a handful affecting configuration or public interfaces. Normal for pre-release software, these will be resolved in parallel with final testing.

How can I help on this project?

  • Prioritize manual testing and sign-off for the two open layout and scope override features currently awaiting final validation.
  • Ensure design and UX stakeholders are available to review the context importer naming and extensions page changes outlined in this issue.

Contributors: Eric Homanchuk (erichomanchuk), Joshua Fernandes (joshua1234511), Kristen Pol (kepol), Pravesh Poonia (Pravesh_Poonia)



Field Widget Actions

No code changes or merge activity occurred during this period. One feature request remains under discussion: Generate UUIDs for list-style widget-action settings applied via config actions. This work would allow recipes to declare multiple action buttons on a single form without conflicts, enabling each button to target its own field correctly. Currently, hard-coded identifiers cause all buttons to write to the same location, limiting the flexibility of automated configuration deployment.

The issue is part of the AI Initiative Sprint and has been assigned for development, but no implementation has been submitted yet. Progress on this feature would improve the experience for teams deploying AI-assisted content editing tools at scale.

How can I help on this project?

  • Clarify priority and timeline expectations for the unique identifier generation feature to help focus development effort.
  • Ensure the assigned developer has protected time and necessary access to move the work forward this sprint.

Pinecone VDB Provider

The Pinecone VDB Provider module enables organizations to integrate with Pinecone, a vector database service used to power AI-driven search and recommendation features. During this reporting period, work began on improving how the system handles large-scale data indexing operations.

A proposal to support batching on indexing operations was opened for review. Currently, indexing large volumes of data into Pinecone can be inefficient. The proposed enhancement would process data in batches, improving performance and reliability when populating the vector database with content. This matters for sites with substantial content libraries or those planning to scale their AI features, as it reduces processing time and resource consumption. The approach is inspired by similar work in a related provider, demonstrating alignment with broader platform improvements.

No code changes were merged during this period. The batch indexing work is currently awaiting review.

How can I help on this project?

  • Allocate reviewer capacity to evaluate the batching implementation currently awaiting feedback, accelerating its path to production readiness.
  • Clarify performance requirements or scaling targets for the vector database integration to help prioritize optimization work.

Contributors: Rob Loach (robloach)


AI powered Search Block

Development activity this period focused on safety and content moderation capabilities. A new merge request was opened to add guardrail set selection to the module, spanning approximately 800 lines of changes. This feature will allow administrators to configure safety boundaries and content filtering rules for AI-powered search interactions, helping organizations maintain appropriate user experiences and reduce risk of inappropriate or off-brand responses.

The work remains in review and has not yet been integrated into the module. No other development activity, issue updates, or commits occurred during this period.

How can I help on this project?

  • Ensure the team has access to code review resources to assess and merge the pending guardrail functionality.
  • Clarify organizational requirements for AI content moderation to guide feature prioritization and testing.
  • Consider allocating quality assurance support to validate safety controls before wider deployment.
Contributors: Abhisek Mazumdar (abhisekmazumdar)

AG-UI

No significant activity was recorded for AG-UI during this reporting period. The module's development continues with an open meta issue tracking improvements to the Drupal Assistant Implementation. This work aims to evolve a proof-of-concept conversational interface into a production-ready feature that could replace an existing chat component. The effort involves refining how the assistant handles requests and aligns with backend services, which would improve the user experience for site editors and administrators seeking contextual help.

No merge requests were completed, commits were made, or status changes occurred in the last 24 hours. This is normal for an actively developed module between work cycles.

How can I help on this project?

  • Confirm strategic priority: clarify whether the Drupal Assistant feature aligns with near-term product goals and allocate developer capacity accordingly.
  • Support cross-team coordination: ensure alignment between AG-UI and AI module teams to avoid duplication and enable shared infrastructure.

References

[1] Tool Explorer does not render correctly with Gin dark theme (ai, Issue)

[2] MDX Editor does not render correctly with Gin dark theme (ai, Issue)

[3] Add SensitiveContentStream guardrail and kernel test for StreamableGuardrailInterface mid-stream buffering and evaluation (ai, Issue)

[4] Remove the deprecated bundled `field_widget_actions` sub-module (it collides with the standalone project) (ai, Issue)

[5] Preserve HTML in streamed output (ai, Issue)

[7] Add a configure-ai-settings agent skill for general AI settings (default models, providers, timeout, trusted domains) (ai, Issue)

[8] Add a setup-guardrails agent skill to configure guardrails, guardrail sets, and global guardrails (ai, Issue)

[9] Support the `ai_json_schema` element inside off-canvas dialogs (ai, Issue)

[10] Batch embeddings for improved indexing performance (ai, Issue)

[14] RestrictToTopic guardrail: add semantic topic matching mode (ai, Issue)

[16] ai_ckeditor: Add option to show or hide the "AI Writer" status information (ai, Issue)

[23] [META] AI background / autonamous agents (ai, Issue)

[25] Tone of voice CKEditor Plugin does not use the translated version of the linked taxonomy (ai, Issue)

[26] Issue #3586556: Remove deprecated bundled field_widget_actions and require standalone. (ai, MR)

[27] Resolve #3586558 "Preserve HTML in streamed output" (ai, MR)

[29] Issue #3586536 Support the `ai_json_schema` element inside off-canvas dialogs (ai, MR)

[30] Issue #3568648: Batch embeddings as a first-class operation type (follow-up to !1704) (ai, MR)

[31] Issue #3584977: RestrictToTopic guardrail: add semantic topic matching mode. (ai, MR)

[32] fix: #3586573 Tone of voice CKEditor Plugin does not use the translated... (ai, MR)

[33] Onboard Gold AI partner: Reading Room (ai_initiative, Issue)

[34] Run AI partner audit report: Reading Room (ai_initiative, Issue)

[35] Add Gold AI partner to d.o pages: Reading Room (ai_initiative, Issue)

[46] add support for batch embeddings (ai_provider_openai, MR)

[48] add support for batching on indexing operations (ai_vdb_provider_milvus, MR)

[53] Canvas AI: In-progress chat messages disappear when editing page metadata during an active run (canvas, Issue)

[55] canvas_ai: AI-created/edited code components render as [object Object] (compiledJs left empty, never compiled server-side) (canvas, Issue)

[56] Merge global asset library updates into one PATCH in CLI push (canvas, Issue)

[66] Canvas AI: Expose Props of Blocks to the Agent (canvas, Issue)

[80] Canvas AI: An unexpected error has occurred while rendering preview (canvas, Issue)

[90] Issue #3591731: Keep in-progress AI chat messages when page metadata is edited mid-run (canvas, MR)

[98] fix: #3591751 Compile JSX server-side for AI-created code components (canvas, MR)

[99] chore(CLI Tool): #3591750 Merge global asset library updates into one PATCH in CLI push (canvas, MR)

[115] Issues/3569120: Canvas AI: Expose Props of Blocks to the Agent. (canvas, MR)

[117] feat(Conflict detection): #3587526 "Client side prevention of publishing" (canvas, MR)

[118] Issues/Canvas AI: An unexpected error has occurred while rendering preview (canvas, MR)

[120] Allow subcontext scope to override parent scope (ai_context, Issue)

[121] Add full view layout for context item canonical and revision pages based on new design (ai_context, Issue)

[124] Clean up CCC tooltip, truncation, and icon-only content (ai_context, Issue)

[125] Clean up CCC accessible interactive links and external links (ai_context, Issue)

[127] Issue #3586218: Allow subcontext scope to override parent scope. (ai_context, MR)

[128] Issue #3586220: Add single context item display. (ai_context, MR)

[129] Issue #3586302: Exposed tooltip/truncated content and icon meaning to assistive tech. (ai_context, MR)

[130] Issue #3586301: Clean up CCC accessible interactive links and external links. (ai_context, MR)

[131] Batch embeddings for improved indexing performance (ai_search, Issue)

[134] Support batching on indexing operations (ai_vdb_provider_pinecone, Issue)

[135] Issue #3586209: Add support for batching on indexing operations (ai_vdb_provider_pinecone, MR)


Period: 29 June 2026 to 30 June 2026  |  Generated: 30 June 2026 05:00 GMT

To view the full AI prompts used to generate this digest check this file: 24h_2026-06-29_prompts.txt

Looking for older digests? Browse all digests here.