Daily Digest

Daily Digest – 23 June 2026

2026 Capabilities Progress

  1. Page generation — Canvas AI added layout fixture support for testing page builder agents [67][92], and work continues on giving AI more context about site styling [66]. The chatbot title/description generation behavior is being refined [63].
  2. Context management — CCC delivered five enhancements including a public API for scope subscription forms [93][108], fixes for custom scope values [99][110], conditional subcontext improvements [97][109], and example context items from the Chicago demo [102][112]. New requests for RAG integration APIs [94] and CKEditor context injection [98] are under consideration.
  3. Background agents — ECA integration progressed with nine new automation action types in development covering audio, image, video, and text processing [26][27][28][29][30][31][32][33][34], with three merge requests under review [35][36][37]. AI Agents saw work assigned on executor tracking [44] and error handling improvements [43].
  4. Design system integration — Canvas progressed on component instance version propagation across translations [57][72], progressed on heuristics for content-entity-reference selection [46][73], and in progress multiple UI fixes [53][78][81]. Next milestone is completing the translation propagation architecture.
  5. Content creation and discovery — Batch embeddings progressed across AI Search [113][117], OpenAI [38], Gemini [40][42], and Pinecone providers [132], significantly improving indexing performance. Field Widget Actions progressed on interactive refinement capability [118][124] and fixed suggestion event handling [120][125]. AI translate work progressed on timeout issues on large content [128][131].
  6. Advanced governance — Canvas progressed on conflict detection improvements [76][83] with resolution UI in draft [75][91], and merged fixes to prevent data loss when reviewing multi-language pending changes [62][88]. A moderation guardrail plugin is under development [9][10].
  7. Intelligent website improvements — No direct progress today.
  8. Multi-channel campaigns — No direct progress today.

Shipped

  1. Context Control Center public API released — A new API allows other modules to build context subscription forms without duplicating internal code, removing integration barriers [108].
  2. Context Control Center integration fixes delivered — Custom scope values from third-party modules are now properly recognized, and conditional context loading now reduces latency and provider costs [109][110].
  3. Canvas translation safety fix deployed — The pending changes review screen now shows only default-language content, preventing accidental corruption or deletion of translations [88].
  4. Field Widget Actions user experience improvements — Automated content suggestions now properly trigger follow-on actions, and configuration menus only show genuinely available tools [125][127].
  5. Canvas test infrastructure enhanced — AI agent testing now runs against realistic layouts, and test suite parallelization reduces pipeline wait times [92][71].

Ongoing

  1. Batch embedding performance upgrades in progress — OpenAI, Gemini, and AI Search providers are adding batch processing to reduce costs and speed up large-volume content indexing [38][42][117].
  2. Canvas translation synchronization under development — Component version updates will automatically propagate to all language translations, preventing content drift across localized sites [72].
  3. AI chatbot permission simplification under review — Administrators currently configure permissions in two separate locations; consolidation into a single model would reduce confusion and access errors [18].
  4. Large content translation reliability being addressed — Pages with over 1000 words currently time out during translation; chunking solution is under review [131].
  5. Field Widget Actions interactive refinement capability proposed — Users would be able to iteratively improve AI-generated content through conversation rather than regenerating from scratch [124].

AI (Artificial Intelligence)

The AI module saw focused activity on June 23rd addressing usability, configuration, and developer experience improvements. No code was merged during this period, but contributors advanced several in-progress features and identified important quality issues.

Work continued on improving the module's usability for site builders. A proposal to simplify chatbot permissions is under review—currently, administrators must configure permissions in two separate places, which can lead to confusing access errors. The solution would consolidate these into a single, clearer permission model. Similarly, contributors identified that the CKEditor AI integration can appear configured even when required provider modules are missing, causing silent failures when users attempt to use the feature.

Several enhancements are progressing with active development: support for using JSON schema elements in dialog windows, adding MariaDB as a vector database option, and batch processing for faster content indexing. The team is also working on expanding moderation capabilities to allow any moderation provider to function as a content guardrail.

Three bugs were documented: incorrect documentation about link security settings, a validation issue affecting forms with multiple AI prompt elements, and indexing failures with custom search data sources.

