Daily Digest

Daily Digest – 9 June 2026

2026 Capabilities Progress

  1. Page generation — Canvas AI work continues on preview rendering and exposing component properties to agents [85][88][120], while the team fixed component update issues affecting sites with disabled themes [84][118]. Progress remains on track toward using AI to build pages from design system components.
  2. Context management — The Context Control Center merged a storage improvement enabling cleaner markdown editing [140][152], and two UI redesigns are in progress to make context items easier to scan and review [139][144][151][154]. The module is approaching its release candidate milestone.
  3. Background agents — Significant architectural work is underway to move agent infrastructure into AI Core v2, including structured input/output, pluggable runners with permission controls, and integration with Symfony Messenger for asynchronous execution [25][26][27][28][29][30][31][32][33][34][35][36][37]. This foundational work will enable agents to operate independently on schedules and triggers.
  4. Design system integration — Canvas completed symmetric translation for content entities, allowing components to maintain consistent structure across languages while enabling translation of appropriate fields [98][103][129][133]. Image field improvements [92][127] and autocomplete widget enhancements [97][128] support richer component authoring workflows.
  5. Content creation and discovery — Work advanced on extending AI Search to support non-content entities with proper access controls [162][164], and the chatbot will soon display images and videos within its viewport [2]. Rich-text image description support for automators is in development [21][49], enabling AI to consider visual context during content analysis.
  6. Advanced governance — Topic restriction guardrails now support semantic matching modes [10], improving content control capabilities. Observability improvements include proper OpenTelemetry semantic conventions [4][39] and fixes for streaming token usage tracking [5][40], strengthening audit capabilities for AI operations.
  7. Intelligent website improvements — No direct progress today, though the foundation for learning from usage continues with observability enhancements [4][5][39][40] and the planned AI Cost & Usage module [51] that would provide performance visibility for data-driven optimization.
  8. Multi-channel campaigns — No direct progress today, though Canvas translation capabilities [98][101][103][129] establish infrastructure for managing content variants across channels in multiple languages.

Shipped

  1. Field widget action dispatch consolidated — Code for handling field widget actions was unified into a shared base class, simplifying future development and reducing maintenance burden [13][44][45][47].
  2. Content suggestions plugin refactored — Logic moved from external service into plugin classes, improving code organization and reducing unnecessary service dependencies [15][46].
  3. Postgres vector database configuration improved — Database server setup now respects configured database settings, making deployments more predictable [68].
  4. Context item text field storage simplified — Text fields switched to improved storage format enabling cleaner markdown editing integration before release candidate [140][152].
  5. Session privacy enhanced in Langfuse module — Raw session identifiers now hashed before transmission, reducing privacy exposure when tracking user interactions [171].

Ongoing

  1. Agent architecture migration to AI module core — Comprehensive planning underway to integrate agent capabilities into AI module version 2.0, including structured input/output, pluggable runners, permission controls, and asynchronous execution [25][26][27][28][29][30][31][32][33][34][35][36][37].
  2. Chatbot media display improvements — Work in progress to constrain images and videos within chatbot viewport and add rich-text image description support to automations [2][21][49].
  3. Canvas translation capabilities advancing — Symmetric translation workflows for content entities under development, with TMGMT integration and translation UI refinements in progress [98][99][100][101][103][104][105][106].
  4. Tool API error handling improvements — Fixes under review to prevent command-line failures from being masked and eliminate crashes when tools fail early [5][80][81][82][83].
  5. Context Control Center interface redesign — New listing page and detail view layouts being built to improve scannability and surface important information more effectively [139][144][151][154].

AI (Artificial Intelligence)

The AI module saw focused development activity over the past day, with work completed on internal quality improvements and new progress toward standardising evaluation frameworks and extending agent capabilities.

Two internal refactoring efforts were completed and merged. The team simplified how field widget actions are handled, consolidating duplicated code into a shared base class so new widget plugins are easier to build and maintain. A second change cleaned up the content suggestions feature, moving logic from an external service into the plugin classes themselves to improve readability and reduce unnecessary service calls.

New work began on extending the chatbot user experience. One effort will constrain images and videos to display properly inside the chatbot viewport, preventing media from overflowing into the surrounding page. A separate proposal aims to add rich-text image description support, allowing automations like summaries or quality checks to consider visual context embedded in formatted text fields.

