Daily Digest

Daily Digest – 20 May 2026

2026 Capabilities Progress

  1. Page generation — The Canvas module saw substantial activity directly relevant to this capability, including work on global layout region management via an HTTP API and a CLI tool [69][72], conflict detection during auto-save to protect editors working simultaneously [70], and fixes to prevent broken component output on published pages [94]. These collectively strengthen the reliability and completeness of the AI-assisted page building experience. Next milestone: merging the several significant features currently in review, including region management and conflict detection.
  2. Context management — No direct progress today.
  3. Background agents — The fix for AI agents entering infinite loops when unable to resolve a task was delivered today, along with a database update hook to ensure existing installations migrate cleanly [59][62]. Error visibility during background queue processing also progressed, with a merge request to rethrow exceptions from the queue processor under review [8][23]. A risk remains: two bugs affecting how agents interpret content structure and field types are open and unresolved [56][57], which could cause agents to act on incorrect information in complex content configurations.
  4. Design system integration — Active progress in Canvas, with work underway to expose content entity type and field endpoints needed for entity reference selection in the visual editor [64], and a configuration option for how code components interact with deployment workflows progressing through review [97]. Fixes were also merged to handle invalid component configurations gracefully [89] and to resolve schema validation inconsistencies between front and back ends [96][98]. These improve the stability of AI working within a structured component environment.
  5. Content creation and discovery — Meaningful progress across multiple workstreams. AI content suggestions can now be configured per entity type rather than appearing globally, giving administrators meaningful control over where AI drafting assistance surfaces [15][26]. Work is also progressing on enabling the MDX markdown editor on plain text fields [1][18] and on adding summarisation capabilities inside CKEditor [17]. AI Search received a stability fix preventing crashes when search servers are misconfigured [101][105][106], and batch embedding improvements for faster content indexing remain in progress [10]. A risk to note: a compatibility issue is currently causing automated tests to fail on the AI Search 2.x line [99], which must be resolved before the module can reach a stable release.
  6. Advanced governance — The guardrail fix addressing the critical gap where safety rules only evaluated the most recent message — rather than the full conversation — is progressing through review [3][21]. A semantic topic matching mode for the RestrictToTopic guardrail also advanced [12], which strengthens policy enforcement on AI outputs. The propagation and validation of user identity through the AI request pipeline is under review [5][22], which is foundational for audit trail completeness. Conflict detection and resolution for selective publishing in Canvas also progressed [82]. The Drupal Eval Commons umbrella proposal [9][13] introduces a longer-term initiative to standardise how AI features are tested and evaluated across projects — early stage, but strategically relevant to governance confidence.
  7. Intelligent website improvements — No direct progress today.
  8. Multi-channel campaigns — No direct progress today.

Shipped

  1. AI Content Suggestions Now Configurable Per Content Type — Site administrators can now control which content types display AI suggestions for editors, replacing the previous all-or-nothing behaviour after installation [15][26].
  2. AI Agents Infinite Loop Fix Completed — A follow-up update was merged ensuring existing sites automatically receive the fix for agents getting stuck in infinite loops, with no manual intervention required from administrators [59][62].
  3. AI Search Crash Fix Shipped for Both Release Lines — A bug causing crashes when a search server is inactive or misconfigured was resolved and delivered across both the current and previous supported versions [101][105][106].
  4. Data Integrity Fix for amazee.ai Search Indexes Under Review — A merge request is open to fix a critical issue where clearing one search index was silently deleting data from all other indexes running in parallel [53][54].
  5. Drupal AI Summit NYC Concluded — The New York summit has been formally closed, with session recordings now being prepared for distribution through the Drupal Association's YouTube channel [48][49].

