Daily Digest

Daily Digest – 25 August 2026

html

2026 Capabilities Progress

  1. Page generation — Active progress on AI-powered page building tools, with a development agent and placement tools now being wired into Canvas [50][92], plus a general-purpose Drupal Canvas Agent to answer questions during the page creation process [54][94]. Next milestone is completing the placement tool integration and expanding the agent's contextual awareness.
  2. Context management — Significant architectural work underway to expand context delivery beyond AI agents through plugin-based generic consumers [99][101], which will enable unified configuration across the platform. A fix is also in progress to prevent visual reordering of scopes from affecting functional priority [96][100]. Next milestone is completing the consumer plugin refactor to unlock CKEditor integration [98].
  3. Background agents — Work continues on making agents more flexible with support for multiple tool instances per agent [39][41] and improved reliability for field agents handling complex reasoning patterns [40]. These changes will better support workflow automation scenarios. Next milestone is merging the tool instances feature.
  4. Design system integration — Canvas made progress on Brand Kit capabilities with color preservation, usage tracking [48][68][71][79][82][84], and font family layout fixes [55][91]. Component schema validation work is also advancing [44][66]. Next milestone is completing SVG media handling fixes [43][69] and resolving file upload issues that affect component asset management [60].
  5. Content creation and discovery — The summarize feature continues to be refined, with a language preservation fix in progress for the core AI module [8][23] and the issue migrated to the AI CKEditor project for standalone tracking [102]. Embeddings support is being added via the Symfony AI library [6][22]. Next milestone is broader CKEditor integration once context consumer plugins are complete [98].
  6. Advanced governance — No direct progress today. Workflow and approval capabilities remain a planned future enhancement.
  7. Intelligent website improvements — No direct progress today. Performance monitoring and AI-driven optimization features have not yet entered active development.
  8. Multi-channel campaigns — No direct progress today. Cross-channel content distribution capabilities are not yet under development.
html

Shipped

  1. Canvas brand kit color support delivered — Content teams can now define, preserve, and track usage of brand color palettes, with multiple improvements integrated to support consistent brand management [68][71][79][82][84].

Ongoing

  1. AI module 1.5.0 quality assurance planning in progress — A comprehensive test plan is being developed to validate new installations, upgrades from 1.4.x, and Drupal CMS integration before the release candidate [2].
  2. AI module deprecation warnings awaiting merge — A merge request implementing updated interface requirements to eliminate compatibility warnings in preparation for future Drupal versions remains under review [20].
  3. AI module embeddings support under development — Work continues to add vector embedding capabilities through the Symfony AI library, expanding options for AI-powered search and content recommendations [22].
  4. AI module language preservation in summarization under review — A fix to ensure the CKEditor summarize feature generates summaries in the same language as the selected content rather than translating to a different language is awaiting merge [23].
  5. AI module chat performance improvements under review — Two optimizations are proposed to reduce page load impact: loading the chat widget only when visitors open it, and removing unnecessary jQuery UI dependencies from every page [25][27].
  6. AI module guardrails messages translation in progress — Work is underway to enable notification messages displayed when AI guardrails are triggered to be translated into multiple languages, improving accessibility for international users [29].
  7. Canvas media library SVG removal bug awaiting merge — A fix is ready for testing that restores the ability for editors to remove SVG files once selected in component forms [69].
  8. Canvas page variant backward compatibility under investigation — Work to ensure sites installed from templates continue to display content correctly after updates is being reviewed, though merge status remains unclear [72].
  9. Context Control Center architecture refactor in progress — Work continues on plugin-based context consumers that will enable any Drupal feature to request contextual information, not just AI agents [101].

AI (Artificial Intelligence)

The AI module continued work toward its 1.5.0 release this period, with progress across compatibility improvements, performance optimization, and foundational feature work. Activity focused on refining recent architectural changes and preparing the release for broader adoption.

A quality assurance plan is being developed for the 1.5.0 release candidate, covering new installations, upgrades from 1.4.x, and integration with Drupal CMS. Separately, work began to support embeddings functionality through the Symfony AI library, expanding the module's capabilities for vector-based operations.

Several refinements addressed recent changes to the chat system. A backwards compatibility issue affecting the DeepChat block configuration was identified, where sites importing existing settings would fail schema validation. Work also continued on clarifying how prompts behave in automators: when a template does not explicitly reference content placeholders, the base field content is not automatically included—this is by design, but the interface now makes it clearer.