The team also opened a comprehensive planning track to move the agent architecture from a separate module into the AI module core for version 2.0. This includes structured input and output definitions, pluggable agent runners (including integration with Symfony AI), permission controls for autonomous agents, and asynchronous execution via message queues. Work is assigned and underway.

How can I help on this project?

  • Prioritise decisions on the agent architecture migration plan to ensure contributors can proceed with structured input, output, and runner abstractions without waiting on open design questions.
  • Allocate resource for documentation updates following the field widget refactor so new contributors can adopt the simplified patterns.

View project on GitLab: ai

Drupal AI Initiative

The team completed a significant milestone in the past 24 hours, closing five interactive demonstration environments. These live demos — covering CKEditor Integration, Content Categorization, Compliance, AI Search, Advanced Drupal Skills, and Simplified Text — allow prospective users to experience AI-powered features hands-on. These tools address common business needs: reducing content creation time, improving search relevance, maintaining brand and accessibility compliance, and automating categorization tasks.

Planning discussions continued around integrating command-line tools into Drupal Core and exploring a new AI Cost & Usage module, which would give site owners visibility into AI spending and usage patterns — helping organizations manage budgets and understand which features drive the most value. The team is also considering an experiment to use AI to review code submissions, which could reduce review time as AI-generated code becomes more common.

How can I help on this project?

  • Prioritize a decision on the command-line integration approach outlined in the CLI entry point discussion to unblock developer tooling work.
  • Approve resources to build the Cost & Usage dashboard, which would give customers budget transparency and provide the initiative with valuable adoption data.

View project on GitLab: ai_initiative

OpenAI Provider

Activity over the past 24 hours was limited to routine maintenance. The Project Update Bot opened a merge request for automated project updates, which involves minor administrative changes to keep the project current with broader platform requirements. No code changes were committed during this period.

This represents normal housekeeping for an active module. There were no user-facing changes, bug fixes, or feature additions delivered in this window. The module remains in a steady state with no new issues or concerns raised.

How can I help on this project?

Given the quiet period, consider reviewing the project's roadmap to ensure it aligns with organizational priorities. If integration with OpenAI services is strategically important, confirm that maintainer resources are adequate for upcoming feature development or support needs.

View project on GitLab: ai_provider_openai

Anthropic Provider

The Anthropic Provider module saw minimal activity during this period. An automated maintenance process opened a merge request for project update fixes, which contains minor housekeeping changes to keep the module aligned with current standards. This work is part of routine maintenance rather than new feature development.

No issues were updated, and no code was merged to the main codebase during the reporting window. The module appears to be in a steady state with no active development momentum or community engagement visible in this 24-hour snapshot.

How can I help on this project?

  • Review whether this module remains strategically important and allocate dedicated development resources if continued advancement is needed.
  • Consider engaging with the community or existing users to identify priority features or improvements that would drive adoption.

View project on GitLab: ai_provider_anthropic

amazee.ai Private AI Provider

Activity this period focused on preparing the module for compatibility with the next major version of Drupal. An automated compatibility issue was opened to track necessary updates, and a corresponding merge request containing proposed fixes has been submitted for review. This proactive work ensures the module will continue to function when organizations upgrade their systems in the future, avoiding potential disruption to AI services that depend on this provider.

The compatibility work is being handled through automated tooling, which identifies deprecated code patterns and suggests modern alternatives. While the changes are machine-generated, they still require human review before being incorporated to ensure they don't introduce unintended behavior.

No commits were merged during this period, indicating the compatibility updates are still under evaluation.

How can I help on this project?

  • Assign a developer to review and validate the automated compatibility fixes to accelerate Drupal 12 readiness.
  • Clarify the timeline and priority for Drupal 12 support to help maintainers plan testing and release activities.

View project on GitLab: ai_provider_amazeeio

AWS Bedrock Provider

Activity on this module over the past 24 hours has been limited to routine maintenance. The Project Update Bot opened a merge request for automated project updates, which applies standardized code fixes to keep the module aligned with Drupal project conventions. This type of automated maintenance helps ensure consistency and reduces technical debt as the project evolves.

No user-facing features, bug fixes, or strategic changes were delivered during this period. The module continues in its current state with no new issues reported or resolved.

How can I help on this project?

  • Assess whether the module requires dedicated development resources to accelerate feature delivery or address user needs.
  • Clarify strategic priorities for integration with cloud-based AI services to guide future roadmap planning.

View project on GitLab: ai_provider_aws_bedrock