Ongoing

  1. Anthropic Provider: Prompt Caching and PDF Support Awaiting Review — A merge request is open that would reduce API costs through prompt caching and add PDF document support, but has not yet been merged [51].
  2. Safety Guardrails Only Checking the Last Message — A correctness gap where content safety checks ignore earlier messages in a conversation is under active work but not yet resolved [3][21].
  3. Anonymous Chat Users Losing Conversation History — A fix is under review for a problem where anonymous visitors to the AG-UI chat widget lose their conversation history between messages, making coherent conversations impossible [108][109].
  4. Rotterdam Dev AI Summit Planning Underway — Full planning is in progress for the developer-focused event co-located with DrupalCon Rotterdam in September, covering speaker confirmation, registration, promotional assets, and press outreach [33][44][45][46].
  5. AI Initiative Governance Document Awaiting Leadership Endorsement — A formal document defining how the initiative plans its work and makes decisions is ready for review but has not yet received leadership approval, which is blocking clearer coordination across teams [28].

AI (Artificial Intelligence)

Activity over the past 24 hours shows steady forward momentum across several capability areas, with one feature delivered and a number of improvements progressing through review.

Delivered

The most significant development is the merge of work allowing AI content suggestions to be configured per entity type. Previously, AI suggestions appeared across all content types and structures automatically after installation, with no way for administrators to control where they appeared. This change, contributed by Artem Dmitriiev (a.dmitriiev), gives site administrators meaningful control over where AI assistance surfaces for editors. The related issue, Configure AI content suggestions settings for different entity types, is now closed.

In Progress

Several other workstreams are active. A UI toggle to enable the MDX markdown editor on plain text fields is under development, alongside a companion bug fix addressing how the editor handles markdown formatting. Work is also continuing on improving the reliability of safety guardrails, which currently only check the most recent message in a conversation rather than the full history -- an important correctness gap. Separately, improvements to how the AI module handles errors during background processing, and how it identifies which user account is executing AI requests, are both in review. A significant architectural improvement to move the Automators feature to structured output is also progressing.

Emerging Initiative

George Kastanis (zorz) has opened an umbrella proposal, Drupal Eval Commons, aimed at establishing a shared framework for testing and evaluating AI features across multiple Drupal projects. This is early-stage planning work with meaningful long-term implications for quality assurance.

How can I help on this project?

  • The Eval Commons initiative is at a critical early design stage where cross-project alignment is needed. Sponsoring a facilitated conversation between the teams involved could prevent duplicated or incompatible work.
  • Several open workstreams are unassigned. Encouraging your team or partners to claim and prioritise these would help maintain delivery pace.

View project on GitLab: ai

Drupal AI Initiative

Summary

Activity over the past 24 hours was concentrated in planning and marketing, with no code changes merged. The most strategically significant item is the Align on AI Initiative Governance and Roadmap issue, which is seeking leadership endorsement of a formal document defining how the initiative plans its work, coordinates with maintainers, and makes decisions. Formalising this will give partners and stakeholders a reliable foundation to build on.

A significant cluster of new issues was opened around the Rotterdam Dev AI Summit, a dedicated developer-focused event co-located with DrupalCon Rotterdam in September. Matthew Saunders (jmsaunders) has structured the full planning lifecycle, covering the call for sessions, speaker confirmation, registration, promotional assets, press outreach, and post-event recordings. Alongside this, the team is actively promoting the AI Summit London in June and the broader Enterprise AI Summit in Rotterdam. The Drupal AI Summit NYC tracker was formally closed, marking the conclusion of that event, with session recordings now being prepared for wider distribution via the Drupal Association's YouTube channel.

An early-stage idea was also raised by Marcus Johansson (Marcus_Johansson) for an AI Cost and Usage module that would give site owners visibility into their AI spending and optionally contribute anonymised usage data back to the community. This is a concept at this stage, not yet in active development.

How can I help on this project?

  • Endorse the governance document: The governance and roadmap alignment is awaiting leadership approval. Reviewing and endorsing it would unblock clearer decision-making across the initiative.
  • Champion event visibility: The Rotterdam and London summits need reach. Executive advocacy through organisational networks or partner channels can drive registrations and speaker submissions that the team cannot generate alone.
  • Signal appetite for the cost transparency concept: Letting the team know whether visibility into AI usage and costs is a priority for your organisation would help determine whether the AI Cost and Usage idea warrants resourcing.

View project on GitLab: ai_initiative

Anthropic Provider

Summary

Activity over the past 24 hours has been focused on a single but meaningful contribution. Carlos Ospina (camoa) has opened a merge request, Bump SDK constraint and drop method_exists defensive check, representing the second phase of a broader effort to strengthen the module's integration with Anthropic's underlying technology.

