Daily Digest

Daily Digest – 26 June 2026

2026 Capabilities Progress

  1. Page generation — Significant progress on the underlying Canvas platform, with conflict detection and resolution features advancing to support multi-editor workflows [87][88][91], and fixes addressing boolean property handling [45][46][47][48] and translation workflow bugs [50][66][74]. The AI-powered page generation interface saw improvements to lock the canvas during builds and add long-running task UI elements [51].
  2. Context management — The Context Control Center completed conversion of the scheduler feature to an optional submodule [93][132], while UX improvements to context listing pages [97][133] and scope plugin renaming for better developer experience [99][134] are in progress toward beta3 release. A comprehensive code quality review generated cleanup issues targeting accessibility, documentation, and API consistency [101][102][103][104][105][106][107][108][109].
  3. Background agents — No direct progress today.
  4. Design system integration — Canvas development addressed component handling bugs including boolean property issues [45][46][47][48][79], translation support for code components [57][80], and fixes for component inputs validation [11][64][85]. Work also progressed on Drush commands to list, audit, and generate Canvas components [81].
  5. Content creation and discovery — A new AI reranking processor for Search API is under development [18][28], and batch embeddings capability advanced across multiple modules to improve indexing performance [1][22][39][40][137][138]. The CKEditor integration gained functional tests [19][29][30][31] and translation fixes for tone of voice [6][26], while work on hiding status indicators is in progress [20][23][32].
  6. Advanced governance — Canvas conflict detection saw major progress with backend support for detecting conflicts during publishing [87], client-side prevention [88], conflict resolution via API [91], and notification infrastructure [89]. Access control improvements require earlier permission checks during auto-save publishing [59][73].
  7. Intelligent website improvements — No direct progress today.
  8. Multi-channel campaigns — No direct progress today.

Shipped

  1. AI CKEditor functional tests added — Quality assurance coverage was added to the 1.4.x release branch, strengthening reliability for the text editor integration [19][29][30][31].
  2. Anthropic Provider now supports prompt caching and PDF documents — Administrators can enable caching to reduce costs and accept PDF files as input, expanding document processing capabilities [37].
  3. OpenAI Provider delivers image-to-image generation — Users can now generate new images from existing images, opening new use cases for visual content creation [36].
  4. Context Control Center scheduler feature made optional — Scheduling is now a submodule rather than a required dependency, simplifying installation for sites that do not need it [132].
  5. Canvas service references standardized — Code quality improved by enforcing class constants instead of magic strings, making the codebase easier to navigate and maintain [82].

Ongoing

  1. AI Search reranking processor in development — This will allow any Search API backend to re-order results using AI models for improved precision [18][28].
  2. Batch embeddings under review for improved indexing performance — Multiple AI modules are implementing batch processing to speed up indexing and reduce costs when handling large content volumes [1][22][39][40][137][138].
  3. Canvas conflict detection and resolution advancing — Backend detection and client-side prevention of publishing conflicts are in progress, critical for multi-editor workflows [87][88][91].
  4. AI CKEditor improvements under review — Work is underway to warn users when no provider is installed, allow hiding status indicators, and fix configuration issues caused by uninstalling the module [3][20][23][24][25][32].
  5. Context Control Center beta3 release in preparation — Quality assurance, codebase review, and accessibility cleanup are underway ahead of the July 2026 target for beta3 [120][122][123].

AI (Artificial Intelligence)

Development this period focused on improving the CKEditor integration, consolidating configuration architecture, and expanding the Search API ecosystem. One significant piece of work merged: functional tests for the AI CKEditor module were added to the 1.4.x release branch, strengthening quality assurance for the text editor integration.

Several improvements to the CKEditor user experience are in progress. Work is underway to warn users when no AI provider is installed, preventing confusion when the feature fails silently. Another change will allow administrators to hide the "AI Writer: Idle" status indicator if they prefer a cleaner interface. A third effort addresses a bug where uninstalling the CKEditor module left behind broken toolbar references, causing configuration pages to fail.

On the architecture side, configuration for AI Content Suggestions plugins is being consolidated into a single settings object to simplify instantiation and reduce overhead. Work is also progressing to allow the JSON schema form element to function correctly inside off-canvas dialogs, expanding its usability beyond full-page forms.

Two new capabilities are being developed. A reranking processor for Search API is in progress, allowing any Search API backend to re-order results using AI models for improved precision. A batch embeddings feature is also underway to speed up indexing by processing multiple content chunks at once rather than sequentially.