How can I help on this project?

  • Prioritize user testing resources for the permission simplification work to validate whether the proposed single-permission model addresses administrator confusion.
  • Support decision-making on the module deprecation strategy being researched—this affects how sites will transition bundled features to standalone modules.

Drupal AI Initiative

The Drupal AI Initiative has entered an intensive planning phase for the Enterprise AI Summit, scheduled for September in Rotterdam. Over the past 24 hours, the team has opened seven new work items focused on event logistics, marketing, and partnership development.

Key preparation work now underway includes finalizing sponsorship arrangements (with three gold, two silver, and one bronze tier confirmed or pending), developing sponsor lead registration forms, and improving the mobile experience of the event website. The team is also exploring partnerships with professional organizations like ThomsonReuters and CIONet to extend the event's reach to their audiences.

On the content side, Paul Johnson (pdjohnson) has initiated work to source case studies from summit session submissions, which will support broader marketing efforts and identify potential contributors to webinars and articles. Two organizational gaps remain: social media coordination and volunteer recruitment for on-site event support are both currently unassigned.

How can I help on this project?

  • Assign an owner for social media promotion to ensure the summit reaches its target audience.
  • Facilitate decision-making on partnership terms with member organizations to finalize outreach agreements.
  • Allocate resources to recruit Dutch-speaking volunteers for registration and event coordination roles.

AI Integration - ECA

The project is advancing toward its version 1.0 milestone with a focused effort to expand support for AI-powered automation workflows. Over the past 24 hours, nine new work items were opened to enable business users to trigger additional AI capabilities through automated processes without writing custom code.

Marcus Johansson (Marcus_Johansson) identified gaps in the current automation coverage and created tasks to add support for advanced AI operations including audio processing, image and video generation, content summarization, and visual analysis tools like object detection and image classification. These additions will allow organizations to automate more sophisticated content workflows—such as automatically generating video from images, detecting objects in uploaded media, or summarizing lengthy documents.

Early community response has been positive, with Joshua Fernandes (joshua1234511) already submitting draft solutions for Text Classification and Summarization, and Marcus Johansson opening a comprehensive solution covering all nine operations. These submissions are under review.

The remaining items—Audio to Audio, Image Classification, Image to Image, Image to Video, Object Detection, and Speech to Speech—are available for contribution.

How can I help on this project?

  • Prioritize code review capacity to evaluate the three pending merge requests, which would deliver all nine automation capabilities in one release cycle.
  • Clarify strategic priorities if certain AI operations (video generation, speech processing) require earlier delivery than others to support specific business use cases.

OpenAI Provider

The OpenAI Provider module saw focused development activity this period, with work advancing on batch embedding capabilities. Paul Sheldrake (paulsheldrake) opened a merge request to add support for batch embeddings, which will allow the system to process multiple embedding requests together rather than one at a time. This enhancement is significant for efficiency: batch processing typically reduces costs and speeds up operations when working with large volumes of content, such as analyzing multiple documents or processing user queries at scale.

The change is currently under review and has not yet been merged into the main codebase. Once completed and tested, users should see improved performance and lower API costs when generating embeddings for multiple items simultaneously.

How can I help on this project?

  • Ensure the batch embeddings work receives timely code review to maintain development momentum and deliver cost savings to users.
  • Clarify priority roadmap items to help contributors focus efforts on the features that matter most to your organization's AI strategy.

Gemini Provider

The Gemini Provider module made progress on two key quality and capability improvements over the past day.

Work continues on Add support for batch embeddings, which will enable the module to process multiple embedding requests simultaneously. This capability is important for performance when working with large volumes of content, as it reduces the number of individual requests needed. Artem Dmitriiev (a.dmitriiev) has prepared a merge request that is currently under review.

The team also closed an issue related to code quality checks. Joshua Fernandes (joshua1234511) resolved Fix pre-existing PHPStan failures (deprecation issues), which was preventing the automated testing system from accurately reporting the status of new features. This was blocking clear visibility into whether new work was ready to ship. A fix has been opened to address known false positive errors in the testing framework.

