Daily Digest

Daily Digest – 5 June 2026

2026 Capabilities Progress

  1. Page generation — Progress on Canvas AI to expose block component properties to AI agents [54], and continued work on interactive refinement for field widgets [1][109][111], which will enable users to iteratively improve generated content before accepting it.
  2. Context management — Substantial progress with Context Control Center completing menu relocation to AI configuration area [85][98], field storage improvements [81][97], updated documentation [89][90][100][101], and simplified data model [94][103]; planning began for starter templates and assisted context creation [83][84].
  3. Background agents — Work continues on AI Automator queue processing efficiency [4][23] and automatic field widget actions now support triggering without manual clicks [110][112]; ECA integration is adding summarization capabilities [34].
  4. Design system integration — Multiple critical Canvas fixes for Drupal 11.3 component generation [43][65] and JSON schema compatibility [45][46][61] are under review; conflict detection infrastructure continues development [51][67][73][74][77].
  5. Content creation and discovery — AI Search resolved indexing issues for long titles [106][108] and added documentation for vector database providers [105]; the AI module is deprecating built-in search in favor of the dedicated contributed module [2].
  6. Advanced governance — Canvas made progress on translation workflows with deletion routes in development [57][69], critical auto-save fix for translation preservation [62], and TMGMT integration planning [49][56]; conflict detection UI is under active development [73][77].
  7. Intelligent website improvements — No direct progress today.
  8. Multi-channel campaigns — No direct progress today.

Shipped

  1. AI module compatibility and editor fixes merged — Resolved compatibility issues with third-party modules and fixed the broken "Create new prompt" button in CKEditor across multiple supported versions [3][5][18][19][20][22][25][26][27][28].
  2. Google Vertex Provider adds structured output and multi-region support — Delivered structured response formatting and global endpoint support for improved automation capabilities and geographic flexibility [37][38][39][40][41].
  3. Canvas block validation fixed — Corrected validation errors for block components missing default label settings, unblocking Drupal CMS integration testing [58][66].
  4. AI Search indexing reliability improved — Merged fix preventing long node titles from causing indexing failures, reducing service interruptions [106][108].
  5. Field Widget Actions automation completed — Delivered capability for automation tasks to run immediately without manual button clicks, removing unnecessary workflow steps [110][112].

Ongoing

  1. AI module interactive refinement in development — Building conversational capabilities allowing users to iteratively improve AI-generated content through back-and-forth dialogue before accepting results [1][109][111].
  2. Canvas Drupal 11.3 compatibility fixes under review — Addressing critical bugs preventing component regeneration after configuration changes and image component generation failures with certain library versions [43][45][61][65].
  3. Canvas translation infrastructure progressing — Developing language deletion routes and addressing auto-save bug that drops translations when publishing, supporting upcoming multilingual workflows [50][57][62][69].
  4. Context Control Center preparing for release — Completing documentation updates, menu relocation, and data model simplification while defining starter templates and user assistant features for future delivery [81][85][89][90][94][97][98][99][100][101][102][103].
  5. AI module platform upgrade and consolidation planned — Evaluating Symfony AI component adoption for embeddings support and proposing to deprecate built-in search in favor of standalone module [2][7][11].

AI (Artificial Intelligence)

The AI module saw important compatibility and stability improvements over the past 24 hours, alongside ongoing development of new capabilities for conversational AI and code quality refinement.

Two key fixes were merged into production. The first resolved a compatibility issue preventing the module from working with third-party modules that extend Drupal's entity management system, such as the Trash module. The second addressed a critical bug where users attempting to create new AI prompts within the CKEditor text editor encountered errors. Both fixes involved substantial code changes (over 1,000 lines combined) and have been backported across multiple supported versions to ensure broad availability.

Development work continues on several fronts. Contributors are building interactive refinement features that will allow users to have back-and-forth conversations with AI to iteratively improve generated content before accepting it. Proposals are also under consideration to consolidate duplicate search functionality with a dedicated contributed module, improve queue processing efficiency for background AI tasks, and adopt newer infrastructure from Symfony's AI component to support embeddings and semantic operations.

Several issues remain open addressing edge cases: conversation history persistence for anonymous users on cached sites, configuration form breakage when certain content structures are missing, and streaming behavior in specific execution contexts. These represent normal development activity for a module in active evolution.