Google Vertex Provider

Activity over the past 24 hours has been limited to automated maintenance. A merge request titled Automated Project Update Bot fixes was opened by the Project Update Bot to apply routine project updates. No commits were merged, and no open issues received updates during this period.

The module continues in its current development phase with no new user-facing features or bug fixes delivered in this window. This level of activity is typical for a specialized integration module between reporting cycles.

How can I help on this project?

  • Review and approve the pending automated maintenance update to keep the project aligned with current standards.
  • Assess whether dedicated developer time is needed to accelerate feature development or address any backlog of community requests.

View project on GitLab: ai_provider_google_vertex

Huggingface Provider

The Huggingface Provider module saw minimal activity in the past 24 hours. An automated maintenance request was opened to apply routine project updates, ensuring the module stays aligned with broader platform standards and dependencies. No issues were updated, and no code was merged during this period.

This represents steady-state maintenance rather than feature development or bug resolution. The module appears to be in a quiet phase with no urgent work items or community-reported problems requiring immediate attention.

How can I help on this project?

  • Consider whether this module aligns with strategic priorities for AI integration—if yes, allocate dedicated development resources to advance new capabilities or documentation.
  • Engage with potential users or partners to identify unmet needs or use cases that could guide the roadmap.

View project on GitLab: ai_provider_huggingface

Microsoft Azure AI

The Microsoft Azure AI module saw minimal activity in the past 24 hours. An automated maintenance task was initiated to keep the project aligned with Drupal development standards. The Automated Project Update Bot fixes merge request was opened by Project-Update-Bot to apply routine updates from the Drupal project infrastructure.

No user-facing features were delivered, and no issues were updated during this period. The project continues to operate in maintenance mode with automated tooling ensuring consistency with broader Drupal ecosystem requirements.

How can I help on this project?

  • Review whether this module aligns with current strategic priorities for AI integration, and clarify whether active development or maintenance-only mode is appropriate going forward.
  • Ensure adequate developer capacity is allocated if expanded Azure AI capabilities are needed to support business objectives.

View project on GitLab: ai_provider_azure

Postgres VDB Provider

The Postgres VDB Provider project made steady progress over the past 24 hours, with work focused on improving configuration flexibility and database setup workflows.

One improvement was completed and integrated: Use configured database for Search API server setup, delivered by Artem Dmitriiev (a.dmitriiev). This enhancement ensures that the module respects database configurations when setting up search servers, making deployment and configuration more predictable for administrators.

A second piece of work is currently in review: Update file PostgresConfigForm.php, contributed by Enrique Worwa (eworwa). This change will enable configuration overrides, giving site operators more flexibility to customize settings without modifying core configuration files—particularly valuable for teams managing multiple environments or deployments.

Both efforts support the module's maturation by addressing real-world deployment needs and reducing friction for teams integrating vector database capabilities into their Drupal installations.

How can I help on this project?

  • Allocate reviewer time to assess the open configuration override work, ensuring it can be validated and merged promptly.
  • Consider funding documentation resources to help teams understand deployment patterns as new configuration options become available.

View project on GitLab: ai_vdb_provider_postgres

AI Image Alt Text

Activity over the past 24 hours was limited to maintenance work. The Project Update Bot (Project-Update-Bot) opened Automated Project Update Bot fixes, a routine update containing automated maintenance changes. This type of work keeps the module's infrastructure current but does not directly deliver new features or fix user-facing issues.

No user-facing improvements, bug fixes, or new capabilities were delivered during this period. The module remains in active maintenance with automated systems ensuring basic upkeep continues.

How can I help on this project?

  • Review current project priorities and ensure development resources are allocated to high-impact features or bug fixes that advance the module's strategic goals.
  • Verify that stakeholder needs are documented and communicated to the development team to guide meaningful progress beyond routine maintenance.

View project on GitLab: ai_image_alt_text

AI Agents

The AI Agents module saw active quality improvement work over the past 24 hours, with six bug reports submitted addressing issues that affect user experience and system reliability. The focus was on identifying and documenting problems rather than merging fixes.

Key areas of attention include data handling errors that prevent users from properly configuring agent tools, interface inconsistencies in the administration menu, and system warnings that occur during normal operation. Contributors identified issues with line ending normalization in property restrictions, error handling when processing tool results, and field display configuration assumptions. Additional polish items were flagged, including a spelling correction in help text and menu label consistency.