Documentation and ecosystem visibility work continues, including a request to add the ai_budget_control module to the related projects list (now closed), and ongoing efforts to create a curated catalog of the growing number of companion modules, providers, and distributions.

How can I help on this project?

  • Review and prioritize the backlog of open configuration and user experience improvements to identify which issues most directly block adoption for new users.
  • Clarify the release roadmap and communicate the differences between minor versions (1.2, 1.3, 1.4) and the upcoming 2.0 to help developers choose the right version.

Contributors: Abhisek Mazumdar (abhisekmazumdar), AKHIL BABU (AkhilBabu) [1], Artem Dmitriiev (a.dmitriiev), Hrishikesh Dalal (hrishikesh-dalal), Marcus Johansson (Marcus_Johansson), Mukeysh, Ricardo Castañeda (cadence96), Thomas Werthmüller (weri), velmir_taky (root_emarketing)


Drupal AI Initiative

Activity this period was limited to planning work. Progress continued on sourcing real-world case studies from the upcoming Enterprise AI Summit in Rotterdam, scheduled for September. The initiative is working to identify new examples of organizations using Drupal with AI capabilities, which will help demonstrate the platform's viability for AI-enabled projects. Access to session submissions has been secured, and the focus is now on reviewing these submissions to identify suitable case studies and establishing contact with the organizations behind them. This outreach will support future marketing efforts, including webinars and published articles showcasing practical applications of Drupal in AI contexts.

No code changes or technical work were completed during this reporting period.

How can I help on this project?

  • Provide resources to accelerate case study curation and outreach once submissions are reviewed, ensuring timely engagement with potential showcase partners before the September summit.
  • Support executive-level introductions to organizations identified in the submissions to facilitate higher-quality conversations about their Drupal AI implementations.

AI Integration - ECA

Planning work advanced this period to expand automation capabilities. The module currently supports building automation workflows for 5 AI operations (chat, content moderation, speech conversion, and text embedding). A roadmap was opened to extend coverage to the remaining 13 operation types exposed by the underlying AI platform, enabling users to automate a wider range of AI tasks without custom development. This work is flagged as part of the path to a stable 1.0 release.

Within that scope, a specific task for translation automation was opened. Once delivered, this will allow workflows to trigger text translation between languages directly, supporting multilingual content strategies through visual workflow tools rather than code.

No code was merged this period; the activity reflects planning and issue structuring. Both issues remain unassigned, which is typical for early-stage modules organizing their development backlog.

How can I help on this project?

  • Assign developer capacity to the translation and broader operation-type expansion work to accelerate delivery of the 1.0 release.
  • Clarify business priority among the 13 planned operation types to sequence development effort where user demand is highest.

OpenAI Provider

The OpenAI Provider module achieved a significant capability expansion during this period. The image-to-image functionality was merged, enabling users to generate new images from existing images. This extends the module's AI capabilities beyond text-based interactions, opening new use cases for content creation and visual asset transformation.

The merge represents a substantial addition to the module's feature set, with over 300 lines of changes integrated. This positions the module to serve a broader range of business needs where visual content generation is required.

No critical issues or blockers emerged during this period. Development momentum remains steady as the module continues to expand its AI service offerings.

How can I help on this project?

  • Identify internal stakeholders who could pilot the new image generation capabilities to validate real-world use cases and gather feedback.
  • Assess whether additional resources are needed to accelerate testing and documentation now that the feature set is expanding.
Contributors: Marcus Johansson (Marcus_Johansson)

Anthropic Provider

The Anthropic Provider module advanced this period with the completion of work enabling prompt caching and PDF document support. The SDK constraint and method check update was merged, delivering two important capabilities: administrators can now enable prompt caching through a simple toggle in the settings interface, choosing between short- or long-duration cache lifetimes to optimize performance and reduce costs; and the system can now accept PDF documents as input, expanding the types of content the module can process.

These enhancements make the module more flexible and cost-efficient for organizations using AI capabilities in their Drupal sites. Prompt caching allows frequently-used content to be reused without repeated processing, while PDF support broadens the range of business documents that can be analyzed or summarized.

How can I help on this project?

  • Consider prioritizing testing resources to validate the new caching and PDF features in realistic business scenarios before wider deployment.
  • Evaluate whether the expanded capabilities align with strategic needs for document processing or content workflows that could benefit from AI integration.

Contributors: Carlos Ospina (camoa)


Fireworks AI

The Fireworks AI module saw maintenance activity during this period, with three commits focused on addressing requirements and implementing reranking functionality using standardized base components. These changes appear to improve the module's compliance with project standards and enhance its core capabilities.