How can I help on this project?

  • Review and approve the strategic decision to deprecate the built-in AI Search component in favor of the standalone contributed module to avoid duplication of effort.
  • Prioritize resource allocation for the Symfony AI component upgrade, which will unlock embeddings and semantic capabilities for future features.

View project on GitLab: ai

AI Integration - ECA

This module bridges Drupal's AI capabilities with workflow automation. During the past 24 hours, development work focused on expanding the range of AI operations that can be automated.

A new task was assigned to add support for text summarization within automated workflows. Currently, users can automate several AI operations—such as chat, moderation, and text-to-speech—but cannot trigger automatic summarization of content. Joshua Fernandes (joshua1234511) has been assigned to build this capability, which will allow organisations to automatically generate summaries of documents, articles, or other content as part of their publishing or content management processes. This work is part of the project's roadmap toward a stable 1.0.0 release.

No code was merged or committed during this period; the work is in the planning and assignment phase.

How can I help on this project?

  • Confirm whether automatic summarization aligns with upcoming content strategy priorities and communicate use cases to the development team.
  • Ensure the assigned developer has protected time to complete this work as part of the 1.0.0 release goals.

View project on GitLab: ai_integration_eca

amazee.ai Private AI Provider

Development activity focused on resolving a configuration management issue that was disrupting routine administrative tasks. When site administrators attempted to import, export, or check configuration status, the system produced warnings due to missing validation logic.

Dan Lemon (dan2k3k4) opened a fix to validate key identifiers before loading configuration keys, addressing the configuration management warnings reported by Ron Raney (rraney). The solution ensures that empty or invalid values are properly handled before the system attempts to process them, preventing errors during standard configuration workflows.

The fix is awaiting review. Once merged, this will improve the reliability of configuration management operations, reducing friction for administrators maintaining the module's settings.

How can I help on this project?

  • Ensure the open merge request receives timely technical review to unblock the bug fix and restore smooth configuration workflows.
  • Consider whether additional quality assurance resources are needed to validate the fix across different deployment scenarios before release.

View project on GitLab: ai_provider_amazeeio

Google Vertex Provider

The Google Vertex Provider module saw significant progress in the last 24 hours, with five updates merged that enhance its capabilities and reliability. The team delivered support for structured output, allowing the system to return information in more predictable, organized formats that applications can reliably process. This makes the module more useful for automation and integration scenarios where consistent data formats matter.

The module now supports global and multi-region endpoints, giving organizations greater flexibility in how they deploy and scale their Google Vertex AI services across different geographic locations. This is particularly important for enterprises with international operations or specific data residency requirements.

Contributors Cameron Prince (cameronbprince), Daniel Mundra (dmundra), and Kristian Ducharme (kducharm) resolved a technical error that was preventing certain requests from completing successfully, improving overall reliability.

All changes were delivered through completed work by active contributors, indicating healthy project momentum.

How can I help on this project?

  • Identify pilot users or teams who could benefit from structured AI outputs and facilitate introductions to the development team for feedback.
  • Clarify organizational requirements around multi-region deployment to help prioritize testing and documentation efforts.

View project on GitLab: ai_provider_google_vertex

Tool API

The Tool API module saw continued development work during this period, with focus on improving compatibility with the AI module ecosystem.

Work progressed on Add contextdefinitionoverrides to the ToolPluginBase, which addresses an integration issue between Tool API and the AI module. The problem prevents certain functionality from working properly when the two modules are used together. Abhisek Mazumdar (abhisekmazumdar) has been assigned to implement the fix, and the required tasks have been completed and marked as done. The issue is currently in "needs work" status, indicating it is undergoing review or refinement before being finalized.

This work is part of the broader AI Initiative Sprint and will ensure that Tool API continues to work seamlessly with all supported versions of the AI module, maintaining interoperability across the platform's AI capabilities.

How can I help on this project?

  • Ensure adequate reviewer capacity is available to move the completed work through final review and merge, preventing delays in delivering the AI module compatibility fix.
  • Confirm whether automated testing coverage is sufficient to catch similar integration issues earlier in the development cycle.

View project on GitLab: tool

Drupal Canvas

Development activity this period focused on resolving critical compatibility and translation issues while progressing toward multilingual support.

Two critical bugs affecting Drupal 11.3 were identified and have active fixes in progress. The first prevents Canvas from regenerating components when site configuration changes (such as creating a new media type), leaving the system with outdated component definitions. The second causes image-based components to fail generation entirely when using certain library versions. Both issues have proposed solutions under review from Christian López Espínola (penyaskito).