This phase introduces two notable capabilities: a prompt caching feature, which allows the system to reuse previously processed instructions rather than repeating work on every request, and support for PDF documents as inputs. Prompt caching in particular has direct cost and performance implications, as it reduces the volume of processing sent to Anthropic's service. An admin interface is included, giving site administrators control over caching behaviour and timing. This builds on work already merged in phase one and continues to move the module toward a more capable and production-ready state.

No issues were updated and no commits were pushed directly during this period. The merge request is awaiting review. For a module at this stage of development, this level of focused, incremental progress is healthy and expected.

How can I help on this project?

  • Ensure a qualified reviewer is available to assess the open merge request promptly, so this phase of work is not left waiting.
  • Consider whether broader organisational interest in cost reduction through prompt caching warrants prioritising this module's progress on the roadmap.

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 data integrity improvements for the module's vector database (VDB) functionality, which powers AI-driven search and content indexing capabilities.

The most significant development is a fix now under review for a critical data integrity issue: VDB: Clearing all indexed data of search index A drops indexed data of others. In practical terms, when a site administrator cleared the indexed data for one search index, it was inadvertently wiping out the indexed data for all other search indexes sharing the same database. A merge request authored by m4olivei is open and awaiting review to resolve this. This is a meaningful fix for any organisation relying on multiple AI-powered search indexes running in parallel.

A separate, lower-priority issue remains open: VDB: Ignored fields should not have database column, reported by mxr576 (mxr576). This concerns unnecessary database storage being allocated for fields that are intentionally excluded from AI processing -- a housekeeping concern rather than an urgent problem.

Both issues are flagged for backporting to an earlier supported release, indicating the team is maintaining compatibility across versions.

How can I help on this project?

  • Ensure the open merge request fixing the data integrity issue is reviewed promptly -- advocate for dedicated review time from a qualified team member if bandwidth is constrained.
  • Consider whether additional developer resource is needed to work through the backlog of open issues alongside new feature development.

View project on GitLab: ai_provider_amazeeio

Model Context Protocol

Activity on the Model Context Protocol module over the past 24 hours has been focused on expanding what the tool can do for end users. A new merge request, Write (Create/Update) Operations Support, has been opened by Shubham Goel (shubhamgoel). This is a substantial contribution that would allow AI-connected tools to not just read content from a Drupal site, but also create and update it. That is a meaningful capability milestone, moving the module from a read-only integration toward a more fully featured two-way connection between Drupal and AI assistants.

No issues were updated and no commits were merged during this period, so the work is in review and has not yet landed. This is normal for a module at this stage of development, and the contribution represents healthy forward progress on a key feature.

How can I help on this project?

  • Encourage colleagues or partners with Drupal expertise to review the open merge request, as timely code review helps contributors stay engaged and keeps momentum going.
  • Consider whether your organisation has use cases for AI-driven content creation in Drupal, and share that feedback with the project team to help prioritise the roadmap.

View project on GitLab: mcp

AI Agents

Progress This Period

Activity over the past 24 hours focused on stability improvements and bug resolution. The most notable delivery was the closure of a previously reported issue where AI agents could get stuck in an infinite loop when unable to complete a task. A supporting fix was merged today by AKHIL BABU (AkhilBabu), ensuring that existing installations will be smoothly updated with the new behaviour without requiring manual intervention from site administrators.

Two additional bugs were surfaced and are now under active review. The first, reported by Marc Orcau (budalokko), concerns incorrect field information being passed to the AI when a site's content structure includes relationship fields -- this could cause the AI to misinterpret content types. The second, raised by AKHIL BABU (AkhilBabu), addresses a related issue where certain tool configurations produce errors when agents try to act on content; a proposed fix is already in review under hide_property skips data-type conversion for forced values, breaking non-scalar context types, alongside a separate open fix for Proper value for entity__colon__node context?.

Overall, the project is progressing at a healthy pace for an early-stage module, with bugs being identified, triaged, and addressed in a timely manner.

