Daily Digest

Daily Digest – 27 May 2026

2026 Capabilities Progress

  1. Page generation — Canvas merged API support for managing page regions [86] and completed form state refactoring [74], both foundational for enabling AI to assemble pages from components. Translation preview capabilities were also delivered [85], which will support multilingual page generation workflows.
  2. Context management — The Context Control Center team opened work on an extensions page to improve discoverability of optional features [93][98] and initiated updates to clarify how scope subscriptions work in the UI [96]. Discussion items were opened exploring freeform tagging [94] and exclusion rules [95] for more sophisticated context filtering.
  3. Background agents — No direct progress today.
  4. Design system integration — Canvas resolved issues affecting component upgrade scenarios when prop definitions change [63][73] and added backend APIs for entity reference selection [55][70], both critical for AI to work intelligently with design system components. Work also progressed on multi-bundle reference field support [48], a blocker for more complex component matching.
  5. Content creation and discovery — Field Widget Actions received a merge request enabling configurable "multiple" settings [100][102], making AI content tools more adaptable to different editorial workflows. Work continues on interactive refinement capabilities [8][101][103], which will allow editors to iteratively improve AI-generated content with natural language instructions.
  6. Advanced governance — Canvas merged conflict detection during autosave polling [79] and progressed work on ensuring component version updates propagate correctly across translations [60][76], both essential for maintaining content integrity when AI makes changes across multilingual sites.
  7. Intelligent website improvements — No direct progress today.
  8. Multi-channel campaigns — No direct progress today.

Shipped

  1. AI module fixed critical infinite loop bug in guardrails — The team resolved an issue where global guardrails triggered recursive calls when validating AI-generated content, preventing system lockups [5][22][23].
  2. AI Agents delivered modernized configuration interface — The agent configuration form now uses a dedicated tool picker instead of a basic text field, making it easier to select and configure information tools [42][45].
  3. AI Agents updated default configurations to current format — The three shipped agent configurations for taxonomy, content types, and fields now match current structure, ensuring consistent installation experience [41][44].
  4. Canvas completed language preview capability — Teams can now view page content in different languages without leaving the editor, supporting multilingual site workflows [58][85].
  5. Canvas delivered page region management APIs — New APIs enable Canvas Workbench to synchronize global layout areas like headers and footers [65][86].

Ongoing

  1. AI module adopting Symfony AI component version 0.8 — Development underway to modernize the platform layer, representing a significant architectural shift requiring validation before stable 2.0 release [1][12].
  2. Canvas advancing multilingual translation features — Multiple merge requests in progress for extending language switcher to templates, propagating version updates across translations, and indicating translation availability [62][82][60][76].
  3. Context Control Center approaching release candidate — Team prioritizing which performance improvements and UI enhancements must be completed before first release candidate versus after version 1.0 [90][91][92][93].
  4. Field Widget Actions adding configurable multiple setting — Merge request submitted to let users control whether automated actions apply to individual items or entire fields without technical intervention [100][102].
  5. Tool API resolving REST serialization compatibility issue — When Tool module is enabled alongside REST API, data handlers interfere with JSON conversion, potentially disrupting third-party integrations [46].

AI (Artificial Intelligence)

The AI module team has resolved a critical bug affecting guardrails and completed several maintenance tasks while advancing work on platform modernization. Key activity over the past 24 hours includes:

A significant bug fix was merged addressing an infinite loop issue where global guardrails would trigger recursive calls when validating AI-generated content. Marcus Johansson resolved this by adding proper re-entrancy guards. Several legacy bugs were also closed, including issues affecting the API Explorer interface and automator routing.

Development is underway on two strategic initiatives: adopting the latest Symfony AI component (version 0.8) to modernize the platform layer, and ensuring the API Explorer works with both new and legacy provider implementations to support thorough manual testing during the transition. Wolfgang Ziegler is leading both efforts.

Several quality improvements are in progress, including visual regression testing for UI components, fixing how the RestrictToTopic guardrail decodes responses when models wrap JSON in prose, and adding interactive refinement capabilities to field widget actions. Ahmad Khalil has a patch ready for review that improves error handling when assistant configurations conflict with code-defined plugins.

Documentation remains slightly outdated, with the changelog referencing version 1.2 rather than current releases—a minor housekeeping item.

How can I help on this project?

  • Prioritize code review resources for the Symfony AI integration work, which represents a significant architectural shift requiring careful validation before the stable 2.0 release.
  • Clarify the product roadmap around guardrails functionality, as user reports indicate the feature may not be working as intended in production scenarios.

