Daily Digest

Daily Digest – 28 May 2026

2026 Capabilities Progress

  1. Page generation — Canvas delivered tools for AI agent testing and component catalog management to support page builder agents [73][74][80][106], while ongoing work on entity reference selection APIs [77][99] will expand the building blocks agents can use to construct pages.
  2. Context management — The Context Control Center closed discussion on taxonomy integration [112] and created a new scope plugin [113] that will let organizations associate context with existing content vocabularies; the team is preparing beta 3 with UI improvements [114][115][150] and heading toward a 1.0 release in late June [138].
  3. Background agents — The AI Integration ECA module proposed a new interceptor submodule [37] that would expose AI request events and streaming responses to workflow automation, enabling scheduled and triggered AI operations with custom governance controls; FlowDrop improved session-based workflow management to support returning to and executing automated processes.
  4. Design system integration — Canvas merged layout management within the workbench [67][92], resolved component cardinality handling [78][107], and advanced multi-bundle reference field support [76], all of which strengthen how AI works with design system components.
  5. Content creation and discovery — The AI Integration ECA module identified a gap covering only 5 of 18 available AI operations [49] and opened tasks to add image generation, translation, summarization, and other content capabilities [38][39][40][41][42][43][44][45][46][47][48]; work also continues on simplifying structured output configuration for content workflows [36].
  6. Advanced governance — The core AI module resolved a critical infinite loop issue in global guardrails [8][23][27] and is working to fix guardrail reliability problems [3][7][19]; Canvas delivered conflict detection for concurrent editing [81][90] and improved test infrastructure [71][104][105] to support audit and versioning features.
  7. Intelligent website improvements — No direct progress today.
  8. Multi-channel campaigns — No direct progress today.

Shipped

  1. AI module version 1.3.6 released — The team completed quality assurance testing and shipped the latest stable version [16].
  2. Global guardrail infinite loop fix delivered — A critical bug causing AI content safety filters to trigger endless recursive calls has been resolved, preventing system failures [8][23][27].
  3. amazee.ai request retry improvements merged — The provider module now better handles network interruptions, reducing user-facing errors [54].
  4. AI Agents default configurations updated — New installations now receive current agent configurations, and the agent creation form now uses an improved tool selection interface [57][58][62][63].
  5. Canvas layout management and multilingual improvements delivered — Developers can now configure page regions directly in Canvas Workbench, the language switcher shows translation availability, and data integrity handling for field cardinality changes has been completed [67][69][78][92][93][107].

Ongoing

  1. AI module Symfony platform migration in progress — Work continues on adopting an industry-standard component as the foundation for future provider integrations, reducing maintenance burden [11][21].
  2. Chat interface customization under review — Multiple fixes addressing administrator ability to customize error messages and loading text are awaiting approval [5][6].
  3. AI Agents machine name collision fix ready for approval — A validation fix preventing silent failures when custom agent names conflict with system types is awaiting final review [55][60].
  4. Tool API REST compatibility issue unassigned — A reported problem where the module interferes with standard REST API responses remains without assigned resources [65].
  5. Context Control Center beta 3 release in planning — The team is preparing Sprint 11 roadmap and organizing beta testing recruitment ahead of the planned 1.0 release [138][147][148][149].

AI (Artificial Intelligence)

The team closed quality assurance testing and released version 1.3.6 during the reporting period, representing successful delivery of the latest stable feature set. Activity centered on three strategic areas: stabilizing the conversational interface, preparing advanced platform architecture, and resolving critical runtime issues.

Several contributors addressed usability gaps in the chat interface. Work is underway to allow administrators to customize error messages and loading text that currently use developer-oriented language like "Calling agents," which can confuse end users. A related defect was identified where agent-based conversations bypass response handling after the first message, preventing extensions from working reliably across multi-turn interactions.

A significant stability issue was discovered and resolved: when guardrails (content safety filters) are configured globally, they triggered infinite loops of AI requests. The fix prevents guardrails from re-checking their own validation calls. A separate issue found that one guardrail fails when AI responses include explanatory text alongside required data; a solution is in review. One user reported guardrails not activating as expected, which may indicate a configuration or documentation gap requiring investigation.