Several issues have proposed solutions awaiting review. Contributors include Sven Decabooter (svendecabooter), Marcus Johansson (Marcus_Johansson), Michael Anello (ultimike), Angelo Keirsebilck (angelokeirsebilck), and Prabhavathi Vanipenta (prabha1997). No code was merged during this period, indicating solutions are still under evaluation.

How can I help on this project?

  • Allocate reviewer capacity to assess the pending merge requests, which are awaiting technical review before these fixes can be deployed.
  • Clarify alignment with the parent AI module's roadmap regarding menu organization to guide resolution of administrative interface issues.

View project on GitLab: ai_agents

Tool API

The Tool API project saw focused activity on improving error handling and planning for better cross-system integration.

The team identified and is fixing a problem where failures are masked when tools are run from the command line. Currently, when a tool encounters an error, users see a confusing technical exception instead of the actual failure message explaining what went wrong. Matt Glaman opened tool:run masks the failure message: getOutputValues() throws on unset outputs of a failed tool and submitted a corresponding merge request to resolve it. This fix will make troubleshooting faster and reduce support burden.

A related issue was discovered in the AI connector component: tool_ai_connector: ToolPluginBase::getReadableOutput() fatals when wrapped tool has no result object. Sven Decabooter submitted a fix that prevents crashes when tools fail early or encounter access restrictions. Both improvements make the system more resilient under real-world conditions.

Looking ahead, Matt Glaman proposed making Tool's declarations introspectable over the CLI, which would allow different systems to discover and understand available tools without custom integration code — laying groundwork for broader ecosystem compatibility.

How can I help on this project?

  • Prioritize review and merge of the two open error-handling fixes to reduce user friction and support costs.
  • Help scope and prioritize the introspection proposal based on which integration partners would benefit most from standardized tool discovery.

View project on GitLab: tool

Drupal Canvas

The team made significant progress on translation capabilities and data integrity. A major milestone was delivered enabling symmetric translation workflows for content entities, where translators can now override only translatable text fields while non-translatable settings remain synchronized with the source language. This reduces translation effort and prevents configuration drift across language versions.

Several technical fixes were merged to improve reliability. The image field now exposes a simpler interface for developers connecting visual content to components. Issues with dropdown menus referencing shared schemas were resolved, restoring functionality after a recent dependency update. An autocomplete widget enhancement was completed, supporting richer entity selection workflows.

Work continues on AI-assisted page building, with active development on preview rendering issues and exposing additional component capabilities to the AI agent. Translation UI features are being refined based on design specifications, with fixes for language selection indicators and default language enforcement when creating new pages.

A critical issue affecting component updates and configuration validation on sites with disabled themes is under review, with a proposed fix awaiting testing. Progress on symmetric translation for configuration-based templates is advancing, enabling professional translation workflows via TMGMT integration.

How can I help on this project?

  • Review and prioritize the critical component update issue affecting sites with disabled themes, which could block production deployments if left unresolved.
  • Ensure testing resources are available for the TMGMT translation integration work, which may require specialized multilingual site configuration.

View project on GitLab: canvas

Context Control Center (CCC)

The Context Control Center module made significant progress toward its upcoming release candidate with one major technical improvement completed and several design enhancements in active development.

The team successfully merged a change to how context item text fields are stored, enabling cleaner integration with the module's markdown editing experience. This storage-level change was prioritized before the release candidate to avoid more complex migration work later. Kristen Pol (kepol) completed this work through MR !172.

Two substantial user interface improvements are progressing. Matt Glaman (mglaman) is refining the context listing page to make it easier to scan, with clearer token usage indicators and streamlined scope information. Eric Homanchuk (erichomanchuk) is building a redesigned view layout for individual context items that surfaces important details more effectively.

The team is also simplifying the module's architecture. Glaman is removing an unnecessary complexity (bundle structure) from context items, building on recent improvements to a dependency module that now makes this possible.

Testing continues on model performance and cost optimization for the Chicago demonstration repository.

How can I help on this project?

  • Prioritize user testing resources for the new listing and detail page designs once they're ready for review, ensuring they meet stakeholder expectations before the release candidate.
  • Clarify the product scope for the release candidate to help the team decide which performance optimization work is essential now versus deferrable to future releases.

View project on GitLab: ai_context

AI Dashboard