How can I help on this project?

  • Assign a reviewer to evaluate the batch embeddings merge request to prevent delivery delays
  • Ensure the team has access to technical expertise on code quality tooling to finalize the testing infrastructure improvements

AI Agents

Activity over the past 24 hours centered on issue assignment and planning, with two existing issues now assigned to team members. Both relate to improving the reliability and flexibility of the AI Agents system.

Ahmad Khader has been assigned to work on Add a way to mark the executor on agent runner, which will enable the system to track who initiated an agent. This capability will allow different users or systems to receive customized responses based on their role or context, making the platform more adaptable to different business needs.

Joonas Meriläinen (mErilainen) is now assigned to address Exceptions in tool execute break the UI for the user. Currently, when configuration errors occur, users see a broken interface without explanation. This work will ensure users receive clear feedback when something goes wrong, improving the overall user experience and reducing support burden.

No code was merged during this period, as both issues are in the planning and assignment phase.

How can I help on this project?

  • Ensure Ahmad Khader and Joonas Meriläinen have dedicated time allocated to complete their assigned work without competing priorities.
  • Consider whether user experience testing resources should be lined up to validate the error handling improvements once implemented.

Tool API

The Tool API module saw discussion this week on improving how data is delivered to different types of systems. Currently, when the module executes a tool, it wraps the results in explanatory text. This works well when the output is being read by AI systems that analyze text, but creates problems when other software systems need to process the raw data directly.

A feature request to allow controlling tool return format was opened to address this limitation. The issue explores several approaches, including delivering raw results without wrapping text or separating the explanatory text from the actual data. Solving this would make the module more flexible and compatible with a wider range of integration scenarios, particularly for systems that consume structured data rather than natural language output.

No code changes were delivered during this period. The module remains in active development as part of the AI Initiative Sprint.

How can I help on this project?

  • Confirm the priority and timeline for the return format feature, as this affects integration architecture decisions for teams building on the module.
  • Identify and connect technical contributors who can evaluate the proposed approaches and begin implementation work.

Drupal Canvas

Over the past 24 hours, the Canvas team completed three key improvements and continued work on translation, conflict resolution, and AI capabilities.

The team merged Split the PHPUnit-Kernel CI test suite across 4 parallel jobs instead of 3, reducing pipeline wait times as the automated test suite has grown. This helps all contributors get faster feedback on their work.

A critical fix was merged to address Only show default-language entities when reviewing auto-saved (pending) changes. Previously, the pending changes review screen showed separate rows for each language translation, but acting on non-default translations could corrupt or delete the wrong content. The system now shows only the primary language version until full multi-language support is ready, preventing data loss.

The team also merged Canvas AI: add layout fixture support so page builder and template builder agent tests can run against a realistic layout, which provides infrastructure for automated testing of AI agents. This reduces the manual verification burden when improving AI prompts and behaviour.

Active development continues on component version updates across translations, conflict detection and resolution interfaces, boolean form field behaviour fixes, and AI chatbot refinements. Christian López Espínola (penyaskito) and Wim Leers (wimleers) are progressing on Symmetric translation: component instance version updates must propagate to all translations, ensuring that when a code component changes, all language versions stay synchronized.

How can I help on this project?

  • Prioritize code review capacity for the translation propagation work (MR !1271), which is marked critical and requires architectural decisions about configuration override handling.
  • Consider resourcing UI polish work, particularly the boolean field fixes that affect day-to-day editing experience.

Context Control Center (CCC)

The Context Control Center project delivered five significant enhancements over the past 24 hours, focused on making the platform easier to integrate and extend for downstream users.

The team merged a new public API for building scope subscription forms, contributed by Kristen Pol (kepol). This removes a barrier for other modules that want to offer context subscription interfaces outside of AI agents, eliminating the need for them to rebuild logic internally.

Two integration fixes were completed: Ahmad Khader (Ahmad-Khader) resolved an issue where custom scope values added by third-party modules were being ignored in forms, and Abhisek Mazumdar (abhisekmazumdar) delivered conditional subcontext provider improvements that reduce latency and provider usage when building dynamic context.

