Daily Digest

Daily Digest – 19 May 2026

2026 Capabilities Progress

  1. Page generation — Canvas is actively building the foundation for AI-assisted page generation, with work underway on a prototype form builder, global page region management via HTTP API, and improved entity reference handling within the editor [67][80][56][61]. None of these have landed yet, but the volume of parallel work in review suggests this capability is approaching a meaningful milestone. Risk: several large pull requests are queued without sufficient reviewer capacity, which could delay delivery.
  2. Context management — Meaningful progress today. The Context Control Center module advanced two redesigned administration screens toward completion, improving how editors and administrators view and manage brand voice, style guides, and governance rules [84][81][87][86]. A fatal error affecting real users trying to configure context items is currently unassigned, which poses a reputational risk and should be prioritised [82].
  3. Background agents — Steady foundational progress. Work on defining and enforcing a clear identity contract for AI tasks that run without a logged-in user continued across multiple issues and merge requests [10][11][12][28], and a fix ensuring queue-based background tasks surface errors properly rather than silently failing is in progress [9][27]. A two-way bridge between the Orchestration and ECA automation frameworks — which would allow background agents to trigger registered services — remains in planning with no code yet written [91]. The execution identity work is unresourced, which is a risk as background agent use grows.
  4. Design system integration — Active progress in Canvas, where work on contrib plugin compatibility would allow AI to work with components from third-party design systems, not just the core Canvas set [77]. JSON Schema support for content entity references is also advancing, which underpins how AI can understand and build with typed components [61][49]. No single milestone landed today, but the direction is clearly toward broader component compatibility.
  5. Content creation and discovery — Several threads advanced. A fix for CKEditor AI streaming failures with OpenAI is under review, directly unblocking AI-assisted inline drafting for editors [3][24]. Support for PDF documents in AI chat was completed and merged, expanding the range of content AI can work with [7][25]. Batch embedding performance improvements for search indexing are in progress [8], and a fix for broken indexing with custom data sources is open [13]. The Anthropic provider now supports extended thinking mode and effort control, giving content teams more precision in AI-assisted drafting tasks [42]. Settings storage for AI content suggestion plugins was also fixed [17][31].
  6. Advanced governance — Limited but relevant progress. The execution principal work — ensuring AI actions are tied to a verified, auditable identity — directly supports comprehensive audit trails for AI changes [10][11][12][28]. Auto-updating default prompt entities only when sites have not customised them protects governance configurations from being silently overwritten during upgrades [19]. A kernel test for mid-stream content guardrails is also in progress, supporting future enforcement of governance rules during live AI generation [14]. No batch approval or branch versioning work was visible today.
  7. Intelligent website improvements — No direct progress today. The Automators work — moving to structured output and generalising field widget action behaviour — is the closest ongoing thread, as it underpins how AI can propose and apply content changes [15][16][33], but none of this landed today and it is not yet connected to performance-data feedback loops.
  8. Multi-channel campaigns — No direct progress today.

Shipped

  1. PDF Chat Support Added — The AI module now formally supports AI-powered chat with PDF documents, bringing it to parity with what providers like OpenAI, Anthropic, and Google Gemini can natively offer [7][25].
  2. Anthropic Provider: Advanced Model Capabilities Released — The Anthropic integration was updated to support effort control, extended reasoning mode, and accurate token usage reporting, giving organisations more precision and cost visibility in AI workflows [42].
  3. Canvas AI Chat Gains Conversation Memory — The Canvas editor's AI assistant now retains conversation history across a session, making it more coherent and useful for editors, with configurable history length [66].
  4. Canvas Release Pipeline Restored — A broken automated release process was repaired, restoring the team's ability to publish new versions of Canvas without manual intervention [72].
  5. Context Control Center Listing Page Redesigned — A redesigned administration listing page for the Context Control Center module has been submitted, improving how administrators view and manage context items by clarifying status, scope, and token usage [84][87].