How can I help on this project?

  • Encourage your team to prioritise reviewing the two open fix proposals currently awaiting approval, as timely review helps maintain momentum.
  • Consider allocating dedicated testing resource to validate bug fixes against real-world content configurations, which would accelerate the path to a stable release.

View project on GitLab: ai_agents

Drupal Canvas

Activity over the past 24 hours has been broad, covering user-facing bug fixes, developer tooling improvements, and meaningful progress on several larger features still in review.

Fixes Delivered

Several bugs were resolved and merged during this period. A fix by wotnak addressed a situation where components with invalid code would produce broken output on published pages. Sapnil Biswas contributed a fix ensuring that misconfigured content blocks are caught early and prevented from causing crashes inside Canvas, rather than failing at the point a user tries to view or edit a page. Christian López Espínola aligned the technical standards used to validate content structures across the editor's front and back ends, which reduces the risk of subtle inconsistencies when editors are working with complex content.

Developer Tooling and Quality

Wim Leers merged two improvements that reduce friction for contributors: a unified linting command and a fix that eliminates redundant automated checks, cutting local feedback times roughly in half. These changes help maintain development pace as the team scales. A drag-and-drop behaviour change was also reverted by Tim Plunkett after review, a routine part of iterative development.

Features in Progress

A significant body of work is advancing through review. Notable among open merge requests are: conflict detection during auto-save (by Feliksas Mazeikis (f.mazeikis)), which will protect editors from accidentally overwriting each other's work; global layout region management in the visual workbench (by wotnak); translation previews (by Ted Bowman (tedbow)); and a configuration option for how code components interact with deployment workflows (by Matt Glaman (mglaman)). These collectively represent material improvements to the editorial and deployment experience.

How can I help on this project?

  • Several substantial features are in review simultaneously. Ensuring dedicated reviewer capacity is available to assess and merge these in a timely way would help maintain momentum.
  • Some merge requests, such as global region management and translation previews, may benefit from early input from editorial stakeholders to confirm the workflows meet real-world needs before they are finalised.

View project on GitLab: canvas

LiteLLM AI Provider

Activity over the past 24 hours was focused on a single but meaningful reliability improvement. A new merge request, fixes streaming failures on some infra and in ddev, has been opened by wouters_frederik (Frederiek Wouters). This addresses a reported problem where streaming responses -- the ability to deliver AI-generated content progressively rather than all at once -- were failing in certain hosting environments and local development setups.

Streaming is important for user experience in AI-powered features, as it makes responses feel faster and more interactive. Fixing reliability issues across different infrastructure configurations broadens the range of environments where the module can be used dependably, which is relevant for teams evaluating or piloting the module in varied setups.

This is an early-stage module and the presence of open issues and work-in-progress contributions is entirely normal and expected at this point in development.

How can I help on this project?

  • Encourage your team to test the module in your own infrastructure and report back on reliability, helping validate fixes like this one more quickly.
  • Consider allocating reviewer time to help move open merge requests from submitted to merged, reducing bottlenecks for contributors.
  • Advocate internally for dedicated time for developers interested in contributing, which helps sustain momentum on a project at this early stage.

View project on GitLab: ai_provider_litellm

AG-UI

Summary

Activity over the past 24 hours has been focused on a single user-facing issue. Takaya Hirose (takayahirose) has identified and opened a fix for a problem where anonymous users of the AG-UI chat widget lose their conversation history between messages. In practice, this means that every time an anonymous visitor sends a message, the system treats them as a brand-new user, making it impossible to hold a coherent conversation. A proposed fix is already under review via Issue 3590036: Fixed lost chat history across requests for anonymous users, addressing the Anonymous users lose chat history across requests issue.

This is a meaningful quality improvement for any deployment where the chat widget is intended to serve visitors who are not logged in. The fix is awaiting review and merge. Given the module is in early development, having a contributor both report and propose a resolution quickly is a positive sign of engagement.

How can I help on this project?

  • Encourage your team to prioritise reviewing and merging the open fix so anonymous users benefit from a working chat experience sooner.
  • Consider whether dedicated reviewer capacity is available to prevent open contributions from stalling, helping maintain contributor momentum.
  • Advocate for broader testing with anonymous user scenarios to surface similar issues before a stable release.