Anikó Viola (violaniko) added example context items from the Chicago Driesnote demo to help new users understand and test the system. Kristen Pol also standardized version requirements across submodules.

Two new feature requests have been raised by integrators: a formal API for external RAG and vector store integrations, and support for injecting context into rich-text editing requests. Both are under consideration for the stable release roadmap.

How can I help on this project?

  • Decide whether the external RAG integration API request should be prioritized for stable release or deferred post-1.0, and ensure the team has clarity on ecosystem expectations.
  • Allocate resources to deliver real-world sample context items for end users, potentially as a recipe, to reduce onboarding friction.


Field Widget Actions

The Field Widget Actions module saw significant progress in the past 24 hours, with three improvements merged and one major feature under review.

Two bug fixes were completed that improve the user experience. The first addresses a problem where automated content suggestion tools were not properly communicating with other parts of the system — for example, users working with autosave features or other integrations would find that selecting a suggestion did not trigger expected follow-on actions. This has now been resolved by Volker Killesreiter (volkerk) through Missing events in suggestion.js. The second fix, contributed by Artem Dmitriiev (a.dmitriiev), eliminates confusion where users could see automation tools in a configuration menu that were not actually usable in their context — the interface now only shows options that are genuinely available (Field Widget Actions show in the "Add New Action" unavailable tools).

The project also received automated compatibility updates to ensure it will work with the next major platform release, and closed out several administrative and testing items.

A new feature is currently under review that would allow users to iteratively refine AI-generated content through a conversational interface, rather than having to regenerate from scratch or manually edit. This capability is being developed by Edward Zwart (ezeedub) in response to Add interactive refinement capability to Field Widget Actions.

How can I help on this project?

  • Review and approve the interactive refinement feature proposal to give the team clarity on whether this strategic direction aligns with your content workflow goals.
  • Connect the team with end users who could provide feedback on the refinement interface before it is finalized.

AI translate

The AI translate project saw progress on two key reliability issues during this period. A solution is now under review to prevent translation failures on large content pages. Currently, when users attempt to translate pages with more than 1000 words or several hundred HTML elements, the system times out and fails. A merge request has been submitted by Miriam Nugent (Peacog) to address 504 Time out on large content by breaking large content into smaller, manageable pieces before processing.

Separately, the team is addressing a significant user experience gap around error visibility. The issue titled Translation batch process does not handle translation errors, assigned to Ilia Nozadze (IliaNoz), highlights that when individual field translations fail, users receive no notification. In some cases, the system creates a translation record containing untranslated content without alerting the user to the failure, which can cause confusion and workflow problems.

A documentation question was also raised by Michael Anello (ultimike) regarding What's the point of the "Chat proxy to LLM" provider?, indicating a need for clearer explanation of certain integration options.

How can I help on this project?

  • Prioritize code review and testing resources for the large content handling solution to unblock deployments for high-volume sites.
  • Support documentation improvements to clarify provider selection and configuration for new users.

Pinecone VDB Provider

The Pinecone VDB Provider module enables Drupal sites to store and search vectorized data using Pinecone's cloud database service, supporting advanced search and AI-driven content features.

During this period, Rob Loach (robloach) opened and self-assigned work on Support batching on indexing operations. This enhancement will allow the system to process large volumes of content more efficiently by grouping indexing tasks together, rather than handling them one at a time. For organizations with substantial content libraries, this means faster indexing performance and reduced operational overhead when updating search indexes.

No code has been merged yet, which is expected for newly opened work. The module continues in active development as part of the broader AI integration ecosystem for Drupal.

How can I help on this project?

  • Ensure Rob Loach has adequate time allocated to complete the batching enhancement, as this will directly impact performance for larger deployments.
  • Consider identifying early adopter sites to test the batching functionality once available, providing real-world feedback on performance improvements.

References

[9] Add a Moderation Guardrail plugin (configurable moderation provider/model as a guardrail) (ai, Issue)

[10] Guardrail plugins only evaluate the last message (ai, Issue)

[18] Remove access deepchat api permission and use Assistant roles as the single source of truth (ai, MR)

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

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

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

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

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

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

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

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

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