Wolfgang Ziegler is leading architectural work to adopt an industry-standard component (Symfony AI) as the foundation for future provider integrations, reducing maintenance burden and expanding compatibility. Parallel development continues on file handling APIs that will enable document uploads for fine-tuning and analysis across multiple AI vendors.

How can I help on this project?

  • Investigate the guardrails activation report to determine whether documentation, training materials, or product changes are needed to prevent user confusion.
  • Approve resourcing for the Symfony AI platform migration to ensure architectural modernization stays on track without disrupting current feature delivery.

View project on GitLab: ai

Drupal AI Initiative

The Drupal AI Initiative has been focused on partnership engagement and strategic planning over the past 24 hours. The team successfully completed a partner meeting on May 28th, which covered general progress updates, development approaches, partner benefits, and feature prioritization through a voting process. Following the meeting, organizers Kristen Pol (kepol) and the product team wrapped up post-event tasks including distributing recordings, slides, and AI-generated notes to partner mailing lists and Slack channels.

Planning is now underway for the June partner meeting, with the team working to establish a date and agenda. A new centralized documentation system has been created in Google Drive to house all partner meeting materials, making it easier for stakeholders to access historical notes and recordings. One organizational task remains blocked: adding notes from previous meetings to the new documentation hub.

Separately, discussions continue on how the initiative should engage with a proposed command-line interface feature being considered for Drupal Core. The team is also developing a visual identity for the Enterprise AI Summit in Rotterdam, positioned as a curated industry showcase rather than a traditional developer conference.

How can I help on this project?

  • Help unblock the historical documentation task by allocating time or resources to compile past partner meeting materials into the new system.
  • Support the June partner meeting by confirming date availability and ensuring key decision-makers can attend the feature roadmap discussions.
  • Provide strategic input on the Enterprise AI Summit positioning and budget allocation for its visual branding needs.

View project on GitLab: ai_initiative

AI Integration - ECA

The team is scoping a significant expansion of the module's capabilities as it prepares for a stable 1.0.0 release. Over the past day, Marcus Johansson (Marcus_Johansson) opened fourteen work items defining the path forward.

The most impactful addition is a proposal for a new submodule that would allow business process flows to intercept and respond to AI requests and failures in real time. The AI ECA Interceptor submodule would expose AI request events, streaming responses, and error conditions directly into workflow automation, enabling organizations to build custom logging, fallback handling, and governance controls around AI operations.

The team also identified a coverage gap: while the module currently supports five AI operations (chat, embedding, moderation, and speech conversion), the underlying AI framework offers thirteen additional capabilities—including image generation, video creation, object detection, text translation, and content summarization. A meta issue and twelve child tasks now document the work needed to bring all of these operations into workflow automation, which will unlock new use cases ranging from automated media pipelines to multilingual content workflows.

Additionally, a quality-of-life improvement was proposed to simplify structured output configuration in chat workflows, replacing a plain text field with a purpose-built editing interface that will reduce configuration errors.

How can I help on this project?

Confirm whether the interceptor submodule and expanded operation coverage align with your AI governance and automation priorities, so the team can sequence work accordingly. If these capabilities are strategic, consider allocating development resources to accelerate delivery of the twelve new operation actions.

View project on GitLab: ai_integration_eca

amazee.ai Private AI Provider

The amazee.ai Private AI Provider module saw focused development activity over the past 24 hours, with three merge requests opened or completed by Dan Lemon (dan2k3k4).

A merge request addressing request retry functionality was successfully merged, improving the module's resilience when communicating with the AI service. This should reduce errors users experience when network or service interruptions occur.

Two new merge requests are now in review. The first adds documentation about the vector database included with the service's free trial, responding to user feedback about the need for clearer guidance on this feature. The second introduces bulk chunking capabilities, which will help the module process larger documents more efficiently.

A security audit issue was also closed during this period, indicating completion of vulnerability assessment work that helps ensure the module meets security standards.

How can I help on this project?

  • Prioritize review and approval of the two open merge requests to accelerate delivery of documentation improvements and bulk processing features.
  • Consider user feedback channels to identify whether additional documentation or onboarding materials are needed beyond the vector database guidance now in development.