With no open issues or merge requests flagged during this period, development appears to be proceeding in a straightforward maintenance mode. The module continues its early-stage development trajectory without any blocking concerns.

How can I help on this project?

  • Consider allocating resources for user testing or feedback collection to validate whether the module meets real-world business needs.
  • Assess whether the project would benefit from documentation investment to support adoption and reduce integration barriers.

Contributors: Marcus Johansson [3]


MCP Client

Activity this period was limited to automated maintenance. A merge request for automated project updates was opened, containing maintenance changes generated by the project's update automation. No substantial feature development, bug fixes, or user-facing improvements were delivered during this 24-hour window.

The module continues in its current state with no new releases or progress toward stability milestones in this period.

How can I help on this project?

Consider evaluating whether the project has adequate resourcing and clear priorities for moving toward a stable release. If the module is strategic, ensuring dedicated development capacity and a defined roadmap would help accelerate progress and delivery of business value.

Contributors: project update bot (Project-Update-Bot)


Gemini Provider

This module integrates Google's Gemini AI capabilities into Drupal. Development activity this period focused on expanding the module's efficiency when processing large volumes of content.

A new merge request was opened to enable batch embeddings processing. This enhancement will allow the system to convert multiple pieces of content into machine-readable formats in a single operation, rather than processing them one at a time. For sites handling significant content volumes or large-scale AI operations, this represents a meaningful performance improvement and cost reduction. The work is currently under review.

The module remains in active development as part of the broader AI Initiative, with this feature building on previous embedding capabilities.

How can I help on this project?

  • Ensure the team has sufficient review capacity to evaluate and merge the batch embeddings work, which could deliver immediate performance benefits.
  • Clarify priority and timeline expectations for advancing the module toward a stable release suitable for production use.

Contributors: Artem Dmitriiev (a.dmitriiev)


Milvus VDB Provider

Development continues on this module, which enables Drupal sites to use Milvus as a vector database provider for AI-driven search and content discovery capabilities.

A new merge request has been opened to add support for batching on indexing operations. This enhancement will allow the system to process multiple items at once when building search indexes, which should improve performance and reduce the time required to make content searchable. This is particularly valuable for sites with large content libraries that need efficient indexing.

The merge request is currently under review. No other issues or commits were recorded during this period.

How can I help on this project?

  • Ensure development resources are available to review and test the batching enhancement to accelerate its delivery.
  • Identify pilot use cases or content-heavy sites that could benefit from improved indexing performance to validate the work.

Contributors: Artem Dmitriiev (a.dmitriiev)


Model Context Protocol

The Model Context Protocol module is undergoing preparation for compatibility with Drupal 12. An automated Drupal 12 compatibility issue has been created to track the removal of deprecated functionality, with a corresponding merge request submitted containing compatibility updates. This work ensures the module will continue functioning when Drupal's next major version is released.

No commits were merged during this period. The compatibility work is being handled through automated tooling that identifies deprecated code patterns and proposes updates. This is standard housekeeping for modules transitioning between Drupal core versions.

How can I help on this project?

  • Allocate developer time to review and validate the automated compatibility fixes to accelerate Drupal 12 readiness.
  • Clarify the roadmap and timeline for achieving a stable release, which would help prioritize compatibility work.

Contributors: project update bot (Project-Update-Bot)


Drupal Canvas

Development activity this period focused on resolving issues with boolean properties in components, advancing conflict detection capabilities, and addressing translation workflow bugs.

Several boolean property bugs were identified and addressed. Work progressed on fixes for issues where boolean values reset when using patterns, auto-enable when other properties change, and are incorrectly cast when serialized as "0". A feature flag was implemented for content entity reference properties, allowing this experimental capability to remain hidden until fully stable.

The conflict detection and resolution system saw significant progress. Backend support was added for detecting conflicts during page publishing, returning HTTP 409 responses when conflicts are present. Client-side handling now prevents users from publishing conflicted changes while still allowing non-conflicted items to proceed. The review interface was enhanced to clearly mark conflicted items and exclude them from bulk selection. Work also advanced on resolving conflicts via API and loading visual previews of both auto-save and published versions.

Translation support received attention following reports of preview failures after language code updates and crashes when translating unpublished pages. Fixes address how Canvas handles URL prefixes that differ from language codes and revision-related conflicts triggered by translation job completion.

A large refactoring to enforce service references using class constants rather than strings was merged, improving code navigation and reducing magic strings across the codebase.

How can I help on this project?

  • Prioritize review bandwidth for conflict detection merge requests currently in progress, as this capability is critical for multi-editor workflows.
  • Consider allocating resources to complete the text-based entity comparison feature, which requires both backend and frontend work plus design input.