Performance work centered on the DeepChat chatbot. Two improvements were proposed: loading the chat widget bundle only when a visitor opens the chat rather than on every page load, and removing unnecessary jQuery UI dialog dependencies that add weight to every page where the block appears.

Additional housekeeping included fixes for deprecation warnings, translatable guardrails messages, and improvements to the developer experience with DDEV configuration. A new option for the tools library element will allow the same tool to be selected multiple times with different configurations, supporting more flexible agent workflows.

How can I help on this project?

  • Allocate resources to execute the 1.5.0 QA plan once it is finalized, particularly for manual testing of upgrade paths and Drupal CMS integration scenarios.
  • Prioritize a decision on backwards compatibility handling for existing DeepChat block configurations to unblock the 1.5.0 release.

Contributors: eduardo morales alberti (EduardoMoralesAlberti), Giorgio Alfredo Pagano (sjpagan), Jan Kellermann (werk21), Joshua Fernandes (joshua1234511), Konstantine Kirkitadze (kotekirkitadze), Ricardo Castañeda (cadence96), Rob Loach (robloach), Scott Euser (scotteuser), Shivam Sen (shivamsen_12579), Tekla Aivazashvili (aivazashvilit)

View project on GitLab: ai

Drupal AI Initiative

Activity this period focused on documentation and testing infrastructure. Work continued on the disclosure module documentation, which will help site builders understand how to configure disclosure settings for AI-generated content and maintain compliance with regulatory requirements. This documentation is being prepared for the upcoming alpha release and will cover both practical implementation steps and the regulatory context behind the disclosure requirements.

Separately, development progressed on documentation for creating testable issues on DrupalForge. A merge request was opened to address a testing challenge: many issues involve multiple modules working together, and reviewers need clear guidance on how to set up test environments that include development versions of all required components. This will streamline the review process and reduce friction for contributors.

No code was merged during this period. Both documentation efforts remain in progress and will improve the experience for site builders implementing AI features and for contributors helping to advance the project.

How can I help on this project?

  • Prioritize reviewer availability to evaluate the pending DrupalForge testing documentation, which will accelerate contribution velocity across multiple AI modules.
  • Consider stakeholder engagement around the disclosure module's regulatory approach to ensure alignment with organizational compliance requirements before the alpha release.
Contributors: Abhinav Jha (ajabhinavjha30)

View project on GitLab: ai_initiative

Microsoft Azure AI

Work has begun on expanding the module's capabilities to support an additional type of content interaction. A [#3614660] Support the Responses API merge request was opened, representing a significant expansion that will enable new use cases for organizations using Azure's AI services within their Drupal applications. This work is currently under review and has not yet been integrated.

No other development activity occurred during this period. The module continues to be in active development as new functionality is added to broaden its feature set.

How can I help on this project?

  • Ensure development resources are available to review and test the pending merge request to maintain development momentum.
  • Clarify strategic priorities for Azure AI integration to help the team sequence future enhancements effectively.

Contributors: Joshua Fernandes (joshua1234511)

View project on GitLab: ai_provider_azure

Milvus VDB Provider

A merge request addressing Milvus connection failures fixes was opened during this period. This work aims to resolve issues preventing the system from establishing reliable connections to the Milvus database, which would otherwise block users from storing and retrieving vector data. The fix spans nearly 500 lines of changes, indicating a comprehensive approach to improving connection stability. Once merged and tested, this should reduce service interruptions and improve the overall reliability of the integration.

The module continues to mature as connection stability issues are identified and addressed. No commits were merged during this period, and the connection fix remains under review.

How can I help on this project?

  • Ensure the team has sufficient testing resources or environments to validate the connection fixes before release.
  • Support prioritization of code review to unblock the merge of stability improvements.
Contributors: Remco Hoeneveld (RemcoHoeneveld)

View project on GitLab: ai_vdb_provider_milvus

Postgres VDB Provider

The Postgres VDB Provider enables sites to use PostgreSQL as a vector database for AI-powered search and content recommendations. This module is part of the broader AI initiative to help Drupal sites deliver smarter, faster search experiences.

Two issues saw activity this period. Work continues on Add batch embeddings, which will allow the system to process multiple content chunks simultaneously rather than one at a time, significantly reducing the time needed to index content for AI-powered features. This aligns the provider with a broader performance improvement across the AI module suite.