A critical validation bug affecting block components without default label settings was resolved and merged by Pamela Barone (pameeela), unblocking Drupal CMS integration testing.

Translation capabilities advanced with the completion of infrastructure work enabling consistent JSON Schema handling across the application, which closed after Christian López Espínola's merge. New routes for deleting translations are in development by Ignacio Sánchez Holgueras (isholgueras) and Wim Leers (wimleers), supporting the upcoming language management interface. Additionally, a critical auto-save bug that caused translations to be lost when publishing has a rework in progress—previously, the system was rebuilding entities in a way that dropped all translations except the one being edited.

Conflict detection work continues, with multiple contributors developing the resolution interface and detection mechanisms needed for collaborative editing scenarios.

How can I help on this project?

  • Prioritize code review and testing resources for the two critical Drupal 11.3 compatibility fixes to accelerate their merge and prevent user-facing component generation failures.
  • Confirm strategic direction on multilingual workflow priorities, particularly whether TMGMT integration for content entities should be resourced now or deferred.

View project on GitLab: canvas

Context Control Center (CCC)

The project team completed key design discussions that will shape the module's future structure and user experience. Two conversations closed this period: one confirming that CCC should be relocated from the top-level admin menu into the AI configuration area alongside other AI modules, and another establishing default settings for optional features like the overview page and subcontext hierarchy.

Multiple improvement efforts are now underway with active work-in-progress. Kristen Pol (kepol) is leading updates to help text and documentation for both the subcontext feature and the overview page, clarifying benefits and tradeoffs for users. She's also implementing the menu relocation and addressing a text field storage change that improves integration with the markdown editor. Matt Glaman (mglaman) is refining the context listing page with a cleaner column structure and status indicators, and working to simplify the data model by removing an unnecessary content type layer.

The team opened several planning issues for future capabilities, including starter templates for common context types like brand guidelines, an assistant to help users create context, and evaluation of the AI Knowledge Connector module for potential integration.

How can I help on this project?

  • Prioritize user experience design resources for the postponed starter templates and user assistant features, which could significantly reduce onboarding friction for new adopters.
  • Confirm alignment on the module's scope and feature roadmap as the team balances pre-release cleanup with future enhancement requests.

View project on GitLab: ai_context

Field Widget Actions

The Field Widget Actions module made significant progress this week, completing a key feature that streamlines content workflows. The team closed work on Allow Automatic Field Widget Action, which enables automation tasks to run immediately without requiring users to manually click a button each time. This removes unnecessary steps in content creation workflows and allows teams to configure when automation should happen automatically versus when it requires user confirmation. The feature was contributed by Ahmad Khader (Ahmad-Khader) and merged into the codebase.

Development continues on Add interactive refinement capability to Field Widget Actions, which addresses a gap in how users can improve automatically generated content. Currently, users must either accept generated content as-is or manually edit it themselves. The proposed refinement capability would allow users to request iterative improvements with simple instructions, bridging the space between fully automated generation and manual editing. This work is in progress through an open merge request by Edward Zwart (ezeedub).

How can I help on this project?

  • Allocate testing resources to validate the interactive refinement capability once development is complete, ensuring it meets real user workflow needs.
  • Provide feedback on prioritization: determine whether additional automation features or user control features should take precedence in the roadmap.

View project on GitLab: field_widget_actions

References

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

[2] Deprecate AI Search in favour for the contrib version (ai, Issue)

[3] Use EntityTypeManagerInterface instead of EntityTypeManager (ai, Issue)

[4] Only one AI Automator worker queue item is processed per cron execution (ai, Issue)

[5] "Create new prompt" button doesn't work in CKEditor plugin configuration (ai, Issue)

[7] Add support embedings via symfony/ai (ai, Issue)

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

[18] Use EntityTypeManagerInterface over concrete EntityTypeManager class to fix... (ai, MR)

[19] Use EntityTypeManagerInterface over concrete EntityTypeManager class to fix... (ai, MR)

[20] Use EntityTypeManagerInterface over concrete EntityTypeManager class to fix... (ai, MR)

[22] Use EntityTypeManagerInterface over concrete EntityTypeManager class to fix compatibility with modules like Trash that decorate the entity type manager. (ai, MR)

[23] Issue #3575190: Add configurable queue items per cron for AI Automators (ai, MR)

[25] Fix/cherry pick 3586485 1.4.x 1 (ai, MR)

[26] Cherry pick 3586485 1.4.x (ai, MR)