View project on GitLab: ai_provider_amazeeio

AI Agents

The AI Agents module closed two quality improvements during this period. The team updated outdated default configuration files that ship with the module, ensuring new installations receive agent configurations that match current standards. A second change modernized the agent creation form by replacing a plain text field with a dedicated tool-picker interface, making it easier for administrators to select and configure the information tools available to each agent.

Two bug fixes are currently under review. The first addresses a validation gap: administrators can currently create agents with names that conflict with system-defined agent types, causing those custom agents to silently fail. A fix has been submitted and is ready for final approval. The second addresses a technical inconsistency in how agents handle certain tool responses, which can affect conversation tracking; a solution is in progress.

The release planning issue for version 1.2.0 was closed, suggesting the team is moving forward with delivery. Contributors active this period include Marcus Johansson, AKHIL BABU, Ahmad Khalil, and Tim Bozeman.

How can I help on this project?

  • Prioritize final review of the machine name collision fix, which prevents a category of silent failures that could confuse administrators.
  • Ensure the team has clarity on release timing and scope for version 1.2.0 now that planning has concluded.

View project on GitLab: ai_agents

Tool API

The Tool API project saw two issues updated during the reporting period, both addressing important functional and compatibility needs.

Work is underway on File Input Handling, which will define how the module securely processes file operations when invoked by AI agents. This research and proof-of-concept phase will determine the approach for enabling AI-driven file workflows, a capability that expands what users can accomplish through automated agents. Once the research concludes, concrete implementation work will be scoped and planned.

A compatibility issue was reported regarding MapDefinitionNormalizer and ContextDefinitionNormalizer break REST serialization. Stephan Huber (stmh) identified that the module's current implementation interferes with standard REST API responses when enabled alongside Drupal's REST module. This affects organizations relying on REST endpoints to expose content and could block adoption in environments using these standard integration patterns. The issue is currently unassigned and awaiting resolution.

How can I help on this project?

  • Assign developer capacity to resolve the REST serialization compatibility issue to unblock adoption in standard REST environments.
  • Provide input on file handling security requirements and use cases to guide the research phase toward real-world deployment needs.

View project on GitLab: tool

Drupal Canvas

The Canvas project saw significant progress across developer experience, multilingual features, and system stability over the past 24 hours, with five major pieces of work delivered.

The team completed work on managing global layouts within Canvas Workbench, enabling developers to configure page regions directly in the development environment. This removes a setup bottleneck and improves iteration speed. A related improvement to developer experience through class renaming was also merged, making the codebase easier to navigate and maintain.

On the multilingual front, the language switcher now shows translation availability for each configured language, giving content editors clearer visibility into what has been translated. This supports the broader roadmap toward full symmetric translation support.

Two data integrity improvements were delivered: graceful handling of cardinality decreases, which prevents page crashes when component field limits are tightened, and a code style rule to reduce merge conflicts by standardizing comment placement.

Ongoing work includes backend APIs for entity reference selection (under review), AI agent test automation, conflict detection for concurrent editing, and several open bug fixes including a flaky video upload test and an Ajax dependency issue.

How can I help on this project?

View project on GitLab: canvas

Context Control Center (CCC)

The team closed a key discussion on (Discuss) Associating adhoc vocabularies (freetagging) with context items, which explored how to better link content to AI context using existing site taxonomies. This decision unlocked the creation of a new taxonomy scope plugin that will allow organizations to associate context items with the terms already used in their content, making context more relevant and easier to maintain.

The project is now organizing its Sprint 11 roadmap through two issues: Sprint 10 planning and Sprint 11 planning. Sprint 11 runs from 30 May to 12 June 2026 and will focus on finalizing features ahead of the release candidate. Beta 3 release planning is underway via this tracking issue, with the team working toward a stable 1.0 release expected in late June.

Progress continues on user experience improvements, including a merge request for optional feature suggestions in the UI and design updates to the context viewing page. Two issues were closed: one on removing the target column from listings, and another on discussion of taxonomy associations.

How can I help on this project?

