Daily Digest
Daily Digest – 11 May 2026
Shipped
- AI module bug fixes ahead of 1.4.0 release — Two bugs were resolved and merged: one that caused AI assistant features to fail by default, and one that was blocking automated tests from passing, clearing the path for the upcoming release.
- Drupal AI TV page upgraded with embedded video — The Drupal AI TV page now displays videos directly rather than linking away, creating a more professional experience for visitors and supporting the initiative's broader marketing push.
- FlowDrop version 1.11.0 released — The release delivers a new admin settings form for no-code configuration, a visual layout fix, and a correction to how interrupted pipeline jobs are reported, improving reliability for teams tracking automation outcomes.
- Drupal Canvas testing infrastructure improved — Automated quality checks were strengthened and external dependencies reduced, making the delivery pipeline more self-sufficient and reliable.
- Context Control Center beta blog post and status video completed — Both communications assets were finished and closed, supporting awareness and adoption of the module ahead of its beta launch.
Ongoing
- AI module 1.4.0 release preparation — A formal quality assurance run is underway, with a fix for AI translation silently skipping custom fields and a performance improvement for settings page load times both under review before launch.
- Enterprise AI Summit preparations — Visual assets, a call for sessions, and a call for sponsors are all in progress ahead of the September 28 event in Rotterdam, with the sponsor deadline falling on May 31.
- Gemini Provider capability expansion — Two proposals adding batch content processing and image understanding are awaiting review, with no approvals yet, despite representing significant new functionality.
- AI Agents conversational chat feature — Work to connect AI agents to chatbot interfaces is stalled pending a product decision on whether a single chat session should support multiple agents or be tied to one.
- AI Content Classification post-install bug — A bug causing an error when content editors create new content immediately after installation remains open and unresolved, risking poor first impressions among early adopters.
2026 Capabilities Progress
- Page generation — Drupal Canvas shipped a testing infrastructure improvement and is advancing work on content referencing between pages and components, which expands what site builders can assemble. However, the volume of unmerged proposals means review capacity is the main risk to reaching a usable page-generation milestone.
- Context management — The Context Control Center (CCC) made meaningful progress today: UX improvements to the context view and listing pages are underway, and a pending contribution would introduce per-agent context configuration, giving administrators precise control over what each AI agent knows. A blog post and status video were also completed, supporting adoption. Next milestone is merging the open contributions and completing the UX redesign.
- Background agents — The AI Agents module is working toward a ChatProcessor that would connect agents to chatbot interfaces, but a design decision on single versus multi-agent chat sessions remains unresolved and is blocking development. The core AI module also fixed a bug where AgentRunner was setting wrong configurations, which had been causing agent features to fail by default — a meaningful reliability improvement. Risk: the unresolved design question could stall progress if not escalated quickly.
- Design system integration — No direct progress today. Drupal Canvas work on content referencing and component tooling is adjacent but not yet delivering the AI-driven design system capability specifically.
- Content creation and discovery — Several threads advanced this capability. The AI module fixed a bug silently skipping custom fields during AI translation, and batch processing for content indexing is in active development. The Gemini Provider has proposals awaiting review for batch embeddings and image embeddings, both of which would meaningfully expand search and discovery. The Huggingface Provider has a pending text classification contribution. The Milvus vector database has an improved content filtering proposal in review. Risk: all provider-level contributions are awaiting review and none are merged yet, creating a potential bottleneck.
- Advanced governance — No direct progress today. The AI Dashboard, which could underpin audit and oversight tooling, saw no feature development in this period.
- Intelligent website improvements — No direct progress today. Field Widget Actions, which supports AI workflow automation relevant to this capability, is in a holding pattern with minimal activity and an unresolved open item. This module's slow pace is a risk worth monitoring.
- Multi-channel campaigns — No direct progress today. The Drupal AI Initiative's marketing sprint is building external awareness of the platform, and the Enterprise AI Summit preparations are gathering pace, but neither advances the technical capability of creating and distributing campaign content from a single goal.
AI (Artificial Intelligence)
Release Preparation and Bug Fixes
The team is actively preparing for the 1.4.0 release, with a formal QA run underway to verify nothing is broken before launch. Two notable bugs were resolved during this period: a fix for AgentRunner sets the wrong configuration, which was causing AI assistant features to fail by default in Drupal CMS, and a fix for failing automated tests blocking a release on supported versions. Both are now merged and closed.
Developer and Editor Experience Improvements
Several improvements aimed at making the module easier to set up and use are in progress. Work is underway to add clear warnings when required interface components have not been built, preventing silent failures for site administrators. Testing documentation is also being updated to guide contributors through required setup steps, reducing friction during quality assurance. A performance issue causing slow initial page loads in the AI provider settings area has a proposed fix in review. Additionally, a bug affecting AI translation silently skipping custom fields has been reported and a fix submitted.
Ongoing Feature Development
Longer-term feature work continues in parallel, including a visual editor to simplify configuration of AI agent tools, batch processing to speed up AI-powered content indexing, and controls allowing site administrators to choose which content areas benefit from AI suggestions rather than having them applied everywhere by default.
How can I help on this project?
Leaders can support progress by ensuring contributors have access to adequate test environments for the 1.4.0 release QA effort. Prioritising a decision on which features are required for the release versus deferred would help the team focus. Encouraging organisational adoption or advocacy within the Drupal community can also attract additional contributors to address the open feature backlog.
Drupal AI Initiative
Summary
Activity over the past 24 hours was concentrated almost entirely in marketing and communications, with the initiative's third marketing sprint now underway (May 11-25). The team is actively promoting Drupal AI across multiple fronts: social media campaigns, event promotion, media outreach, and content development.
A notable win was the completion of two improvements to the Give d.o editors the ability to embed YouTube videos capability, which directly enabled the team to close out Replace YouTube links with video embeds on AI TV page -- meaning the Drupal AI TV page now offers a more professional, engaging experience for visitors. Several media outreach planning tasks were also formally closed, signalling the conclusion of Phase 1 groundwork by Pritam Prasun (pritamprasun).
Preparations for the Enterprise AI Summit (Rotterdam, September 28) are gathering pace, with work initiated on visual assets, a call for sessions, and a call for sponsors -- the latter carrying a deadline of May 31. The summit's website is also being redesigned for a more premium, enterprise-grade appearance. These efforts are time-sensitive and depend on design and approval resources being available promptly.
A proposal is also in progress to separate marketing work into its own dedicated project space, which would make it easier to manage the growing volume of activity without it obscuring other initiative work. The FOUNDATION - Finalise podcast name task is close to a decision, assigned to Dominique De Cooman (domidc) and Matthew Saunders (jmsaunders), with a name needed before any public launch activity can begin.
How can I help on this project?
- Unblock the sponsor and speaker pipeline for the Enterprise AI Summit by making introductions or endorsing outreach to potential sponsors before the May 31 deadline.
- Support official channel access for the podcast and YouTube presence by helping facilitate conversations with the Drupal Association.
- Champion the messaging guide effort, currently assigned to Will Huggins (ZoochaWill) and Shruti Desai (shruti.desai-at-acquia.com), by prioritising it as a strategic asset and ensuring dedicated time is allocated.
Gemini Provider
Activity over the past 24 hours was focused on expanding the capabilities of the Gemini Provider module, with two new merge requests submitted by Artem Dmitriiev (a.dmitriiev) and awaiting review.
Expanding What the Module Can Do
The first proposal, Support batch embeddings, would allow the system to process multiple pieces of content at once rather than one at a time. This is a meaningful efficiency improvement that could reduce processing time and costs when working with large volumes of content.
The second proposal, feat: #3588392 Image Embeddings, would extend the module's understanding beyond text to include images. This opens the door to richer, more intelligent content experiences for end users, such as image-based search or recommendations.
Both contributions are substantial in scope and represent meaningful forward progress. However, they are currently awaiting review and have not yet been approved or merged, so the work remains in progress.
How can I help on this project?
Consider ensuring that qualified reviewers have dedicated time to evaluate these contributions promptly, as delays in review can discourage contributors. If expanded AI capabilities are a strategic priority, signalling that to the team can help accelerate decisions and attract further investment in this module.
Huggingface Provider
Progress This Period
Activity on the Huggingface Provider module was light but purposeful during this period. A new contribution from Ahmad Khader (Ahmad-Khader) introduces text classification capability through the open merge request Resolve #3583809 "Add text classification". Text classification allows the system to automatically categorise content -- for example, sorting documents by topic or flagging submissions by sentiment -- which broadens the range of AI-powered tasks the module can support.
This work is still under review and has not yet been accepted into the project. No other changes or discussions were recorded in the past 24 hours, suggesting the team's focus is on getting this contribution reviewed and approved.
Key Risks
With only a single open contribution and no visible review activity, there is a risk of the work stalling if reviewers are unavailable or stretched across other priorities.
How can I help on this project?
Consider ensuring that a qualified reviewer has dedicated time to assess the pending contribution promptly. If the project depends on expanded AI capabilities to meet strategic goals, advocating for additional contributor resources or community engagement could help maintain momentum and reduce bottlenecks.
Milvus VDB Provider
Recent Activity
The past 24 hours saw two proposed improvements submitted for review, though no changes have been finalised and merged into the product yet.
Scott Euser (scotteuser) has submitted a proposal addressing Resolve #3589484 "Milvus restart on failure", which aims to improve the reliability of the Milvus integration by handling situations where the service stops unexpectedly. This reduces the risk of disruption to any AI-powered search or content features that depend on this module.
Separately, Richard Gaunt (RichardGaunt) has submitted Issue #3540662 - Added filter for index, which improves how content is organised and retrieved within the data store. This supports more accurate and targeted results for end users interacting with AI-driven features.
Both contributions are awaiting review and approval before they can be delivered. No issues were updated and no code was committed during this period, suggesting the project is in a review-dependent phase.
How can I help on this project?
Consider ensuring there are sufficient resources allocated to code review so these pending contributions are not left waiting. Encouraging team leads to prioritise reviewing open proposals will help maintain momentum and avoid contributor frustration that can stall open-source projects.
AI Agents
Current Focus
Activity over the past 24 hours was light, with two issues under discussion but no code merged or delivered during this period. The primary area of focus is enabling the AI Agents module to power conversational chat experiences in a way that matches the capabilities already available in the broader AI platform.
The most substantive open item is the Create an ChatProcessor issue, assigned to Ahmad Khalil (ahmad-khalil-imagex). This work would allow organisations to connect a specific AI agent directly to a chatbot interface, giving users a consistent, configurable conversational experience. The team is working through design decisions around whether a single chat session should support switching between multiple agents, or whether each chatbot should be tied to one agent. Resolving this question is important before development can move forward. The issue is currently under review.
A separate Test Issue assigned to Alphons Jaimon (AJV009) is also open and marked high priority, though its purpose appears to be administrative or process-related rather than a user-facing feature.
How can I help on this project?
Consider facilitating a quick decision on the product direction for multi-agent chat support, as this is blocking development. If the team lacks capacity to move faster, advocating for dedicated sprint time or additional resourcing would help. Connecting the right product stakeholders to weigh in on the user experience question could also unblock meaningful progress.
Drupal Canvas
Summary
Activity on Drupal Canvas over the past 24 hours shows a broad front of development work in progress, with one concrete delivery: a testing infrastructure improvement was merged and shipped. Sally Young (justafish) successfully merged Issue #3529128: Run Cypress tests in the drupal-testing image, which strengthens the project's automated quality checks and reduces reliance on external dependencies -- a quiet but important step toward a more self-sufficient and reliable delivery pipeline.
Beyond that, the team is advancing work across several strategically significant areas. Improvements to how the editing tool handles content translations are in progress, alongside work to give editors better visibility into publishing conflicts before they go live. Efforts to support referencing content between pages and components are also moving forward, which would significantly expand what site builders can do with the platform. Developer tooling -- including local setup, command-line workflows, and code quality checks -- is also receiving attention across multiple open proposals.
The volume of open, unmerged work remains high, with many proposals carrying substantial changes. Progress would benefit from focused review capacity to move these from draft to delivery.
How can I help on this project?
Leaders can support progress by ensuring the team has adequate capacity for code review, which is currently a bottleneck given the volume of open work. Prioritising which features matter most to the business -- such as translation support or conflict resolution for publishing -- would help the team sequence their efforts. Sponsoring dedicated reviewer time could accelerate delivery meaningfully.
Context Control Center (CCC)
Summary
Activity over the past 24 hours reflects a module in active development, with work spanning user experience improvements, new capabilities, and communication milestones. Two issues were closed, including the CCC beta blog post and a CCC status update video, both of which support broader awareness and adoption of the module.
On the product side, design updates are underway for both the context view page and the context listing page, reflecting feedback from a recent UX review. These changes aim to make the interface clearer and more usable for site builders and content editors.
Two merge requests are open and awaiting review. One, raised by Rob Loach (robloach), addresses the addition of Document Loader as a recommended module, enabling users to load content from documents directly into their AI context. The other, from Kristen Pol (kepol), introduces per-agent context configuration, giving administrators finer control over how much information each AI agent receives. A separate proposal by Rob Loach (robloach) would surface feature suggestions directly within the interface, helping users discover functionality they may not know is available.
How can I help on this project?
Leaders can support progress by ensuring dedicated developer capacity to review and merge the open contributions. Connecting the team with marketing stakeholders to act on the completed blog post and video would amplify the beta launch. Confirming prioritisation between UX polish and new feature work would help the team focus effectively.
AI Dashboard
Current Activity
Activity on the AI Dashboard project was light during this period, with no new code delivered or merge requests completed. The primary visible work involves an internal process investigation led by Christoph Breidert (breidert), exploring how issues and tasks can be migrated between projects. While this may appear minor, it has practical implications for how the team manages and organises its work across the broader AI initiative -- smoother project administration means less friction for contributors and clearer visibility into progress.
No new features, fixes, or enhancements were shipped in this 24-hour window. The project appears to be in a relatively quiet phase, at least within this snapshot.
How can I help on this project?
Leaders can support this project by ensuring the development team has sufficient dedicated time to maintain momentum between sprints. If the project is waiting on decisions around scope or priorities, bringing the right stakeholders together promptly can prevent delays. Consider also asking for a brief progress summary at the next leadership check-in to confirm the project is on track strategically.
Field Widget Actions
Activity on the Field Widget Actions module was minimal during this reporting period. A single item, Testing AI Workflow Automation, was opened by Artem Dmitriiev (a.dmitriiev) and is currently awaiting review. No code was merged or committed during the period, so there is no direct user-facing progress to report at this time.
Given the low volume of activity, the project appears to be in a holding pattern. There are no signs of active development momentum this cycle, which may indicate resourcing constraints or competing priorities among contributors. Leadership should monitor whether this pace reflects a temporary lull or a broader stall that could delay the module's roadmap.
How can I help on this project?
- Prioritise resourcing: Consider assigning dedicated development time to keep the project moving forward.
- Encourage review participation: Prompt team members or partners to actively review open items so work does not stall.
- Clarify strategic priority: Confirm whether this module remains a priority, so contributors understand where to focus their efforts.
FlowDrop
Summary
The FlowDrop project saw a focused burst of development activity during this period, with all work delivered by Shibin Das (shibindas). The team shipped version 1.11.0, marking a minor release that bundles several improvements for end users and administrators.
On the user-facing side, a new settings form has been introduced, giving site administrators control over the appearance and behaviour of the interface directly through the Drupal admin panel -- no code changes required. This lowers the barrier for teams to configure the module to their needs. A visual layout fix was also applied to ensure the interactive preview area displays correctly, improving the experience for anyone evaluating or testing interface components.
On the reliability side, a fix was made to ensure that pipeline jobs which end in an interrupted state are now correctly reflected in status summaries. Previously, such jobs may have been silently overlooked, which could have led to misleading reporting on workflow progress. This is a meaningful quality improvement for teams relying on FlowDrop to track automation outcomes accurately.
How can I help on this project?
Consider allocating dedicated testing time from a product owner or power user to validate the new admin settings form against real-world use cases. If there are stakeholders waiting on specific configuration capabilities, now is a good moment to align on priorities. Recognising the contributor's consistent solo output may also help with retention and sustained momentum.
AI Content Classification
Activity on this project over the past 24 hours was limited but notable from a quality standpoint. The team is tracking a Error when saving new node bug that affects users immediately after installation. When a content editor creates a new piece of content, an unexpected error is thrown, disrupting their workflow even though the AI-powered content tagging itself is functioning correctly in other scenarios. This is a reliability issue that could undermine confidence in the module among early adopters.
The issue has been logged and categorised as a normal-priority bug. No fixes were merged or committed during this period, meaning the problem remains open and unresolved. Progress will depend on a developer picking up the work and investigating the root cause.
Key risk: If left unaddressed, this bug creates a poor first impression for new users and could slow adoption of the AI content classification capability across the organisation.How can I help on this project?
- Prioritise assigning a developer to investigate the open bug, as it directly affects the user experience at first install.
- Consider advocating for dedicated sprint time or resources to move this module from early-stage to stable release.
- Help align stakeholders on the importance of AI-assisted content workflows to build organisational momentum behind the project.
Shipped
- AI module AgentRunner configuration fix — A regression blocking the 1.4.0 QA run was resolved by correcting a call to
setConfiguration()that should have beensetAiConfiguration(), which had been causing AI Assistants API to fail when using the default provider. - AI module ProviderProxyHostnameFilterTest unblocked on 1.2.x and 1.3.x — Missing params were added to YAML fixtures via two cherry-pick merges, resolving kernel test failures that were blocking releases on both branches.
- FlowDrop 1.11.0 released — The release adds the
INTERRUPTEDstatus to thegetPipelineJobs()summary map inflowdrop_pipeline, adds a UI settings configuration form toflowdrop_ui_components, and fixes a playground container height collapse. - Drupal Canvas Cypress tests migrated to drupal-testing image — Cypress test execution now runs on the
drupal-testingimage with a GitLab CI cache added, clearing a path toward removing the dependency on upstream GitLab templates. - Drupal AI Initiative media outreach planning completed — Phase 1 media outreach foundation issues and the step-wise outreach plan were closed, and YouTube embed support was enabled on the AI TV page.
Ongoing
- Context Control Center agent schema fields — A 1,331-line MR adds optional
max_global_items,max_items,max_tokens, andselection_modekeys toai_context.agentsconfig schema and updatesAiContextRequestFactory::fromAgent()to read per-agent limits, but is awaiting review. - Drupal Canvas shared Vite infrastructure for CLI builds — A 7,700-line MR from Bálint Kléri is blocking the CLI push-command fix for named-component style overrides and has not yet been merged.
- Gemini Provider batch embeddings and image embeddings — Two substantial MRs adding batch embedding support and image embedding capability are open with no reviewer feedback and appear stalled on review capacity.
- AI Agents ChatProcessor plugin — Implementation of a
ChatProcessorplugin to give agents feature parity with the AI Assistant layer is in needs-review state but has no code posted yet, with open design questions around multi-thread support. - AI module 1.4.0 QA run — The QA run required to clear the 1.4.0 release remains open and unassigned.
AI (Artificial Intelligence)
Merged and Shipped
Four MRs landed during the reporting period. The most impactful fix resolves a regression blocking the 1.4.0 QA run: AgentRunner sets the wrong configuration corrected a call to setConfiguration() that should have been setAiConfiguration(), causing AI Assistants API to fail when using the default provider. Artem Dmitriiev (a.dmitriiev) merged two cherry-pick MRs adding missing params to YAML fixtures, directly resolving the ProviderProxyHostnameFilterTest kernel test failures on 1.2.x and 1.3.x that were blocking a release. Sapnil Biswas (sapnil_biswas) also landed the banana test replacement to improve patch-testing documentation clarity.
Open Work Needing Attention
Norman Kämper-Leymann (koiwo) opened both an issue and MR to replace hardcoded field-name patterns in TextExtractor::shouldExtract() with an instanceof FieldConfigInterface check, fixing silent translation skips when field_prefix is empty. Pieter Frenssen (pfrenssen) flagged and submitted a fix for incorrect namespace declarations on OperationType input parameters, surfaced by PHPStan. The missing built assets warning MR from Joshua Fernandes (joshua1234511) is at RTBC. The 1.4.0 QA run remains open and unassigned.
How can I help on this project?
- Review MR 1569 for the missing built assets status report warning, which is already marked RTBC.
- Pick up the unassigned 1.4.0 QA run and follow the linked test instructions to help clear the release.
- Review the
TextExtractor::shouldExtract()fix and verify theFieldConfigInterfaceapproach does not unintentionally include base fields.
Drupal AI Initiative
Activity over the past 24 hours was entirely on the marketing and coordination side -- no code commits or merge requests landed in this window.
Closed Issues
Three issues were closed during the period. Notably, Give d.o editors the ability to embed YouTube videos, assigned to Brendan Blaine (B_man), reached a fixed state, unblocking the follow-up task to replace YouTube links with actual video embeds on the AI TV page. Accordingly, Replace YouTube links with video embeds on AI TV page was also closed by Duncan Worrell (dunx). Two media outreach tracking issues -- [Meta] Media Outreach - Phase 1: Foundation & Research and Prepare Step-wise Media Outreach Plan -- were closed by Pritam Prasun (pritamprasun), marking the completion of the outreach planning foundation ahead of the NYC Summit.
Open Work in Progress
Marketing Sprint #3 (May 11-25) kicked off, tracked by Jeremy Chinquist (jjchinquist) in the Marketing Sprint #3: May 11 - 25 [Meta] issue. Several sprint-scoped tasks are now open and unassigned, including visual assets for the Enterprise AI Summit's Call for Sessions and Call for Sponsors (both filed by wouters_frederik), with the sponsors deadline of 31 May 2026 creating time pressure.
A structural proposal from Jeremy Chinquist (jjchinquist) and Christoph Breidert (breidert) -- Marketing of the ai_initiative receives a dedicated ai_initiative_marketing Drupal project -- suggests splitting marketing issues into a separate project/ai_initiative_marketing repository to reduce noise on the main board. The FOUNDATION - Finalise podcast name issue, assigned to Dominique De Cooman (domidc) and Matthew Saunders (jmsaunders), is marked RTBC but remains blocked pending a name conflict check and stakeholder sign-off before platform setup can proceed.
How can I help on this project?
- The Enterprise AI Summit - Call for Sessions visual asset task is unassigned and time-sensitive -- pick it up if you have design capacity.
- Review and weigh in on the ai_initiative_marketing project split proposal -- it affects how all future work is triaged.
- The Update Chicago Driesnote repo to include demo prompts task is unassigned and straightforward for a developer familiar with the demo codebase.
Gemini Provider
Activity in the last 24 hours was limited to two open merge requests authored by Artem Dmitriiev (a.dmitriiev), with no commits merged or issues updated during the reporting period.
Open Merge Requests Awaiting Review
Dmitriiev opened Support batch embeddings (303 diff lines), which wires up batch embedding support tied to issue #3589183, and feat: #3588392 Image Embeddings (303 diff lines), adding image embedding capability. Both are substantial patches covering new API surface. Neither has been merged, and there are no blocking comments on record. Progress appears stalled pending reviewer attention rather than any technical blocker.
How can I help on this project?
Review Support batch embeddings and feat: #3588392 Image Embeddings -- both are open with no reviewer feedback. Focus on API contract consistency, error handling, and whether tests cover the new embedding methods. Either MR would benefit from a functional test covering edge cases such as empty input arrays.
Huggingface Provider
Activity on the Huggingface Provider module over the last 24 hours was limited to a single open merge request. Ahmad Khader (Ahmad-Khader) opened Resolve #3583809 "Add text classification", a 108-line diff that introduces text classification as a new operation type for the provider. This expands the module's coverage of Hugging Face inference capabilities beyond its existing operations. No commits were pushed and no issues received comments during the reporting period, so the MR is currently awaiting review and has not yet been merged.
How can I help on this project?
Milvus VDB Provider
Recent Activity
No commits were merged and no issues saw discussion during the reporting period, but two merge requests are open and awaiting review.
Scott Euser (scotteuser) opened Resolve #3589484 "Milvus restart on failure", a 12-line change aimed at improving resilience when the Milvus service restarts unexpectedly. Separately, Richard Gaunt (RichardGaunt) has a long-standing open MR, Issue #3540662 - Added filter for index, which adds index-level filtering support across 16 diff lines. Neither MR has seen reviewer activity or been merged yet, suggesting a bottleneck around code review capacity on this module.
How can I help on this project?
- Review and test the restart-on-failure MR against a live Milvus instance to validate the resilience logic.
- Check the index filter implementation in MR !15 for correctness and leave a substantive review comment to help move it forward.
AI Agents
Recent Activity
Activity in the AI Agents module over the last 24 hours was limited to issue triage and assignment, with no merges or commits landing in the reporting period.
The most substantive open work is the Create an ChatProcessor issue, which has been moved to Needs Review and assigned to Ahmad Khalil (ahmad-khalil-imagex). The goal is to implement a ChatProcessor plugin for agents, providing feature parity with the AI Assistant layer introduced upstream in the parent AI module. Open design questions remain around multi-thread support and whether a single agent-per-chatbot model is the right initial scope. The form is expected to expose settings for agent selection, error messaging, and conversation history. No code has been posted for review yet, so the issue is likely blocking dependent integrations.
A second item, Test Issue, was filed by Marcus Johansson (Marcus_Johansson) and assigned to Alphons Jaimon (AJV009) at high priority, though its purpose is unclear from available context.
How can I help on this project?
Review the open design questions on Create an ChatProcessor -- particularly around multi-thread support -- and leave concrete recommendations in the thread. If you have experience with the AI module's existing processor plugin architecture, drafting an initial plugin class or writing a test stub would accelerate progress.
Drupal Canvas
Merged and Shipped
The one merge in the reporting period was Issue #3529128: Run Cypress tests in the drupal-testing image, landed by Sally Young (justafish). The change migrates Cypress test execution onto the drupal-testing image and adds a GitLab CI Cypress cache, clearing a path toward removing the dependency on upstream GitLab templates.
Active MR Activity
Several substantial MRs remain open and under active development. Bálint Kléri (balintbrews) has opened feat(CLI Tool): Make CLI builds use shared Vite infrastructure, a 7,700-line diff that other CLI work depends on -- notably fix(CLI Tool): Push command overrides all components when using named component style, which lists it as a hard dependency. Christian López Espínola (penyaskito) continues work on feat: JSON Schema content-entity-reference, covering prop resolution in JsComponent, schema validation, and SDC definition injection. Tim Plunkett (tim.plunkett) opened a small but important housekeeping MR, chore: Fix deprecated PHPCS syntax, and Ben Mullins (bnjmnm) submitted #3589544 dont commit invalid props to prevent invalid prop values from being persisted.
Blockers
The CLI push-command fix is explicitly blocked on the shared Vite infrastructure MR merging first. The translation preview draft (Draft: Create preview for translations) and symmetric content inputs (Draft: Resolve #3583684 "Symmetric content inputs") both remain in draft status with no recorded activity in the period.
How can I help on this project?
Review Make CLI builds use shared Vite infrastructure to unblock the named-component push fix. The Fix deprecated PHPCS syntax MR is a 36-line change ready for a quick approval. You could also add missing testing instructions to #3589565 lint all, lint quiet, which currently has a placeholder checklist.
Context Control Center (CCC)
Open MRs and Active Development
No commits landed in the reporting period, but two merge requests are open and awaiting review. Rob Loach (robloach) opened Issue #3586228: Add Document Loader as a recommended module, a 32-line change that surfaces drupal/document_loader as a recommended dependency to support MDXEditor-based markdown source loading in context items. This is tied to the broader Integrate CCC with Document Loader for MDXEditor integration feature, which emphasises progressive enhancement.
The more substantial open MR is Issue #3586160: Add agent schema fields from Kristen Pol (kepol), a 1,331-line diff targeting the ai_context.agents config schema. It adds optional max_global_items, max_items, max_tokens, and selection_mode keys, updates the agent context configuration form, and modifies AiContextRequestFactory::fromAgent() to read per-agent limits rather than always falling back to global settings and a hardcoded minimal selection mode.
On the UI side, Update context listing page per new design is assigned to Aidan Foster (aidanfoster) and Eric Homanchuk (erichomanchuk), while Update context view page per new design sits with Eric Homanchuk (erichomanchuk). Both are still in progress. Rob Loach (robloach) also opened User Interface: Suggestions Directly in the UI, proposing in-UI nudges toward optional integrations currently only listed in composer.json.
How can I help on this project?
- Review the agent schema fields MR -- particularly the
AiContextRequestFactory::fromAgent()changes and config schema correctness. - Pick up the unassigned UI suggestions feature and prototype the in-UI optional module recommendations.
- Write a kernel test covering the new per-agent
selection_modeand token limit paths inAiContextRequestFactory.
AI Dashboard
Activity on the AI Dashboard module was minimal during the reporting period, with no merge requests merged and no commits pushed. The only updated issue was a housekeeping task opened by Christoph Breidert (breidert): Test copy issues between projects, which is focused on understanding GitLab's issue migration workflow rather than any functional change to the module itself. The issue remains open and assigned to breidert, with the stated goal of documenting how cross-project issue migration behaves.
With no code activity this cycle, the module's development queue appears quiet. There are no API changes, bug fixes, or new features to report.
How can I help on this project?
- Review the open codebase for untested functionality and open a patch or MR adding test coverage.
- Check the issue queue for unassigned bugs or feature requests and pick one up.
- Help close out Test copy issues between projects by running the migration test and adding a documenting comment.
Field Widget Actions
Activity on the Field Widget Actions module was minimal during this reporting period. No merge requests were opened or merged, and no commits landed in the last 24 hours.
The only notable movement was on Testing AI Workflow Automation, a test issue opened by Artem Dmitriiev (a.dmitriiev) that moved to a Needs Review state. Based on its description, this appears to be a sandbox or process-validation issue rather than a substantive bug or feature, and no comments or code changes accompanied the status update during this window.
In short, the module saw no functional changes, API updates, or bug fixes land this cycle. There are no active blockers of technical substance visible from this period's data.
How can I help on this project?
- Review the Testing AI Workflow Automation issue and confirm whether it can be closed as a test artifact.
- Browse the module's open issue queue and pick up an unassigned bug or feature request that lacks a maintainer response.
- Audit existing test coverage for field widget action handlers and open an issue if gaps are found.
FlowDrop
Release 1.11.0 Shipped
Shibin Das (shibindasp) pushed four commits during the reporting period, culminating in a version bump to 1.11.0. The changes span two submodules:
- flowdrop_pipeline: A bug fix adds the
INTERRUPTEDstatus to the summary map insidegetPipelineJobs(), correcting an omission that would have caused interrupted pipeline jobs to be silently dropped from status summaries. - flowdrop_ui_components: A new UI settings configuration form was added, and a layout fix gives the playground container a definite height, resolving a rendering issue where the container would collapse.
No issues were updated and no merge requests were opened or merged during this period. All activity came from a single contributor with no open blockers or discussion threads recorded.
How can I help on this project?
Review the new UI settings config form introduced in flowdrop_ui_components and check whether it covers all necessary validation. Consider writing a functional test for the INTERRUPTED status path in getPipelineJobs(). If you use the playground component, verify the height fix holds across different themes.
AI Content Classification
Activity on this project in the last 24 hours was limited to triage and discussion rather than any merged code or commits.
Open Bugs
The Error when saving new node issue remains open and unassigned. Originally reported by breidert (breidert), this bug surfaces an AssertionError in EntityStorageBase.php (line 266) when attempting to load a node entity with a NULL ID during the AI classification process triggered on new node save. The error occurs after the recipe is applied and AI tag assignment is otherwise working, suggesting the classification callback is firing before the new entity has been fully persisted and assigned a valid ID. No fix or patch has been proposed yet, and the issue remains unassigned at normal priority under the AI Initiative Sprint.
How can I help on this project?
A contributor could make immediate progress by:
- Picking up the unassigned Error when saving new node bug -- trace which hook or service triggers entity loading prematurely and propose a fix that guards against a NULL entity ID before classification runs.
- Writing a functional test that reproduces the
AssertionErroron new node save to prevent regressions once a fix lands.