View project on GitLab: ai

Drupal AI Initiative

The Initiative closed out its fourth marketing sprint and progressed work on the Enterprise AI Summit in Rotterdam. Two marketing tasks related to the Summit—visual assets and the call for sessions—were migrated to a dedicated marketing project repository and closed in the main project. A merge request to improve sprint management was opened by Jeremy Chinquist (jjchinquist), adding summary statistics to sprint reports and removing marketing templates now maintained elsewhere.

The UX team met on May 25 and confirmed the design direction for AI Review, noting that a long-running timeout issue in demos is an architectural problem requiring further updates. Aidan Foster (aidanfoster) is conducting an internal UX demo review based on strategic plans before wider release.

Two organisational improvements are underway: Christoph Breidert (breidert) is working to improve partner communication by setting up topic-specific contact lists, addressing missed sponsorship opportunities. Tim Hestenes Lehnen (hestenet) is exploring how to allow partner backlinks without enabling spam on Drupal.org.

How can I help on this project?

  • Review and approve partner communication workflows to ensure the right stakeholders are engaged for sponsorship and collaboration opportunities.
  • Support decision-making on the backlink policy for partner content, balancing SEO value with platform integrity.

View project on GitLab: ai_initiative

AI Agents Test

This module supports automated testing of AI capabilities. Over the past 24 hours, work continued on expanding testing efficiency and flexibility.

A task was updated to enable running multiple test groups together. Currently, teams can only run one set of tests at a time. The proposed enhancement would allow users to select and execute multiple test groups simultaneously or organize tests using tags. This capability is particularly valuable when comparing different AI models or conducting broader quality assessments, as it would reduce the time needed to evaluate system performance across various scenarios.

No code was merged during this period. The work remains in the planning and design phase as the team determines the best approach for the user interface and organizational structure.

How can I help on this project?

  • Clarify priority: Confirm whether bulk testing capability should be prioritized for the next development cycle or if other features take precedence.
  • Validate use cases: Connect the team with end users who would benefit from this feature to ensure the solution addresses real workflow needs.

View project on GitLab: ai_agents_test

AI Agents

The AI Agents module closed out its 1.2.0 release milestone this period, delivering two quality improvements that modernize the module's configuration and user interface.

The team fixed a bug where the three default agent configurations shipped with the module (for taxonomy, content types, and fields) were using an outdated format. AKHIL BABU (AkhilBabu) updated these to match the current structure, ensuring a consistent experience when installing the module. Marcus Johansson (Marcus_Johansson) also upgraded the agent configuration form to use a modern tool-selection interface introduced in the AI module 1.4.0, replacing a basic text field with a dedicated tool picker. This makes it easier for users to select and configure the information tools their agents will use.

With these fixes completed, the module has achieved its Roadmap 1.2.0 release goals. Both changes improve the out-of-box experience and align the module with current platform capabilities.

How can I help on this project?

  • Support planning for the next release cycle by allocating time for the team to define priorities and scope for version 1.3.0.
  • Ensure adequate testing resources are available to validate the 1.2.0 release candidate across different deployment scenarios before final release.

View project on GitLab: ai_agents

Tool API

Two new issues were opened during this period, both relating to how the Tool API module handles data structures used by other systems.

A compatibility problem with REST serialization was reported by Stephan Huber (stmh). When the Tool module is enabled alongside Drupal's REST API, certain internal data handlers interfere with the process of converting content entities into JSON format for external consumption. This affects any custom integration that exposes Drupal content via REST endpoints, potentially disrupting third-party applications or mobile apps that rely on this data exchange.

Marcus Johansson (Marcus_Johansson) opened and self-assigned an issue to add context definition overrides to the plugin base. This work ensures that when the AI module creates multiple instances of tools, each receives its own isolated configuration context rather than sharing state. The issue is marked as needing review and has tasks already completed, indicating progress toward resolution.

No code was merged or committed during this period. Both issues remain open and under investigation.

How can I help on this project?

  • Prioritize review capacity for the context definition issue, which is ready for technical review and blocking AI module integration.
  • Consider engaging stakeholders using REST APIs to validate the serialization fix once a solution is proposed.

View project on GitLab: tool

Drupal Canvas

Canvas closed two important technical tasks this period. The first completed a significant refactoring to improve how the page editor manages form state, which should reduce unnecessary re-rendering and improve responsiveness. The second delivered a language preview capability, allowing teams to view page content in different languages without leaving the editor—an essential step toward supporting multilingual sites.