Separately, a maintainer offer to help maintain was logged, indicating growing community interest in supporting the module's development and coordination among multiple contributors. This represents positive momentum for the project's sustainability.

No code was merged this period. The batch embeddings work has an active merge request under review.

How can I help on this project?

  • Facilitate maintainer access decisions to capitalize on new volunteer capacity and accelerate delivery of pending improvements.
  • Ensure the team has access to PostgreSQL infrastructure for testing performance improvements as batch embedding capabilities are finalized.

View project on GitLab: ai_vdb_provider_postgres

AI Image Alt Text

A merge request was opened to expand the module's compatibility with additional image-based editing interfaces. Currently, the module's automated alt text generation works with a limited set of image editing tools. This expansion would allow more content creators across different workflows to benefit from AI-generated alternative text descriptions, reducing manual effort and improving accessibility compliance across a wider range of content types.

The work also includes optimizations to reduce unnecessary code loading when the AI alt text features are not actively being used on a page, which should improve overall site performance.

As an alpha-stage project, this development work is progressing normally. The module continues to expand its capabilities while refining its technical foundation.

How can I help on this project?

  • Identify content teams or sites that could pilot the expanded widget support once merged, providing real-world feedback on accessibility improvements.
  • Allocate testing resources to validate the performance optimizations across different content workflows before wider rollout.

Contributors: codebymikey

View project on GitLab: ai_image_alt_text

AI Agents

Development activity this period focused on two areas aimed at improving the module's flexibility and reliability. Work is underway to enable the creation of multiple tool instances within a single agent. Currently, users are limited to one tool per agent, which restricts functionality when working with generic or reusable tools. A merge request addressing tool instances was opened, which also introduces a proper configuration schema to improve consistency. This change will allow more flexible agent configurations and better support complex workflows.

Separately, improvements are being made to the field agent's function calls. Testing revealed that more advanced reasoning agents can trigger errors by attempting to load multiple configuration types simultaneously, or by requesting them in the wrong sequence. The Better function calls for field agent issue was updated to address these reliability concerns, ensuring the agent can handle more verbose reasoning patterns without failing.

How can I help on this project?

  • Prioritize testing resources for the tool instances feature once the merge request is ready for review, as this unlocks significant new capabilities.
  • Ensure the team has access to diverse AI models for testing reasoning agent behaviors under real-world conditions.

Contributors: Nicolae Procopan (thebumikgmail.com)

View project on GitLab: ai_agents

Tool API

Activity this period focused on planning enhancements to the user experience. A new feature request was opened to Display Tool Description in Tool Explorer, which would help users better understand their options when browsing available tools. The proposal has been accepted and tagged as a quick win, indicating it should be straightforward to implement once work begins.

No code was merged or committed during this period. The module continues in active development with feature refinement underway.

How can I help on this project?

  • Allocate developer time to implement the accepted Tool Explorer enhancement, which is ready to proceed and flagged as low-effort.
  • Clarify product priorities to help the team decide which user-facing improvements should be tackled next.

View project on GitLab: tool

Drupal Canvas

Canvas made progress on several fronts over the past day, focusing on brand management, backward compatibility, and bug fixes affecting media uploads and SVG handling.

The Brand Kit color support work advanced significantly, with three merge requests integrated to deliver color preservation features and usage tracking. These changes enable content teams to define and manage brand color palettes more reliably. Layout fixes for the Brand Kit font family and variant rows were also completed, resolving visual issues in the brand management panel.

A fix was merged to improve page variant backward compatibility for recipes, ensuring that sites installed from templates continue to display content correctly after Canvas updates. This reduces disruption for teams using site templates and avoids the need for immediate recipe rewrites.

Two active issues remain under review. A media library bug affecting SVG files has a merge request ready for testing; the issue prevents editors from removing SVG assets once selected in component forms. Separately, a proposed fix for file upload failures when filenames contain spaces is under consideration; this constraint currently blocks uploads across the entire site, not just Canvas-managed content.

How can I help on this project?

  • Prioritize reviewer time for the SVG removal and file upload bug fixes to restore expected media handling behavior for content teams.
  • Allocate design resources for the brand management and user interface polish work currently in draft or awaiting final direction.