View project on GitLab: agui

AI Content Classification

Summary

Activity over the past 24 hours was light but meaningful. The one notable update was the closure of Error when saving new node, a bug originally reported by breidert (breidert) that caused an unexpected error when creating new content after installing the module. Resolving this improves the reliability of the core user-facing workflow: getting AI-generated content tags applied when new content is saved. No new commits or merge requests were recorded in this period.

As an alpha-stage module, having a small number of open issues under active triage is entirely normal. The closure of this bug is a positive sign that the team is keeping quality in check as the project matures.

How can I help on this project?

  • Encourage colleagues or partners to install the module in test environments and report their experiences, helping surface real-world issues early.
  • Consider whether dedicated testing or review time can be allocated to keep momentum going, particularly as the module moves toward a more stable release.

View project on GitLab: ai_recipe_content_classification

References

[1] Add UI toggle to enable MDXEditor on plain text field widgets (ai, Issue)

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

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

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

[9] Drupal Eval Commons umbrella (ai, Issue)

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

[12] RestrictToTopic guardrail: add semantic topic matching mode (ai, Issue)

[13] [Layer 2] Cross-project result envelope tracking (every_eval_ever 0.2.2 + additional_details) (ai, Issue)

[15] Configure AI content suggestion settings for different entity types (ai, Issue)

[17] Make it possible to use Summarize model in CKEditor (ai, Issue)

[18] Issue #3586451: Allow to use MDX Editor in Text plain widget (ai, MR)

[21] Resolve #3579088 "Guardrail plugins only" (ai, MR)

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

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

[26] Resolve #3574169 "Ai content suggestions setting for enities" (ai, MR)

[28] Align on AI Initiative Governance and Roadmap (ai_initiative, Issue)

[33] [META] Rotterdam Dev AI Summit (ai_initiative, Issue)

[44] Rotterdam AI Dev Summit - PLANNING - Confirm Speaker Commitments (ai_initiative, Issue)

[45] Rotterdam AI Dev Summit - PLANNING - Call for Sessions (ai_initiative, Issue)

[46] Rotterdam Dev AI Summit - CONTENT - Finalise Agenda and Schedule (ai_initiative, Issue)

[48] Drupal AI Summit NYC META (ai_initiative, Issue)

[49] Session recordings AI Summit NYC (ai_initiative, Issue)

[51] Issue #3590963: Bump SDK constraint and drop method_exists defensive check (ai_provider_anthropic, MR)

[53] VDB: Clearing all indexed data of search index A drops indexed data of others (ai_provider_amazeeio, Issue)

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

[56] GetEntityFieldInformation leaks target_entity_type / target_bundle_type across fields (ai_agents, Issue)

[57] hide_property skips data-type conversion for forced values, breaking non-scalar context types (entity, list, JSON, YAML) (ai_agents, Issue)

[59] Follow up #3547457. Add post update hook for max_loops_message (ai_agents, Issue)

[62] Issues/3586024: Add post update hook. (ai_agents, MR)

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

[69] feat(CLI Tool) #3576837 Prototype managing the global layout (aka regions) within Canvas Workbench (canvas, MR)

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

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

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

[89] Issue #3580070: Reject invalid default block configs (canvas, MR)

[94] fix: #3591072 getFallbackCompiledJs() returns malformed JS (canvas, MR)

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

[97] Issue #3591147: Provide config sync toggle for code components (canvas, MR)

[98] fix: #3591133 strip draft-04 'id' keyword before sending schema to AJV v8 (canvas, MR)

[99] Fix 2.x branch integration with AI 2.x now that Symfony Platform is integrated (ai_search, Issue)

[101] Ensure valid server in boost plugins (ai_search, Issue)

[105] Resolve "Ensure valid server in boost plugins" (ai_search, MR)

[106] Resolve "Ensure valid server in boost plugins 1x" (ai_search, MR)

[108] Anonymous users lose chat history across requests (agui, Issue)

[109] Issue 3590036: Fixed lost chat history across requests for anonymous users. (agui, MR)

Period: 20 May 2026 to 21 May 2026  |  Generated: 21 May 2026 15:49 GMT

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

Looking for older digests? Browse all digests here.