The AI Dashboard project made significant progress on improving documentation and user experience during this period. The team delivered a new ecosystem documentation page that provides a browsable catalogue of all modules in the AI ecosystem, including descriptions and installation statistics. This will help users discover and evaluate available AI tools more easily. Work was led by Rob Loach (robloach) with Artem Dmitriiev (a.dmitriiev) assigned to review, and the initial version was merged and deployed. Further enhancements to add categorisation to this documentation are now underway.

Separately, the project is addressing compatibility with the upcoming Drupal 12 release through automated updates. An automated compatibility fix has been submitted and is awaiting review. The project also added a content classification recipe to its recommended components, expanding the range of pre-configured solutions available to users.

How can I help on this project?

  • Review and approve the ecosystem categorisation enhancement currently in progress to help users navigate the AI module catalogue more effectively.
  • Prioritise testing and approval of Drupal 12 compatibility updates to ensure the module remains supported when the new platform version is released.

View project on GitLab: ai_dashboard

AI Drush Agents

The AI Drush Agents module saw minimal development activity over the past 24 hours. An automated maintenance process opened a merge request for project update fixes, which represents routine housekeeping to keep the module's infrastructure current. No user-facing features were delivered, and no issues were updated during this period.

This level of activity is normal for an early-stage module and does not indicate any obstacles to progress. The project continues in a maintenance state with no critical issues blocking development.

How can I help on this project?

  • Consider whether this module aligns with current strategic priorities, and if so, allocate dedicated development resources to advance feature work.
  • Identify and engage potential pilot users who could provide feedback to guide the module's roadmap and validate its business value.

View project on GitLab: ai_drush_agents

AI translate

The AI translate module saw automated compatibility work initiated this period. An automated system has begun preparing the module for Drupal 12 by identifying and addressing deprecated code that will no longer function in the next major platform version. A merge request containing compatibility fixes has been opened and is awaiting review, covering 370 lines of changes across the codebase.

This work is part of routine platform maintenance. Drupal 12 compatibility ensures the module will continue operating when sites upgrade to the newest platform version, protecting the translation functionality that users rely on. The changes are being handled through automated tooling, which helps maintain currency with platform standards but will require human review before being incorporated into the module.

How can I help on this project?

  • Allocate developer time to review and merge the pending Drupal 12 compatibility updates, ensuring the module remains viable when the platform upgrades.
  • Consider whether translation capabilities are strategically important enough to warrant dedicated maintainer resources rather than relying solely on automated updates.

View project on GitLab: ai_translate

Groq Provider

The Groq Provider module saw minimal activity during this period. An automated maintenance update was opened to keep project dependencies current, generated by the Project Update Bot. This type of routine maintenance helps ensure the module remains compatible with the broader Drupal ecosystem.

No functional changes, bug fixes, or feature development occurred in the last 24 hours. There were no issue updates, merged changes, or direct commits to the codebase.

How can I help on this project?

  • Review whether the project has sufficient maintainer capacity to address incoming issues and move toward a stable release.
  • Consider whether additional resources or promotion would help expand the contributor base for this integration.

View project on GitLab: ai_provider_groq

LiteLLM AI Provider

The LiteLLM AI Provider module saw minimal activity during this period. An automated maintenance process opened a merge request for project update fixes, created by the Project Update Bot. This represents routine housekeeping to keep the module's configuration and dependencies aligned with current project standards.

No issues were updated, and no code was merged or committed during the reporting window. The module appears to be in a stable maintenance phase with no active development or user-reported concerns requiring immediate attention.

How can I help on this project?

  • Assess whether the module requires dedicated development resources to advance new features or prepare for a stable release.
  • Review the project roadmap to confirm it aligns with organizational AI integration priorities and timelines.

View project on GitLab: ai_provider_litellm

AI powered Search Block

Activity over the past 24 hours has been limited to automated maintenance. A merge request titled Automated Project Update Bot fixes was opened by Project-Update-Bot to keep the module's dependencies and configuration current. This type of routine maintenance ensures the module remains compatible with the broader Drupal ecosystem and reduces technical debt. No new features were delivered, and no community-reported issues were addressed during this period.

The module continues in a relatively quiet phase with minimal contributor activity. While automated updates are valuable for sustainability, the lack of human-driven development or issue resolution suggests limited momentum on feature development or user support.

How can I help on this project?

  • Consider whether this module aligns with strategic priorities and warrants dedicated developer time or community engagement resources.
  • If the module serves important use cases, advocate for it within the Drupal community to attract contributors and maintainers.