Two new infrastructure capabilities were also merged. The project now exposes APIs for managing page regions (the global layout areas like headers and footers), enabling Canvas Workbench—the standalone development tool—to synchronize those layouts. The team also resolved a build system issue that was blocking continuous integration.

Active development continues on several translation features. Work is progressing on extending the language switcher to content templates, ensuring version updates propagate correctly across all language variants, and providing visual indicators of which translations exist. Multiple merge requests are open for these features.

Several foundational issues remain open, including support for multi-bundle reference fields (marked as a critical blocker) and handling attachments in processed text fields. The team is also working through component upgrade scenarios where developers change prop definitions after content has been created.

How can I help on this project?

  • Prioritize code review bandwidth for the open translation merge requests, which have working implementations but need final approval to unblock the multilingual workflow.
  • Confirm product decisions on data loss scenarios when component definitions change, as multiple open issues depend on clarity about acceptable tradeoffs.

View project on GitLab: canvas

Context Control Center (CCC)

Over the past 24 hours, the team focused on planning and prioritization work as the module approaches its release candidate milestone. Seven issues were updated, primarily centered on clarifying scope, documentation, and determining which features should be finalized before the first release candidate versus after version 1.0.

Key areas of activity include:

How can I help on this project?

  • Prioritize which of the three performance issues must be resolved before the release candidate versus after version 1.0, as the team needs direction on scope boundaries.
  • Assess whether additional design or UX resources are needed to support the documentation and interface clarity work currently underway.

View project on GitLab: ai_context

Field Widget Actions

The Field Widget Actions module saw focused development activity over the past 24 hours, with progress on making the tool more flexible and user-friendly for content editors working with AI-generated content.

A new merge request was submitted by Andy Marquis (apmsooner) to address Allow "Multiple" to be configured in widget. This work will give users control over whether automated actions apply to individual form items or entire fields, removing the current limitation where developers must create duplicate versions of the same tool just to change this setting. The change means content teams can adapt the same automation tool to different workflows without technical intervention.

Separately, work continues on Add interactive refinement capability to Field Widget Actions, which aims to let users iteratively improve AI-generated content with instructions like "make it shorter" without starting over. An existing merge request from Edward Zwart (ezeedub) is under review for this enhancement.

How can I help on this project?

  • Prioritize review and testing resources for the open merge requests to accelerate delivery of these user-facing improvements.
  • Connect the development team with content editors who can provide feedback on the interactive refinement feature to ensure it meets real workflow needs.

View project on GitLab: field_widget_actions

References

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

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

[8] Add interactive refinement capability to Field Widget Actions (ai, Issue)

[12] [Meta] Use Symfony AI (ai, Issue)

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

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

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

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

[44] Issues/3586028 (ai_agents, MR)

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

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

[48] [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)

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

[58] Create a preview mode for non-default languages (canvas, Issue)

[60] Symmetric translation: component instance version updates must propagate to all translations (canvas, Issue)

[62] Extend language switcher support to Content Templates (canvas, Issue)

[63] Introduce a JsComponentInstanceUpdater that allows prop shape ("type") changes and accepts data loss (canvas, Issue)

[65] Expose HTTP API for managing Page Regions (canvas, Issue)

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

[73] #3587711 fix: code component exceptions after prop type change (canvas, MR)

[74] #3562896 React Hook Form integration. (canvas, MR)

[76] Draft: Resolve "Symmetric translation: component instance version updates must propagate to all translations" (canvas, MR)

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

[82] Draft: #3590577 Language preview for templates (canvas, MR)

[85] #3585452 Create preview for translations (canvas, MR)

[86] feat(Internal HTTP API): #3589801 Expose HTTP API for managing Page Regions (canvas, MR)

[90] CCC Non-Agent `match_all` Convenience API (ai_context, Issue)

[91] Conditional Subcontext Provider Calls (ai_context, Issue)

[92] CCC Usage Tracking Query/Save Pattern (ai_context, Issue)

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

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

[95] (Discuss) Add boundaries / exclusions to scope plugins (ai_context, Issue)

[96] Clarify scope items are additive in docs and UI (ai_context, Issue)

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

[100] Allow "Multiple" to be configured in widget (field_widget_actions, Issue)

[101] Add interactive refinement capability to Field Widget Actions (field_widget_actions, Issue)

[102] Configurable multiple setting. (field_widget_actions, MR)

[103] feat: #3547306 Add interactive refinement capability to Field Widget Actions (field_widget_actions, MR)

Period: 27 May 2026 to 28 May 2026  |  Generated: 28 May 2026 09:07 GMT

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

Looking for older digests? Browse all digests here.