Contributors: **** (project_19391_bot_17a61b0edeafd5a3db3e8b2462b6c010), **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Adam G-H (phenaproxima), Ahmad Khalil (ahmad-khalil-imagex), Ben Mullins (bnjmnm) [3], Bálint Kléri (balintbrews), Chandan Singh (chandu7929), Georgi Ivanov (givanov), Harjot Singh (harjot.singh), Harumi Jang (hooroomoo), julio retkwa (julioretkwa), Konstantine Kirkitadze (kotekirkitadze), Lauri Timmanee (lauriii) [1], Matt Glaman (mglaman), Narendra Singh Rathore (NarendraR), Wolfgang Ziegler (fago), wotnak [1]

View project on GitLab: canvas

Context Control Center (CCC)

Development work this period focused on preparing the module's architecture for broader use beyond AI agents. Two foundational improvements are in progress that will enable the Context Control Center to deliver contextual information to more parts of Drupal applications.

Work continued on implementing plugin-based generic context consumers, which will allow any feature in Drupal to request and receive context through a unified system, not just AI agents. This architectural shift will make the module more flexible and reusable across different use cases.

A new improvement was initiated to split scope display weight from subscription scoring weight. Currently, when administrators reorder context scopes in the interface, it unintentionally changes which context items take priority in scoring decisions. This fix will separate the visual ordering from the functional ranking, preventing unexpected behavior when the interface is reorganized.

Testing capabilities were enhanced with automated integration tests that verify context injection works correctly without requiring a live AI model. This reduces manual verification effort before releases.

Planning also began for CKEditor integration, which remains blocked pending completion of the consumer plugin architecture.

How can I help on this project?

  • Prioritize review cycles for the large consumer plugin refactor to accelerate the beta release timeline.
  • Clarify requirements for CKEditor integration once the blocking architectural work is complete.

Contributors: Kristen Pol (kepol), Pravesh Poonia (Pravesh_Poonia)

View project on GitLab: ai_context

AI CKEditor

Activity this period focused on issue tracking and project organization. A language behavior issue was migrated into the AI CKEditor project from the broader AI initiative. The summarize feature generating summaries in a different language than the selected text has been formally documented and is now being tracked in the correct repository. This issue affects the summarize function, where users experience summaries being produced in an unexpected language rather than matching the language of the content they selected.

No merge requests were completed and no code changes were committed during this period. The module remains in active development as part of the AI Initiative Sprint.

How can I help on this project?

  • Prioritize resources to investigate and resolve the language inconsistency in the summarize feature, as it directly impacts user experience and content accuracy.
  • Clarify product requirements around multilingual content handling to guide technical decisions and prevent similar issues.

View project on GitLab: ai_ckeditor

Field Widget Actions

No development activity was recorded during this period. A new issue was opened regarding the Bug when trying to "Remove action"?, where users are unable to remove previously configured actions from field settings. This affects the ability to modify or reverse configuration decisions once actions have been added to a field, which could impact workflow flexibility for site administrators.

The module remains in active use with version 1.4.1, and the issue is currently unassigned and awaiting investigation. As this is an early-stage module, open issues are part of the normal development process.

How can I help on this project?

  • Allocate developer resources to investigate and resolve the configuration removal issue, which affects day-to-day site administration workflows.
  • Consider prioritizing bug fixes if this module is part of critical content management processes within your organization.

View project on GitLab: field_widget_actions

FlowDrop

Over the past 24 hours, thirteen detailed conformance issues were opened and documented as part of a systematic specification audit. This work focuses on ensuring that FlowDrop's runtime behavior matches its published specification across workflow validation, API behavior, data processing, and orchestration. The issues range from how the system handles misconfigured workflow gateways to inconsistencies in error responses and data exposure rules.

Key areas identified for alignment include: ensuring that gateway failures produce clear errors rather than silent execution paths (Unmatched gateway outcome must be loud: default branch port or error Output, never a silent subtree), preventing double-execution of asynchronous workflows (ORC-14: The asynchronous handover is not atomic — the same run can be queued and claimed twice), and standardizing API error responses with machine-readable codes (API-8: Most API refusals still carry no error_code). Several issues concern data validation edge cases, such as schema enforcement and port naming rules.

No merge requests or code changes were completed during this period. The activity represents diagnostic groundwork that will inform upcoming fixes to improve reliability and specification compliance.

How can I help on this project?

  • Prioritize which specification conformance issues should be addressed first, balancing user-facing impact with technical dependencies.
  • Ensure engineering capacity is allocated to resolve the atomic orchestration and silent gateway failure issues, which carry operational risk.