View project on GitLab: ai_search_block

Langfuse

The Langfuse module made progress on privacy and data handling capabilities during this period. Ivo Van Geertruyen (mr.baileys) completed work to improve how user session information is handled, ensuring that raw session identifiers are protected through hashing before being transmitted. This enhancement was merged and is now available to users, reducing privacy exposure when the module tracks user interactions.

Additionally, work is underway on storing trace data, which will enable the module to retain records of system activity for analysis and troubleshooting. This functionality is currently in development and under review.

These improvements support the module's core goal of providing observable, privacy-conscious tracking capabilities for Drupal sites using Langfuse services.

How can I help on this project?

  • Review and approve the pending trace storage functionality to accelerate its availability to users
  • Ensure the contributor has access to any testing or staging environments needed to validate privacy enhancements
  • Consider documenting the business case for these features to support adoption among potential users

View project on GitLab: langfuse

AI Translate Plus

Activity over the past 24 hours has been minimal, with automated maintenance work comprising the only update. The Project Update Bot (Project-Update-Bot) opened a merge request for automated project fixes, containing 13 lines of changes to keep the project aligned with current standards. This type of routine maintenance helps ensure the module remains compatible with the broader Drupal ecosystem.

No user-facing features, bug fixes, or community-reported issues were addressed during this period. The project saw no commits merged and no issue tracker activity, indicating a quiet day with no significant progress on functionality or outstanding problems.

How can I help on this project?

  • Assess whether the project has sufficient developer capacity to move forward with new features or address user needs, as recent activity has been limited to automated maintenance.
  • Consider whether the project roadmap aligns with organizational priorities, and if advocacy or promotion is needed to attract contributors or users.

View project on GitLab: ai_translate_plus

AI Related Content

The AI Related Content module saw automated maintenance activity during this period focused on ensuring future compatibility with Drupal 12. An automated process identified necessary updates to prepare the module for the next major platform version and opened Automated Drupal 12 compatibility fixes for ai_related_content 1.0.x-dev. A corresponding merge request was created containing the proposed changes.

This work represents proactive technical debt management. By addressing compatibility requirements early, the module is being positioned to continue functioning when the Drupal platform evolves. This type of preventative maintenance reduces future disruption and ensures users can upgrade their systems without losing functionality.

No code changes were finalized during this period. The compatibility updates are awaiting review before being incorporated into the module.

How can I help on this project?

  • Allocate developer time to review and approve the pending compatibility updates, ensuring the module stays current with platform requirements.
  • Consider establishing a policy or resource allocation for ongoing automated maintenance review to prevent accumulation of technical debt.

View project on GitLab: ai_related_content

AI Content Classification

The AI Content Classification module saw minimal activity during this period, with a single configuration update committed by Artem Dmitriiev. This represents routine maintenance work rather than feature development or issue resolution.

No issues were updated, and no merge requests were completed during the reporting period. The module appears to be in a quiet phase with limited active development or community engagement at present.

How can I help on this project?

  • Review the project roadmap with the maintainer to confirm whether additional development resources are needed to advance strategic goals.
  • Consider promoting the module to relevant user communities to increase adoption and gather feedback for future improvements.

View project on GitLab: ai_recipe_content_classification

References

[2] Render images and videos inside the chatbot viewport (ai, Issue)

[4] [Layer 2] Align ai_observability OTel emission to GenAI semantic conventions (gen_ai.*) (ai, Issue)

[5] ai_observability: streaming OTel spans drop final token usage (span ended on un-consumed iterator) (ai, Issue)

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

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

[15] Method getPluginResponse should be in AiContentSuggestionsPluginBase class and not in external service (ai, Issue)

[21] Add rich-text image description support to AI Automators (ai, Issue)

[25] Add structured input to agents following Tool API input definitions (ai, Issue)

[26] Add structured output to agents following the Tool API (ai, Issue)

[27] Switch agents to the Tool API and extract function calls to a contrib module (ai, Issue)

[28] Move the agent entity structure into the AI module (ai, Issue)

[29] Create an agent runner abstraction as plugins (ai, Issue)

[30] Create a Drupal agent runner (ai, Issue)

[31] Create a Symfony AI agent runner (ai, Issue)

[32] Agent runners must support running tools under a configured role/permissions (ai, Issue)

[33] Shared event points for both agent runners (ai, Issue)