Approve budget or staff time for beta testing recruitment and user feedback sessions to ensure the product meets real-world needs before the 1.0 release. Champion internal adoption of the module to provide early validation and surface issues before wider deployment.

View project on GitLab: ai_context

Field Widget Actions

The Field Widget Actions module made significant progress this week, delivering a new capability that gives site administrators more control over how action buttons appear in forms. Previously, the system rigidly determined whether action buttons would appear once per form item or once per field based on hardcoded settings. This forced teams to create duplicate configurations when they needed different behavior for different use cases.

Andy Marquis (apmsooner) completed and merged Configurable multiple setting, resolving the Allow "Multiple" to be configured in widget issue. This change allows administrators to configure button placement directly in the interface based on their specific needs, eliminating redundant setup work and making the system more flexible for different workflows.

As a follow-up, Artem Dmitriiev (a.dmitriiev) opened Deprecate multiple property in plugin attribute to ensure the codebase transitions cleanly to this new approach in future releases. This maintenance work will prevent confusion and technical debt as the module matures.

How can I help on this project?

  • Ensure testing resources are available to validate the new configuration flexibility across different form scenarios before the next release.
  • Support documentation efforts to help site administrators understand when to use different button placement options.

View project on GitLab: field_widget_actions

FlowDrop

FlowDrop saw concentrated development activity over the past 24 hours, with contributor Shibin Das (shibin_das) delivering 14 commits focused on improving the user experience for working with sessions and workflows.

The main progress centers on introducing session-based workflows. Users can now create and access individual sessions through dedicated URLs, making it easier to organize and return to specific work. The interface has been streamlined: navigation menus now group related tasks and actions more logically, and outdated interface elements have been removed. The terminology has also been clarified, with sessions now consistently labeled as "Playground Sessions" to help users understand what they're working with.

Behind the scenes, the module now provides a cleaner way to launch and run workflows, and sessions can accept messages without immediately executing them. These capabilities expand what's possible for users building automated processes.

Overall, this represents solid incremental progress on making FlowDrop more intuitive and capable for users who need to design and manage workflow automation.

How can I help on this project?

  • Arrange user testing sessions with target users to validate whether the new session-based interface meets their workflow needs.
  • Clarify the roadmap timeline and release goals to help prioritize remaining feature work versus stabilization.

View project on GitLab: flowdrop

References

[3] RestrictToTopic guardrail should use the prompt JSON decoder service (ai, Issue)

[5] Unable to override the 'Calling agents' / 'Contacting agents' text (ai, Issue)

[6] Unable to override the 'An error occurred while fetching messages' text (ai, Issue)

[7] Guardrails and Chat Generation Explorer - not working... (ai, Issue)

[8] Global LLM-based guardrails cause infinite recursive LLM calls (no re-entrancy guard) (ai, Issue)

[11] Adopt symfony/ai component v0.8 as platform provider (ai, Issue)

[16] Release 1.3.6 (ai, Issue)

[19] Issue #3586469: Use prompt JSON decoder service in RestrictToTopic guardrail (ai, MR)

[21] Draft: Symfony AI Store integration with AI (no changes to ai_search) (ai, MR)

[23] Resolve "Global LLM-based guardrails cause infinite recursive LLM calls (no re-entrancy guard)" (ai, MR)

[27] Resolve "Global LLM-based guardrails cause infinite recursive LLM calls (no re-entrancy guard)" (ai, MR)

[36] Simplify structured output configuration in the Chat action (ai_integration_eca, Issue)

[37] Add AI ECA Interceptor submodule: intercept AI requests/responses through ECA (ai_integration_eca, Issue)

[38] Add ECA execute action for Audio to Audio (ai_integration_eca, Issue)

[39] Add ECA execute action for Image Classification (ai_integration_eca, Issue)

[40] Add ECA execute action for Image to Image (ai_integration_eca, Issue)

[41] Add ECA execute action for Image to Video (ai_integration_eca, Issue)

[42] Add ECA execute action for Object Detection (ai_integration_eca, Issue)

[43] Add ECA execute action for Rerank (ai_integration_eca, Issue)

[44] Add ECA execute action for Speech to Speech (ai_integration_eca, Issue)

