Daily Digest
Daily Digest – 25 June 2026
2026 Capabilities Progress
- Page generation — Progress continues on Canvas AI capabilities, with work advancing on exposing block properties to agents [107] and UI improvements for long-running AI tasks during page builds [108]. Work continues on component context and preview rendering, with issue [100] about hardcoded component source IDs closed [100], while issues remain open for required props missing required flag [99] and preview rendering failures [101].
- Context management — Significant progress in the Context Control Center, with four key issues closed including fixes to scope form configuration [136], public API access for scope subscription forms [134], and proper support for third-party extensions via hook_ai_context_scope_values_alter [137]. Work is in progress on a new agent skill to configure guardrails [9][44], which will provide programmatic control over governance rules.
- Background agents — Work continues on fundamental agent infrastructure, including improvements to automator documentation [24][49] and discussions on agent architecture patterns [12][14][16]. Process system integration for automators is under active development [15], which will enable agents to respond to triggers and scheduled events.
- Design system integration — Canvas delivered critical translation infrastructure ensuring component instances remain synchronized across all language variants when definitions change [113], and strengthened validation to catch component tree health issues [87][103][104]. The system now properly handles component version updates across multilingual content [88][93].
- Content creation and discovery — Multiple advances across the stack: work is in progress on batch embeddings for faster indexing in AI Search [158][159] and developed for OpenAI [66] and Milvus [75] providers; work is in progress on an AI reranking processor for Search API [28]; and Field Widget Actions interactive refinement capability has been merged [161][165], allowing users to iteratively improve AI-generated content before insertion.
- Advanced governance — No direct progress today, though foundational work on agent guardrails configuration [9][44] and context scope management [134][136][137] provides infrastructure that governance features will build upon.
- Intelligent website improvements — No direct progress today, though agent tool execution limits [80] and improved error handling in the Tool API [84] represent foundational work toward systems that can propose and track changes over time.
- Multi-channel campaigns — No direct progress today.
Shipped
- AI module: Token usage preserved in streaming chat — A fix was merged to prevent loss of cost tracking data during streaming chat operations [38][55][56][57][58][59][60].
- AI module: Content Suggestions separated into standalone project — The AI Content Suggestions module was removed from the core AI module to enable independent development [10][45].
- AI module: Prompt Library relocated for better discoverability — The Prompt Library menu item was moved under AI Infrastructure, improving navigation for site builders [21][46][47][48].
- AI module: Vector database default provider capability — Vector database providers can now opt in as the default when none is configured, reducing manual setup [39][61].
- Field Widget Actions: Interactive refinement now available — Users can review and improve AI-generated content in a modal dialog before inserting it into fields [161][165].
Ongoing
- AI module: Batch embeddings under development — A new operation type to process multiple embedding requests together is under review to accelerate indexing performance [3][43].
- AI module: Provider warnings and configurable messages — Work continues on clearer warnings when no AI provider is installed and customizable agent delegation messages to reduce user confusion [4][32][42][53].
- Canvas: Translation synchronization delivered — Automatic version updates for component instances now apply across all translations, ensuring language variants stay synchronized [88][113].
- Context Control Center: Beta polish and API stabilization — Multiple UI refinements and public API fixes were completed ahead of release candidate, including scope form improvements and third-party integration support [134][135][136][137].
- AI Related Content: Pinecone integration fixed — A critical bug preventing related content results when using Pinecone was resolved [176][178][179].
AI (Artificial Intelligence)
The AI module made progress on infrastructure improvements, bug fixes, and developer experience during the reporting period. Several foundational changes were merged that strengthen platform capabilities and correct issues affecting production use.
A critical fix was merged to preserve token usage data in streaming chat responses. Previously, when chat operations ran inside PHP Fibers, token usage information was lost during output reconstruction, preventing accurate cost tracking and observability. This issue now affects fewer deployments.
The AI Content Suggestions module was separated into its own standalone project, streamlining the core AI module and allowing independent development cycles. The Prompt Library menu item was relocated under AI Infrastructure where it belongs, improving discoverability for site builders. A new capability allowing vector database providers to opt in as the default was merged, matching behaviour already available to AI providers and reducing manual configuration.
Work continues on several front-end improvements: clearer user warnings when no AI provider is installed for CKEditor, and configurable agent delegation messages to avoid confusing terminology in chatbot interfaces. A batch embeddings operation type is under active development to accelerate indexing performance for vector databases.
How can I help on this project?
- Prioritise user-experience work flagged as "Needs UX review" — clearer provider warnings and hardcoded message fixes improve adoption but need design input.
- Support decisions on the deprecation and migration strategy for bundled submodules moving to standalone projects; this affects upgrade paths for production sites.
Contributors: Abhisek Mazumdar (abhisekmazumdar), Ahmad Khalil (ahmad-khalil-imagex), Ann Mary Sruthy (annmarysruthy), Arnaud Willame (arwillame), Artem Dmitriiev (a.dmitriiev), Dimitar Rupov (mrupal), Eric Homanchuk (erichomanchuk), Jérôme Tchania (codeitwisely), m4olivei, Ricardo Castañeda (cadence96), Sujal Kshatri (sujal_31), Wolfgang Ziegler (fago)
Drupal AI Initiative
The AI Initiative is focusing on making Drupal ready for external AI agents and automated systems while maintaining control and safety. The 2026 roadmap emphasizes building reliable foundations: identity management, permissions enforcement, schema validation, and audit trails that let organizations safely allow AI agents to perform real work within defined boundaries.
Over the past day, standardized issue templates for initiative work were finalized and closed. These templates will help contributors across all four initiative tracks (AI Core, Products, Marketing, and UX) create consistently structured issues for coordination, research, decisions, meetings, and community activities. This organizational infrastructure should accelerate collaboration as the contributor base grows.
The 2026 Outside-in / Innovation Roadmap remains in active planning. The strategy prioritizes making Drupal governable and auditable when external AI systems interact with it, rather than requiring organizations to use only Drupal-native AI tools.
How can I help on this project?
- Ensure sufficient resourcing is allocated to the identity and permissions work, which forms the security foundation for agent integration.
- Support cross-functional alignment between the four initiative tracks to maintain coherent delivery of the roadmap.
AI Integration - ECA
Work continued on preparing this module for Drupal 12 compatibility. An automated process identified code that uses outdated programming interfaces that will no longer be supported in the next major version of Drupal. A merge request containing compatibility fixes was prepared and is now ready for review as part of ongoing Drupal 12 compatibility work. This type of maintenance is routine for modules as the platform evolves, ensuring the integration between AI capabilities and event-driven automation remains functional when Drupal's core framework is upgraded. No commits were merged during this period, and the compatibility updates await further assessment.
How can I help on this project?
- Prioritize technical review capacity to assess and approve the pending Drupal 12 compatibility changes, ensuring the module remains viable as the platform evolves.
- Clarify the strategic timeline for Drupal 12 adoption to help determine urgency and resource allocation for this compatibility work.
OpenAI Provider
Two development efforts are underway to improve the module's capabilities and maintenance. A new merge request to add support for batch embeddings has been opened, which would enable the system to process multiple embedding requests together rather than one at a time. This can improve efficiency when working with larger volumes of content that needs to be analyzed or processed by AI services.
Additionally, an automated project update has been prepared to keep the module aligned with current Drupal project standards and tooling requirements.
No commits were merged during this period, indicating these contributions are still under review. Both items represent routine development activity consistent with an evolving module.
How can I help on this project?
- Ensure technical reviewers have capacity to evaluate the pending batch embeddings feature, which could improve performance for higher-volume use cases.
- Confirm whether batch processing capabilities align with planned business applications of AI-powered content features.
Contributors: Paul Sheldrake (paulsheldrake), project update bot (Project-Update-Bot)
amazee.ai Private AI Provider
This module provides integration with amazee.ai's private AI services. Over the past 24 hours, work continued on stabilising the module and preparing for future platform compatibility.
Two fixes were merged to address runtime issues. A missing dependency on the PostgreSQL extension was added to prevent errors when connecting to the vector database. Separately, validation was added to ensure key identifiers are properly checked before use, preventing configuration errors from causing failures.
An automated compatibility assessment for Drupal 12 was also initiated. A merge request with compatibility updates has been prepared and is awaiting review. This work ensures the module will remain functional as the Drupal platform evolves.
The module is progressing steadily with fixes that improve reliability for organisations using private AI capabilities in their Drupal environments.
How can I help on this project?
- Prioritise review and approval of the pending Drupal 12 compatibility changes to ensure the module remains supported on future platform versions.
- Consider dedicating testing resources to validate the module's behaviour with PostgreSQL-based vector database configurations in production-like environments.
Contributors: Dan Lemon (dan2k3k4), project update bot (Project-Update-Bot)
Gemini Provider
The Gemini Provider module saw preparatory work for future platform compatibility this period. An automated issue tracking Drupal 12 compatibility was opened, along with a corresponding merge request containing automated fixes. This work ensures the module will remain functional as the Drupal platform evolves, protecting the investment made in this integration.
No commits were merged during this period, indicating this compatibility work is still under review. The module appears to be in active maintenance with automation helping identify necessary updates ahead of time.
How can I help on this project?
- Ensure development resources are available to review and validate the automated compatibility changes, so the module stays current with platform requirements.
- Clarify the strategic roadmap for this module to help prioritize compatibility work against other feature development needs.
Contributors: project update bot (Project-Update-Bot)
Milvus VDB Provider
During this reporting period, two new development efforts were initiated to improve the module's capabilities and quality.
Work began on add support for batching on indexing operations, which will enable the system to process multiple indexing tasks together rather than one at a time. This should improve performance when handling large volumes of content, reducing the time needed to make information searchable.
Additionally, Automated Project Update Bot fixes were prepared to maintain code quality standards and keep the module aligned with Drupal project requirements.
No issues were updated and no code was merged during this period, indicating that development work is progressing through the review stage. Both efforts are in progress and represent incremental improvements to system performance and maintainability.
How can I help on this project?
- Ensure dedicated review resources are available to assess and merge pending development work, preventing bottlenecks in the delivery pipeline.
- Confirm that performance improvement initiatives like batching align with broader organizational priorities for scaling content operations.
Contributors: Artem Dmitriiev (a.dmitriiev), project update bot (Project-Update-Bot)
AI Agents
The AI Agents module saw maintenance and quality work this period. Several longstanding issues with the Views agent were identified, where display configuration changes requested by users were not being correctly applied to non-default displays due to how the system handles inherited settings and coupled configuration pairs.
A merge request was opened to bring the module into compatibility with Drupal 12, addressing deprecated code patterns. This is routine preparation work as the platform evolves.
No code was merged during this period. The module has six open issues covering functionality gaps and error handling improvements, including limits on tool execution frequency and better user feedback when tools encounter errors. These are typical refinements for a module in active development.
How can I help on this project?
- Prioritize the Views agent display override bugs if they affect user-facing functionality you need.
- Consider allocating review time to evaluate the Drupal 12 compatibility changes and the streaming fix to move them toward merge.
Contributors: project update bot (Project-Update-Bot)
Tool API
The Tool API module made progress on error handling this period. A defect preventing useful error messages from being displayed was resolved. Previously, when a tool operation failed, users would see a technical exception rather than the intended failure message explaining what went wrong. This issue has been closed and marked as fixed, meaning administrators and content teams using tools built on this module will now receive clearer feedback when operations do not complete successfully, reducing time spent troubleshooting.
This represents continued refinement of the module's core functionality, improving the day-to-day experience for end users who rely on tool-based workflows.
How can I help on this project?
- Assess whether additional testing resources are needed to validate error handling improvements across different tool implementations before wider deployment.
- Determine if documentation updates are required to communicate these user-facing improvements to site administrators and support teams.
Drupal Canvas
Over the past 24 hours, Canvas delivered significant progress on translation infrastructure and data integrity. A critical feature enabling automatic version updates for component instances across all translations was completed. Previously, when a component's definition changed, only the actively edited language received the update; other translations were left with mismatched version markers. The system now applies updates to every language variant of a content or configuration entity, ensuring all translations stay synchronized with the latest component versions.
Work continued on conflict detection tooling, with the feature now placed behind a development flag to prevent interference with the translation rollout. A related fix resolved a PHP warning on multilingual sites where draft asset libraries were incorrectly scanned for translation strings. The project also addressed a data-consistency issue where test assertions failed on certain database backends due to differing JSON key ordering, and resolved a problem where AI-related configuration updates inadvertently stripped critical metadata.
Several smaller quality-of-life improvements were merged, including fixes to component validation in the CLI tool and removal of hardcoded identifiers in AI-related update hooks. Multiple open issues remain in active development, covering conflict-resolution UI, AI prompt stability, and validation tooling for checking component tree health at scale.
How can I help on this project?
- Prioritize scoping and stakeholder review for the CLI command validating component tree health across all entities and translations, which will help prevent costly data integrity issues in production deployments.
- Allocate developer time to address open validation errors when optional component properties are removed, particularly for config-defined instances, to prevent regressions for sites upgrading to multilingual support.
Contributors: **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Abhishek Dhariwal (adaptative) [1], Adam G-H (phenaproxima), AKHIL BABU (AkhilBabu), Bálint Kléri (balintbrews) [1], Christian López Espínola (penyaskito) [2], Feliksas Mazeikis (f.mazeikis) [1], Kunal Sachdev (kunal.sachdev), Matt Glaman (mglaman) [1], scott falconer (scottfalconer), Wim Leers (wimleers) [1]
Context Control Center (CCC)
This period saw substantial progress on user interface improvements and code quality across the Context Control Center. Multiple efforts to refine how site builders understand and configure context selection moved forward, addressing feedback from beta testing.
Four issues were closed, focusing on polish and developer experience. Work included Copy and layout updates on context item scope form to simplify form presentation, Add Configure Link in Modules Page for easier navigation, and Fix PHPStan failures in CCC to resolve code quality issues. Two bugs blocking stable release were resolved: hook_ai_context_scope_values_alter() is ignored by scope forms and labels now properly enables third-party modules to extend scope options, and No public API for building scope subscription forms established a supported integration path for other modules needing scope UI components.
Several issues progressed toward release candidate readiness. Discussions continued on improving how conditional subcontext behavior is presented to editors, clarifying scope selection concepts, and stabilizing the Document Loader integration. Automated compatibility work for Drupal 12 was initiated.
How can I help on this project?
Support the community testing initiative to gather feedback before the first release candidate. Consider allocating resources to finalize documentation and naming conventions across the scope and subcontext features, which will reduce onboarding friction for site builders.
Contributors: project update bot (Project-Update-Bot)
AI Dashboard
Activity this period focused on documentation improvements and issue management. Work continued on the Improve AI Ecosystem initiative, which aims to help users discover and understand available AI modules for Drupal. The ecosystem browser is being refined to make it easier to navigate the growing landscape of AI integrations, with improvements to visual presentation and filtering capabilities now complete. Plans include automating content updates and enhancing how modules are categorized for easier discovery.
A usability issue affecting the recipe installation feature was closed. The AI Recipe modal is missing the path argument issue, which prevented users from successfully running installation commands shown in the interface, has been postponed. This was causing confusion when users attempted to install pre-configured AI features from the dashboard.
How can I help on this project?
Consider prioritizing the postponed recipe modal issue, as it currently blocks a key self-service installation feature. If the ecosystem browser shows strategic value, advocate for its integration directly into the dashboard interface to improve module discoverability for site administrators.
Contributors: Rob Loach (robloach)
AI Search
Work is underway to improve how the AI Search module handles content indexing at scale. A solution for batch embeddings for improved indexing performance has been prepared and is now under review. This capability processes content in batches rather than one item at a time, which will reduce server load and speed up the indexing process when large volumes of content need to be analyzed. This is particularly important for sites with extensive content libraries or those performing initial setup.
The work is part of a broader consolidation effort, bringing functionality previously developed elsewhere into the AI Search module to ensure it remains current and supported going forward.
How can I help on this project?
- Ensure the team has access to testing environments with realistic content volumes to validate performance improvements before release.
- Clarify deployment timelines and communicate expectations to stakeholders waiting for indexing performance enhancements.
Contributors: Artem Dmitriiev (a.dmitriiev)
Field Widget Actions
Field Widget Actions now supports interactive refinement of AI-generated content. A new interactive refinement capability was merged, allowing users to review generated content in a modal dialog and improve it with follow-up instructions before inserting it into their fields. For example, users can ask the system to make content shorter or adjust its tone without starting over. This capability is optional and turned off by default, so existing workflows remain unchanged. The feature gives content teams more control over AI outputs and reduces the need for manual post-editing.
Two new feature requests are under review. Work is progressing on allowing other modules to mark their field widgets as compatible with Field Widget Actions, which will expand the range of form controls that can benefit from automation. Separately, support for checkboxes and radio buttons is being developed to extend automation beyond text fields and dropdowns. Both features have draft implementations in review.
How can I help on this project?
Support testing of the two in-progress features by arranging user acceptance sessions with content teams who rely on diverse form controls. Consider allocating design or product resources to define refinement use cases beyond text fields, such as image or media workflows.
Contributors: Edward Zwart (ezeedub) [1], Scott Euser (scotteuser)
AI translate
The AI translate module saw automated maintenance activity this period, with compatibility work underway for Drupal 12. A compatibility fix issue was opened to address deprecated code, ensuring the module can function on the next major version of Drupal. A corresponding merge request containing automated fixes has been prepared and is awaiting review.
This work is essential for keeping the module viable as the platform evolves. Without these updates, the module would be unable to support sites upgrading to Drupal 12, limiting its usefulness and adoption. The changes are part of routine maintenance to preserve compatibility across platform versions.
No commits were merged during this period. The automated fixes remain under review. This is a normal part of the development cycle for modules preparing for future platform releases.
How can I help on this project?
- Allocate developer time to review and merge the pending Drupal 12 compatibility updates to keep the module current with platform evolution.
- Consider prioritizing resources for testing the compatibility changes in a staging environment before the Drupal 12 release window.
Contributors: project update bot (Project-Update-Bot)
AI powered Search Block
Activity in the last 24 hours was limited to automated maintenance. A merge request for automated project updates was opened to keep the module aligned with current Drupal standards and tooling. This type of routine maintenance helps ensure the module remains compatible with the broader Drupal ecosystem as it evolves.
No functional changes or bug fixes were delivered during this period. The module continues in its current state with no material progress on features or issue resolution.
How can I help on this project?
- Consider whether dedicated development resources should be allocated to move this module forward with new capabilities or address outstanding issues.
- Clarify strategic priority: determine if this module aligns with organizational goals and warrants continued investment.
Contributors: project update bot (Project-Update-Bot)
FlowDrop
Work has begun to prepare FlowDrop for compatibility with the upcoming Drupal 12 release. An automated compatibility update was opened to identify and address deprecated code that will no longer be supported in the next major version of Drupal. A corresponding merge request has been created containing proposed fixes.
This work is routine maintenance necessary to ensure the module remains functional when users upgrade their Drupal installations. Addressing these updates proactively reduces the risk of disruption for organizations relying on FlowDrop after Drupal 12 launches. The changes are still under review and have not yet been integrated.
How can I help on this project?
- Allocate maintainer time to review and validate the compatibility updates, ensuring they can be merged before Drupal 12's release.
- Consider funding testing resources to verify FlowDrop functions correctly with the updated codebase in real-world scenarios.
Contributors: project update bot (Project-Update-Bot)
FlowDrop UI Agents
Progress continues on preparing the module for Drupal 12 compatibility. A merge request containing automated compatibility fixes was opened to address deprecated code patterns, supporting the longer-term goal of ensuring the module remains viable as the Drupal platform evolves. This work relates to the ongoing Automated Drupal 12 compatibility fixes effort.
The changes are part of routine modernization activities to keep the module aligned with upcoming platform requirements. This type of proactive maintenance reduces technical debt and helps avoid compatibility issues when Drupal 12 becomes the primary supported version.
No code was merged during this period, and the compatibility work remains in progress. This is typical for early-stage platform transition efforts, where changes are reviewed and tested before integration.
How can I help on this project?
- Allocate developer time to review and validate the pending Drupal 12 compatibility changes to accelerate the transition timeline.
- Clarify the strategic priority of Drupal 12 readiness relative to other module development efforts to guide resource planning.
Contributors: project update bot (Project-Update-Bot)
AG-UI
Work has begun to prepare the AG-UI module for compatibility with Drupal 12. An automated process identified deprecated code that will need to be updated before the next major version of Drupal is released. A merge request containing compatibility fixes has been opened and is awaiting review. This work ensures the module will continue to function when the platform is upgraded, reducing future technical debt and avoiding disruption to users.
This is routine maintenance for an evolving codebase. No other development activity was recorded during this period.
How can I help on this project?
- Assign a developer with knowledge of the module to review and approve the pending Drupal 12 compatibility changes, ensuring they align with project standards.
- Clarify the project's roadmap and priority level to determine whether active feature development or maintenance-only support is expected going forward.
Contributors: project update bot (Project-Update-Bot)
References
[1] Uninstalling ai_ckeditor leaves stale toolbar items in editor.editor.* configuration
[2] Config action to verify if any vector database is there and it is setup
[3] Batch embeddings for improved indexing performance
[4] Improve ai_ckeditor UX when no provider modules are installed
[9] Add a setup-guardrails agent skill to configure guardrails, guardrail sets, and global guardrails
[10] Move out AI Content Suggestions
[12] [Discuss] Consider adding Agents.md
[15] Implement Process System Integration for Automators
[16] [Discuss] Allow usage of Tool API in Agents
[21] Prompt Library menu item missing due to incorrect parent
[24] Improvement suggestions for ai_automators docs
[28] Add an AI reranking processor for Search API (owned by the AI module)
[32] Unable to override the 'Calling agents' / 'Contacting agents' text
[39] Allow vector database providers to opt in as the default VDB when none is set
[42] feat(ai_ckeditor): warn users when no AI provider is installed in the CKEditor settings tab
[43] Issue #3568648: Batch embeddings as a first-class operation type (follow-up to !1704)
[44] task: #3586561 Add a setup-guardrails agent skill to configure guardrails,...
[45] Remove ai_content_suggestions module for ai core
[46] Issue #3585596: Move Prompt Library under AI Infrastrcture
[47] Issue #3585596: Move Prompt Library under AI Infrastrcture
[48] Issue #3585596: Move Prompt Library under AI Infrastrcture
[49] docs: #3572751 Add docs for the Field widget Actions automator worker
[53] Issue #3586389: Add agent delegation message setting
[55] Issue #3586522: Keep token usage in the chat() Fiber branch
[56] Issue #3586522: Keep token usage in the chat() Fiber branch
[57] Issue #3586522: Keep token usage in the chat() Fiber branch
[58] Issue #3586522: Keep token usage in the chat() Fiber branch
[59] Issue #3586522: Keep token usage in the chat() Fiber branch
[60] Issue #3586522: Keep token usage in the chat() Fiber branch
[61] Cherry-pick changes from #3586500
[66] add support for batch embeddings
[75] add support for batching on indexing operations
[80] Add limits on how often a tool can run
[84] tool:run masks the failure message: getOutputValues() throws on unset outputs of a failed tool
[88] Symmetric translation: component instance version updates must propagate to all translations
[93] Strengthen test coverage for multi-translation multi-component instance automatic version updating
[99] Canvas AI: Component context required props missing required flag
[100] Canvas AI: Remove hardcoded component source IDs
[101] Canvas AI: An unexpected error has occurred while rendering preview
[107] Canvas AI: Expose Props of Blocks to the Agent
[135] Add Configure Link in Modules Page
[136] Copy and layout updates on context item scope form
[137] `hook_ai_context_scope_values_alter()` is ignored by scope forms and labels
[158] Batch embeddings for improved indexing performance
[159] Resolve "Batch embeddings for improved indexing performance"
[161] Add interactive refinement capability to Field Widget Actions
[165] Issue #3547306: Add interactive refinement capability to Field Widget Actions
[176] Pinecone: fix `getVectorFromNode()` returning no results
[178] Resolve "Pinecone: fix `getVectorFromNode()` returning no results" 2x
[179] Resolve "Pinecone: fix `getVectorFromNode()` returning no results" 1x
Shipped
- AI Core Fiber branch token usage fix — OpenAiBasedProviderClientBase::chat() now correctly preserves token usage metadata when reconstructing ChatOutput objects in the streaming Fiber branch, backported to 1.3.x, 1.4.x, 1.5.x, and 2.0.x [38][55][56][57][58][59][60].
- Prompt Library menu reorganization — The Prompt Library menu link was moved from under Vector Database Configuration to directly under AI Infrastructure [21][46][47][48].
- AI Content Suggestions removed from core — The ai_content_suggestions module was removed from AI Core and will continue as a standalone contrib project [10][45].
- amazee.ai provider key loading fix — The ai_provider_amazeeio module now checks that key identifiers are non-empty strings before loading keys, preventing errors when empty values are passed to the Key module [70].
- Canvas symmetric translation propagation — Component instance version updates now propagate to all translations of an entity, ensuring automatic reconciliation applies to every language when code components change [88][113].
Ongoing
- Batch embeddings as first-class operation type — MR introduces BatchEmbeddingsInterface to AI Core with events and logging support, awaiting review [3][43].
- AI CKEditor UX when no provider installed — MR adds warning message in CKEditor settings tab when no AI provider modules are installed, awaiting review [4][42].
- OpenAI provider batch embeddings support — MR adds batched embeddings support to ai_provider_openai with 284 lines of changes, awaiting review [66].
- Field Widget Actions interactive refinement — MR implementing server-side Form API modal for iterative content refinement with follow-up prompts is under review [161][165].
- Canvas AI component props exposure to agents — Work continues on exposing block properties to Canvas AI agents to enable richer agent interactions [107][125].
AI (Artificial Intelligence)
Several key fixes and infrastructure improvements were merged across the 1.x and 2.x branches. The Fiber branch token usage bug was resolved; the streaming chat path in OpenAiBasedProviderClientBase now correctly preserves token usage metadata when reconstructing ChatOutput objects. This fix was backported to 1.3.x, 1.4.x, 1.5.x, and 2.0.x.
The Prompt Library menu link was moved out from under Vector Database Configuration and now lives directly under AI Infrastructure, where it belongs. The AI Content Suggestions module was removed from core and will continue as a standalone contrib project. Documentation for the Field Widget automator worker type was added to the ai_automators index.
Open work includes MRs awaiting review for batch embeddings as a first-class operation type, which introduces a new BatchEmbeddingsInterface and ensures the operation receives events and logging, and improved UX when no provider is installed in ai_ckeditor. A proposal to verify if any vector database is configured via config actions also has an open MR. Progress remains blocked on defining a repeatable deprecation mechanism for bundled submodules being moved to contrib.
How can I help on this project?
Review MR !1726 for batch embeddings or MR !1701 for ai_ckeditor provider warnings. Tackle the Tools UI overview page crash, which has no MR and needs investigation. Help define the deprecation playbook in the ai_validations migration research issue.
Contributors: Abhisek Mazumdar (abhisekmazumdar), Ahmad Khalil (ahmad-khalil-imagex), Ann Mary Sruthy (annmarysruthy), Arnaud Willame (arwillame), Artem Dmitriiev (a.dmitriiev), Dimitar Rupov (mrupal), Eric Homanchuk (erichomanchuk), Jérôme Tchania (codeitwisely) [1], m4olivei, Ricardo Castañeda (cadence96), Sujal Kshatri (sujal_31), Wolfgang Ziegler (fago)
Drupal AI Initiative
The AI Initiative saw organizational progress this period. The issue Add standardized GitLab issue templates for initiative work was closed, introducing a standardized set of GitLab issue templates to organize work across the initiative's four tracks (AI Core, AI Products, AI Marketing, and AI UX). These templates aim to provide consistent structure for coordination, research, decisions, meetings, and community activities.
The [META] 2026 Outside-in / Innovation Roadmap (draft) continues active development. The roadmap focuses on optimizing Drupal for agents by providing a reliable, governable action surface with schema validation, permissions, workflow state, auditability, and blast-radius limits. The approach emphasizes outside-in design as a first-class requirement, assuming users will integrate external agents and orchestrators alongside built-in agents.
No merge requests were merged and no commits were pushed during this period.
How can I help on this project?
- Review the roadmap meta issue to understand the initiative's technical direction and contribute feedback on the outside-in agent optimization approach.
- Test the new GitLab issue templates across different work types and provide feedback on their usability for cross-track collaboration.
AI Integration - ECA
Activity this period focused on automated Drupal 12 compatibility preparation. The Automated Drupal 12 compatibility fixes for ai_integration_eca 1.0.x-dev issue was updated, with a corresponding Automated Project Update Bot fixes merge request opened to address deprecated API usage. The MR contains 210 diff lines targeting the 1.0.x-dev branch and awaits review. No commits were merged during this period, leaving the Drupal 12 compatibility work as the primary item requiring attention.
How can I help on this project?
Review the automated Drupal 12 compatibility MR to verify the proposed deprecation fixes are appropriate and don't introduce regressions. Manual testing of the changes against Drupal 12 development releases would help validate compatibility before merging.
Contributors: project update bot (Project-Update-Bot)OpenAI Provider
Two new merge requests were opened during the reporting period. Add support for batch embeddings introduces support for batched embeddings with 284 lines of changes. Separately, Automated Project Update Bot fixes was opened with 13 lines of automated maintenance updates. No merge requests were merged and no commits were pushed during this period.
How can I help on this project?
Review the batch embeddings MR to help move it toward merge. Test the 284-line changeset against realistic embedding workloads. Verify the automated fixes in MR 77 for any unintended side effects.
Contributors: Paul Sheldrake (paulsheldrake), project update bot (Project-Update-Bot)amazee.ai Private AI Provider
Two merge requests were merged during this period. The first addressed a bug where the module attempted to load encryption keys even when key identifiers were empty strings, leading to errors. The fix for checking that key identifiers are non-empty strings before loading keys was merged, preventing calls to the Key module with invalid values.
The second merge added a missing dependency to composer.json. The ext-pgsql requirement was merged to resolve runtime errors when the PostgresPgvectorClient class attempted to call pg_connect() without the PostgreSQL extension loaded. This closed pgsql ext dependency missing in composer.json.
A new automated merge request for Drupal 12 compatibility fixes was opened, containing 388 lines of changes to remove deprecated API uses. This work relates to ongoing Drupal 12 preparation tracked in Automated Drupal 12 compatibility fixes for ai_provider_amazeeio 2.0.x-dev.
How can I help on this project?
Review the automated Drupal 12 compatibility fixes merge request to verify the proposed deprecation removals are correct and do not introduce regressions. Test the changes against Drupal 12 development builds to confirm compatibility.
Contributors: Dan Lemon (dan2k3k4), project update bot (Project-Update-Bot)Gemini Provider
Activity this period focused on automated Drupal 12 compatibility preparation. An Automated Drupal 12 compatibility fixes for gemini_provider 1.x-dev issue was opened to track removal of deprecated API uses ahead of Drupal 12. A corresponding merge request, Automated Project Update Bot fixes, was created with 62 lines of changes addressing these deprecations. The MR remains open and awaiting review. No commits were merged during this reporting period.
How can I help on this project?
Review the Automated Project Update Bot fixes merge request to verify the Drupal 12 compatibility changes are appropriate and don't introduce regressions. Test the changes against a Drupal 12 development environment to confirm deprecated API calls are properly replaced.
Contributors: project update bot (Project-Update-Bot)Milvus VDB Provider
Development activity this period focused on performance improvements and automated maintenance. A new merge request was opened to add support for batching on indexing operations, introducing 297 lines of changes to optimize how records are indexed into Milvus. The branch targets batch insert functionality for index operations only.
Additionally, an Automated Project Update Bot fixes merge request was opened containing maintenance updates from the latest automated run.
No merge requests were completed during this period, and no commits were pushed to the main branch. Both open merge requests are awaiting review and could benefit from testing and feedback.
How can I help on this project?
- Review the batching on indexing operations merge request to validate the API changes and performance improvements.
- Test the batch insert functionality with various data volumes to ensure it handles edge cases correctly.
Contributors: Artem Dmitriiev (a.dmitriiev), project update bot (Project-Update-Bot)
AI Agents
No code was merged in the past 24 hours. Activity focused on bug reports and automated compatibility work.
Several Views agent issues were updated, including Views agent: style/row and filters/filter_groups must be overridden as pairs on non-default displays and UpdateViewPlugins: display option updates on non-default displays do not override defaults inheritance. Both describe problems where the Views agent fails to properly override display options on non-default displays, causing Views to fall back to default values at runtime.
Work continues on Fix streaming, which addresses broken streaming in ai_chatbot. The issue describes adding streaming properties to AiAgentEntityWrapper and passing setStreamedOutput to ChatInput before provider calls.
An automated Drupal 12 compatibility MR was opened, related to Automated Drupal 12 compatibility fixes for ai_agents 1.4.x-dev, containing patches to remove deprecated API uses.
How can I help on this project?
- Review the Drupal 12 compatibility MR to verify the automated fixes are correct.
- Pick up one of the unassigned Views agent bugs (3582782 or 3582781) to fix display option override handling.
- Help investigate Exceptions in tool execute break the UI for the user to add proper error handling.
Contributors: project update bot (Project-Update-Bot)
Tool API
The tool:run masks the failure message: getOutputValues() throws on unset outputs of a failed tool issue was closed as fixed during the reporting period. This issue addressed a problem where the drush tool:run command failed to display useful error messages when a tool execution failed. Previously, the command unconditionally called getOutputValues() after reading the result status, which threw a ContextException when outputs were unset on failed tools. This masked the actual failure message that would have been helpful for debugging. The fix ensures that failure messages from tools returning ExecutableResult::failure() are properly surfaced to users rather than being hidden by context exceptions.
How can I help on this project?
Review the issue queue for unresolved bugs or feature requests that could benefit from testing or feedback. Consider adding test coverage for edge cases in tool execution workflows. Check documentation for the Tool API to ensure it reflects current best practices.
Drupal Canvas
A significant translation milestone was reached as the symmetric translation system now propagates component instance version updates to all translations of an entity. The Symmetric translation: component instance version updates must propagate to all translations feature ensures that when a code component's props or slots change, the automatic reconciliation applies to every language, not just the default. A related fix addressed database-backend-dependent component input key ordering in Component inputs order is database-backend-dependent: fix inputs key order assertions in tests and enforce it via PHPStan when possible, where MySQL and PostgreSQL were reordering JSON object keys on storage.
On the Canvas AI front, a post-update hook bug was fixed in Canvas AI: canvas_ai_post_update_0003 strips the orchestrator agent UUID via setData(), which had been inadvertently dropping UUIDs during reimport. Hardcoded component source plugin IDs were replaced with constants via Canvas AI: Remove hardcoded component source IDs.
The CLI tool received a fix for Flat named component validation in @drupal-canvas/eslint-config misses sibling entrypoints, ensuring ESLint rules now correctly identify all flat component entrypoints in a single directory. A multilingual site issue was resolved where draft asset library JavaScript URLs triggered file_get_contents() warnings in locale's JS scanner, addressed in Draft asset library JS asset registered as a file triggers file_get_contents() warning in locale's JS scan. Conflict detection features were placed behind a development flag in Put conflict detection behind a dev mode flag to unblock translation work.
How can I help on this project?
Review the open merge request for translating unpublished page crashes canvas (!1282). Help design notification UX for Use notifications to inform users about the detected conflicts. Investigate the regression in Deleting optional props from an SDC/code component causes validation errors in config-defined component instances.
Contributors: **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Abhishek Dhariwal (adaptative) [1], Adam G-H (phenaproxima), AKHIL BABU (AkhilBabu), Bálint Kléri (balintbrews) [1], Christian López Espínola (penyaskito) [2], Feliksas Mazeikis (f.mazeikis) [1], Kunal Sachdev (kunal.sachdev), Matt Glaman (mglaman) [1], scott falconer (scottfalconer), Wim Leers (wimleers) [1]
Context Control Center (CCC)
Four issues were closed during the reporting period, primarily addressing code quality and API refinements. Fix PHPStan failures in CCC resolved 16 static analysis errors across entity field typing, diff builder return types, and interface inheritance issues. Fix phpstan error in AiContextSubcontextToggleTrait corrected an undefined method call in the toggle trait. Two API issues were also closed: No public API for building scope subscription forms addressed the lack of a supported mechanism for contrib modules to render scope-subscription UIs outside of agents, and hook_ai_context_scope_values_alter() is ignored by scope forms and labels fixed the documented alter hook being bypassed by forms and resolvers.
Administrative improvements were also closed: Add Configure Link in Modules Page added standard configuration links, and Copy and layout updates on context item scope form refined help text and badge ordering in the Context Scope section.
Several issues remain open as the project moves toward rc1, including Add full view layout for context item canonical and revision pages, Introduce explicit scope types and item inclusion modes, and [Feature] Add ExternalContextProviderInterface and ContextQueryInterface to support RAG/vector store integrations, which proposes formal APIs for external retrieval-augmented generation integrations.
How can I help on this project?
Review the open Automated Project Update Bot fixes merge request for Drupal 12 compatibility. Pick up Add #[RunTestsInSeparateProcesses] attribute to all kernel test classes, which needs the attribute added to 35 remaining kernel tests. Help test beta releases via CCC beta / pre-rc1 community testing.
Contributors: project update bot (Project-Update-Bot)AI Dashboard
Activity this period focused on the AI Ecosystem documentation and tooling. Work continued on Improve AI Ecosystem, which provides a browsable catalog of AI-related Drupal modules. The open merge request addresses CSS legibility issues with the Zensical theme and explores using the JSON manifest directly within the AI Dashboard module to allow users to browse modules from their own site. Remaining work includes implementing a cron rebuild process to fetch new modules from Drupal.org and refining the category detection logic, which currently falls back to "Utility" when it cannot classify a module by name and description.
Separately, AI Recipe modal is missing the <path> argument was closed as postponed. The issue had identified that the "View Commands" buttons for AI Recipe features were generating incomplete commands that failed with a "missing path" error when executed.
How can I help on this project?
Review MR !24 for the AI Ecosystem improvements, particularly testing the JSON manifest integration. Consider implementing the cron rebuild process to sync modules from Drupal.org, or refine the category detection algorithm to improve classification accuracy.
Contributors: Rob Loach (robloach)
AI Search
Work is underway to implement batch embeddings for improved indexing performance. A merge request has been opened to address Batch embeddings for improved indexing performance, porting functionality from the AI Core module as development of the ai_search submodule has been deprecated. The MR contains 732 lines of changes and is currently awaiting review. No commits were pushed or merged during the reporting period, indicating the work is in review phase.
How can I help on this project?
- Review the batch embeddings merge request to provide feedback on the API implementation and help move it toward completion.
- Test the batch embedding functionality with different data volumes to validate performance improvements.
Contributors: Artem Dmitriiev (a.dmitriiev), Sergiu Nagailic (Nikro)
Field Widget Actions
The interactive refinement capability was merged during this period, adding opt-in support for iterative content improvement. The feature introduces a server-side Form API modal that displays generated content and allows users to refine it with follow-up prompts before inserting the result into a field. The implementation extends FieldWidgetFormActionBase and is disabled by default, leaving existing actions unchanged.
Two open merge requests saw activity: MR !26 addresses the need to let contrib modules declare their field widgets as childless, removing hard-coded dependencies on specific widget types like chosen_select and tagify. Meanwhile, MR !25 implements Ajax JS command support for checkboxes and radio buttons, which require different handling than the select-type widgets previously supported. Both MRs are open and awaiting review.
How can I help on this project?
Review MR !26 for the childless widget API or MR !25 for checkbox/radio support. Test the newly merged interactive refinement feature with various field widget actions and report any edge cases.
Contributors: Edward Zwart (ezeedub) [1], Scott Euser (scotteuser)
AI translate
The AI translate module saw automated Drupal 12 compatibility work this period. A merge request was opened to address deprecated API usage as part of Automated Drupal 12 compatibility fixes for ai_translate 2.0.x-dev. The Automated Project Update Bot fixes MR contains 409 lines of diff targeting compatibility updates for Drupal 12. No commits were merged during this period, and the compatibility work remains in progress.
How can I help on this project?
Review the Automated Project Update Bot fixes merge request to validate that the automated Drupal 12 compatibility changes are correct and do not introduce regressions. Test the changes against a Drupal 12 environment to confirm functionality is preserved.
Contributors: project update bot (Project-Update-Bot)
AI powered Search Block
Activity this period was limited to automated maintenance. A merge request titled Automated Project Update Bot fixes was opened, containing automated changes with 753 lines of diff. The MR remains open and awaiting review. No commits were pushed during this period, and no issues saw activity in their comment threads.
How can I help on this project?
Review the open Automated Project Update Bot fixes merge request to verify the automated changes are appropriate. Check the issue queue for unassigned issues that need attention. Test the module with recent Drupal core versions to identify compatibility issues.
Contributors: project update bot (Project-Update-Bot)FlowDrop
Activity this period focused on Drupal 12 compatibility. An automated Drupal 12 compatibility fixes issue was opened, with a corresponding merge request created to address deprecated API usage. The MR contains 4588 lines of automated refactoring changes and remains open for review. No commits were merged during this period.
How can I help on this project?
Review the open Automated Project Update Bot fixes merge request to verify the Drupal 12 compatibility changes are correct and do not introduce regressions. Test the patched module against Drupal 12 to ensure functionality remains intact.
Contributors: project update bot (Project-Update-Bot)FlowDrop UI Agents
Activity this period focused on Drupal 12 compatibility preparation. An Automated Drupal 12 compatibility fixes for flowdrop_ui_agents 1.0.x-dev issue was opened to track automated removal of deprecated API uses. A corresponding merge request, Automated Project Update Bot fixes, was created with 232 lines of changes addressing these compatibility issues. The MR remains open and awaiting review. No commits were merged during this period, leaving the Drupal 12 compatibility work as the primary blocking item for forward progress.
How can I help on this project?
- Review the Automated Project Update Bot fixes MR to verify the automated Drupal 12 compatibility changes are correct and complete.
- Test the MR against Drupal 12 development environments to identify any remaining deprecated API usage or compatibility issues.
AG-UI
The AG-UI module saw automated Drupal 12 compatibility work during this period. An Automated Drupal 12 compatibility fixes for agui 1.0.x-dev issue was opened to track removal of deprecated API uses, with changes being posted periodically. A corresponding merge request, Automated Project Update Bot fixes, was opened with 41 lines of diff addressing these compatibility concerns. The MR remains open and awaiting review. No commits were merged during this period.
How can I help on this project?
Review the Automated Project Update Bot fixes merge request to verify the Drupal 12 compatibility changes are correct and complete. Test the patched module against Drupal 12 to ensure no regressions are introduced by the automated changes.
Contributors: project update bot (Project-Update-Bot)References
[1] Uninstalling ai_ckeditor leaves stale toolbar items in editor.editor.* configuration
[2] Config action to verify if any vector database is there and it is setup
[3] Batch embeddings for improved indexing performance
[4] Improve ai_ckeditor UX when no provider modules are installed
[10] Move out AI Content Suggestions
[21] Prompt Library menu item missing due to incorrect parent
[42] feat(ai_ckeditor): warn users when no AI provider is installed in the CKEditor settings tab
[43] Issue #3568648: Batch embeddings as a first-class operation type (follow-up to !1704)
[45] Remove ai_content_suggestions module for ai core
[46] Issue #3585596: Move Prompt Library under AI Infrastrcture
[47] Issue #3585596: Move Prompt Library under AI Infrastrcture
[48] Issue #3585596: Move Prompt Library under AI Infrastrcture
[55] Issue #3586522: Keep token usage in the chat() Fiber branch
[56] Issue #3586522: Keep token usage in the chat() Fiber branch
[57] Issue #3586522: Keep token usage in the chat() Fiber branch
[58] Issue #3586522: Keep token usage in the chat() Fiber branch
[59] Issue #3586522: Keep token usage in the chat() Fiber branch
[60] Issue #3586522: Keep token usage in the chat() Fiber branch
[66] add support for batch embeddings
[70] fix(#3586231): check that key identifiers are non-empty strings before loading keys
[88] Symmetric translation: component instance version updates must propagate to all translations
[107] Canvas AI: Expose Props of Blocks to the Agent
[125] Issues/3569120: Canvas AI: Expose Props of Blocks to the Agent.
[161] Add interactive refinement capability to Field Widget Actions
[165] Issue #3547306: Add interactive refinement capability to Field Widget Actions