Ongoing

  1. CKEditor AI Streaming Fix Under Review — A bug preventing real-time AI-assisted content editing in CKEditor when used with OpenAI is awaiting review, and until resolved it blocks a key editorial workflow [3][24].
  2. amazee.ai Data Integrity Fix Pending Approval — A fix is under review that prevents clearing one search index from accidentally wiping data from unrelated indexes, a potentially serious issue for production sites running multiple indexes [44].
  3. AI Execution Security Architecture in Progress — Work to ensure background and automated AI tasks correctly identify and authenticate themselves is advancing across multiple related issues, reducing the risk of unauthorised or misconfigured AI operations [10][11][12].
  4. Deprecated OpenAI Image Model Awaiting Removal — A fix to remove DALL-E 3 as a default image generation option following its deprecation by OpenAI is open and awaiting review, and leaving it unresolved may cause failures for teams relying on image generation [41].
  5. Context Control Center Fatal Error Unassigned — A crash reported by an early adopter when configuring context items has no assigned developer, posing a reputational risk as the module gains wider adoption [82].

AI (Artificial Intelligence)

Activity over the past 24 hours across the AI module reflects a broad push on product quality, security foundations, and platform reliability.

Delivered

One concrete improvement landed: support for PDF documents in AI-powered chat was completed and merged. The Add ChatWithPdf capability to AiModelCapability enum change, contributed by Abhisek Mazumdar (abhisekmazumdar), means the module can now formally advertise and consume PDF chat capabilities from providers such as OpenAI, Anthropic, and Google Gemini.

In Progress

Several significant workstreams are advancing. A fix for a streaming failure affecting the CKEditor AI integration with OpenAI is under review via CKEditor AI streaming fails for OpenAI when Guzzle uses StreamHandler for "stream => true" requests, addressing a real-world barrier to AI-assisted content editing. Work continues on tightening security around how background and automated AI tasks identify and authenticate themselves, tracked across multiple related issues on execution identity. A proposal for a shared evaluation framework across several Drupal AI projects -- Drupal Eval Commons umbrella -- was raised, aiming to prevent duplicated effort and incompatible approaches as AI quality testing matures.

On the usability front, Artem Dmitriiev (a.dmitriiev) is assigned to work that would allow site builders to enable the MDX rich text editor through the administration interface without requiring developer intervention, as described in Add UI toggle to enable MDXEditor on plain text field widgets. A new Add SECURITY.md to project root task was opened to give security researchers a clear, responsible disclosure path -- an important step as the module's adoption grows.

How can I help on this project?

  • Prioritise the evaluation framework: The Drupal Eval Commons proposal needs cross-project alignment. A leadership nudge to bring the relevant project leads together could prevent duplicated work and set a shared quality standard.
  • Resource the security foundations: The execution identity and security disclosure work has no assigned contributors. Directing developer time here reduces risk as the module is adopted more broadly.

View project on GitLab: ai

Drupal AI Initiative

Summary

Activity over the past 24 hours has been focused on marketing, event preparation, and tidying up assets from recent AI events. No code changes or technical merges occurred during this period -- the work is entirely centred on outreach, branding, and content.

On the post-event side, the team is working to make the most of content captured at the AI Summit in New York City. Work is underway on Session recordings AI Summit NYC, with Matthew Saunders (jmsaunders) and Paul Johnson (pdjohnson) coordinating to get videos onto YouTube and Drupal TV, followed by a promotional push. This turns a one-time event into lasting, reusable content for the community.

Looking ahead, preparations are accelerating for the Enterprise AI Summit in Rotterdam (September 2026). Visual identity work is in progress via Look and feel for Enterprise AI Summit Rotterdam, and a separate effort is tracking the creation of marketing assets in Enterprise AI Summit - Visual assets. LinkedIn promotion for both Rotterdam and the nearer-term AI Summit London (June 2026) is being coordinated by Amber Henry (amber.henry).

On the technical demonstration front, Kristen Pol (kepol) is addressing issues with the demo repository used at the Chicago Driesnote, including fixing a search capability that was not functioning and adding example prompts so the demo is more immediately useful for future audiences.

How can I help on this project?

  • Amplify reach: Share or encourage your organisation's social channels to promote the Enterprise AI Summit Rotterdam and the upcoming London Summit to reach senior decision-makers beyond the existing Drupal community.
  • Sponsor or connect sponsors: The Rotterdam event is actively seeking sponsors -- leadership connections to enterprise brands or budget decisions here could directly unblock event planning.
  • Prioritise the demo backlog: The Chicago Driesnote demo work is currently unassigned in part. Directing a resource or contractor to own it would ensure polished demonstrations are ready for future executive-audience events.

View project on GitLab: ai_initiative

OpenAI Provider

Activity Summary

