Daily Digest
Daily Digest – 20 June 2026
2026 Capabilities Progress
- Page generation — New interactive refinement capability [1] would enable users to iteratively improve AI-generated content through conversation before accepting it, directly supporting the goal of generating usable pages from descriptions. This feature is planned but not yet assigned to a developer.
- Context management — Significant progress on the Context Control Center with documentation clarifying supported APIs [34], subcontext features [41], and example context items [35] now available. A critical user experience issue was identified requiring clearer explanation of scope matching versus guaranteed inclusion [22], currently blocking the 1.0 stable release.
- Background agents — AI Agents module improved error handling to prevent tool execution failures from breaking the user interface [9], which is essential for reliable unattended operation. Chat action configuration is being simplified to reduce setup errors [6].
- Design system integration — No direct progress today.
- Content creation and discovery — AI Search gained long-running chunking support [2][5][45] to handle unlimited-length content indexing without timeouts, addressing a key constraint for large content libraries. Rich-text image description support [3][4] now enables AI to analyze both text and visual elements together during content moderation. Batch embeddings capability [7][8] will significantly improve processing performance for large content volumes.
- Advanced governance — No direct progress today.
- Intelligent website improvements — No direct progress today.
- Multi-channel campaigns — No direct progress today.
Shipped
- Context Control Center API documentation completed — Documentation distinguishing supported APIs from internal implementation details was merged [34], enabling third-party developers to safely extend the module without breaking on future updates.
- Context Control Center subcontext documentation updated — Help text and documentation clarifying benefits and trade-offs of the subcontext feature was merged [41], making configuration clearer for end users.
- Canvas test failure resolved — The fix for failing language selection tests was merged [14], stabilizing automated testing and reducing risk of regressions reaching users.
- Tool API skills generation completed — Work enabling developers to automatically generate new tools using AI coding assistants was closed [10], making it easier to expand module functionality and integrate tool creation into development workflows.
Ongoing
- AI module rich-text image description support in review — Merge requests enabling automated analysis of images embedded in content fields are under review [3][4], which will allow AI-powered content moderation to evaluate both text and visual elements together.
- AI Search long-running indexing under review — A merge request backporting extended indexing capability to the stable version is pending [45], which will allow organizations with large content libraries to process material without timing out.
- Gemini Provider batch embeddings in review — A merge request enabling simultaneous processing of multiple embedding requests is awaiting feedback [8], which will significantly reduce processing time for large content volumes.
- Context Control Center scope clarity blocking stable release — An issue clarifying when context is guaranteed versus eligible for AI agents was opened as a blocker [22], as beta testers found the current interface confusing.
- AI Agents error handling improvement proposed — A merge request to prevent tool execution errors from breaking the user interface is under review [9], which will improve system stability and user experience.
AI (Artificial Intelligence)
During the past 24 hours, the AI module team made progress on expanding content moderation and search capabilities. Two related features are advancing to help organizations handle richer content types and larger volumes of material.
Levente Besenyei (LeventeB) opened merge requests for rich-text image description support, enabling the system to automatically analyze images embedded in content fields like article bodies. This allows AI-powered content moderation to evaluate both text and visual elements together. When images cannot be fully processed—due to quantity limits or technical issues—the system flags content for human review rather than making an automated decision, maintaining quality control. The work is being prepared for both current and future versions of the module.
Scott Euser (scotteuser) submitted a merge request to support long running chunking in the current branch, which will allow AI Search to handle unlimited-length content items. This removes a previous constraint that limited processing to shorter content pieces.
A new issue was opened for interactive refinement capability, which would let users have a back-and-forth conversation with the AI to iteratively improve generated content before accepting it—similar to how users might refine outputs in consumer AI tools.
How can I help on this project?
- Prioritize review and testing of the image description and long-running content features currently in merge requests, which will expand the module's practical business applications.
- Allocate development capacity to the interactive refinement feature, which currently has no assigned contributor but would improve user experience significantly.
AI Integration - ECA
Activity this week focused on improving usability for teams configuring automated workflows with AI capabilities. A new task was opened to Simplify structured output configuration in the Chat action, assigned to Jürgen Haas (jurgenhaas). Currently, users must manually enter and validate complex configuration data as plain text, which is error-prone and difficult to review once saved. The proposed improvement would introduce a dedicated input interface that validates entries automatically and makes configurations easier to read and maintain.
This work is part of the Road to 1.0.0 initiative and will reduce setup time and configuration errors for business users building AI-powered automation. No code has been merged yet; the task is in planning.
How can I help on this project?
- Confirm prioritization of the 1.0.0 roadmap to ensure user experience improvements like configuration simplification are resourced appropriately.
- Facilitate access to real-world user feedback on current configuration workflows to validate proposed improvements.
Gemini Provider
The Gemini Provider module saw focused development activity this week on expanding its embedding capabilities. A merge request was opened by Artem Dmitriiev (a.dmitriiev) to enable Add support for batch embeddings, allowing the system to process multiple embedding requests simultaneously rather than one at a time. This capability matters for performance and efficiency: when analyzing or categorizing large volumes of content, batch processing significantly reduces processing time and resource usage compared to handling items individually.
This work builds on earlier infrastructure improvements and takes advantage of capabilities already available in Google's Gemini models. The enhancement is currently in review, with the Support batch embeddings merge request awaiting feedback before integration.
How can I help on this project?
- Assign a technical reviewer to evaluate the batch embeddings merge request to keep momentum on this performance improvement.
- Clarify strategic priorities for the module's roadmap to help contributors focus their efforts on the highest-value features.
AI Agents
Development work continued on the AI Agents module with a focus on improving system reliability. A solution has been proposed to address a problem where errors in the underlying tools cause the user interface to break, leaving users unable to complete their work. Jürgen Haas (jurgenhaas) has opened a merge request to handle tool execution exceptions, which would prevent system errors from cascading into user-facing failures. This work aims to improve the overall stability and user experience of the platform by ensuring that technical problems are handled gracefully rather than disrupting workflows.
The proposed solution is currently under review and has not yet been merged into the codebase.
How can I help on this project?
- Prioritize code review resources to evaluate and merge the error handling improvement, ensuring users receive a more stable experience quickly.
- Consider whether additional testing or quality assurance capacity is needed to validate exception handling across different usage scenarios.
Tool API
The Tool API project saw one issue closed during this period. Add skills for generating Tools was completed by Marcus Johansson (Marcus_Johansson). This work enables developers to automatically generate new tools using AI coding assistants, drawing on patterns from over 100 existing examples. The capability makes it easier to expand the module's functionality and allows teams using AI development workflows to integrate tool creation into their processes. This positions the module to scale more quickly as adoption grows.
No merge requests were completed or commits pushed during the reporting period, suggesting the issue may have been closed for administrative or planning reasons rather than through code delivery.
How can I help on this project?
- Confirm whether the skills generation work requires development resources or if closure indicates a change in approach that needs stakeholder alignment.
- Consider funding documentation or training materials to help teams adopt AI-assisted tool development workflows.
Drupal Canvas
Development work over the past 24 hours has focused on resolving test infrastructure issues and maintaining dependency health. The team is working to stabilize automated testing in the current release line, which ensures quality and reduces the risk of regressions reaching users.
Ben Mullins is addressing a failing test affecting language selection functionality. A fix has been proposed and is under review. Reliable automated testing is essential for confident releases and reduces the time needed for manual quality assurance.
Separately, an automated dependency update for several development tools has been submitted via update npm minor and patch. Keeping dependencies current reduces security exposure and ensures compatibility with the broader ecosystem. The project's automated dependency tracking flagged some configuration warnings in the Dependency Dashboard that may limit the effectiveness of this monitoring, though these do not affect end users.
How can I help on this project?
- Consider providing access tokens for dependency monitoring tools to improve automated security and compatibility tracking.
- Ensure the team has sufficient time allocation for test infrastructure maintenance alongside feature development.
Context Control Center (CCC)
The Context Control Center made significant progress toward its stable 1.0 release during the past day, with work focused on clarifying how the system works for end users and establishing what third-party developers can safely build upon.
Two documentation improvements were completed and merged. Rob Loach (robloach) delivered guidance distinguishing supported APIs from internal implementation details, giving outside developers clear boundaries for extending the module without breaking when future updates arrive. Matt Glaman (mglaman) added documentation explaining how the Tag scope feature works. Separately, Kristen Pol (kepol) merged work updating the subcontext feature's help text and documentation to clarify benefits and trade-offs for users configuring the system.
Beta user feedback surfaced confusion about when context is guaranteed versus merely eligible for AI agents. A new issue was opened to clarify scope matching versus guaranteed inclusion in the interface and docs, flagged as a blocker for the stable release. Two open merge requests are under review: one adding example context items for testing by Anikó Viola (violaniko), and another creating a Document Loader submodule to support PDF, text, and URL imports. Sprint 12 planning activity continued throughout the period.
How can I help on this project?
- Prioritize resources for the user experience issue on scope clarity, as beta testers found the current interface confusing and it blocks the stable release.
- Approve budget or staffing for a configuration video, which would reduce support load as users report setup difficulties.
AI Search
The AI Search project made progress on improving how large content sets are indexed for search. Scott Euser (scotteuser) opened work on backporting a long-running indexing capability to the current stable version without disrupting existing implementations. This feature, previously added to the next major version, allows the system to handle chunked content indexing over extended periods—important for organizations with large content libraries that need to be processed and made searchable without timing out or failing partway through.
A merge request has been submitted for the Attempt long running chunk indexing for 1.x branch without BC issue, demonstrating active development. The work is currently under review. This enhancement will allow users on the stable version to benefit from more reliable indexing of large content volumes without needing to upgrade to a new major version.
How can I help on this project?
- Ensure Scott Euser has adequate review resources to expedite feedback on the pending merge request and move it toward completion.
- Consider whether user documentation or change communication will be needed once this indexing improvement is released to current users.
References
[1] Add interactive refinement capability to Field Widget Actions
[2] Support long running chunking in 1.x branch for AI Search 1.x readiness
[3] Issue #3586478: "Add rich-text image description support to AI Automators"
[4] Issue #3586478: "Add rich-text image description support to AI Automators"
[5] Non-BC support for long running chunks
[6] Simplify structured output configuration in the Chat action
[7] Add support for batch embeddings
[9] Issue #3537123 by jurgenhaas: Exceptions in tool execute break the UI for the user
[10] Add skills for generating Tools
[14] Resolve "languageSelect.spec.ts Failing in 1.x"
[22] Clarify scope matching vs guaranteed inclusion in agent UI and docs
[34] Issue #3586241: Document Supported vs Internal APIs
[35] Issue #3586244: Add example context items from the Chicago Driesnote demo.
[41] Issue #3586251: Update subcontext feature help text and docs.
[45] #3584014: Resolve "Attempt long running chunk indexing for 1.x branch without BC"
Shipped
- CCC API documentation completed — The ai_context module merged documentation distinguishing supported public APIs (AiContextRequestFactory, selector pipeline events) from internal implementation details to guide contrib developers[34].
- CCC subcontext feature documentation updated — The ai_context module merged clarifications on subcontext benefits and tradeoffs to reduce user confusion[41].
- Canvas test stability addressed — The canvas module merged a fix for languageSelect.spec.ts flaky test failures affecting the 1.x branch[14].
- Canvas dependency updates merged — The canvas module updated npm minor and patch dependencies including @axe-core/playwright from 4.11.1 to 4.11.3[13].
Ongoing
- Long running chunking backport to AI 1.x — MR !1690 is open for review to backport unlimited length content item processing from 2.x to 1.x branch without breaking changes[2][5].
- Rich-text image description support — Dual merge requests targeting both 1.x and 2.x branches enable AI-powered analysis of embedded images in text fields for content moderation workflows[3][4].
- Batch embeddings for Gemini Provider — MR !37 adds support for processing multiple embeddings at once using the Gemini client's batchEmbedContents method[7][8].
- AI Search 1.x long running chunk indexing — MR !45 backports long-running chunk indexing functionality to 1.x using method existence testing for backward compatibility[44][45].
- CCC scope value customization hook not honored — MR !177 extends hook_ai_context_scope_values_alter() to work properly in scope value forms for downstream module customization[33][43].
AI (Artificial Intelligence)
Development activity this period focused on feature expansion and cross-version compatibility for AI Search integration. Scott Euser (scotteuser) opened work on Support long running chunking in 1.x branch for AI Search 1.x readiness, backporting functionality originally added to the 2.x branch to handle unlimited length content items. MR !1690 is now open for review, providing non-breaking-change support for processing items longer than 10 chunks in the 1.x branch, updating src/Base/AiVdbProviderClientBase.php and related components.
Edward Zwart (ezeedub) opened Add interactive refinement capability to Field Widget Actions to enable iterative AI content improvement through conversational prompts. This issue focuses on wiring automator plugins to the modal infrastructure being added in the companion field_widget_actions issue.
Levente Besenyei (LeventeB) continued work on rich-text image awareness with dual merge requests targeting both 1.x (MR !1628) and 2.x (MR !1679) branches for Add rich-text image description support to AI Automators, enabling AI-powered analysis of embedded images in text fields for content moderation workflows.
How can I help on this project?
- Review MR !1690 for long running chunking support to validate the non-BC backport approach
- Test MR !1628 and !1679 for rich-text image description functionality across both branch versions
- Pick up the unassigned interactive refinement capability issue to implement automator plugin integration
AI Integration - ECA
Activity was light over the past 24 hours, with no merges or commits pushed. The main development focus remains on Simplify structured output configuration in the Chat action, which was updated on 2026-06-20. This task, now assigned to Jürgen Haas (jurgenhaas), aims to replace the plain text JSON schema field in the Chat action's configuration form with the AI module's dedicated '#type' => 'ai_json_schema' form element. The current implementation stores structured-output schemas as raw JSON strings that are decoded at runtime (line 115 of src/Plugin/Action/Chat.php), making configuration error-prone and difficult to review. The issue is tagged for the AI Initiative Sprint and the Road to 1.0.0 milestone, indicating it is a priority for stabilization work.
No blocking issues were reported during this period.
How can I help on this project?
- Pick up Simplify structured output configuration in the Chat action alongside Jürgen Haas (jurgenhaas) by investigating how the
AiJsonSchemaform element works and drafting a patch that refactors the Chat action's configuration. - Test the current Chat action implementation with various JSON schemas to document edge cases and validation gaps that the new form element should address.
Gemini Provider
The Gemini Provider module saw progress on batch embeddings support during this period. Artem Dmitriiev (a.dmitriiev) opened Support batch embeddings (MR !37), which adds support for processing multiple embeddings at once using the Gemini client's batchEmbedContents method. This work follows up on earlier AI module development around EmbeddingsInput handling. The merge request includes 329 lines of changes and addresses Add support for batch embeddings, though no commits were pushed during the reporting period and the MR remains open for review.
How can I help on this project?
- Review and test Support batch embeddings to help move this feature toward completion.
- Check the module's issue queue for unassigned bugs or feature requests that need work.
AI Agents
The AI Agents module saw one new merge request opened in the past 24 hours. Jürgen Haas (jurgenhaas) submitted Issue #3537123: Exceptions in tool execute break the UI for the user, which addresses problems where exceptions thrown during tool execution cause UI breakage for users. The MR includes 296 lines of changes and is currently awaiting review.
No commits were merged and no issues had status changes during this reporting period. The module appears to have one active area requiring attention around exception handling in tool execution workflows.
How can I help on this project?
- Review the open merge request for exception handling in tool execution to help move it toward merge
- Test the exception handling changes locally to verify UI behavior remains stable when tools encounter errors
Tool API
The Tool API project saw one issue close during the reporting period. The issue Add skills for generating Tools, opened by Marcus Johansson (Marcus_Johansson), was closed on 2026-06-20. This issue proposed creating generic skills for generating Drupal tools using AI coding agents, based on successful experiments in the ai_agents_experimental_collection project. The proposal included creating Drush templates and generation commands to enable any coding agent (such as Claude Code or Codex) to create tools through frameworks like ai_best_practices or Vercel Skills.
No merge requests were merged and no commits were pushed during this period. The closure of the issue suggests either the work was completed outside the tracked window or the proposal was resolved through other means.
How can I help on this project?
Review the recent closure of Add skills for generating Tools to understand whether implementation occurred or if follow-up work is needed. Check the project's issue queue for other open issues that may need attention or testing.
Drupal Canvas
The Drupal Canvas project saw diagnostic activity over the past 24 hours focused on test stability issues. Ben Mullins (bnjmnm) has been assigned to investigate languageSelect.spec.ts Failing in 1.x, a test failure affecting the 1.x branch. The issue involves intermittent timeouts where a menu element with [data-state="open"][role="menu"] fails to become visible within the expected 10-second window. A second merge request (MR !1269) is currently open to address these flaky test conditions, following an earlier partial fix.
On the dependency management front, Renovate bot activity continues with fix(deps): update npm minor and patch (MR !1238) proposing updates to dependencies including @axe-core/playwright from 4.11.1 to 4.11.3. The project's Dependency Dashboard reports configuration warnings related to missing GitHub token configuration, which is preventing proper rate limiting and release notes retrieval.
How can I help on this project?
Context Control Center (CCC)
The project merged two key documentation improvements in the last 24 hours. Rob Loach (robloach) completed Document supported vs internal CCC APIs via MR !186, establishing clear boundaries between public APIs (AiContextRequestFactory, selector pipeline events) and internal implementation details to guide contrib developers. Matt Glaman committed documentation for the Tag scope plugin, closing Issue #3586270. Kristen Pol (kepol) merged MR !169 to Update subcontext feature description and docs, clarifying benefits and tradeoffs of the subcontext feature.
Active development continues on several fronts. Anikó Viola (violaniko) has MR !185 open to Provide test context items for testing CCC, adding example content from the Chicago Driesnote demo. Ahmad Khader (Ahmad-Khader) opened MR !177 addressing hook_ai_context_scope_values_alter() is not honored in scope value forms, extending scope value customization for downstream modules. Abhisek Mazumdar (abhisekmazumdar) is working on performance in MR !166 for conditional subcontext calls and MR !174 to batch N+1 queries in AiContextUsageTracker.
Blocking stable release: Review and update CCC permissions remains assigned to kepol, and Clarify scope matching vs guaranteed inclusion in agent UI and docs needs UX review to address beta tester confusion about context item eligibility versus guaranteed inclusion.
How can I help on this project?
- Review MR !185 for test context items and provide feedback on example content quality.
- Pick up Add #[RunTestsInSeparateProcesses] attribute to all kernel test classes (35 of 39 classes need the attribute for Drupal 12 compatibility).
- Help define UX improvements for scope matching clarification to distinguish eligibility from guaranteed inclusion.
AI Search
Scott Euser (scotteuser) opened a merge request to backport long-running chunk indexing functionality to the 1.x branch without breaking backward compatibility. The feature was previously implemented for 2.x in #3487487 but included interface changes. The new #3584014: Resolve "Attempt long running chunk indexing for 1.x branch without BC" takes a different approach by testing if methods exist and gracefully falling back when they don't, avoiding BC breaks while maintaining test coverage. The MR spans 1634 diff lines and is currently in needs review status.
No commits were merged during the reporting period, with the module awaiting review on this substantial MR.
How can I help on this project?
- Review the 1.x long-running chunk indexing MR, focusing on the backward compatibility approach and test coverage adequacy.
- Test the changes locally against existing 1.x installations to verify graceful fallback behavior works as expected.
References
[2] Support long running chunking in 1.x branch for AI Search 1.x readiness
[3] Issue #3586478: "Add rich-text image description support to AI Automators"
[4] Issue #3586478: "Add rich-text image description support to AI Automators"
[5] Non-BC support for long running chunks
[7] Add support for batch embeddings
[13] fix(deps): update npm minor and patch
[14] Resolve "languageSelect.spec.ts Failing in 1.x"
[33] hook_ai_context_scope_values_alter() is not honored in scope value forms
[34] Issue #3586241: Document Supported vs Internal APIs
[41] Issue #3586251: Update subcontext feature help text and docs.
[43] Issue #3586246: hook_ai_context_scope_values_alter() is not honored in scope value forms
[44] Attempt long running chunk indexing for 1.x branch without BC
[45] #3584014: Resolve "Attempt long running chunk indexing for 1.x branch without BC"