Daily Digest
Daily Digest – 16 June 2026
2026 Capabilities Progress
- Page generation — Progress on AI-assisted page and component creation continues with fixes to the Canvas AI prompt system that prevented text from being cleared when metadata changed [64][82], and improvements to the component generation agent addressing deprecated imports and error handling [59][78]. Next milestone is stabilizing the AI component generation workflow.
- Context management — Active development on the Context Control Center delivered a redesigned display layout for context items [90][95], document import capabilities for PDFs and URLs [96], and conditional context inclusion based on request characteristics [97]. Performance optimization work is underway to improve scope filtering [92], and example context items are being prepared to aid adoption [94].
- Background agents — Configuration improvements were merged to allow processing multiple automator queue items per cron run rather than just one [18][22], and token replacement handling was refined [6]. A schema validation error affecting automator fields remains under investigation [12].
- Design system integration — Canvas delivered fixes for component instance updates with dynamic field bindings [58][74] and resolved validation errors when source modules are removed [57][72], ensuring more reliable component reuse. Translation integration work for content entities is progressing [53][68], and conflict detection during auto-save operations was completed [63][88].
- Content creation and discovery — Search capabilities advanced with a proposal to add AI reranking support to Search API [10] and completion of Drupal 12 compatibility for the search block module [103]. Work on the CKEditor AI Assistant addressed an integration issue [3], and multilingual content support improved with configuration translation for AI prompts [9].
- Advanced governance — Canvas made significant progress with backend conflict detection during auto-save operations now functional [63][88], a delete confirmation modal added for translations [66][89], and ongoing work on selective publishing with conflict resolution UI [83]. Permission controls for limiting publish access are under consideration [61].
- Intelligent website improvements — Observability infrastructure was enhanced with improved summarization of AI request and response data for logs and spans [14][21], supporting better analysis of AI performance. Chat memory storage capabilities are being designed to enable learning from conversation history [19].
- Multi-channel campaigns — No direct progress today on multi-channel campaign orchestration, though foundational work on translation workflows [53][68][9] and the AI Dashboard ecosystem browser [99] may support future campaign management capabilities.
Shipped
- AI module agent delegation messaging — Users can now customize the "Calling agents" text shown during AI processing to better fit their audience and context [5][20].
- AI module queue processing configuration — Administrators can now control how many AI Automator tasks are processed per cron run, improving system resource management [18][22].
- AI module logging improvements — Enhanced summarization of AI request and response data in logs and observability traces [14][21].
- AI Agents file-based instructions — Parent agents can now store and share instructions via files, reducing redundancy and improving coordination between sub-agents [46].
- Canvas security and stability fixes — Six critical issues resolved including JavaScript security patches, content template preview errors, config validation after module removal, field binding regressions, translation deletion confirmation, and auto-save conflict detection [58][59][63][65][66][69][71][72][74][78][88][89].
Ongoing
- AI module version regression investigation — Team is investigating whether fixes from version 1.3.x failed to carry forward to 1.4.x, which could require a patch release [1].
- AI module multilingual prompt support — Work underway to enable translation of AI prompts into multiple languages for better content processing [9].
- AI Search reranking capability — Proposal to add AI-powered result reranking to improve search relevance and precision across the ecosystem [10][101].
- Canvas translation and conflict resolution — Multiple translation workflow enhancements and publishing conflict detection features remain in development [53][63][66][68][76][80][83][84][85][88][89].
- Huggingface Provider ecosystem expansion — Eight new AI service integrations under review that would connect additional image generation, language processing, and specialized AI platforms [34][35][36][37][38][39][40][41].
AI (Artificial Intelligence)
The AI module saw active development planning and issue resolution over the past 24 hours, with focus on user experience improvements, multilingual capabilities, and addressing technical gaps in existing features.
Progress was made on improving the conversational interface for chatbots. A merge request was opened to allow organizations to customize the "Calling agents" or "Contacting agents" message shown during AI processing, addressing feedback that this technical language can confuse end users in different contexts. Separately, work continued on refining how chat history is stored and managed across sessions.
Several new capabilities are under consideration. The team accepted proposals to support translating AI prompts into multiple languages for better content processing, to add reranking functionality that can improve search precision across the ecosystem, and to enhance how video generation models accept text prompts. Work also began on enabling a mock testing provider to support summarization operations, making it easier for developers to build integrations.
The team identified a potential regression where fixes present in version 1.3.x may not have carried forward to the 1.4.x release line. Investigation is underway to confirm scope and impact. Additionally, several user-reported issues around image processing in automators, schema validation errors, and interface bugs are awaiting review or have solutions in progress.
How can I help on this project?
- Prioritize review and resolution of the version 1.3.x to 1.4.x regression investigation to determine whether a patch release is needed for current users.
- Allocate resources to address the backlog of open user-facing bugs, particularly those affecting content creation workflows and image processing features.
Drupal AI Initiative
The AI Initiative saw progress on internal project management capabilities over the past 24 hours. A new sprint statistics tool was submitted by Jeremy Chinquist (jjchinquist) that will help the team track progress across development sprints and milestones. This tool generates reports showing which work items are completed, in progress, or waiting, and attempts to identify who is responsible for each piece of work.
This tooling represents an investment in the project's ability to measure and communicate progress systematically. Once integrated, it should provide clearer visibility into sprint velocity and help the team identify bottlenecks earlier. The work is awaiting review and has not yet been merged into the main codebase.
No critical issues or blocking problems were reported during this period. Activity levels remain modest, consistent with ongoing development work.
How can I help on this project?
- Ensure the team has dedicated reviewer capacity to evaluate and merge the sprint reporting tool promptly so progress tracking can begin.
- Consider whether sprint metrics should be shared more widely with stakeholders to improve transparency and accountability across the initiative.
AI Integration - ECA
The project is making strategic progress toward a stable 1.0.0 release, with focused work to expand coverage of AI operations and modernise internal architecture.
Marcus Johansson opened a draft merge request to deliver the AI ECA Interceptor submodule, which will allow site builders to intercept and respond to AI requests and responses through visual workflows—useful for logging, rate limiting, or content filtering without custom code.
Five new planning issues were created to fill gaps in the module's capabilities. A meta issue now tracks the addition of workflow actions for all remaining AI operation types; the first child issue addresses Rerank support. A separate issue proposes adding vector search functionality, which would let users query databases using AI-generated embeddings. Finally, an issue outlines a technical refactoring of the ECA agent architecture to align with modern patterns used elsewhere in the platform.
All issues remain unassigned except Rerank, which Marcus Johansson has taken on. No commits were merged during this period.
How can I help on this project?
- Assign development resource to the unassigned issues tagged "Road to 1.0.0" to accelerate delivery of the stable release.
- Confirm whether vector search is a priority use case; if so, prioritise the vector search issue to unlock retrieval-augmented workflows.
MCP Client
The MCP Client project saw minimal activity over the past 24 hours. An automated maintenance process opened a merge request to apply project-wide updates, submitted by Project-Update-Bot. This automated maintenance helps keep the project aligned with Drupal coding standards and infrastructure changes, reducing technical debt without requiring manual intervention.
No other development work, issue resolution, or community engagement occurred during this reporting period. The project appears to be in a quiet phase with no active feature development or bug fixes underway.
How can I help on this project?
- Assess whether dedicated development resources should be allocated to advance the project roadmap and core functionality.
- Review the project's strategic priority and confirm whether it aligns with current business objectives.
- Consider connecting with the maintainer community to understand any blockers or resource constraints.
Mini Kanban
Activity over the past 24 hours has been limited to automated maintenance work. A merge request titled Automated Project Update Bot fixes was opened by the Project Update Bot, containing routine updates to keep the project aligned with current standards. This type of maintenance ensures the module remains compatible and follows best practices, reducing technical debt over time.
No feature development, bug fixes, or user-facing improvements were delivered during this period. There were no commits merged and no substantive issue activity.
How can I help on this project?
- Review and approve the pending automated maintenance updates to keep the project health strong.
- Consider allocating development resources if feature development or user-facing improvements are strategic priorities.
- Connect with the community to understand whether additional investment would accelerate adoption or address user needs.
Mini Kanban AI Agents
Development activity over the past 24 hours has been minimal, with the project in a maintenance phase. An automated system opened a merge request for routine project maintenance updates, submitted by Project Update Bot. This automated work helps keep the project aligned with current standards but does not represent new features or user-facing improvements.
No issues were updated, no code was committed, and no active development milestones were advanced during this period. This level of activity is typical for projects between major development cycles.
How can I help on this project?
- Clarify the project roadmap and priorities to guide contributor focus toward the next phase of development.
- Evaluate whether the project has sufficient development resources to meet upcoming goals, and consider allocating additional capacity if needed.
Huggingface Provider
The Huggingface Provider module saw focused development activity over the past 24 hours, with maintenance updates and a significant expansion of AI service integrations underway.
One automated maintenance update was successfully completed and merged, keeping the project's infrastructure current. More substantially, contributor Ahmad Khader (Ahmad-Khader) has submitted eight new integration proposals that would extend the module's capabilities to connect with additional AI service platforms including image generation, language processing, and specialized AI providers. These integrations represent a strategic expansion of the module's ecosystem, giving users more flexibility in choosing AI services that fit their specific needs and budgets.
All eight new integration proposals are currently open and awaiting review. The scope of work is considerable, with each integration averaging over 1,300 lines of changes. This expansion would position the module to serve a broader range of use cases and make it more competitive as an AI integration layer for Drupal sites.
How can I help on this project?
- Assign reviewers with technical expertise to evaluate the eight pending integration proposals, ensuring quality and timely feedback for the contributor.
- Clarify the strategic prioritization: should all eight integrations be pursued, or should certain platforms be prioritized based on user demand or partnership opportunities?
Postgres VDB Provider
During this period, development work advanced on database efficiency. Edward Zwart (ezeedub) opened a merge request to reduce schema bloat, which addresses how the module structures its database storage. This work aims to optimize the way data is organized internally, which should improve performance and reduce storage overhead as the system scales.
The module continues to progress through active development. No new issues were created or updated during this period, suggesting the team is focused on completing current work rather than addressing new problems.
How can I help on this project?
- Ensure the development team has sufficient time allocated for code review to evaluate and merge the pending schema optimization work.
- Consider whether performance testing resources are available to validate the storage improvements before release.
Model Context Protocol
The Model Context Protocol module is progressing toward compatibility with Drupal 12. During this reporting period, automated compatibility work was initiated to identify and address deprecated code that will no longer be supported in the next major version of Drupal. A merge request containing automated fixes has been prepared and is awaiting review as part of the Drupal 12 compatibility effort.
This work ensures the module will continue to function when Drupal 12 is released, protecting organizations that depend on it from potential service disruptions during future platform upgrades. The changes are being generated systematically to update outdated code patterns.
No commits were merged during this period, indicating the compatibility updates are still under evaluation. This is typical for early-stage compatibility work where automated changes require human validation before integration.
How can I help on this project?
- Allocate developer time to review and validate the automated Drupal 12 compatibility fixes currently awaiting approval.
- Clarify the timeline and priority for Drupal 12 readiness to help maintainers sequence this work appropriately.
AI Agents
The AI Agents project made steady progress over the last 24 hours, closing three issues that improve how agents handle tools and share information. This work strengthens the foundation for more flexible and reliable agent behavior.
Two bug fixes and feature additions were completed: Agent ModelOwner missing description_override handling and str_contains safety check for tool settings resolved a problem where certain tool configuration options were causing failures, and Add possibility for an agent to store and read instructions from a file now allows parent agents to share context more efficiently with sub-agents without creating redundant information or losing important details. This latter change reduces processing overhead and improves coordination between agents working together.
Additionally, work concluded on Create a better UI/system for restricting tools, which will make it easier to configure which tools agents can use and under what conditions.
One issue remains in progress: Add possibility to catch all errors on a tool, assigned to Ahmad Khader (Ahmad-Khader), which will allow agents to continue operating even when individual tools encounter permission or execution problems.
How can I help on this project?
- Ensure the developer working on error handling has access to testing environments with different permission scenarios to validate the solution works across user roles.
- Clarify strategic priorities around agent reliability versus feature expansion to help the team sequence remaining work effectively.
Tool API
The Tool API project saw documentation and usability improvements this period, with two open merge requests advancing work that will make the module easier to adopt and more flexible for different use cases.
A documentation task is progressing with an open merge request from Marcus Johansson (Marcus_Johansson) that will help developers create Tool plugins correctly. This addresses a key adoption barrier: the Tool API allows modules to expose actions that AI agents can use, but getting all the required configuration elements right has been challenging. Better documentation will reduce the learning curve and help teams build integrations faster.
Separately, work continues on a feature request to control Tool return formats. Currently, Tool outputs are text-based, which works for AI analysis but limits use in other contexts that need structured data. Scott Falconer (scottfalconer) has an open merge request exploring solutions. This flexibility will expand where and how Tool API can be deployed, particularly in emerging AI interface patterns.
Both items remain in review with no merges yet this period, indicating careful consideration of these foundational changes.
How can I help on this project?
- Assign review capacity to evaluate the two open merge requests, which address documentation and data format flexibility—both critical for wider adoption.
- Clarify the project's roadmap priorities to help contributors understand whether expanding use cases or improving developer experience should take precedence.
Drupal Canvas
The team delivered six critical fixes and improvements over the past 24 hours, focusing on stability and translation workflows.
Christian López Espínola (penyaskito) resolved three issues: security vulnerabilities in JavaScript dependencies were patched through Update JS packages; a regression causing errors when previewing content templates was fixed in UI Exception / 500 Error when triggering Preview on Content Templates causes persistent state lock; and validation errors affecting pages using components whose source modules had been removed were addressed in Config schema validation rejects existing inputs on Fallback components after their source module/theme is removed.
John Locke (freelock) corrected a regression in LogicException on content templates with dynamic field bindings after upgrading from 1.4.1 to 1.5.1 that prevented templates using entity field bindings from loading after upgrade. Feliksas Mazeikis (f.mazeikis) completed backend conflict detection during auto-save operations in Detect conflicts for Page entities during the handling of auto-saves/pending calls, an important step toward preventing users from overwriting each other's work. Utkarsh_33 improved the translation experience by adding a confirmation prompt before deleting translations in Missing delete translation confirmation modal.
How can I help on this project?
Consider prioritizing review and decision-making on permission models for Add Permissions to Canvas Pages Limiting Publish Access, as this affects multi-user editorial workflows. Supporting frontend development capacity for conflict resolution UI work would help deliver the full publishing safety feature set.
Context Control Center (CCC)
Development continues on the Context Control Center module with progress across user experience improvements, performance optimization, and content quality enhancements during this reporting period.
Work is advancing on a redesigned display for viewing context items. The team is implementing a new two-column layout to replace the current plain field list, making it easier for users to scan context information and navigate between related items. This work is being led by Eric Homanchuk.
Two new features are under active development. The first adds import capabilities for documents (PDF and URL sources) directly into context content fields, simplifying how users populate context items. The second introduces controls that allow context to be conditionally included based on request characteristics, giving users more flexibility in how context is applied. Both features are in merge request stage.
The team is also addressing quality-of-life improvements, including a checkbox alignment issue on Drupal 11 (in progress with Juan Correa) and work on validation rules to prevent configuration errors when setting context limits (assigned to Tamas Balog).
Anikó Viola is working on providing example context items to help new users understand and adopt the module more quickly.
Two open issues await assignment: a performance optimization for scope filtering and validation enforcement for configuration settings.
How can I help on this project?
- Assign a developer to scope prefiltering performance optimization to ensure the system scales efficiently before the release candidate.
- Consider user testing resources for the redesigned context item display and document import features once merge requests are completed.
AI Dashboard
During this period, work continued on improving the AI ecosystem documentation and tooling. Rob Loach (robloach) is leading an effort to enhance how users discover and understand AI-related modules available in the Drupal ecosystem. The work includes refining the presentation and categorization of modules to make it easier for site administrators to find relevant AI capabilities.
Progress was made on user interface improvements, specifically addressing readability concerns with font sizing and filter visibility. The team has also begun exploring how to integrate module browsing directly into the AI Dashboard itself, which would allow administrators to discover and evaluate AI extensions without leaving their site. This represents a move toward making the module more self-service and reducing friction in adoption.
Outstanding work includes setting up automated updates to keep module listings current and improving how modules are automatically categorized. These are normal development tasks for a project at this stage.
How can I help on this project?
- Consider whether automated module discovery aligns with organizational security or procurement policies, and provide guidance to the team if approval processes are needed.
- Clarify priority between ecosystem documentation and core dashboard features to help focus development effort.
AI Search
The AI Search module saw moderate activity over the past day focused on enhancing search capabilities and clarifying how to work with vector databases.
One request for reranking support in search results was closed. Reranking would improve the relevance of what users see by applying AI to sort results more intelligently after the initial search. This feature had been proposed to align search results more closely with user intent, but no work has progressed in the reporting period.
A separate query was raised about How to Apply Filters in VDB for RAG Chatbot, asking for guidance on passing filters to a Zilliz vector database so that results can be pre-filtered before being returned to the chatbot. This remains open and reflects ongoing interest in using the module with AI-powered conversational interfaces.
Overall, the module is attracting interest around advanced search features like reranking and filtering, which are important for improving user experience in content discovery. No code was merged or committed during this period, indicating planning and discussion rather than delivery.
How can I help on this project?
- Clarify priorities: decide whether reranking and advanced filtering are strategic features worth resourcing, or lower-priority enhancements.
- Provide documentation or consulting support to help users apply filters in vector database queries, reducing repetitive support requests.
Deepgram
The Deepgram project saw minimal activity in the past 24 hours. An automated maintenance process opened a merge request to apply project update fixes, created by the Project Update Bot. This routine update helps keep the project aligned with current Drupal standards and practices. No issues were updated, and no code was merged during this period.
The project remains in a quiet maintenance phase with no user-facing changes or strategic developments to report at this time.
How can I help on this project?
- Clarify the project's strategic priority and allocate development resources if Deepgram integration remains a business objective.
- Review whether the automated maintenance update should be approved and merged to keep the project current.
AI powered Search Block
The AI powered Search Block module completed important modernization work during the reporting period. A migration to support Drupal 12 was merged, ensuring the module remains compatible with the latest platform version. This work, contributed by wouters_f (wouters_frederik), updated the core module and its three extensions to align with current platform standards.
This update positions the project to continue serving users as the Drupal ecosystem evolves. It removes a potential barrier to adoption for organizations running or planning to upgrade to Drupal 12, and ensures the module can access future platform improvements and security updates.
How can I help on this project?
- Support testing efforts by allocating user acceptance resources to validate search functionality across different content types and use cases.
- Consider documenting business cases or success metrics that demonstrate the value of AI-powered search to help guide future feature prioritization.
FlowDrop
Progress continues on preparing FlowDrop for compatibility with the upcoming Drupal 12 platform release. An automated process has identified necessary updates to ensure the module will work with the new version, and a merge request containing these compatibility fixes has been prepared and is awaiting review. This work addresses the Automated Drupal 12 compatibility fixes for flowdrop 1.x-dev issue.
This represents normal maintenance activity to keep the module current with the evolving Drupal ecosystem. Ensuring compatibility with Drupal 12 will allow organizations to upgrade their platforms when the new version becomes available without losing FlowDrop functionality.
How can I help on this project?
- Allocate developer time to review and approve the pending Drupal 12 compatibility changes so they can be integrated promptly.
- Consider funding additional development capacity if the module requires features or enhancements beyond routine maintenance.
Langfuse
Activity on the Langfuse module over the past 24 hours has been limited to automated maintenance work. A merge request for automated project updates was opened by the Project Update Bot to apply routine fixes and keep the module aligned with current Drupal standards. This type of maintenance helps ensure the module remains compatible and sustainable over time, though no new features or user-facing improvements were delivered during this period.
No issues were updated, and no code was merged into the main codebase in the last 24 hours, indicating a quiet period for development activity.
How can I help on this project?
- Consider allocating development resources if the project requires active feature development or user-facing enhancements beyond automated maintenance.
- Review the project roadmap to ensure alignment with organizational priorities and confirm whether current activity levels match expected delivery timelines.
References
[1] Regression in 1.4x release vs 1.3.x
[3] Issue when creating content and click on AI Assistant on Ckeditor
[5] Unable to override the 'Calling agents' / 'Contacting agents' text
[6] AI Automator Token Replacement with removing unresolved Tokens (Checkbox?)
[9] Support configuration translation for all AI prompts
[10] Add an AI reranking processor for Search API (owned by the AI module)
[12] Schema errors for an Automator field
[14] Improve summarizer for AI request input and output data for logs and spans
[18] Only one AI Automator worker queue item is processed per cron execution
[19] Add a ChatMemoryInterface for storing ChatBot chat history
[20] Issue #3586389: Add agent delegation message setting
[21] Resolve #3566762 "Improve summarizer for"
[22] Issue #3575190: Add configurable queue items per cron for AI Automators
[34] Resolve #3601107 "Add image to"
[35] Resolve #3601120 "Add a z.ai"
[36] Resolve #3601119 "Add a black"
[37] Resolve #3601117 "Add a wavespeedai"
[38] Resolve #3601116 "Add a fal ai"
[39] Resolve #3601114 "Add a scaleway"
[40] Resolve #3601113 "Add a sambanova"
[41] Resolve #3601112 "Add a hyperbolic"
[46] Add possibility for an agent to store and read instructions from a file
[53] Add TMGMT translation integration for content entities
[58] LogicException on content templates with dynamic field bindings after upgrading from 1.4.1 to 1.5.1
[61] Add Permissions to Canvas Pages Limiting Publish Access
[63] Detect conflicts for Page entities during the handling of auto-saves/pending calls
[64] Changing Metadata Clears Canvas AI Prompt Text
[65] Follow-up: Stabilize Canvas preview for in-place `vh` updates and tall content
[66] Missing delete translation confirmation modal
[68] Resolve #3590948 "Add TMGMT translation integration for content entities"
[69] chore: #3591688 Update JS packages to address npm audit findings
[71] Skip canvas_page-only layout requests in content template preview
[72] fix: #3591685 Fix config schema rejecting existing inputs on Fallback components
[74] bug: #3591642 Fix LogicException on component instance updates and config...
[78] Issue #3584136: Fix canvas_component_agent prompt bugs (Image import,...
[80] Draft: feat(Conflict detection): #3587526 "Client side prevention of publishing"
[82] Fix Canvas AI prompt reset on metadata changes
[83] Add conflict detection and resolution UI for selective publishing
[84] Draft: Resolve #3546597 "Create canvas page in other languages"
[85] Issue #3569959: Module that manages asymmetric translations
[88] feat(Conflict detection): #3589076 "Detect conflicts during auto-save polling"
[89] #3591649: "Missing delete translation confirmation modal"
[90] Add full view layout for context item canonical and revision pages based on new design
[92] Avoid Full Published-ID Scans Before Scope Prefiltering
[94] Provide example context items
[95] Issue #3586220: Add single context item display.
[96] Issue #3586275: Add ai_context_document_loader submodule for MDXEditor imports.
[97] Issue #3586207: Add conditional subcontext toggle, cap, and per-request cache.
[99] Improve AI Ecosystem
[101] Add Reranking Support to AI Search
[103] Add D12 OOP hook migration for all submodules (#3594805)
Shipped
- AI module agent delegation message configuration — Merged MR adding a configurable setting to override the "Calling agents" and "Contacting agents" text[5][20].
- AI module queue processing configuration — Merged MR adding configurable queue items per cron for AI Automators, resolving the limitation of only one worker queue item being processed per cron execution[18][22].
- Huggingface Provider automated maintenance — Merged automated project update bot fixes addressing project maintenance tasks[33].
- Canvas critical bug fixes — Merged fixes for Content Template preview 500 errors[56][71], config schema validation rejecting Fallback component inputs[57][72], LogicException with dynamic field bindings after upgrade[58][74], and Canvas AI prompt reset on metadata changes[64][82].
- AI Search Block Drupal 12 compatibility — Merged OOP hook migration for all submodules, converting procedural hooks to object-oriented hook classes across ai_search_block, ai_search_block_extras, ai_search_block_log, and ai_search_block_log_tag[103].
Ongoing
- AI module regression investigation — Active bug report identifying commits present in 1.3.x but missing from 1.4.2 release[1].
- AI ECA Interceptor submodule — Draft MR with 4,731 lines exposing AI module events (PreGenerateResponseEvent, PostGenerateResponseEvent, PostStreamingResponseEvent) as ECA Events, Conditions, and Actions for intercepting and modifying AI provider calls[25][29].
- Tool API return format control — Open MR addressing limitation where tool returns are textual only, enabling raw structured results for MCP and AG-UI integrations[50][52].
- Canvas TMGMT content entity integration — Open MR adding translation management integration for content entities[53][68].
- Context Control Center performance optimization — Unassigned issue requiring refactoring of AiContextSelector::getPrefilteredPublishedItemIds() to avoid full published-ID scans before scope prefiltering[92].
AI (Artificial Intelligence)
Activity over the past 24 hours centered on new feature proposals, bug reports, and merge request submissions rather than merged code.
On the documentation front, Marcus Johansson (Marcus_Johansson) opened Documentation staleness audit: automator-type ID drift, ai_eca/ai_validations deprecation notices, streaming API method names, identifying confirmed mismatches between documentation and code, particularly around automator-type plugin IDs. He also proposed adding last-modified dates to documentation pages via Show last-modified date on documentation pages (mkdocs-git-revision-date-localized-plugin).
Two merge requests saw activity: m4olivei submitted MR !1539 addressing Unable to override the 'Calling agents' / 'Contacting agents' text, adding a configurable setting for agent delegation messages. Meanwhile, MR !1330 by harivansh sharma (harivansh) remains open for Improve summarizer for AI request input and output data for logs and spans.
New bug reports included a CKEditor integration error reported by Jean-Marc PAMBRUN (dpalicepeio-at-drupbuilder.org) and Scott Euser (scotteuser) flagging a Regression in 1.4x release vs 1.3.x where commits exist in 1.3.x but are missing from 1.4.2.
How can I help on this project?
Review MR !1539 for Unable to override the 'Calling agents' / 'Contacting agents' text to validate the configuration approach. Pick up Add Summarization operation type support to the echoai test provider to implement the summarize operation in EchoProvider. Tackle Hamburger menu button doesn't open collapsed chat / deepchat, a Novice-tagged bug in toolbar-chatbot.js.
Drupal AI Initiative
A new merge request was opened in the past 24 hours focused on sprint reporting infrastructure. Jeremy Chinquist (jjchinquist) submitted Issue #3586510: Add sprint-stats skill + reports script, introducing a sprint-stats skill alongside a runnable script for generating per-sprint statistics reports for AI Marketing Initiative milestones. The 2,004-line MR includes documentation covering prerequisites, state buckets, and a best-effort heuristic for identifying developers and responsible persons, along with refinement notes flagging known limitations such as drupalbot label-automation noise and assignee versus actual contributor discrepancies. The companion script fetches issues and state-label events from drupalcode.org and outputs reports in markdown and optionally HTML formats.
How can I help on this project?
AI Integration - ECA
The AI Integration - ECA module saw significant planning activity during the reporting period, with no merges but several new issues opened as part of the Road to 1.0.0 initiative.
Marcus Johansson opened a draft merge request for Add AI ECA Interceptor submodule: intercept AI requests/responses through ECA (!8), a 4,731-line addition that will expose AI module events (PreGenerateResponseEvent, PostGenerateResponseEvent, PostStreamingResponseEvent) as first-class ECA Events, Conditions, and Actions. This new submodule aims to let site builders intercept and modify AI provider calls directly from ECA models.
On the agent architecture front, Migrate the ECA agent to the Tools + ReAct architecture (create-only) was opened to modernize the legacy AiAgentBase implementation. The current agent uses three YAML sub-prompts (determineTask.yml, buildModel.yml, answerQuestion.yml) with hand-rolled control flow; the proposal is to shift to the Tools + ReAct pattern.
A meta issue was created to track coverage of all AI operation types with ECA execute actions. Child issues include Add ECA execute action for Rerank (assigned to Marcus Johansson) and Add an ECA action for vector search, which will enable site builders to run similarity searches against vector databases from ECA models.
How can I help on this project?
- Review the 4,731-line draft MR !8 for the AI ECA Interceptor submodule to help validate event exposure and plugin structure.
- Pick up Add an ECA action for vector search, which is unassigned and has no MR yet.
MCP Client
Activity in the MCP Client module over the past 24 hours was limited to maintenance work. The Project Update Bot (Project-Update-Bot) opened a new merge request for Automated Project Update Bot fixes, containing 100 lines of automated changes from run 12-848511. The MR remains open and awaiting review. No commits were merged and no issues saw updates during this reporting period.
How can I help on this project?
Review the pending Automated Project Update Bot fixes merge request to validate the automated changes and help get it merged. Check the issue queue for unassigned issues that need attention or testing.
Mini Kanban
Activity in the Mini Kanban module over the past 24 hours was limited to automated maintenance. The Project Update Bot opened a new merge request for Automated Project Update Bot fixes, containing 346 lines of changes in the project-update-bot-only branch. This MR relates to automated project maintenance tasks but has not yet been merged. No commits were pushed and no issues were updated during this period.
How can I help on this project?
Developers can contribute by reviewing the open Automated Project Update Bot fixes merge request to verify the automated changes are appropriate. Additionally, check the issue queue for unassigned bugs or feature requests that need attention and consider picking one up.
Mini Kanban AI Agents
Activity over the past 24 hours has been minimal, with no issues updated and no commits merged to the main branch. The Project Update Bot (Project-Update-Bot) opened Automated Project Update Bot fixes, containing 163 lines of automated maintenance changes. The MR remains under review with no merges during the reporting period.
How can I help on this project?
- Review the pending Automated Project Update Bot fixes MR to validate the automated changes and help move it toward merge.
- Test the module with recent Drupal core versions to identify any compatibility issues that may need addressing.
Huggingface Provider
Minimal maintenance activity during this period. The project merged Automated Project Update Bot fixes from Project Update Bot (Project-Update-Bot), addressing automated project maintenance tasks.
Development work continues with Ahmad Khader (Ahmad-Khader) opening eight substantial merge requests, each adding integration support for different AI provider platforms. The MRs range from 1326 to 1488 diff lines and cover providers including Hyperbolic, SambaNova, Scaleway, Fal AI, WaveSpeed AI, Black Forest Labs, z.ai, and image-to-text functionality. All eight MRs remain open and awaiting review, representing a significant expansion of the module's provider ecosystem.
How can I help on this project?
Review the open merge requests from Ahmad Khader, particularly focusing on code quality, API consistency across the eight new provider integrations, and testing the authentication flows. Help validate the image-to-text implementation in MR 15. Test provider integrations against live endpoints if you have API access.
Postgres VDB Provider
Edward Zwart (ezeedub) opened a new merge request addressing Resolve #3576852 "Reduce schema bloat" during the reporting period. The MR spans 1665 lines of diff, suggesting a significant refactoring effort to optimize the module's database schema. This work is currently awaiting review and has not yet been merged.
No commits were pushed directly to branches, and no issues received updates or status changes in the past 24 hours. The module appears focused on this schema optimization effort as its primary active development work.
How can I help on this project?
- Review the schema bloat reduction MR — with 1665 lines changed, testing the changes and providing feedback would help move this work forward.
- Check the project issue queue for unassigned bugs or feature requests that need attention beyond the current schema work.
Model Context Protocol
The Model Context Protocol module saw automated Drupal 12 compatibility work during this period. The Project Update Bot opened Automated Drupal 12 compatibility fixes for mcp 1.x-dev to track necessary API updates for the upcoming Drupal major version. As part of this effort, the bot created Automated Project Update Bot fixes, an MR containing 166 lines of changes addressing deprecated API usage. The MR remains open and awaiting review from maintainers.
No commits were merged during the reporting period, leaving the automated compatibility fixes as the primary outstanding work. The module would benefit from maintainer attention to review and merge the pending compatibility updates, ensuring readiness for Drupal 12.
How can I help on this project?
- Review MR 53 for Drupal 12 compatibility fixes, testing the changes against current Drupal core development builds.
- Audit the module codebase for additional deprecated API usage not caught by automated tooling to ensure comprehensive Drupal 12 readiness.
AI Agents
The AI Agents module saw cleanup activity over the reporting period, with three issues closed on 2026-06-16. The team addressed a bug in Agent ModelOwner missing description_override handling and str_contains safety check for tool settings, which corrected missing extraction of the description_override field to tool_settings and added safety checks to prevent failures when processing malformed keys. A feature enabling agents to store and read instructions from a file was also closed, allowing orchestration agents to pass context more efficiently to sub-agents by making initial requests available as tokens. Additionally, work on creating a better UI/system for restricting tools was completed, moving beyond simple type restrictions to support more complex configurations.
One issue remains open: Add possibility to catch all errors on a tool, assigned to Ahmad Khader (Ahmad-Khader). This feature would allow agent creators to decide whether permission or other errors should halt execution or continue gracefully. The issue currently needs tests and screenshots.
How can I help on this project?
- Review and provide feedback on MR !220 for the error catching feature, which needs tests and screenshots added.
- Help test recently closed features for regressions, particularly the description_override handling and file-based instruction storage.
Tool API
The Tool API module saw documentation and API refinement work progress over the past 24 hours, though no merge requests were completed during the period.
Two open merge requests advanced toward review. Marcus Johansson (Marcus_Johansson) continues work on Create a skill for generating Tool plugins (best practices, how-to, placement), with MR !93 providing comprehensive documentation on authoring Tool plugins. The effort aims to document the complete lifecycle of creating #[Tool] attribute-based plugins, including proper use of ToolOperation enums, InputDefinition structures, and integration with the tool_ai_connector submodule that exposes tools as AiFunctionCalls for AI agents.
Separately, scott falconer (scottfalconer) has MR !85 open addressing Allow controlling Tool return format, which tackles a current limitation where tool returns are textual only. This creates friction for integrations like MCP or AG-UI that need raw structured results rather than text-wrapped output.
How can I help on this project?
Review MR !93 for documentation completeness and technical accuracy regarding Tool plugin authoring best practices. Test MR !85 with real-world MCP or AI agent integrations to validate the return format control implementation meets practical use cases.
Drupal Canvas
The past 24 hours saw significant progress on critical bugs and infrastructure improvements. Christian López Espínola (penyaskito) shipped three important fixes: Update JS packages addressed npm audit vulnerabilities without forcing major upgrades to Astro or Cypress. A regression causing 500 errors when previewing Content Templates was resolved by skipping canvas_page-only layout requests in the preview controller. Another critical regression fix landed for config schema validation rejecting Fallback component inputs after source modules are uninstalled—the schema now uses a permissive sequence of mapping types rather than an empty mapping.
John Locke (freelock) merged a fix for a LogicException in content templates with dynamic field bindings after upgrading from 1.4.1 to 1.5.1, resolving missing keys in EntityFieldPropSource::parse(). Feliksas Mazeikis (f.mazeikis) landed conflict detection during auto-save polling via MR !1213, enabling backend detection of conflicts when updating entities with existing auto-save entries. A missing delete translation confirmation modal was added by utkarsh_33.
Active development continues on TMGMT integration (MR !1232), AI agent prompt fixes (MR !1237), and full-screen page extensions (MR !1233).
How can I help on this project?
Review MR !1233 implementing full-screen page extensions or MR !1232 for TMGMT content entity integration. Help test MR !530 fixing Canvas AI prompt resets on metadata changes. Investigate Canvas CLI pull removing source_url from image provenance—it's unassigned with no existing MR.
Context Control Center (CCC)
Activity this period focused on user interface improvements and performance optimizations. Eric Homanchuk (erichomanchuk) continues work on Add full view layout for context item canonical and revision pages based on new design with MR !151 open for review, replacing the default field-list entity view with a two-column layout that surfaces scope and subcontext navigation.
Two new merge requests were opened: Kristen Pol (kepol) submitted MR !176 introducing an ai_context_document_loader submodule that integrates MDXEditor with Document Loader for PDF and URL source plugins. Abhisek Mazumdar (abhisekmazumdar) opened MR !166 addressing conditional subcontext toggle and caching.
Several issues received assignments: Tamas Balog (tbalog) picked up Add context settings validation: max_global_items must not exceed max_items, requiring constraint validation and kernel tests. Anikó Viola (violaniko) is working on Provide example context items to help new users learn the module. Juan Correa (jucs7) has an open MR !180 for the Show this overview page checkbox is misaligned on vanilla Drupal 11 styling issue.
How can I help on this project?
AI Dashboard
Activity was quiet over the last 24 hours, with no merge requests or commits. The main ongoing effort is Improve AI Ecosystem, assigned to Rob Loach (robloach). This work involves enhancing the AI ecosystem documentation site, with some items already completed including CSS improvements for the filter display and exploring integration of the JSON manifest directly into the AI Dashboard module for browsing modules from within a site.
Outstanding tasks include implementing a cron rebuild process to fetch new modules from Drupal.org, refining category detection logic (which currently analyzes module names and descriptions, falling back to "Utility" when no appropriate category is found), and adding a column to track module installation status. The issue remains in progress with no blocking items identified.
How can I help on this project?
- Review the existing ecosystem documentation site and provide feedback on category detection accuracy or suggest additional metadata fields.
- Contribute to implementing the cron rebuild process to automatically fetch new AI-related modules from Drupal.org.
AI Search
Activity this period focused on issue triage and planning. The Add Reranking Support to AI Search feature request was closed on 2026-06-16, following the introduction of new reranking operation types in AI Core module (issue #3488114). This would have enhanced search result relevance by allowing results to be reordered based on AI-driven scoring.
Meanwhile, How to Apply Filters in VDB for RAG Chatbot remains open, seeking guidance on passing filters to Zilliz vector databases at query time. The issue involves integrating filterable attributes (stored as integers) with the AI explorer to pre-filter chunks before retrieval. No code activity or merge requests were recorded in the past 24 hours.
How can I help on this project?
Pick up the Zilliz filters issue, which is unassigned and has no active MR. You could provide documentation or code examples showing how to pass filter parameters through the Search API integration to the VDB backend at query time.
Deepgram
The Deepgram module saw minimal activity in the past 24 hours. The Project Update Bot (Project-Update-Bot) opened Automated Project Update Bot fixes, an automatically generated merge request containing 35 lines of changes from run 12-848511. The MR remains open and awaiting review. No commits were merged during this period, and no issues were updated.
How can I help on this project?
Review Automated Project Update Bot fixes to verify the automated changes are appropriate and can be merged. Check the Deepgram issue queue for unassigned issues that need attention or testing with current Drupal core versions.
AI powered Search Block
The AI powered Search Block module completed its Drupal 12 compatibility work this period. wouters_f (wouters_frederik) merged Add D12 OOP hook migration for all submodules (#3594805), migrating all procedural hooks to object-oriented hook classes across the main module and its submodules.
The migration affected four components: the core ai_search_block module now uses AiSearchBlockHooks for hook_theme, ai_search_block_extras implements AiSearchBlockExtrasHooks for hook_form_alter with a new services configuration, ai_search_block_log converts hook_theme, hook_cron, template_preprocess, and hook_form_alter to AiSearchBlockLogHooks, and ai_search_block_log_tag migrates hook_theme, hook_cron, hook_entity_delete, and hook_entity_update into AiSearchBlockLogTagHooks. The 620-line changeset ensures all submodules are compatible with Drupal 12's hook system requirements.
How can I help on this project?
Test the newly merged Drupal 12 OOP hook migration on a Drupal 12 instance to verify all hook implementations function correctly across the module and its submodules. Help triage or fix any compatibility issues that emerge from real-world testing.
FlowDrop
The FlowDrop project saw automated Drupal 12 compatibility work during this period. Project Update Bot opened Automated Drupal 12 compatibility fixes for flowdrop 1.x-dev and created a corresponding merge request, Automated Project Update Bot fixes, containing 1110 lines of diff targeting deprecated API removals. The MR remains in an opened state awaiting review.
No commits were merged during the reporting period, indicating the automated compatibility fixes have not yet been accepted into the codebase. The work is being coordinated by Project Update Bot, with the issue and MR both created on 2026-06-16. Progress appears blocked pending maintainer review of the substantial automated refactoring.
How can I help on this project?
Langfuse
The Langfuse module saw limited activity in the past 24 hours. The Project Update Bot (Project-Update-Bot) opened Automated Project Update Bot fixes, a merge request containing automated updates with 101 lines of changes. The MR relates to issue #3599498 and remains open awaiting review.
No issues were updated, and no commits were pushed during this reporting period. The automated MR represents the only development activity, suggesting the module is in a stable state with maintenance being handled through automated tooling.
How can I help on this project?
- Review the open Automated Project Update Bot fixes merge request to help move automated maintenance forward.
- Check the issue queue for unassigned issues that need attention or patches.
References
[1] Regression in 1.4x release vs 1.3.x
[5] Unable to override the 'Calling agents' / 'Contacting agents' text
[18] Only one AI Automator worker queue item is processed per cron execution
[20] Issue #3586389: Add agent delegation message setting
[22] Issue #3575190: Add configurable queue items per cron for AI Automators
[25] Add AI ECA Interceptor submodule: intercept AI requests/responses through ECA
[29] Draft: Resolve #3584407 "Ai eca interceptor"
[33] Automated Project Update Bot fixes
[50] Allow controlling Tool return format
[52] Resolve "Allow controlling Tool return format"
[53] Add TMGMT translation integration for content entities
[56] UI Exception / 500 Error when triggering Preview on Content Templates causes persistent state lock
[58] LogicException on content templates with dynamic field bindings after upgrading from 1.4.1 to 1.5.1
[64] Changing Metadata Clears Canvas AI Prompt Text
[68] Resolve #3590948 "Add TMGMT translation integration for content entities"
[71] Skip canvas_page-only layout requests in content template preview
[72] fix: #3591685 Fix config schema rejecting existing inputs on Fallback components
[74] bug: #3591642 Fix LogicException on component instance updates and config...
[82] Fix Canvas AI prompt reset on metadata changes
[92] Avoid Full Published-ID Scans Before Scope Prefiltering
[103] Add D12 OOP hook migration for all submodules (#3594805)