Activity over the past 24 hours was light but focused on keeping the module current with changes in the underlying AI landscape. Abhisek Mazumdar (abhisekmazumdar) has submitted a fix addressing the fact that DALL-E 3, an image generation model from OpenAI, has been deprecated and should no longer be offered as a default option within the module. The proposal is captured in fix: #3590873 Dall-E 3 has been deprecated and should be removed as default, which is currently open and awaiting review.

While this is a small change, it reflects an important ongoing maintenance need: as AI providers retire or update their offerings, the module must keep pace to avoid presenting users with options that no longer work. Leaving deprecated defaults in place can cause confusion or failures for teams relying on image generation capabilities.

How can I help on this project?

  • Ensure there is dedicated reviewer capacity available so that open fixes like this do not sit unreviewed for extended periods.
  • Consider advocating for a lightweight process to track AI provider changes proactively, reducing the lag between a provider deprecating a feature and the module being updated.

View project on GitLab: ai_provider_openai

Anthropic Provider

Activity over the past 24 hours was focused on a single but meaningful delivery. A significant enhancement has been merged into the project that adds support for Anthropic's latest model capabilities, contributed by Carlos Ospina (camoa).

What was delivered

This update unlocks three important capabilities for users of the Anthropic integration:

  • Effort control: Editors and developers can now instruct Anthropic's AI models to apply more or less processing effort to a task, helping balance response quality against speed and cost.
  • Extended thinking mode: Users can opt into a deeper reasoning mode where the AI works through complex problems more thoroughly before responding, with controls over how much budget is allocated to that thinking process.
  • Improved token transparency: The integration now accurately captures and reports how many tokens are consumed during AI interactions, supporting better cost visibility and usage tracking.

Together, these features bring the Drupal integration closer to parity with what Anthropic's models can natively offer, giving organisations more precision and insight when deploying AI-assisted content workflows.

How can I help on this project?

Leaders can support momentum by ensuring the team has access to Anthropic API credits to test new capabilities at scale. Encouraging adoption of these features within internal workflows would also provide valuable real-world feedback. Finally, aligning stakeholders on acceptable AI cost thresholds will help the team make informed decisions about effort and thinking settings.

View project on GitLab: ai_provider_anthropic

amazee.ai Private AI Provider

Summary

Activity over the past 24 hours has been focused on quality and reliability. A significant bug fix is now under review addressing a data integrity risk in the module's search and indexing functionality. When clearing indexed content, the existing behaviour was inadvertently wiping data from unrelated indexes that share the same storage collection -- a potentially serious issue for sites running multiple search indexes. The proposed fix, submitted by m4olivei in Issue #3579517: Fix clearing index data destroying other indexes' data, targets this precisely so that only the intended content is removed. This reduces the risk of silent data loss and improves confidence in the module's reliability for production use.

Separately, an issue concerning the onboarding and upgrade experience for trial account users has been closed. This work, originally raised by Jürgen Haas (mxr576), aimed to make it easier for organisations moving from free trials to paid subscriptions -- an important step for user retention and commercial adoption of the amazee.ai integration.

How can I help on this project?

  • Prioritise review and sign-off on the open data integrity fix to prevent it from blocking a stable release.
  • Consider whether dedicated resourcing is available to accelerate testing of production-readiness issues like this one.
  • Champion closer alignment between the amazee.ai commercial team and the module maintainers to ensure trial-to-subscription journeys remain a funded priority.

View project on GitLab: ai_provider_amazeeio

AI Agents

Recent Progress

Activity over the past 24 hours on the AI Agents module has been modest, with two open issues receiving attention but no new code merged or committed during this period.

One area of focus is improving how agents handle certain content-saving operations. A user encountered an error when trying to lock down a specific value within an agent's configuration, and a fix is now under review via Issue #3555863: Support forced values for context parameters containing a colon. If accepted, this will make it easier for site builders to create focused, predictable agents without running into unexpected errors. Avinash jha (avinash.jha) authored the proposed fix, and it is awaiting review assigned to Akhil Babu (AkhilBabu).

A second issue, ContentEntitySeeder crashes on double-wrapped entity_array when ComplexToolItems + multiple=TRUE context definition produces nested array schema, flags a bug where the module can crash when handling certain complex data structures. This is currently unassigned and has no proposed fix in progress, representing a gap that could affect reliability for users working with more advanced content workflows.

How can I help on this project?

