Daily Digest
Daily Digest – 9 August 2026
2026 Capabilities Progress
- Page generation — Significant progress with nine new issues opened to architect a multi-agent AI system for conversational page building in Canvas, including tools for component placement and a dev page builder agent that will construct pages from design system components [62][64][65][67][69]. Next milestone is completing the client-side orchestration loop and component property exposure to agents [68][69].
- Context management — The Context Control Center made progress on pre-1.0 improvements including merged documentation on trust boundaries, merged purpose field guidance for conditional subcontext selection, and merged renamed scope plugins for better clarity [76][78][82][115][118]. Active work continues on token budget UI, priority fields for selection ordering, and preparing a demonstration recipe for DrupalCon Rotterdam [77][81][110][113][116][126]. The module is approaching 1.0 release with QA testing underway [98][111].
- Background agents — A new AI Agents framework built on Symfony components was introduced with support for human-in-the-loop approval controls [20]. Concurrent development addresses permission models, tool execution limits, approval modes (pre-approved/approve-once/always), and agent role assignment to enable autonomous workflows with proper governance [40][41][43][45][47]. FlowDrop shipped confirmation gates for workflow approval [137][138].
- Design system integration — Canvas work includes exposing component properties to AI agents and making the component tree loader extensible to support AI-driven component selection and placement [68][75]. The planned page builder agent will construct layouts using available components and propose new ones when gaps are identified [65][66].
- Content creation and discovery — AI Search identified two critical data-loss bugs where progressive indexing can drop content chunks and re-indexing can silently produce empty results, threatening search accuracy [12][128][131]. Batch embedding support is planned to improve indexing performance [129]. The AI CKEditor module encountered compatibility issues with Gemini 2.x streaming [9], and work continues on preserving HTML in streamed output [11].
- Advanced governance — Context Control Center is implementing granular permissions, priority-based selection ordering, and comprehensive token budget tracking with UI visibility ahead of 1.0 [81][84][94][95][110][121]. The AI Agents framework added configurable approval modes allowing per-tool governance controls with loop pause-resume capability [47]. Tool API strengthened input validation to fail safely when tool input is invalid, denying access rather than exposing errors [54][56].
- Intelligent website improvements — Thumbs-up and thumbs-down icons are being added to the shared icon set to enable consistent feedback collection across AI features [1]. Langfuse introduced a feedback scoring API as a separate submodule to capture user responses [139]. Planning discussions covered how providers should notify administrators of better model availability [17], and AI usage reporting in the admin panel remains under development [19].
- Multi-channel campaigns — AI Translate addressed cost efficiency with proposals for batch translation (consolidating multiple fields into single requests) and caching/deduplication to prevent re-translating unchanged content [133][136]. A workflow refactor is planned to support agent-driven translation alongside existing interfaces [134]. A bug preventing media entity translation was identified and a fix proposed [135].
Shipped
- FlowDrop confirmation controls released — Issue [137] was closed, completing work on a pause-and-approve feature that lets organizations review high-risk actions before automated workflows execute them [137].
- Context Control Center documentation and guidance finalized — Pre-release documentation covering security boundaries and API usage was merged, and purpose description guidance was finalized ahead of the 1.0 release [76][78].
- Context Control Center scope plugins renamed for clarity — Two plugins were renamed to better reflect their actual behavior, improving understanding for developers configuring context selection [82][117].
- Langfuse feedback collection feature prepared — A new submodule for capturing and scoring user feedback is under development in an open merge request, enabling quality improvement tracking once integrated [139].
- Tool API input validation strengthened — Two merge requests are open to ensure the system validates all inputs and fails safely when data is invalid or missing [54][56].
Ongoing
- AI Search data loss issues identified — Two critical bugs can cause content to be incompletely indexed or lost during re-indexing, affecting search accuracy and completeness [128][131].
- Canvas multi-agent AI architecture underway — Nine issues outline a new conversational system for page building, component creation, and user assistance that addresses timeout and error recovery limitations [62][63][64][65][66][67][68][69][70][71].
- Context Control Center preparing for 1.0 release — Work continues on token budget displays, priority controls, permissions documentation, and quality assurance testing ahead of the stable release [77][81][84][94][95][98][110][111].
- AI Translate cost reduction features in planning — Proposals to batch multiple fields into single requests and cache repeated translations aim to reduce token usage and infrastructure costs [133][136].
- AI Agents governance and safety controls advancing — Multiple features for permission management, tool approval workflows, and execution limits are under development to enable secure autonomous operations [40][41][43][45][47].
AI (Artificial Intelligence)
Development activity over the past 24 hours centered on expanding the module's strategic capabilities and addressing user experience improvements across the chatbot and content generation features.
A significant new AI Agents framework was introduced, built on Symfony AI components. This addition enables more sophisticated automation workflows with support for controls that can pause execution for human approval, providing organizations with better governance over AI-driven processes. The framework includes configurable agents and integration with command-line tools for testing and management.
Several user interface refinements are in progress. Work continues on standardizing feedback controls across the ecosystem through a shared icon set for thumbs-up and thumbs-down, which will create visual consistency across different AI features. An evaluation of modern chatbot frontend libraries is underway to reduce technical coupling and improve customization options for organizations deploying conversational interfaces.
Several compatibility and functionality issues received attention, including problems with chatbot functionality in Drupal 11.4, streaming errors with newer Gemini models, and HTML preservation during content streaming. A merge request addressing token replacement behavior is under review to prevent unnecessary data from being sent to AI services.
How can I help on this project?
Consider prioritizing resources for the chatbot library evaluation to inform architectural decisions before broader adoption. Ensure testing capacity is available for the new Agents framework as organizations will need clear documentation and examples before deploying approval-gated automation workflows in production environments.
Contributors: harivansh sharma (harivansh), project update bot (Project-Update-Bot), Rodel Duterte (rduterte)
Drupal AI Initiative
Activity this period focused on planning and coordination for the September demonstration at DrupalCon Rotterdam. The team is working toward a single integrated site that will showcase AI search, content review, translation, editor chat, and quality guardrails working together on multilingual content. The goal is to let visitors experience these capabilities as a unified system rather than separate features, with the ability to launch the demonstration themselves in seconds.
Progress continued on the AI Content Review Workflow, which was closed during this period. Work continues on the supporting recipe and documentation to make these features easy to install and configure. Planning discussions also covered compliance requirements, including work needed for EU AI Act disclosure obligations.
Several coordination and process improvements are underway, including exploration of GitLab workflow automation to reduce manual maintenance overhead, and competitive research into WordPress 7.x AI features to inform design decisions. The initiative is also examining how to streamline testing across multiple development modules simultaneously.
How can I help on this project?
- Ensure the team has access to higher-education content partnerships or sample datasets needed for the Rotterdam demonstration site
- Support outreach to potential users or partners who could provide feedback on the integrated demonstration before the conference
AI Integration - ECA
Work has begun on preparing the module for compatibility with the next major version of the platform (Drupal 12). An automated process has identified areas where the module uses features that will no longer be supported, and a merge request with compatibility fixes has been prepared for review. This proactive work addresses technical debt before it becomes a problem, ensuring the module will continue to function when the platform evolves. The changes are ready for evaluation but have not yet been integrated.
The compatibility tracking issue remains open and will be updated as further adjustments are identified. This is standard maintenance work for a module in active development.
How can I help on this project?
Consider allocating developer time to review and test the pending compatibility updates, ensuring they meet quality standards before integration. If this module is strategically important, confirm ongoing maintenance support is resourced through the next platform release cycle.
Contributors: project update bot (Project-Update-Bot)
AI Agents Test
No significant development activity occurred during this period. The project continues to track an open enhancement request for Run more than one test group in Bulk - Test Collections?, which would allow users to execute multiple test groups at once rather than running them individually. This capability would support faster evaluation of different models and streamline automated testing workflows, helping teams compare performance across various configurations more efficiently.
The module remains in active development as part of the AI Initiative Sprint, with no commits or merged changes in the last 24 hours.
How can I help on this project?
- Confirm whether bulk test execution is a priority feature that should be resourced and scheduled for delivery.
- Ensure the team has dedicated capacity to work on enhancements beyond the current sprint commitments.
Gemini Provider
The Gemini Provider module saw continued planning activity focused on expanding its embedding capabilities and improving compatibility with the broader AI module ecosystem. Three issues were updated during the period, all related to ongoing sprint work.
Work is underway to add support for batch embeddings, which would allow multiple pieces of content to be processed together more efficiently. Progress on exposing provider capabilities continues, ensuring the module can properly communicate what features it supports to other parts of the system. Additionally, planning for image embeddings is ongoing, which would enable searching and indexing based on visual content rather than just text—a capability that distinguishes Gemini from most other AI providers.
No code was merged during this period. The work remains in the development and review stages, which is typical for active feature development in an evolving module.
How can I help on this project?
- Ensure the team has access to subject matter experts who can validate whether image embedding capabilities meet real user needs and business use cases.
- Clarify priority between batch processing efficiency improvements and new image features to help the team sequence work effectively.
Model Context Protocol
The Model Context Protocol module saw development progress during this period focused on security and access control. A merge request addressing OAuth scope validation was opened, introducing controls to ensure proper authorization checks when the module interacts with external systems or resources. This work strengthens the module's ability to enforce permissions and prevent unauthorized access, which is important for protecting sensitive content and maintaining compliance in enterprise environments.
The module remains in active development with work continuing on foundational security features. As an early-stage project, ongoing development activity like this is expected and healthy.
How can I help on this project?
- Ensure the development team has access to security review expertise to validate OAuth implementation patterns before release
- Clarify the timeline and business priority for reaching a stable release to help focus development efforts
Contributors: Shubham Goel (shubhamgoel)
AI Agents
The reporting period saw continued work on governance, safety, and multi-agent orchestration capabilities. Ten existing feature and improvement issues were updated, primarily around permission models, tool execution controls, and agent coordination.
Key themes include efforts to allow agents to adopt specific roles or permissions when executing tools (decoupling agent authority from end-user sessions), mechanisms to limit how often a tool can run (preventing infinite loops or runaway behaviour), and a new approval-mode system that would let administrators gate sensitive tool calls with human review before execution. Work is also progressing on multi-agent memory management, enabling parent agents to pass context efficiently to child agents without losing fidelity or incurring excessive token costs.
A new bug was identified around agent machine-name validation: the system currently allows administrators to create agents whose identifiers collide with code-defined plugins, causing silent failures. An automated compatibility merge request for Drupal 12 was opened but not yet merged.
Overall, the project is advancing steadily toward production-grade agent orchestration with better safety controls and clearer operational boundaries. No blocking issues were reported during the period.
How can I help on this project?
- Prioritise resourcing for the permission and role model work, which underpins secure autonomous agent deployments.
- Review and approve the proposed tool approval-mode design to unblock development of human-in-the-loop safeguards.
Contributors: project update bot (Project-Update-Bot)
Tool API
Three merge requests addressing input validation and developer tooling were opened during this period.
Two security-oriented improvements were prepared to strengthen how the system handles invalid or incomplete tool inputs. The first ensures that validation now checks every item when multiple values are provided, rather than stopping at the first error—meaning users will see all problems at once instead of fixing issues one at a time. The second change makes the system fail safely when tool input is invalid or missing, denying access rather than exposing errors or allowing unintended behavior.
A third request introduces tooling to help developers generate Tool plugins following best practices, which should reduce onboarding time and improve consistency across implementations.
All three changes remain under review. No issues were updated and no code was merged during the period, indicating the project is in an active development phase with work progressing toward integration.
How can I help on this project?
- Ensure reviewer capacity is available to evaluate and merge the three open validation and tooling improvements.
- Clarify timelines or priority for stabilizing input handling ahead of broader adoption.
Contributors: Alex Urevick-Ackelsberg (alexua), Marcus Johansson (Marcus_Johansson)
Drupal Canvas
Development activity this period focused on artificial intelligence capabilities and infrastructure improvements. Nine new issues were opened to outline the architecture for a multi-agent AI system that will enable the platform to build pages, create components, and answer user questions through a conversational interface. The work establishes a foundation for a tool selection interface that lets users direct which AI capability handles their request, rather than relying solely on automated routing.
A merge request addressing language prefix handling was opened, fixing an issue where users editing content in multilingual configurations could encounter broken redirects or blank screens. Separately, dependency management infrastructure continued routine updates.
The AI work represents a significant evolution in how users will interact with the page building system. Currently, timeout limitations on hosted platforms prevent complex operations from completing, and any validation error forces a complete rebuild. The planned architecture breaks work into smaller requests that can provide progressive feedback and recover from partial failures.
How can I help on this project?
- Provide guidance on whether the AI chat interface should expose all available tools to users immediately, or introduce them progressively as the feature matures and testing validates their reliability.
- Ensure hosting platform constraints (timeout limits, rate limits) are documented and shared with the development team to inform architectural decisions around request chunking.
Contributors: **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Fons Vandamme (f0ns), Rajab Natshah (RajabNatshah), Tim Plunkett (tim.plunkett), AKHIL BABU (AkhilBabu)
Context Control Center (CCC)
Progress this period focused on stabilizing documentation, guidance, and developer experience ahead of the 1.0 release. Three substantial pieces of work were merged: comprehensive pre-release documentation covering security guidance, API annotation, and trust boundaries; improved guidance on writing effective "Purpose" descriptions for conditional subcontext features, helping authors understand how models use this field to decide which context applies; and a developer experience improvement that renamed two scope plugins to better reflect their actual use—clarifying that one applies to entire entity types rather than bundles, and the other to individual entity items rather than generic targets.
Planning activity continued around the upcoming Inside AI Rotterdam demo, including the design of a recipe to ship university-specific context and wire consumer subscriptions for the demo site. Several open issues are now being refined to address selection behavior, token budgets, permissions documentation, and quality assurance readiness. Work to remove the overlapping "max items" limit in favor of the more accurate token budget control remains in progress, as does the addition of a priority field to give editors explicit control over selection order when multiple items compete.
The project is in active beta. Multiple merge requests covering permissions, scope behavior alignment, and conditional subcontext configuration are under review. Quality assurance planning has begun to prepare for pre-1.0 testing, and beta testing feedback is driving refinements to UI help text and selection transparency.
How can I help on this project?
- Confirm resourcing and timeline commitments for the Inside AI Rotterdam demo, particularly recipe content creation and demo-site integration testing.
- Prioritize internal review bandwidth for in-progress merge requests covering permissions, scope alignment, and token budget UI—several are prerequisites for the stable release.
Contributors: Juan Correa (jucs7), Kristen Pol (kepol) [2], Tamas Balog (tbalog) [1]
AI CKEditor
The AI CKEditor module saw minimal activity over the past 24 hours. A maintenance update was opened to apply automated fixes generated by the project's update tooling. This type of work helps keep the codebase aligned with current Drupal standards and prevents technical debt from accumulating. The update has not yet been reviewed or integrated.
No issues were actively discussed or resolved during this period, and no code changes were finalized. This represents a quiet day for the module with routine maintenance as the only visible progress.
How can I help on this project?
- Ensure the team has sufficient capacity to review and merge the pending automated maintenance update, which keeps the module compliant with platform standards.
- Assess whether additional developer resources are needed to maintain momentum on module enhancements and issue resolution.
Contributors: project update bot (Project-Update-Bot)
AI Search
The AI Search module saw significant quality and reliability work during this period, with five issues opened that address data-loss risks and functional gaps in the search indexing pipeline.
Two critical data-integrity problems were identified and documented. Progressive indexing can drop tail chunks describes a scenario where content is marked as fully indexed even though large portions of it were never embedded or made searchable. A separate issue, Clearing/resetting an index in 1x doesn't reset chunk-slicing progress so items silently re-index with zero embeddings, highlights that re-indexing operations can result in completely empty search results for previously indexed content. Both issues affect search accuracy and completeness—users may not find content they expect to be available.
Work is also underway to support batch embeddings for improved indexing performance, which will reduce the time and cost required to index large content libraries. Two user-interface issues were logged: one around preview reporting and another concerning access to structured search result data.
No code was merged during this period; all activity focused on issue documentation and scoping.
How can I help on this project?
- Prioritize resolution of the two data-loss issues to restore confidence in search completeness and accuracy.
- Allocate development capacity to implement the batch embedding performance improvement, which will reduce infrastructure costs at scale.
AI translate
The AI Translate project saw significant planning activity this period, with four new strategic issues opened to address cost efficiency and architectural flexibility. No code was merged or committed in the past 24 hours.
Two issues focus on reducing translation costs. Currently, the system sends one request per field, repeating the same instructions with each call—wasting tokens and budget. The batch translation proposal would consolidate multiple fields into a single request. Separately, a caching and deduplication feature would prevent re-translating unchanged content and eliminate duplicate work when the same text appears multiple times across a page.
A refactoring proposal aims to make the module's translation workflow reusable across different interfaces—including a new AI agent-driven translation path—by centralizing shared logic rather than duplicating it across endpoints.
One bug was reported: media translation fails with an error when attempting to translate media entities. A fix has been proposed.
How can I help on this project?
- Prioritize which cost-saving feature (batching or caching) delivers the highest return, and allocate resources accordingly to avoid duplicated effort.
- Clarify strategic direction on agent integration and approve scope for the workflow refactor to prevent over-engineering.
FlowDrop
FlowDrop delivered two releases over the past 24 hours, focused on governance controls for automated workflows. Version 2.1.0 introduced a confirmation gate that allows workflow operators to pause and approve high-risk actions—such as publishing content, sending emails, or calling external services—before the system executes them. This safeguard reuses existing human-in-the-loop infrastructure and is backward-compatible with existing workflows.
Work immediately began on version 2.2.0, which refines the confirmation model based on the principle that requiring approval is a governance decision, not a technical property of individual tools. The update introduces permission controls so organizations can centrally manage which actions require human oversight, regardless of context. Security improvements include redacting sensitive credentials from approval prompts, ensuring consent can only be granted once, and failing safely when the system cannot determine risk level. The confirmation gate feature that shipped in 2.1.0 has been closed, and planning continues on the governance settings refinement for the next release.
How can I help on this project?
- Review and approve the governance model being designed for 2.2.0 to ensure it aligns with organizational risk and compliance requirements.
- Identify pilot teams who can test the confirmation controls with real workflows and provide feedback before wider rollout.
Contributors: Shibin Das [17]
Langfuse
Development activity this period focused on expanding the module's capabilities for collecting user feedback. A merge request was opened to introduce feedback functionality, which will allow site administrators to capture and score user responses. This feature is being packaged as a separate submodule, giving implementers the flexibility to enable feedback collection only where needed. The work represents a significant enhancement to the module's value proposition, as feedback mechanisms are essential for improving content quality and user engagement.
No commits were merged during this period, and the module continues its early-stage development without critical blocking issues.
How can I help on this project?
- Allocate review resources to evaluate and merge the pending feedback functionality, accelerating time to market for this capability.
- Clarify the strategic roadmap and release timeline to help prioritize which features should advance toward a stable release.
Contributors: Abhisek Mazumdar (abhisekmazumdar)
AG-UI
Activity this period focused on preparing the module for future compatibility. An automated process identified updates needed to align with Drupal 12, and a corresponding merge request was opened to address deprecated code usage. This work ensures the module can continue functioning as the Drupal platform evolves, reducing technical debt and preventing future maintenance burdens.
Separately, progress continued on a larger effort to improve the Drupal Assistant implementation. The goal is to transition from a proof-of-concept demonstration to a production-ready component that could replace existing chat interfaces. This initiative aims to better integrate with the broader AI tooling ecosystem and improve the user experience for site administrators interacting with the assistant feature.
No critical issues or blocking risks were identified during this period. The module continues to mature with routine maintenance and feature enhancement work underway.
How can I help on this project?
- Clarify strategic priority and timeline expectations for the Drupal Assistant enhancement to help the team sequence work effectively.
- Ensure adequate resourcing is available to support both compatibility maintenance and feature development simultaneously.
Contributors: project update bot (Project-Update-Bot)
References
[1] Add thumbs-up and thumbs-down icons to the shared AI icon set
[2] Automated Drupal 12 compatibility fixes for ai 2.0.x-dev
[9] ai_ckeditor: streamGenerateContent causes 400 Bad Request with Gemini 2.x models
[11] Preserve HTML in streamed output
[12] Indexing breaks with custom SearchAPI DataSource
[17] How does the provider notify of better models
[19] Provide AI usage reports in Drupal admin panel
[20] AI Agents framework built on Symfony AI Agent
[40] Add limits on how often a tool can run
[41] Let an agent use a role when running a tool
[43] Allow agents to have permissions, user or a role
[45] Make it possible to restrict the order of tools during agent executions
[47] feat: Per-tool approval mode (pre-approved / approve-once / always) with loop pause-resume
[54] fix: #3582961 fail closed when tool input is invalid or missing
[56] fix: #3582960 validate every multiple input item
[62] Canvas AI: Add a Drupal Canvas Agent that answers general questions
[63] Canvas AI: Research how a user can cancel a running chat turn
[64] Canvas AI: Add end-to-end kernel coverage for the dev page builder agent
[65] Canvas AI: Add a dev page builder agent and wire the placement tools
[66] Canvas AI: Add a catalog-only parameter to the get_component_context tool
[67] Canvas AI: Run the agent selected in configuration instead of a hardcoded one
[68] Canvas AI: Expose Props of Blocks to the Agent
[69] Canvas AI: Client-side orchestration loop for Canvas AI(POC)
[70] Canvas AI: Add Tools dropdown to chat UI
[71] Canvas AI: page builder discards the whole build when the LLM names a region that does not exist
[75] task: #3567225 Make the component tree loader extensible
[76] Pre-1.0 documentation, trust, and compatibility follow-up to issue 3586363
[77] Remove max_items context limit and rely on the token budget
[78] Document Purpose field guidance for conditional subcontext selection
[81] Add context item Priority field and use it for selection ordering
[82] Rename entity bundle and target entity scope plugins for better DX
[84] Introduce more granular permissions to CCC
[94] Review and update CCC permissions before rc1
[95] Document the AI Context role and permission matrix for 1.0
[98] CCC QA scripts for 1.0 testing
[110] Persist context-item token counts and show token-budget usage in CCC UI
[111] QA team start testing CCC to get familiar with functionality and create QA plan
[113] Issue #3586378: Remove max_items context limit and rely on token budget.
[115] Issue #3586382: Pre-1.0 documentation, trust, and compatibility follow-up.
[116] Issue #3586376: Add context item priority field and selection tie-breakers.
[117] Issue #3586276: Rename entity bundle and target entity scope plugins for better DX
[118] Issue #3586390: Document purpose guidance for conditional subcontext.
[121] Issue #3586395: Document the AI Context role and permission matrix for 1.0.
[126] Issue #3586379: Persist token counts and show budget usage in CCC UI.
[128] Progressive indexing can drop tail chunks
[129] Batch embeddings for improved indexing performance
[133] Aggregate a node's translatable field-columns into a single chat request (opt-in batch translation)
[134] Refactor translation workflow to support Tool API and agent-driven translation
[135] InvalidArgumentException: Invalid translation language (und) when translating media entities
[136] Feature: Translation result caching and cross-field deduplication
[137] Add a requires_confirmation flag to flowdrop_node_type, wired to the existing interrupt/HITL engine
[139] Issue #3548465: Add createScore() for feedback and a langfuse_feedback submodule
Shipped
- Context Control Center scope plugin DX improvements — Renamed AiContextScopeEntityBundle to Entity Types and AiContextScopeTargetEntity to Entity Item for clearer developer experience [117].
- Context Control Center pre-1.0 documentation and security hardening — Completed documentation, API annotation, security guidance, and release-policy work identified during TDT preparation [115].
- Context Control Center Purpose field guidance — Added inline documentation to help authors write effective Purpose text for AI-based conditional subcontext selection [118].
- FlowDrop 2.1.0 confirmation gates — Added requires_confirmation flag to flowdrop_node_type wired into the existing interrupt and human-in-the-loop engine [137].
Ongoing
- AI Agents framework built on Symfony AI Agent — Major merge request introducing ai_agent module with plugin-based runtimes, controls, input processors, and config entities spanning over 17,000 lines [20].
- AI Automator token replacement stripping unresolved tokens — Merge request in progress to strip unresolved tokens from prompts when checkbox is enabled [22].
- Tool API input validation hardening — Two merge requests open to validate all items in multiple inputs and fail closed when tool input is invalid or missing [54][56].
- Context Control Center priority field and token budget tracking — Multiple merge requests open adding priority field for selection ordering, removing max_items limit, and persisting token counts with budget usage display [113][116][126].
- AI Search progressive indexing chunk-dropping bug — Tokenizer mismatch between computeItemChunks and getEmbedding causing items to be marked complete before all chunks are embedded [12].
- FlowDrop 2.2.0 governance refactor — Open issue to replace requires_confirmation tri-state with a confirmation settings map, add dedicated permission, and implement fail-closed plugin resolution with secret redaction [138].
AI (Artificial Intelligence)
Activity over the past 24 hours centered on issue triage, feedback, and one major new feature proposal. No merge requests were merged during this period.
A significant new merge request was opened for an AI Agents framework built on Symfony AI Agent, introducing the ai_agent module with plugin-based runtimes, controls, input processors, and config entities. The implementation spans over 17,000 lines and includes six controls such as system_context, deny_tool, and require_approval, along with Drush commands and an agent runner service.
Several issues received updates addressing specific pain points. Discussion continued on non streaming broken (fiber branch), which identifies an issue in OpenAiBasedProviderClientBase::chat() where Fiber::getCurrent() forces streaming even when not requested. Work progressed on AI Automator Token Replacement with removing unresolved Tokens via MR !1884. The ai_ckeditor: streamGenerateContent causes 400 Bad Request with Gemini 2.x models issue documents a malformed request body when calling streamGenerateContent against newer Gemini models.
Other active issues include Preserve HTML in streamed output, Drupal 11.4 DeepChat Block does not work with Webprofiler enabled, and Introduce a modern AI Chatbot frontend library proposing assistant-ui as an alternative to DeepChat.
How can I help on this project?
Review the open AI Agents framework merge request for architecture feedback. Investigate and provide fixes for the Fiber streaming bug in OpenAiBasedProviderClientBase. Test and diagnose the Webprofiler compatibility issue with DeepChat in Drupal 11.4.
Contributors: harivansh sharma (harivansh), project update bot (Project-Update-Bot), Rodel Duterte (rduterte)
Drupal AI Initiative
Activity this period focused on planning and coordination for DrupalCon Rotterdam. The AI Content Review Workflow meta issue was closed, marking completion of that feature set. Discussion continued on the 2026 AI Inside Roadmap to DrupalCon Rotterdam 2026, which aims to demonstrate AI Search, AI content review, AI translation, editor-facing chat, observability, and guardrails working together on a single multilingual site deployable via Drupal Forge. The recipe does not yet install cleanly.
Planning work continued on several infrastructure items: AI Starterkit setup, AI Validations Recipe creation, and GitLab workflow automation exploration. A UX task was opened to investigate WordPress 7.x AI features for reference. The DrupalForge documentation issue remains blocked on determining how to handle issues spanning multiple dev module versions.
No merge requests were merged and no commits were pushed during this period.
How can I help on this project?
- Pick up the AI Validations Recipe issue, which needs a recipe created compatible with Drupal CMS.
- Help explore automation platforms for the GitLab workflow automation task by evaluating Rules, ECA, or custom module approaches.
AI Integration - ECA
An automated merge request for Drupal 12 compatibility was opened during this period. The Automated Project Update Bot fixes MR addresses deprecated API usage identified in the Automated Drupal 12 compatibility fixes for ai_integration_eca 1.0.x-dev issue. The merge request contains 478 lines of changes targeting the project-update-bot-only branch. No commits were merged during the reporting period, leaving the Drupal 12 compatibility work pending review and integration.
How can I help on this project?
Review the Automated Project Update Bot fixes merge request to validate the Drupal 12 compatibility changes. Test the proposed deprecation removals against current Drupal 12 APIs to ensure functionality is preserved. Provide feedback on the MR to help move it toward merge.
Contributors: project update bot (Project-Update-Bot)AI Agents Test
The AI Agents Test module saw no merges or commits during this period. One issue remains under discussion: Run more than one test group in Bulk - Test Collections?, which proposes adding functionality to execute multiple test groups simultaneously. The issue explores potential UI approaches, including a views-style bulk operations interface with checkboxes or a tagging system for test groups. This feature would support automated testing workflows and model comparison scenarios. MR !11 is related to this work.
How can I help on this project?
- Review the existing merge request !11 related to bulk test execution and provide feedback on the proposed approach.
- Test the current implementation with different AI models to help validate the bulk operations workflow.
Gemini Provider
No merge requests were completed during this period, but several open issues saw activity around capabilities and embeddings support.
Discussion continued on Add support for batch embeddings, which has been updated to reflect naming decisions and CI adjustments to load the required AI Core branch. This work would enable the Gemini provider to leverage the batchEmbedContents method when handling multiple embeddings.
The Implement getSupportedCapabilities method in Provider class issue remains open. The AiProviderInterface includes a getSupportedCapabilities() method, but the Gemini provider currently returns an empty array, which will cause issues once capability checking is added to AI Core.
Work on Image Embeddings is also in progress. Gemini supports file embeddings including images, but the current embedding solution only handles text.
How can I help on this project?
Review the merge request on Add support for batch embeddings, which is in needs review state. Help implement the getSupportedCapabilities() method to properly expose Gemini's capabilities. Test and provide feedback on image embedding functionality once available.
Model Context Protocol
Activity in the Model Context Protocol module over the past 24 hours focused on OAuth security improvements. A merge request for Add Oauth Scope Validation was opened, introducing validation for OAuth scopes across 865 lines of changes. This work aims to strengthen authentication controls within the module's OAuth implementation. The merge request is currently awaiting review before it can be integrated into the codebase.
How can I help on this project?
Review the open OAuth scope validation merge request to provide feedback on the implementation and help move it toward completion. Testing the changes against various OAuth configurations would be particularly valuable.
Contributors: Shubham Goel (shubhamgoel)
AI Agents
The project saw extensive planning and issue refinement during the reporting period, though no merge requests were landed. The Automated Project Update Bot fixes merge request was opened to address Automated Drupal 12 compatibility fixes for ai_agents 1.4.x-dev, containing automated compatibility updates for Drupal 12.
Several new issues were filed focusing on agent configuration and control. AI Agent entity form should reject machine names that collide with existing code-plugin IDs identifies a namespace collision bug in AiAgentManager::findDefinitions() where config entities can silently override code-defined plugins. feat: Per-tool approval mode (pre-approved / approve-once / always) with loop pause-resume proposes approval gates for sensitive tool execution. Allow callers to supply additional tags for the chat calls made by AiAgentEntityWrapper addresses ai_logging correlation gaps. Use the ai_json_schema editor for the AI Agent structured-output schema field suggests replacing the plain textarea with the ai_json_schema element for better validation and editing.
How can I help on this project?
Review the open Automated Project Update Bot fixes merge request for Drupal 12 compatibility. Pick up AI Agent entity form should reject machine names that collide with existing code-plugin IDs to add validation in the entity form. Work on Use the ai_json_schema editor for the AI Agent structured-output schema field to improve the schema editing UX.
Contributors: project update bot (Project-Update-Bot)Tool API
Three merge requests addressing tool input validation and developer experience were opened during this period. fix: #3582960 validate every multiple input item updates TypedInputsTrait to validate all items in multiple inputs rather than stopping at the first violation, ensuring comprehensive error reporting. fix: #3582961 fail closed when tool input is invalid or missing hardens ToolBase::access() to catch InvalidArgumentException during input value retrieval, returning a forbidden result with uncacheable denial to prevent exposure of validation details. The type signature for the $return_as_object parameter was also aligned with ToolInterface. Meanwhile, Resolve "Create a skill for generating Tool plugins (best practices, how-to, placement)" introduces developer-facing guidance for plugin creation. All three requests remain open awaiting review.
How can I help on this project?
Review and test MR !112 or MR !113 to verify input validation behavior. Test MR !93 for completeness and accuracy of plugin generation guidance.
Contributors: Alex Urevick-Ackelsberg (alexua), Marcus Johansson (Marcus_Johansson)
Drupal Canvas
Canvas AI Development
A significant roadmap of Canvas AI improvements is now tracked across multiple new work items targeting Sprint 16. The focus is on multi-agent orchestration, tool wiring, and UX enhancements. Key areas include adding a general-purpose Drupal Canvas Agent for answering questions, wiring the dev page builder agent with placement tools, and adding a catalog-only parameter to the get_component_context tool. A major infrastructure change will make the controller run the agent selected in configuration rather than a hardcoded instance. Test coverage is a priority, with new issues opened for Playwright coverage of the agent hop loop and end-to-end kernel tests for the page builder agent.
Two active issues received updates: page builder discards the whole build when the LLM names a region that does not exist and Expose Props of Blocks to the Agent. Work continues on the client-side orchestration loop POC and Tools dropdown for the chat UI.
Bug Fixes and Code Quality
An open merge request addresses PHPStan failing on global $argv usage to eliminate intermittent pipeline failures. A language-prefix redirect issue was refined in MR !1387 to preserve query strings and strip default language prefixes correctly. Dependency updates are tracked via Renovate, with MR !1238 proposing npm package updates.
How can I help on this project?
- Review MR !1485 addressing the PHPStan
$argvissue. - Pick up unassigned AI issues like add a catalog-only parameter to get_component_context or cover the error path for stored agent state.
- Research and propose a solution for how a user can cancel a running chat turn.
Contributors: **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Fons Vandamme (f0ns), Rajab Natshah (RajabNatshah), Tim Plunkett (tim.plunkett)
Context Control Center (CCC)
Three significant merges landed during the period, advancing the module toward its 1.0 release. The Pre-1.0 documentation, trust, and compatibility follow-up (MR !253) was merged, completing documentation, API annotation, security guidance, and release-policy work identified during TDT preparation. The scope plugin DX rename (MR !195) was also merged, renaming AiContextScopeEntityBundle to Entity Types and AiContextScopeTargetEntity to Entity Item for clearer developer experience. Additionally, the Purpose field guidance for conditional subcontext (MR !246) was merged, providing authors clearer inline documentation on writing effective Purpose text to improve AI-based selection decisions.
Several issues were closed after validation, including conditional subcontext selection testing, permissions review, and Drupal 10 attribute-based hook invocation fixes. Progress remains blocked on several fronts: scope scoring and language alignment requires coordination with another issue, and multiple open MRs—including token budget removal, priority field addition, and provider config resolution—await review before stable release.
How can I help on this project?
Review the open MR for Global context checkbox description rendering (!240), which fixes a literal <br> display bug. Test the use_default provider config resolution MR !247 with real providers to verify conditional subcontext selection works correctly. Help draft QA scripts for 1.0 testing, which currently has no related MRs.
Contributors: Juan Correa (jucs7), Kristen Pol (kepol) [2], Tamas Balog (tbalog) [1]
AI CKEditor
Activity over the past 24 hours was limited to automated maintenance. A merge request titled Automated Project Update Bot fixes was opened, containing changes from an automated project update run. The MR spans 432 lines of diff and remains in an opened state. No commits were pushed and no issues were updated during the reporting period.
How can I help on this project?
Review the Automated Project Update Bot fixes merge request to assess whether the automated changes are safe to merge. Check the project's issue queue for unassigned bugs or feature requests that need attention.
Contributors: project update bot (Project-Update-Bot)
AI Search
No merge requests or commits landed during this period. Activity focused on issue tracking and triage for progressive indexing problems introduced by recent chunk-slicing work.
Five issues were updated, all tagged for the current sprint. Two critical bugs affect the progressive/long-chunk embedding strategy: Progressive indexing can drop tail chunks describes a tokenizer mismatch where computeItemChunks() hardcodes gpt-3.5 while getEmbedding() uses the configured tokenizer, causing items to be marked complete before all chunks are embedded (106 counted vs 370 actually produced in one case). A related clearing bug is tracked in Clearing/resetting an index in 1x doesn't reset chunk-slicing progress, where search_api_item.processed_chunks state persists after index resets, causing items to silently re-index with zero embeddings.
The Preview reports first batch as total chunks issue documents a UX problem where the index fields preview form shows only the first slice (up to ten chunks) as the total. Meanwhile, RagTool::execute() should expose structured per-result data and check entity access requests API improvements to surface per-result metadata and entity access checks, and Batch embeddings for improved indexing performance is a placeholder for porting batch functionality from AI Core.
How can I help on this project?
Pick up Progressive indexing can drop tail chunks and investigate the tokenizer mismatch between computeItemChunks() and getEmbedding(). Work on the index clearing bug to ensure search_api_item.processed_chunks resets properly. Add entity access checks to RagTool::execute() per the RagTool structured output issue.
AI translate
No code was merged during this period. Four design and architecture issues were opened or updated, all aimed at improving translation efficiency and workflow flexibility.
The current single field-column per chat request approach is being reconsidered. Aggregate a node's translatable field-columns into a single chat request (opt-in batch translation) proposes batching multiple columns into one prompt to avoid re-sending identical instructions on every field. This would significantly reduce token usage for typical multi-field content.
A broader refactoring is under discussion in Refactor translation workflow to support Tool API and agent-driven translation, which aims to consolidate the current UI batch and Drush workflows with a new Tool API entry point, avoiding logic duplication across three translation triggers.
Two concrete issues were also raised: InvalidArgumentException: Invalid translation language (und) when translating media entities blocks media translation due to improper language handling, and Feature: Translation result caching and cross-field deduplication proposes a caching layer to avoid re-translating unchanged or repeated content.
How can I help on this project?
- Fix the media translation bug in InvalidArgumentException: Invalid translation language (und) when translating media entities, marked as a Quick Win with a proposed patch in the description.
- Weigh in on the API design for batch translation in Aggregate a node's translatable field-columns into a single chat request or the Tool API refactor in Refactor translation workflow to support Tool API and agent-driven translation.
FlowDrop
FlowDrop shipped two releases over the reporting period. Version 2.1.0 introduced a confirmation gate for tool nodes, closing Add a requires_confirmation flag to flowdrop_node_type, wired to the existing interrupt/HITL engine. The feature wires a requires_confirmation flag on flowdrop_node_type into the existing interrupt and human-in-the-loop machinery, allowing operators to pause workflows before risky actions execute.
Work immediately continued toward 2.2.0, which refactors the confirmation model from a tri-state processor property into a governance settings map. Multiple fixes landed in flowdrop_runtime, flowdrop_interrupt, and flowdrop_node_type: gate interrupts now expire with cancellation semantics, consent consumption is atomic, resolved secrets are redacted from persisted gate prompts, and unassigned gate interrupts are surfaced. A dedicated permission for confirmation governance was added, and the runtime now resolves confirmation governance-first and fails closed when plugin resolution fails. Legacy requires_confirmation values are folded forward in preSave(). Documentation updates include 2.2.0 release notes, upgrade paths, trust boundary coverage, and rewritten gate governance rules (RT-GATE-7 through RT-GATE-10).
How can I help on this project?
Review the design proposal in Confirmation is governance, not a processor property: replace the requires_confirmation tri-state with a confirmation settings map, which remains open. Test the 2.2.0 governance refactor against your use cases, particularly around permission boundaries and upgrade paths from 2.1.0.
Contributors: Shibin Das [17]Langfuse
A new merge request was opened to add feedback capabilities to the Langfuse module. The Add createScore() for feedback and a langfuse_feedback submodule proposal introduces a createScore() method and packages feedback functionality into a dedicated submodule. The merge request spans over 800 lines of diff and is currently awaiting review.
No commits were pushed or merge requests merged during this period. The feedback implementation represents the primary development activity for the module over the past 24 hours.
How can I help on this project?
Review the feedback submodule merge request to provide technical feedback on the createScore() implementation and API design. Test the functionality against Langfuse's scoring API to verify integration correctness.
Contributors: Abhisek Mazumdar (abhisekmazumdar)
AG-UI
Activity in the AG-UI module over the past 24 hours focused on automated compatibility improvements for Drupal 12. A new Automated Drupal 12 compatibility fixes for agui 1.0.x-dev issue was opened to track removal of deprecated API uses, with corresponding Automated Project Update Bot fixes merge request submitted. The MR introduces changes across 68 lines to address deprecation warnings.
The [META] Improve Drupal Assistant Implementation issue also saw activity. This meta issue tracks work to refactor the current proof-of-concept Drupal Assistant demo page to align with the ai_chatbot (Deepchat) module and integrate with the Polling service for AG-UI event emission. The work aims to move from a proof-of-concept to a production-ready implementation that properly hooks into AI module events.
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 appropriate. Help scope out child issues for the Drupal Assistant meta by identifying specific refactoring tasks needed to integrate with the ai_chatbot module and Polling service.
Contributors: project update bot (Project-Update-Bot)
References
[1] Add thumbs-up and thumbs-down icons to the shared AI icon set
[2] Automated Drupal 12 compatibility fixes for ai 2.0.x-dev
[12] Indexing breaks with custom SearchAPI DataSource
[17] How does the provider notify of better models
[20] AI Agents framework built on Symfony AI Agent
[22] Issue #3586535: AI Automators strip unresolved tokens from prompts
[54] fix: #3582961 fail closed when tool input is invalid or missing
[56] fix: #3582960 validate every multiple input item
[113] Issue #3586378: Remove max_items context limit and rely on token budget.
[115] Issue #3586382: Pre-1.0 documentation, trust, and compatibility follow-up.
[116] Issue #3586376: Add context item priority field and selection tie-breakers.
[117] Issue #3586276: Rename entity bundle and target entity scope plugins for better DX
[118] Issue #3586390: Document purpose guidance for conditional subcontext.
[126] Issue #3586379: Persist token counts and show budget usage in CCC UI.
[137] Add a requires_confirmation flag to flowdrop_node_type, wired to the existing interrupt/HITL engine