[35] Resolve "9 different new actions" (ai_integration_eca, MR)

[36] Issue #3585009: Added ECA execute action for Summarization. (ai_integration_eca, MR)

[37] Issue #3585010: Added ECA execute action for Text Classification. (ai_integration_eca, MR)

[38] add support for batch embeddings (ai_provider_openai, MR)

[40] Add support for batch embeddings (gemini_provider, Issue)

[42] Support batch embeddings (gemini_provider, MR)

[43] Exceptions in tool execute break the UI for the user (ai_agents, Issue)

[44] Add a way to mark the executor on agent runner (ai_agents, Issue)

[46] Add heuristics for exposing fields/props to the content-entity-reference selection UI (canvas, Issue)

[53] Boolean props auto-enable when another prop is changed in the Canvas form (canvas, Issue)

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

[62] Only show default-language entities when reviewing auto-saved (pending) changes (canvas, Issue)

[63] Canvas AI: Chatbot generates page title and description without user request (canvas, Issue)

[66] Give AI more context around the styling of the site (canvas, Issue)

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

[71] chore(Project management): #3591722 Split the PHPUnit-Kernel test suite across 4 parallel CI jobs instead of 3 (canvas, MR)

[72] Draft: feat: #3591596 ALTERNATE Propagate component instance updates to content/config translations; introduce `StagedLanguageConfigOverride` to treat both similarly (canvas, MR)

[73] feat(Internal HTTP API): #3591669 Heuristics for the content-entity-reference selection UI (canvas, MR)

[75] Draft: feat(Conflict detection): #3591601 "Conflict resolution via API call and layout endpoint support for published entities" (canvas, MR)

[76] feat(Conflict detection): #3587526 "Detect conflicts during publishing of changes to Page entity" (canvas, MR)

[78] fix(ui): #3591716 boolean props auto-enable when another prop is changed (1.6.0) (canvas, MR)

[81] fix(ui): #3591716 boolean props auto-enable when another prop is changed (canvas, MR)

[83] feat(Conflict detection): #3587526 "Client side prevention of publishing" (canvas, MR)

[88] fix: #3591704 Hide non-default-translation auto-saves from the pending-changes GET response (canvas, MR)

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

[92] Issues/3591591: Add fixture support for layout to use in tests (canvas, MR)

[93] No public API for building scope subscription forms; consumers must depend on the internal scope manager (ai_context, Issue)

[94] [Feature] Add ExternalContextProviderInterface and ContextQueryInterface to support RAG/vector store integrations (ai_context, Issue)

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

[98] Inject context into ai_ckeditor requests (ai_context, Issue)

[99] hook_ai_context_scope_values_alter() is not honored in scope value forms (ai_context, Issue)

[102] Provide test context items for testing CCC (ai_context, Issue)

[108] Issue #3586287: No public API for building scope subscription forms; consumers must depend on the internal scope manager. (ai_context, MR)

[109] Issue #3586207: Add conditional subcontext toggle, cap, and per-request cache. (ai_context, MR)

[110] Issue #3586246: hook_ai_context_scope_values_alter() is not honored in scope value forms (ai_context, MR)

[112] Issue #3586244: Add example context items from the Chicago Driesnote demo. (ai_context, MR)

[113] Batch embeddings for improved indexing performance (ai_search, Issue)

[117] Resolve "Batch embeddings for improved indexing performance" (ai_search, MR)

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

[120] Missing events in suggestion.js (field_widget_actions, Issue)

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

[125] Trigger events in case of value update on suggestion (field_widget_actions, MR)

[127] Issues #3536116: Omit unavailable plugins in field widget actions configuration field widget form (field_widget_actions, MR)

[128] 504 Time out on large content (ai_translate, Issue)

[131] Issue #3545381 Split large HTML fields into chunks of a maximum number of characters (ai_translate, MR)

[132] Support batching on indexing operations (ai_vdb_provider_pinecone, Issue)


Period: 23 June 2026 to 24 June 2026  |  Generated: 24 June 2026 05:00 GMT

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

Looking for older digests? Browse all digests here.