Consider assigning a developer to investigate the unresolved crash bug, as it currently has no owner or fix in progress. You could also help by encouraging broader code review participation to move the pending fix across the finish line more quickly. Ensuring the team has adequate capacity during this active development phase would reduce the risk of quality issues accumulating.

View project on GitLab: ai_agents

Drupal Canvas

The past 24 hours saw steady progress across stability, AI capabilities, and the editor experience, with six changes merged into the codebase.

Stability and Quality

A bug fix addressing a crash caused by an earlier workaround was merged by Mykola Podpriatov (nickolaj) via Issue #3576410: Replace `count($settings['allowed_formats'])` with..., ensuring text content fields behave reliably. Separately, a previous change that caused errors when editors reduced the number of repeating content items was rolled back by Ignacio Sánchez Holgueras (isholgueras) -- a replacement fix is already in progress. The automated release pipeline was also repaired by Bálint Kléri (balintbrews), restoring the team's ability to publish new versions without manual intervention.

AI Assistant Improvements

The Canvas AI chat feature now retains conversation history, making interactions more coherent and useful. This improvement, contributed by Levente Besenyei (LeventeB), also makes the history length configurable so it can be tuned as needs evolve.

Work in Progress

A large volume of open work is under review, including multilingual editing support, a prototype form builder, conflict detection during autosave, global page region management, and improved handling of entity references within the editor. These represent significant capability additions that are moving through the review process but have not yet landed.

How can I help on this project?

  • Prioritise review capacity: Several large, high-value features are awaiting review. Ensuring sufficient developer time is allocated to reviewing open contributions would accelerate delivery.
  • Align on multilingual scope: Multiple workstreams around translation are running in parallel. Leadership alignment on the desired end-state could help the team sequence and complete this work more efficiently.

View project on GitLab: canvas

Context Control Center (CCC)

The past 24 hours have seen meaningful forward momentum on the Context Control Center module, with activity spanning user experience improvements, a newly surfaced bug, and a clarification request from an early adopter.

Redesigned User Interface Moving Forward

Two significant pieces of work are underway to bring the module's interface in line with a recently completed UX review. Matt Glaman (mglaman) has submitted a merge request implementing the Update context listing page per new design, which overhauls how administrators see and manage context items in list view -- improving clarity around status, scope, and token usage. Separately, Eric Homanchuk (erichomanchuk) has an open merge request for the Update context view page per new design, addressing how individual context items are displayed. Together, these changes represent a more polished, user-friendly administration experience.

Bug Affecting Early Adopters

Michael Anello (ultimike), testing the module through a public demo environment, has reported a fatal error when attempting to configure context items. This issue is currently unassigned and unresolved, which represents a risk to user confidence, particularly as the module gains wider adoption.

Community Engagement and Documentation Gaps

The same contributor also raised a question about feature availability and configuration guidance, suggesting that documentation or onboarding materials may not yet reflect the module's current capabilities.

How can I help on this project?

  • Prioritise the bug fix: The unassigned fatal error affecting real users carries reputational risk. Leadership could advocate for dedicated developer time to resolve it promptly.
  • Invest in documentation: Early adopters are encountering gaps in guidance. Funding or resourcing a documentation effort would reduce friction and support wider adoption.

View project on GitLab: ai_context

Field Widget Actions

Activity on the Field Widget Actions module over the past 24 hours has been light, with discussion continuing on two open issues but no new code merged or committed during this period.

User Experience Improvement in Progress

Work is underway to improve how action buttons appear on content editing pages. Currently, the buttons are styled too prominently and positioned in a way that can confuse editors, making them appear as important as the main "Save" button. An open proposal, Suggestions buttons should not be primary and should be closer to the field, addresses this by restyling and repositioning the buttons so they feel more appropriately secondary. A code change from Adam Gefen (manandearth) is already prepared and awaiting review. Bruno Bruno (bbruno) is assigned to this task.

Expanding AI Workflow Capabilities

A feature request from Zsolt Gere (gerezs), Support Automator Chain trigger with Field Widget Actions, proposes enabling more complex, multi-step AI workflows to be triggered directly from content editing pages. This would allow editors to run sophisticated AI processes without needing additional fields or page reloads. No contributor is currently assigned to this request.

How can I help on this project?

Consider assigning a developer to the unowned AI workflow feature request, as it has no one currently driving it forward. You could also advocate for prioritising the review of the button styling fix, which is ready and waiting, and champion this module within your organisation to grow the contributor base.