Contributors: **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Ahmad Khalil (ahmad-khalil-imagex), Ben Mullins (bnjmnm), Bálint Kléri (balintbrews), Christian López Espínola (penyaskito), Feliksas Mazeikis (f.mazeikis), Gábor Hojtsy (goba), Kunal Sachdev (kunal.sachdev), Matt Glaman (mglaman), Narendra Singh Rathore (NarendraR), Oleksandr Antonchyk (Anton4yk), Ravi Maniyar (ravi.maniyar.123), Wim Leers (wimleers)


Context Control Center (CCC)

The module continued progress toward its beta3 release, which is targeted for early July 2026. Sprint 12 planning closed on schedule, and Sprint 13 is now underway. Key work this period included simplifying dependency management and addressing technical quality ahead of the release candidate milestone.

The scheduler feature was moved to a submodule, making it an optional progressive enhancement rather than a required dependency. This reduces installation complexity and lets sites adopt scheduling only when needed.

An internal code review based on automated best practices checks was completed, generating a structured set of follow-up issues covering accessibility, documentation, test consistency, and caching behavior. These issues are now queued for resolution before the release candidate, with prioritization focused on items affecting the public API, configuration, or stable expectations.

Work is also in progress to improve the user interface for context listings, including merging scope and use case columns into a unified view and introducing cascading filters for easier navigation. Planning for beta3 quality assurance and the beta3 release itself are both underway, with community testing still open for feedback.

How can I help on this project?

Consider resourcing manual QA support for the beta3 testing script to accelerate the release timeline. If feasible, advocate within the community for broader testing participation to surface edge cases before RC1. Review the accessibility and documentation cleanup queue to identify any that may require design or policy decisions rather than just code fixes.

Contributors: Kristen Pol (kepol), Matt Glaman (mglaman) [1], Tamas Balog (tbalog)



Field Widget Actions

The Field Widget Actions module saw continued development this period, with progress on expanding functionality and a new bug report relating to multilingual capabilities.

A merge request was opened to add support for checkboxes and radio buttons using dynamic page updates. This enhancement will allow users to interact with these common form elements within field widgets, expanding the module's usefulness across a wider range of content editing scenarios.

A bug was reported concerning button label translation. Currently, button labels configured through form displays cannot be translated through the standard translation interface, limiting the module's usability for multilingual sites. This represents a functional gap for organizations operating in multiple languages, though it does not block core functionality for single-language deployments.

How can I help on this project?

  • Prioritize the translation bug fix if your organization requires multilingual content management capabilities.
  • Allocate resources to test the checkbox and radio button functionality once merged to validate it meets real-world editing workflows.

Contributors: Scott Euser (scotteuser)


AI powered Search Block

A new capability to select guardrail settings for the AI-powered search functionality is under development. The guardrail set selection feature has been prepared for review. This addition will give administrators more control over how the AI search behaves, ensuring that responses stay within defined boundaries and meet organizational standards. This is an important step toward making the search feature more configurable and suitable for enterprise deployment.

No issues were updated or commits merged during this period, indicating the work is in a review phase.

How can I help on this project?

  • Allocate technical review resources to evaluate the guardrail selection feature so it can move toward completion.
  • Clarify organizational requirements for AI guardrails to ensure the feature meets business and compliance needs.

Contributors: Abhisek Mazumdar (abhisekmazumdar)


Langfuse

A merge request was opened to apply automated project maintenance updates to the Langfuse module. This type of maintenance work helps keep the module aligned with current Drupal platform standards and ensures compatibility as the platform evolves. The changes are pending review but represent routine upkeep rather than new features or fixes.

No issues were updated, and no code was merged during this period. Activity remains limited as the module continues in its early phase of development.

How can I help on this project?

  • Consider allocating developer time to review and merge the pending maintenance updates to keep the project current.
  • Assess whether additional resources or contributors are needed to accelerate development and move the module toward a stable release.

Contributors: project update bot (Project-Update-Bot)


References

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

[3] Uninstalling ai_ckeditor leaves stale toolbar items in editor.editor.* configuration (ai, Issue)

[6] Tone of voice CKEditor Plugin does not use the translated version of the linked taxonomy (ai, Issue)

[11] Validation of unexisting fields on paragraphs actions (ai, Issue)

[18] Add an AI reranking processor for Search API (owned by the AI module) (ai, Issue)

[19] Add Functional Tests for AI CKEditor (ai, Issue)

[20] ai_ckeditor: Add option to show or hide the "AI Writer" status information (ai, Issue)