[27] Issue #3586485: Fix ai_prompt form element in nested forms (ai, MR)

[28] Issue #3586485: Fix ai_prompt form element in nested forms (ai, MR)

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

[37] Resolve #3583566 "417 expectation failed" (ai_provider_google_vertex, MR)

[38] #3572381 Added structured output support for 2.x (ai_provider_google_vertex, MR)

[39] #3572381 Added structured response support to payload. (ai_provider_google_vertex, MR)

[40] Resolve #3592824 "Support for global" (ai_provider_google_vertex, MR)

[41] Adding support for global and multi-region endpoints. (ai_provider_google_vertex, MR)

[43] On Drupal 11.3, Components are not regenerated when configuration changes (e.g. creating a media type) (canvas, Issue)

[45] PropShape strips only `id`, not `$id`, so `$ref`-based components (e.g. image) are not generated with `justinrainbow/json-schema` 6.9.0 (canvas, Issue)

[46] Consistently use JSON-Schema Draft-07 dialect in frontend and backend by updating `justinrainbow/json-schema` to ^6.8.0 (canvas, Issue)

[49] Symmetrically translatable config-defined component trees, STEP 4: allow translating component instance inputs via TMGMT for ContentTemplates & PageRegions (canvas, Issue)

[50] `Evaluator` must respect the referencing entity's language when evaluating a referenced entity, or fall back to the negotiated content language (canvas, Issue)

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

[54] Canvas AI: Expose Props of Blocks to the Agent (canvas, Issue)

[56] Add TMGMT translation integration for content entities (canvas, Issue)

[57] Create Routes for Deleting Translations (canvas, Issue)

[58] Block validation is broken for any block without a default value for `label_display` (canvas, Issue)

[61] fix(Shape matching): #3591629 Strip `$id` as well as `id` when normalizing resolved prop schemas (canvas, MR)

[62] fix: #3591584 Auto-save should not re-create entities, but set the fields of them: otherwise translations get lost (canvas, MR)

[65] fix(Component sources): #3591628 Generate Components from the live container after canvas_stark install reboots the kernel on Drupal 11.3 (canvas, MR)

[66] Fix default value (canvas, MR)

[67] revert(Conflict detection) #3589076 Detect conflicts during autosave polling (canvas, MR)

[69] Draft: Issue #3591588: Use new DELETE route for language switcher. (canvas, MR)

[73] Draft: feat(conflict): Add conflict resolution UI with viewport selection and route integration (canvas, MR)

[74] Draft: fix(Conflict detection): Exclude computed internal fields from Page entity normalization (canvas, MR)

[77] Add conflict detection and resolution UI for selective publishing (canvas, MR)

[81] Switch context item text fields to string_long for clean MDXEditor integration (ai_context, Issue)

[83] Create context starter templates (ai_context, Issue)

[84] Create assistant to help users create context and configure context selection (ai_context, Issue)

[85] Move CCC menu from top-level to under AI configuration section (ai_context, Issue)

[89] Update subcontext feature description and docs (ai_context, Issue)

[90] Update overview page description and docs (ai_context, Issue)

[94] Remove AiContextItemType (ai_context, Issue)

[97] Issue #3586256: Change text_long to string_long and remove workaround. (ai_context, MR)

[98] Issue #3586253: Move CCC from main menu into AI configuration area. (ai_context, MR)

[99] Issue #3586214: Hide non-global scope when scope is enabled. (ai_context, MR)

[100] Issue #3586252: Update overview page help text and docs. (ai_context, MR)

[101] Issue #3586251: Update subcontext feature help text and docs. (ai_context, MR)

[102] Issue #3586219: Update context listing page per new design (ai_context, MR)

[103] Issue #3584775: Remove AiContextItemType and make ai_context_item bundleless (ai_context, MR)

[105] Add info about amazee.ai VectorDB provider (ai_search, Issue)

[106] Backport "Long node titles can trigger exception 'The minimum overlap cannot be equal to or exceed the maximum chunk size.' when indexing content" (ai_search, Issue)

[108] #3584019: Backport long title minimum overlap (ai_search, MR)

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

[110] Allow Automatic Field Widget Action (field_widget_actions, Issue)

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

[112] Resolve "Allow Automatic Field Widget Action" (field_widget_actions, MR)

Period: 5 June 2026 to 6 June 2026  |  Generated: 6 June 2026 05:00 GMT

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

Looking for older digests? Browse all digests here.