View project on GitLab: field_widget_actions

Orchestration

Progress and Activity

Activity over the past 24 hours has been light, with a single issue seeing updates. Shibin Das (D34dMan) is working on a meaningful capability gap in the Orchestration module: currently, the integration between Orchestration and the ECA automation framework only works in one direction. External systems can trigger ECA-driven workflows through Orchestration, but ECA itself cannot reach back and call upon other services registered within Orchestration.

The issue [orchestration_eca] Add "Execute Orchestration service" ECA action to allow ECA to invoke registered services aims to close this gap, enabling ECA's event and logic-handling capabilities to trigger any registered Orchestration service. This would make the integration genuinely two-way, unlocking more sophisticated automation scenarios and increasing the value of the module for teams relying on workflow automation.

No code was merged or committed during this period, so this work remains in the planning and discussion stage.

How can I help on this project?

  • Consider whether dedicated development time can be allocated to move this issue from discussion into active implementation.
  • If your organisation relies on workflow automation, signal its strategic importance to help prioritise this work.
  • Identify internal stakeholders or teams who could review and validate the proposed functionality once a prototype is available.

View project on GitLab: orchestration

References

[3] CKEditor AI streaming fails for OpenAI when Guzzle uses StreamHandler for "stream => true" requests (ai, Issue)

[7] Add ChatWithPdf capability to AiModelCapability enum (ai, Issue)

[8] Batch embeddings for improved indexing performance (ai, Issue)

[9] Rethrow exceptions from queue processor (ai, Issue)

[10] [PLAN] Define "Execution Principal" contract for sessionless, queued, and outside-in AI runs (ai, Issue)

[11] Enforce execution principal in AiAssistantApiRunner (no fallback to session user when executor is provided) (ai, Issue)

[12] Propagate server-resolved executor UID from /api/deepchat to AiAssistantApiRunner (ai, Issue)

[13] Indexing breaks with custom SearchAPI DataSource (ai, Issue)

[14] Add kernel test for StreamableGuardrailInterface mid-stream buffering and evaluation (ai, Issue)

[15] Move Automators to Structured Output (ai, Issue)

[16] Generalize behaviour of FWA with Automators (ai, Issue)

[17] Save AI Content Suggestion plugin settings inside ai_content_suggestions.settings config object (ai, Issue)

[19] Auto-update default prompt entities on module updates, but only if the site has not customized them (ai, Issue)

[24] Issue #3586446: Add per-provider HTTP handler configuration (ai, MR)

[25] Issue #3586448: Add ChatWithPdf capability to AiModelCapability enum (ai, MR)

[27] Issue #3571498: Rethrow queue worker exceptions (ai, MR)

[28] Issue #3574877: Propagate and validate DeepChat execution principal (ai, MR)

[31] Resolve "Save AI Content Suggestion plugin settings inside ai_content_suggestions.settings config object" (ai, MR)

[33] feat: #3577170 Move Automators to Structured Output (ai, MR)

[41] fix: #3590873 Dall-E 3 has been deprecated and should be removed as default (ai_provider_openai, MR)

[42] Issue #3572402: Add effort, adaptive thinking, and native token usage support (ai_provider_anthropic, MR)

[44] Issue #3579517: Fix clearing index data destroying other indexes' data (ai_provider_amazeeio, MR)

[49] Use draft-07 consistently in backend and frontend. (canvas, MR)

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

[61] feat: #3586613 JSON Schema content-entity-reference (canvas, MR)

[66] chore(canvas-orchestrator): #3555239 adds short term memory for ai chat (canvas, MR)

[67] #3590937 "Prototype form builder" (canvas, MR)

[72] ci: #3590944 Image used for the release CI job is missing git (canvas, MR)

[77] feat: #3552818 Contrib compatibility: ComponentPluginManager decorator should... (canvas, MR)

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

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

[82] TypeError when trying to "Configure context items" from /admin/ai/context/settings/agents (ai_context, Issue)

[84] Update context listing page per new design (ai_context, Issue)

[86] Add single context item display (ai_context, MR)

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

[91] [orchestration_eca] Add "Execute Orchestration service" ECA action to allow ECA to invoke registered services (orchestration, Issue)

Period: 19 May 2026 to 20 May 2026  |  Generated: 20 May 2026 10:20 GMT

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

Looking for older digests? Browse all digests here.