[34] Control-mechanism plugin system used by both runners (ai, Issue)

[35] Migration scripts: existing agents → Drupal agents (ai, Issue)

[36] Integrate the runner with Symfony Messenger (or similar) (ai, Issue)

[37] [META] Move AI Agents architecture into the AI module (ai, Issue)

[39] feat: #3586479 Add gen_ai.* semantic conventions to ai_observability (ai, MR)

[40] fix: #3586473 Finalize streaming OTel spans on the terminal event (ai, MR)

[44] refactor: #3577050: Generalize field widget action dispatch in the base class. (ai, MR)

[45] refactor: #3577050: Generalize field widget action dispatch in the base class. (ai, MR)

[46] Issue #3586436: Refactor AiContentSuggestionsPluginBase (ai, MR)

[47] refactor: #3577050: Generalize field widget action dispatch in the base class. (ai, MR)

[49] Issue #3586478: "Add rich-text image description support to AI Automators" (ai, MR)

[51] Idea: AI Cost & Usage module — local cost dashboard + opt-in aggregated community telemetry (ai_initiative, Issue)

[68] Issue #3594427: Use configured database for Search API server setup (ai_vdb_provider_postgres, MR)

[80] tool:run masks the failure message: getOutputValues() throws on unset outputs of a failed tool (tool, Issue)

[81] tool_ai_connector: ToolPluginBase::getReadableOutput() fatals when wrapped tool has no result object (tool, Issue)

[82] Issue #3582942: tool:run masks the failure message by reading outputs on a failed tool (tool, MR)

[83] #3582941: Avoid fatal error when tool result is unavailable in getReadableOutput() (tool, MR)

[84] Fix LogicException on component instance updates and config schema validation errors on fallback components (canvas, Issue)

[85] Canvas AI: An unexpected error has occurred while rendering preview (canvas, Issue)

[88] Canvas AI: Expose Props of Blocks to the Agent (canvas, Issue)

[92] Add a computed `src` field property to the image field type (canvas, Issue)

[97] Add client-side transform for entity_reference_autocomplete to ReduxIntegratedFieldWidgetsHooks::fieldWidgetInfoAlter (canvas, Issue)

[98] Symmetrically translatable config-defined component trees, STEP 4: allow translating component instance inputs via TMGMT for ContentTemplates & PageRegions (canvas, Issue)

[99] Implement Language Selection and Translation UI Features (canvas, Issue)

[100] Symmetric translation: component instance version updates must propagate to all translations (canvas, Issue)

[101] Add TMGMT translation integration for content entities (canvas, Issue)

[103] Symmetric translations for content entities' component tree fields should allow only translatable keys in `inputs` to be overridden (canvas, Issue)

[104] Missing checkmark for languages with translations for Content Templates (canvas, Issue)

[105] Add validation constraint similar to core's `ContentTranslationSynchronizedFieldsConstraint` to guarantee symmetrical translations have the same values as the default translation for non-translatable input keys (canvas, Issue)

[106] Missing delete translation confirmation modal (canvas, Issue)

[118] bug: #3591642 Fix LogicException on component instance updates and config... (canvas, MR)

[120] Issues/3569120: Canvas AI: Expose Props of Blocks to the Agent. (canvas, MR)

[127] feat(Data model): #3591638 Add a computed `src` field property to the image field type (canvas, MR)

[128] Issue #3574857: Add client-side transform for entity_reference_autocomplete (canvas, MR)

[129] ADR #12: Symmetric content translation: store all inputs on every translation, sync non-translatable keys at write time (canvas, MR)

[133] Resolve #3583684 "Symmetric content inputs" (canvas, MR)

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

[140] Switch context item text fields to string_long for clean MDXEditor integration (ai_context, Issue)

[144] Add full view layout for context item canonical and revision pages based on new design (ai_context, Issue)

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

[152] Issue #3586256: Change text_long to string_long and remove workaround. (ai_context, MR)

[154] Issue #3586220: Add single context item display. (ai_context, MR)

[162] [PP-1] Provide an API for performing access check on non-content entities (ai_search, Issue)

[164] Issue #3579758: Provide API for access checks on non-content entities (ai_search, MR)

[171] feat: #3594076 hash raw session_id (langfuse, MR)

Period: 9 June 2026 to 10 June 2026  |  Generated: 10 June 2026 05:00 GMT

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

Looking for older digests? Browse all digests here.