[45] Add ECA execute action for Summarization (ai_integration_eca, Issue)

[46] Add ECA execute action for Text Classification (ai_integration_eca, Issue)

[47] Add ECA execute action for Text to Image (ai_integration_eca, Issue)

[48] Add ECA execute action for Translate Text (ai_integration_eca, Issue)

[49] [Meta] Cover remaining AI operation types with ECA execute actions (ai_integration_eca, Issue)

[54] Retry requests (ai_provider_amazeeio, MR)

[55] AI Agent entity form should reject machine names that collide with existing code-plugin IDs (ai_agents, Issue)

[57] Default agent configs in config/install are outdated (ai_agents, Issue)

[58] Use the new ai_tools_library form element for 'Default information tools' in the agent form (ai_agents, Issue)

[60] Issue #3586026: Reject AI Agent IDs that collide with code-defined AiAgent plugins (ai_agents, MR)

[62] Issues/3586028 (ai_agents, MR)

[63] Resolve "Use the new ai_tools_library form element for 'Default information tools' in the agent form" (ai_agents, MR)

[65] MapDefinitionNormalizer and ContextDefinitionNormalizer break REST serialization (same as #3568588) (tool, Issue)

[67] Manage the global layout (aka regions) within Canvas Workbench (canvas, Issue)

[69] Indicate translation availability per language in the Canvas language switcher dropdown (canvas, Issue)

[71] Decouple kernel tests from `CanvasTestSetup`: painful to work on, and VERY slow (canvas, Issue)

[73] Canvas AI: add layout fixture support so page builder and template builder agent tests can run against a realistic layout (canvas, Issue)

[74] Canvas AI: Restrict component catalog to canvas_test_sdc components when canvas_ai_agents_test is installed (canvas, Issue)

[76] [PP-1] Add support for matching against multi-bundle reference fields (e.g. a media field referencing 2 media types of different MediaSource plugins) (canvas, Issue)

[77] Backend APIs for Entity Reference Selection (canvas, Issue)

[78] Handle change of cardinality (fewer/more values allowed): upgrade component instances with more values than cardinality allows by dropping those values (acceptable data loss) (canvas, Issue)

[80] Canvas AI: Create tests for Canvas AI Page builder Agent and Canvas AI Template Builder Agent (canvas, Issue)

[81] Detect conflicts for Page entities during the handling of auto-saves/pending calls (canvas, Issue)

[90] Resolve #3589076 "Detect conflicts during autosave polling" (canvas, MR)

[92] feat(CLI Tool) #3576837 Manage the global layout (aka regions) within Canvas Workbench (canvas, MR)

[93] #3590572 Indicate translation availability per language in the Canvas language switcher dropdown (canvas, MR)

[99] Draft: feat: #3585354 add content-entity-types / fields endpoints for entity reference selection UI (canvas, MR)

[104] Draft: Resolve "Decouple kernel tests from `CanvasTestSetup`: painful to work on, and VERY slow" (canvas, MR)

[105] Remove CanvasTestSetup dependency from CanvasFieldTrait and test-discovery guard (canvas, MR)

[106] #3591516: Canvas AI Restrict component catalog to canvas_test_sdc components when canvas_ai_agents_test is installed (canvas, MR)

[107] Issue #3587024: Handle decrease of cardinality (canvas, MR)

[112] (Discuss) Associating adhoc vocabularies (freetagging) with context items (ai_context, Issue)

[113] Create taxonomy scope plugin (ai_context, Issue)

[114] CCC optional feature suggestions in UI (ai_context, Issue)

[115] Update context view page per new design (ai_context, Issue)

[138] CCC beta3 release planning (ai_context, Issue)

[147] Recruit CCC beta testers (ai_context, Issue)

[148] CCC beta / pre-rc1 community testing (ai_context, Issue)

[149] Sprint 11 CCC roadmap updates, sprint planning, and issue triage (ai_context, Issue)

[150] Issue #3586229: Add extensions page under settings. (ai_context, MR)

Period: 28 May 2026 to 29 May 2026  |  Generated: 29 May 2026 05:00 GMT

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

Looking for older digests? Browse all digests here.