View project on GitLab: flowdrop

Langfuse

A new merge request titled Resolve #3594090 "Trace is stored" was opened during this period, representing nearly 1,000 lines of changes. This work focuses on storing trace data within the module. The implementation is now awaiting review before it can be integrated into the project. Once merged, this will expand the module's capability to capture and persist trace information, which is foundational for tracking and analyzing system behavior.

No other issues were updated or commits pushed during this reporting period. The module continues its development trajectory with this storage capability representing a key building block for future functionality.

How can I help on this project?

  • Ensure the team has access to technical reviewers who can evaluate the open merge request and provide feedback to move it toward integration.
  • Clarify the project's roadmap priorities to help contributors focus effort on the most strategically important features after this storage work is completed.

Contributors: Ivo Van Geertruyen (mr.baileys)

View project on GitLab: langfuse

References

[1] DeepChat block lost backwards compatibility for its old configuration in 1.5.x (ai, Issue)

[2] Write QA plan for 1.5.0 (ai, Issue)

[3] AiFunctionCall plugins trigger ExecutableInterface::execute() deprecation notice (ai, Issue)

[6] Add support embeddings via symfony/ai (ai, Issue)

[8] AI CKEditor Summarize generates summaries in a different language than the selected text (ai, Issue)

[20] Issue #3586667: Add the $object parameter to ExecutableInterface::execute() implementations. (ai, MR)

[22] Resolve #3586495 "Add support embeddings via symfony/ai" (ai, MR)

[23] Issue #3586580: Fix summarize prompt translating text instead of preserving original language (ai, MR)

[25] bug: #3586670 DeepChat block loads the whole jQuery UI dialog stack on every page (ai, MR)

[27] feat: #3586671 Load the DeepChat bundle on demand instead of on every page (ai, MR)

[29] Issue #3586687: Guardrails: Make messages translatable (ai, MR)

[39] [DISCUSS] Make it possible to create tool instances (ai_agents, Issue)

[40] Better function calls for field agent (ai_agents, Issue)

[41] Resolve #3552038 "Make it possible" (ai_agents, MR)

[43] Media library remove button is not visible in Canvas component form when selected media is SVG (canvas, Issue)

[44] Add missing request body schemas to `openapi.yml` (canvas, Issue)

[48] Brand Kit color support (canvas, Issue)

[50] Canvas AI: Add a dev page builder agent and wire the placement tools (canvas, Issue)

[54] Canvas AI: Add a Drupal Canvas Agent that answers general questions (canvas, Issue)

[55] Fix Brand Kit font family and variant row layout (canvas, Issue)

[60] Canvas breaks uploading files with spaces for the whole site (canvas, Issue)

[66] Issue #3472584: Add missing request body schemas to openapi.yml (canvas, MR)

[68] #3591838 style updates (canvas, MR)

[69] 3591987: Media library remove button is not visible in Canvas component form when selected media is SVG (canvas, MR)

[71] #3591838 prevent duplicate names (canvas, MR)

[72] fix: #3591967 Improve page variant backward compatibility for recipes (canvas, MR)

[79] #3591838 preserve color format in addition to color scheme (canvas, MR)

[82] #3591838 css variable name can be edited (canvas, MR)

[84] #3591838 Phase 3: Usage data + deletion (canvas, MR)

[91] Brand Kit font family and variant rows lost their layout (canvas, MR)

[92] Resolve "Canvas AI: Add a dev page builder agent and wire the placement tools" (canvas, MR)

[94] Add a tool-less Drupal Canvas Agent that answers general questions and names... (canvas, MR)

[96] Split scope display weight from subscription scoring weight (ai_context, Issue)

[98] Create ai_ckeditor context consumer plugin (ai_context, Issue)

[99] Implement plugin-based generic context consumers and unified consumer configuration (ai_context, Issue)

[100] Issue #3586438: Split scope display weight from subscription scoring weight (ai_context, MR)

[101] Issue #3586346: Implement plugin-based generic context consumers and unified consumer configuration. (ai_context, MR)

[102] AI CKEditor (Standalone): Summarize generates summaries in a different language than the selected text (ai_ckeditor, Issue)

Period: 25 August 2026 to 26 August 2026  |  Generated: 26 August 2026 11:10 GMT

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

Looking for older digests? Browse all digests here.