[22] Batch embeddings for improved indexing performance (ai, MR)

[23] ai-3586569: ai_ckeditor: Add option to show or hide the "AI Writer" status information (ai, MR)

[24] feat(ai_ckeditor): warn users when no AI provider is installed in the CKEditor settings tab (ai, MR)

[25] fix(ai_ckeditor): remove stale toolbar items on uninstall and warn on confirm page (ai, MR)

[26] fix: #3586573 Tone of voice CKEditor Plugin does not use the translated... (ai, MR)

[28] Issue #3586543: Add AI reranking processor for Search API. (ai, MR)

[29] Issue #3477173: Add functional tests for AI CKEditor (ai, MR)

[30] Add AICKeditor tests (Target 1.4.x) (ai, MR)

[31] Added Functional JavaScript Tests (ai, MR)

[32] fix: ai_ckeditor: Add option to show or hide the "AI Writer" status information (ai, MR)

[36] Resolve #3593019 "Add imagetoimage possibilities" (ai_provider_openai, MR)

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

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

[40] Support batch embeddings (gemini_provider, MR)

[45] Boolean field values resetting when using Patterns (canvas, Issue)

[46] Boolean prop values not retained correctly on SDC components with multiple boolean props (canvas, Issue)

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

[48] Cast transform treats serialized "0" as true for boolean props (canvas, Issue)

[50] Canvas Page Preview Fails After Language Code Update for Existing Translations (canvas, Issue)

[51] Canvas AI: UI/Functional update. Lock the canvas during a build and add a long-running AI-tasks UI element to the chat (canvas, Issue)

[57] Add translation data to code component data provider (canvas, Issue)

[59] Access check when publishing auto-save items needs be performed earlier (canvas, Issue)

[64] Component inputs order is database-backend-dependent: fix inputs key order assertions in tests and enforce it via PHPStan when possible (canvas, Issue)

[66] Translating unpublished page crashes canvas (canvas, Issue)

[73] Access check in ApiAutoSaveController::post() should be performed earlier (canvas, MR)

[74] fix(Internal HTTP API, Translation): #3591713 Fix Canvas page preview for translated pages when the URL prefix differs from the langcode (canvas, MR)

[79] chore(Data model): #3591727 Store each prop's translatability per component version so deleting an optional prop keeps config-defined component trees valid (canvas, MR)

[80] #3591738 add translation data to code component provider (canvas, MR)

[81] feat(Drush): #3585531 Add commands to list, audit, and generate Canvas components (canvas, MR)

[82] #3581133: Automate MR review using PHPCS: disallow `\Drupal::service('something')`, require `\Drupal::service(Something::class)` whenever possible, with automatic fixing (canvas, MR)

[85] Issue #3591726: Compare component inputs order-independently in tests and enforce it via PHPStan (canvas, MR)

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

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

[89] Draft: feat(Notifications, Conflict detection): #3591723 Add conflict notification... (canvas, MR)

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

[93] Move scheduler feature to submodule or progressive enhancement (ai_context, Issue)

[97] UX improvements on new context listing page (ai_context, Issue)

[99] Rename entity bundle and target entity scope plugins for better DX (ai_context, Issue)

[101] [Meta] Fix CCC issues based on AI Best Practices results (ai_context, Issue)

[102] Clean up CCC test and documentation consistency before rc1 (ai_context, Issue)

[103] Clean up CCC accessible interactive links and external links (ai_context, Issue)

[104] Clean up CCC tooltip, truncation, and icon-only content (ai_context, Issue)

[105] Clean up CCC JavaScript filter feedback (ai_context, Issue)

[106] Clean up CCC form and table accessibility cleanup (ai_context, Issue)

[107] Clean up CCC documentation and API consistency (ai_context, Issue)

[108] Clean up CCC configuration policy checks (ai_context, Issue)

[109] Clean up CCC cacheability and access metadata (ai_context, Issue)

[120] CCC beta3 QA (ai_context, Issue)

[122] Create CCC beta3 release (ai_context, Issue)

[123] CCC beta3 codebase review (pre-release) (ai_context, Issue)

[132] Issue #3577429: Make Scheduler an optional progressive feature. (ai_context, MR)

[133] Issue #3586274: Merge Use cases/Scope columns and add cascading scope filter (ai_context, MR)

[134] Issue #3586276: Rename entity bundle and target entity scope plugins for better DX (ai_context, MR)

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

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


Period: 26 June 2026 to 27 June 2026  |  Generated: 27 June 2026 05:00 GMT

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

Looking for older digests? Browse all digests here.