Daily Digest
Daily Digest – 3 August 2026
2026 Capabilities Progress
- Page generation — No direct progress today on automated page generation from natural language descriptions.
- Context management — Significant progress on the Context Control Center with a critical Drupal 10 compatibility fix merged [94], and planning work advancing on cleanup of UI inconsistencies [95] and scope plugin improvements [93][96]. Next milestone is beta4 release followed by QA testing for 1.0 stable release.
- Background agents — New self-configuration capabilities are in development allowing agents to programmatically set up guardrails [7][13] and core AI settings [8][14], reducing manual administrative overhead. Risk: these features remain under review with no merge timeline confirmed.
- Design system integration — Canvas made progress with headless content endpoints under development [46] and merged [47], RTL editor support in draft [50], and editable stored patterns under review [38]. Upgrade path issues affecting component version changes were identified and fixes are in progress [31][39].
- Content creation and discovery — Infrastructure improvements merged for AI-powered search [105], and automatic translation of referenced entities now under review [97][100] plus proposed caching to reduce costs [98]. A search relevance bug affecting chunk-based retrieval was identified [3].
- Advanced governance — EU AI Act Article 50 compliance module entered planning phase [18] to address legal disclosure requirements for AI-generated content, with regulation already in effect since August 2026. Risk: no development resources assigned yet despite immediate regulatory obligations for EU organizations.
- Intelligent website improvements — No direct progress today on performance-based learning or automated improvement proposals.
- Multi-channel campaigns — No direct progress today on unified campaign content creation across channels.
Shipped
- AI Agents can now use different AI providers — Administrators can assign premium models to high-value agents and economical models to routine tasks, improving cost control and performance optimization [22][27].
- Context Control Center Drupal 10 compatibility restored — A critical fix repairs failed upgrades and restores full support for Drupal 10 and PHP 8.1 sites that were broken in beta3 [68][94].
- Canvas headless content endpoint backend merged — Backend API endpoint is now available, with SDK integration for framework-native document handling across Next.js, Astro, Nuxt, and TanStack still in progress [46][47].
- LiteLLM video generation and moderation detection fixed — Models supporting video generation and content moderation are now properly identified, helping users select appropriate AI models [103][104].
- Canvas CLI authentication support added — The reconcile-media command now supports bearer token authentication, aligning with production security models [35][52].
Ongoing
- EU AI Act compliance module in planning — New transparency module under development to meet Article 50 disclosure requirements for AI-generated content, helping organizations avoid fines up to EUR 15 million [18].
- Automated translation of referenced content in development — Feature to automatically translate taxonomy terms and related entities when translating pages, reducing manual work for multilingual editorial teams [97][100].
- Agent self-configuration capabilities under review — Two new features would allow agents to programmatically set up guardrails and core AI settings without manual administration [7][8][13][14].
- Canvas upgrade path issues being resolved — Fixes in progress for configuration import failures when component versions change and schema parsing errors affecting pre-1.8 URL properties [31][32][39].
- Context Control Center preparing for stable release — QA planning underway and architecture redesign proposed to support editing tools, translation workflows, and automation systems beyond AI agents [72][75][84].
AI (Artificial Intelligence)
The AI module made progress on several fronts during the past 24 hours. A fix addressing the disappearing "Interactive" section in agent configuration forms was completed and is now ready for final review. When users added tools to an agent, the interface would revert to a plain text editor rather than maintaining the interactive editing experience; this issue has been resolved.
Work continued on improving prompt quality through automatic removal of unresolved tokens from AI prompts. When optional fields are left empty, placeholder tokens were being sent unnecessarily to AI services; a solution is now under review.
Two new capabilities are being developed to let agents configure their own operational settings. These would allow agents to set up guardrails and core AI settings programmatically rather than requiring manual admin interface work.
Three technical issues require attention: a compatibility problem between Drupal 11.4 and the chatbot interface, a streaming issue with Gemini 2.x models, and a bug affecting search result quality when using chunk-based retrieval.
How can I help on this project?
Prioritize resolution of the Drupal 11.4 chatbot compatibility issue, as it affects users who have upgraded to the latest core version. Consider assigning additional testing resources to the Gemini streaming fix to accelerate its path to production.
Contributors: Ann Mary Sruthy (annmarysruthy), Bharat Kelotra (bharatkelotra), Marcus Johansson (Marcus_Johansson), Prabhavathi Vanipenta (prabha1997), Rodel Duterte (rduterte)
Drupal AI Initiative
Activity this period centered on planning for EU regulatory compliance. A new meta issue was opened to track development of a transparency module addressing EU AI Act Article 50 transparency requirements. This regulation, which came into effect August 2, 2026, requires websites to visibly disclose AI-generated or AI-manipulated content published on matters of public interest, unless a person has exercised genuine editorial responsibility. Non-compliance carries fines up to EUR 15 million or 3% of worldwide turnover.
The proposed module would help site operators meet this legal obligation by providing disclosure mechanisms for AI-generated text and deep-fake media. This positions Drupal to support organizations navigating the new regulatory landscape in the EU market, particularly media publishers, government agencies, and other content-heavy platforms.
No code has been committed yet; the issue remains in the planning stage. The initiative is tracking recent European Commission guidelines to ensure the solution aligns with the latest regulatory interpretation.
How can I help on this project?
- Secure dedicated development resources to move the compliance module from planning into implementation, ensuring timely delivery for organizations already subject to the regulation.
- Connect the team with legal or regulatory affairs expertise to validate the technical approach against Article 50 requirements.
OpenAI Provider
A new merge request was opened to add automated setup capabilities for the OpenAI provider. The setup-provider agent skill is designed to simplify initial configuration by reading API credentials from environment variables and configuring the provider via command-line tools. This reduces manual setup steps and makes it easier to deploy the provider consistently across different environments.
The work follows established patterns from the core AI module, keeping the implementation lightweight with no additional code dependencies to maintain. This approach supports faster onboarding and reduces configuration errors during deployment.
No commits were merged during this period, so the functionality remains under review.
How can I help on this project?
- Prioritize review and testing resources for the pending setup automation work to accelerate deployment improvements.
- Confirm whether simplified provider configuration aligns with broader infrastructure and security policies before implementation proceeds.
Microsoft Azure AI
The Microsoft Azure AI module saw progress on two fronts during this period. A bug fix addressing a method error was merged, improving stability. Separately, a larger refactoring effort has been opened that restructures how the provider integrates with the broader AI framework, which should improve code maintainability and consistency with other providers going forward.
This work represents incremental improvement to the module's technical foundation. The merged fix resolves an immediate error, while the refactoring proposal signals ongoing investment in long-term code quality.
How can I help on this project?
- Allocate review capacity for the open refactoring work to ensure it can be evaluated and merged in a timely manner.
- Confirm alignment on the module's strategic priority within the organization's AI integration roadmap.
Contributors: Ishani Patel (IshaniPatel) [1], Jukka Huhta (jhuhta)
AI Agents
The AI Agents module made significant progress this period on provider flexibility. A major feature allowing administrators to pick providers per agent was completed and merged. This gives organisations better control over cost and performance: they can now assign premium AI models to high-value agents while using more economical models for routine tasks, rather than relying on a single default provider across the board.
Work is also underway to improve orchestration efficiency. A proposed feature would allow parent agents to forward requests directly to sub-agents without re-interpreting them, which should reduce errors, speed up responses, and lower operating costs when users ask straightforward questions.
Several quality issues are being addressed. A user interface bug where interactive tool options disappear unexpectedly is marked ready for review. Additionally, the AI Agents Explorer tool is not currently accessible from standard navigation menus, which may make it harder for users to discover—a proposal to improve menu placement is under consideration.
How can I help on this project?
- Prioritise review resources for the user interface bug fix, which affects the day-to-day experience of configuring agents.
- Clarify navigation and discoverability priorities: confirm whether making the Explorer more accessible aligns with user onboarding goals.
Contributors: Bharat Kelotra (bharatkelotra), Marcus Johansson (Marcus_Johansson)
Drupal Canvas
Development activity over the past 24 hours focused on unblocking deployment workflows and expanding headless capabilities. A new Canvas-owned content endpoint for headless applications was delivered, providing a foundation for framework-native document head and redirect handling across Next.js, Astro, Nuxt, and TanStack integrations. The CLI tool's reconcile-media command was updated to support bearer token authentication, aligning it with the security model used in production and continuous integration environments.
Work continued on several feature branches. Proposals under review include RTL language support for the visual editor, the ability to edit stored patterns directly, and enhanced CLI pull operations that restore not only configuration but also local helper modules and binary assets. Two upgrade path issues were identified for users migrating from earlier versions: a configuration import failure when component versions change, and a schema parsing error affecting stored URL properties created before version 1.8. Both issues have merge requests in progress.
Several dependency updates remain open for review as part of ongoing maintenance.
How can I help on this project?
- Prioritize review and decision-making on the RTL editor support and editable patterns features, both of which expand the platform's usability but require design and technical validation before merging.
- Consider resourcing additional backend reviewers to accelerate assessment of PHP-heavy contributions, where blind trust in generated code has been flagged as a risk.
Contributors: **** (project_19391_bot_17a61b0edeafd5a3db3e8b2462b6c010), **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Amandeep Singh (amangrover90) [1], Ben Mullins (bnjmnm), Canvas version bot [1], Dave Long (longwave), Fons Vandamme (f0ns), Harumi Jang (hooroomoo), Jeremy Chinquist (jjchinquist), Lionel Enkaoua (heyyo), mariosr, Matt Glaman (mglaman), wotnak [1]
Context Control Center (CCC)
A critical fix restoring Drupal 10 compatibility was merged. The beta3 release had inadvertently broken support for Drupal 10 sites, causing upgrade failures and runtime errors on admin pages. The Restore Drupal 10 compatibility and repair incomplete beta3 upgrades work repairs failed upgrade paths and re-enables full support for Drupal 10 and PHP 8.1. This clears the way for a beta4 release.
Planning and design work continued across several fronts. The team is preparing to shift from an agent-only model to a broader consumer architecture, allowing the module to support not just AI agents but also editing tools, translation workflows, and automation systems. Related design issues include plugin-based generic context consumers and clarifying scope eligibility and ranking in the UI.
Several open merge requests are under review, including work to decouple context item form descriptions from scope plugin descriptions and a large consistency cleanup pass. QA planning has begun to prepare for stable release testing.
How can I help on this project?
- Assign dedicated QA resource time to develop and execute the beta testing plan ahead of the stable release window.
- Approve prioritization of the consumer architecture redesign, confirming it aligns with broader product goals before implementation begins.
Contributors: Juan Correa (jucs7), Reinhold Schachner (reinimax) [1], Tamas Balog (tbalog), Tekla Aivazashvili (aivazashvilit)
AI translate
The AI Translate module saw development activity focused on expanding its automation and addressing usability issues. A new capability is in development to automatically translate referenced content—such as taxonomy terms and other related entities—when translating a page. Currently, editors must translate each referenced term separately, creating repetitive manual work on multilingual sites. A merge request addressing this feature was opened during the period, with work underway to reduce the translation workload for editorial teams.
Two additional feature requests were discussed. One proposes caching and cross-field deduplication to avoid re-translating unchanged or repeated content, which would lower AI service costs and improve performance. Another addresses a translation error affecting media entities that currently causes batch failures—a fix has been proposed in the issue description.
These enhancements aim to streamline the translation workflow, reduce operational costs, and improve reliability for multilingual content teams.
How can I help on this project?
- Review and prioritize the caching and deduplication feature to determine whether cost savings justify immediate development effort.
- Ensure the team has capacity to review and test the referenced-entity translation work now in development.
Contributors: Carlos Romero (o0Charly0o)
LiteLLM AI Provider
The LiteLLM AI Provider module made steady progress over the past 24 hours, with two corrections merged and two new capabilities under review.
Two fixes were merged to improve how the system identifies which models support specific features. One ensures that models capable of video generation are properly detected, while the other addresses detection of models supporting content moderation. These changes help users select the right AI models for their intended purposes.
Two additional improvements are now under review. One adds support for text translation capabilities, expanding the module's language handling features. The other introduces a more resilient approach to retrieving model information when administrative credentials are required, reducing potential access failures.
This development pace reflects active refinement of the module's core functionality, with work focused on expanding AI capabilities and improving reliability.
How can I help on this project?
- Prioritize testing and review resources for the two open merge requests to accelerate their path to production.
- Clarify whether text translation and enhanced model access are strategic priorities requiring dedicated support or documentation efforts.
Contributors: Carlos Romero (o0Charly0o), Darren Oh (darrenoh) [2]
AI powered Search Block
Development infrastructure improvements were completed during this period. A merge request addressing code quality standards and test execution issues was merged. This work ensures the module's codebase meets Drupal coding standards and that automated testing runs correctly, which supports more reliable releases and makes it easier for contributors to maintain code quality as new features are added.
With these foundational improvements in place, the project is better positioned for ongoing development and contribution from the community.
How can I help on this project?
- Clarify the roadmap priorities for moving the module toward a stable release, helping the team focus effort on the highest-value features.
- Consider promoting the module to potential users or partners who could benefit from AI-powered search capabilities and provide feedback.
Contributors: Sergiu Nagailic (Nikro)
References
[1] AI Automator Token Replacement with removing unresolved Tokens (Checkbox?)
[3] `AiReranker::extractItemText()` should prefer chunk text over configured indexed fields
[7] Add a setup-guardrails agent skill to configure guardrails, guardrail sets, and global guardrails
[13] task: #3586561 Add a setup-guardrails agent skill to configure guardrails,...
[14] task: #3586562 Add a configure-ai-settings agent skill for general AI settings...
[18] [Meta] ai_disclosure: EU AI Act Article 50 transparency module
[22] Make it possible to pick providers per agent
[27] Issue #3535760: Provider picker
[32] Dependency Dashboard
[38] #3591851: Allow editing stored patterns
[39] #3591905: `drush config:import` can fail to update a Component whose `active_version` changed
[46] feat(Headless): #3591861 Add a Canvas-owned routed content endpoint for headless apps
[47] bug: #3591839 Preserve the query string when stripping the language prefix; a...
[52] #3591885: Add `document` object $ref for linking locally hosted documents
[68] Switch CCC documentation link to clean version
[72] Design an indicator for the CCC UI that conveys subscription limits
[75] [Meta] Prepare demo content and demo context items for the CCC to show how it works
[84] Test current conditional subcontext selection before changing the prompt
[93] Issue #3586271: Clean up CCC inconsistencies and DX issues before rc1 (part 3)
[94] Issue #3586361: Decouple context item form descriptions from scope plugin descriptions.
[95] Auto-translate referenced taxonomy terms (and other translatable entities) when translating a node
[96] Feature: Translation result caching and cross-field deduplication
[97] feat: Add batch translation for referenced translatable entities in AiTranslateController
[98] feat: add translateText method and support for translation in LiteLlmAiProvider
[100] fix: #3614721 Models supporting video generation are not detected
Shipped
- AI Agents provider picker merged — Per-agent provider configuration was merged to 1.4.0, enabling users to assign different LLM providers to individual agents instead of relying on a single default provider [22][27].
- Canvas content API endpoint shipped — A new routed content endpoint at /canvas/content-api was merged, returning Canvas component trees and Unhead-compatible document head data for headless applications [47].
- Canvas reconcile-media authentication fixed — The reconcile-media command now supports bearer token authentication via CANVAS_ACCESS_TOKEN, fixing production and CI workflows that previously required client credentials [35][52].
- CCC Drupal 10 compatibility restored — Drupal 10 compatibility and incomplete beta3 upgrade repairs were merged, fixing attribute-based hook registration failures and PHP 8.1 incompatibilities [68][94].
- LiteLLM model detection fixes merged — Video generation and moderation model detection capabilities were fixed in the LiteLLM provider [103][104].
Ongoing
- AI Automator unresolved token handling under review — MR 1884 proposes stripping unresolved tokens from prompts when optional fields are empty, awaiting review [1][11].
- ai_ckeditor Gemini 2.x streaming fix open — MR 1584 addresses malformed request bodies causing 400 errors with Gemini 2.x streaming endpoints [10][16].
- Canvas config import failure blocking deploy workflows — Changes to a Component's active_version cause drush config:import failures, blocking standard drush deploy workflows [31][39].
- CCC scope plugin description decoupling in review — MR 239 decouples context item form descriptions from scope plugin descriptions to improve developer experience [55][96].
- AI Translate batch translation for referenced entities proposed — MR 35 implements automatic translation of referenced taxonomy terms and translatable entities during node translation [97][100].
AI (Artificial Intelligence)
Progress this period focused on addressing bugs in the user interface and streaming functionality. Default information tools | Interactive section disappears after adding tool was moved to RTBC after a fix was opened that re-mounts the React editor following AJAX form rebuilds. The issue affected the AI Agents form, where adding a tool caused the Interactive/YAML toggle to disappear until a full page reload.
Work continued on several open merge requests. AI Automator Token Replacement with removing unresolved Tokens remains under review with MR !1884, which strips unresolved tokens from prompts when optional fields are empty. ai_ckeditor: streamGenerateContent causes 400 Bad Request with Gemini 2.x models has an open MR addressing the malformed request body sent by the PHP client for Gemini 2.x streaming endpoints.
Two new bug reports were accepted: ai_provider_configuration renders an empty Configuration widget when the provider has no configuration options and AiReranker::extractItemText() should prefer chunk text over configured indexed fields, which causes chunk-mode results to rerank against full entity text rather than individual chunks. A new issue was also reported regarding Drupal 11.4 DeepChat Block does not work with BigPipe enabled.
How can I help on this project?
Review MR !1884 for AI Automator Token Replacement or MR !1584 for Gemini streaming fix. Pick up the unassigned ai_provider_configuration empty widget bug or AiReranker chunk text extraction issue and provide a patch.
Contributors: Ann Mary Sruthy (annmarysruthy), Bharat Kelotra (bharatkelotra), Marcus Johansson (Marcus_Johansson), Prabhavathi Vanipenta (prabha1997), Rodel Duterte (rduterte)Drupal AI Initiative
Activity over the past 24 hours centered on planning for EU AI Act compliance. A meta issue for [Meta] ai_disclosure: EU AI Act Article 50 transparency module was updated, tracking work on a new disclosure module to help Drupal site operators meet transparency requirements that took effect 2 August 2026. Article 50 mandates visible disclosure of AI-generated or AI-manipulated content published on matters of public interest, unless the content underwent substantive human review with editorial responsibility. The module aims to provide tools for marking AI-generated content and displaying appropriate disclosures to end users.
No merge requests were merged and no commits were pushed during this period. The focus remains on scoping and architectural planning for the compliance tooling.
How can I help on this project?
Review the ai_disclosure meta issue and contribute to architectural discussions around how disclosure metadata should be stored and rendered. Help identify edge cases for what constitutes "substantive human review" in typical Drupal editorial workflows.
OpenAI Provider
A merge request was opened to add a setup-provider agent skill to configure the OpenAI provider from an environment variable. The proposed skill would enable automated setup of the OpenAI provider via CLI, reading API keys from environment variables without exposing secrets. The implementation follows the pattern established in the AI module core by using a single SKILL.md file driven by drush key:save and core config commands, avoiding the need for tool plugins, drupal/tool dependencies, or additional PHP code.
No merge requests were merged and no commits were pushed during this reporting period.
How can I help on this project?
- Review the setup-provider agent skill MR for security and compatibility with the AI module skill patterns.
- Test the proposed skill locally to validate the CLI workflow for provider configuration from environment variables.
Contributors: Joshua Fernandes (joshua1234511)
Microsoft Azure AI
A fix for a method existence error was merged during the reporting period, addressing issues with argument handling in the #3562514: Resolved method exist error merge request. The 30-line change was committed and merged on 2026-08-03.
A significant refactoring effort is underway with the [#3552969] feat: Refactor AzureProvider to use OpenAiBasedProviderClientBase merge request now open for review. This 680-line diff refactors the AzureProvider to leverage the OpenAiBasedProviderClientBase, which should improve code reuse and consistency across OpenAI-based providers. The merge request remains in an opened state and is awaiting review.
How can I help on this project?
Review the AzureProvider refactor merge request to help move the substantial 680-line change toward completion. Testing the refactored provider with Azure endpoints and validating the OpenAiBasedProviderClientBase integration would be particularly valuable.
Contributors: Ishani Patel (IshaniPatel) [1], Jukka Huhta (jhuhta)
AI Agents
The provider picker refactor was merged to the 1.4.0 branch, closing Make it possible to pick providers per agent. This feature enables configuring different LLM providers per agent rather than relying solely on the default Chat with Tools provider, allowing users to assign premium models to orchestration agents while using smaller models for specialized tasks. The implementation includes a new provider form element, updated config schema, and automatic fallback to default providers when a configured provider is uninstalled.
Several patches are under review. A merge request addressing Give a parent agent possibility to forward request as is proposes a token-based mechanism allowing orchestration agents to pass requests directly to subagents without re-interpretation, improving consistency and reducing costs. Two additional merge requests target bugs around solvability determination and assistant API tool handling.
Two issues require attention: Default information tools | Interactive section disappears after adding tool is marked RTBC but not yet merged, and Backport PHPUnit/PHPStan CI hardening to 1.2.x and 1.1.x needs review to ensure test stability on older supported branches.
How can I help on this project?
Review the open merge requests for parent agent request forwarding, solvability determination, or assistant API tool handling. Investigate the UI bug in Default information tools | Interactive section disappears after adding tool or address the menu placement request in AI Agents Explorer does not appear in any menu.
Contributors: Bharat Kelotra (bharatkelotra), Marcus Johansson (Marcus_Johansson)
Drupal Canvas
Two significant merge requests landed in the past 24 hours. The new Canvas-owned routed content endpoint for headless apps was merged, introducing GET /canvas/content-api?requestUri={requestUri}. This endpoint routes requests through Drupal and returns Canvas content when Canvas manages the complete component tree, along with Unhead-compatible document head data and normalized route information. Routes that Canvas does not render return successful responses with content set to null, while route-not-found and access-denied responses use RFC 9457 Problem Details. A follow-on MR to integrate this endpoint into the headless SDK remains open.
A fix for the reconcile-media command's authentication was also merged. The command previously required clientId and clientSecret directly via ensureConfig(), bypassing ensureAuthConfig() and preventing bearer token authentication in production and CI environments. The fix now allows the command to work with CANVAS_ACCESS_TOKEN, consistent with push, pull, and build commands.
Active work continues on several issues. Config import failures when a Component's active_version changes remain under review, blocking standard drush deploy workflows. An upgrade path issue affecting stored default-relative-url prop sources written before Canvas 1.8 has been identified, where legacy schemas containing $id keys cause DefaultRelativeUrlPropSource::parse() to fail.
How can I help on this project?
Review the open MR for drush config:import failures with active_version changes, which addresses a major blocker for deploy workflows. Test the RTL support implementation covering logical CSS properties, Radix DirectionProvider, and editor UI components. Help triage or reproduce the default-relative-url upgrade path issue affecting Canvas 1.4 to 1.8 migrations.
Contributors: **** (project_19391_bot_17a61b0edeafd5a3db3e8b2462b6c010), **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Amandeep Singh (amangrover90) [1], Ben Mullins (bnjmnm), Canvas version bot [1], Dave Long (longwave), Fons Vandamme (f0ns), Harumi Jang (hooroomoo), Jeremy Chinquist (jjchinquist), Lionel Enkaoua (heyyo), mariosr, Matt Glaman (mglaman), wotnak [1]
Context Control Center (CCC)
Drupal 10 compatibility and upgrade stability were restored after beta3 introduced hooks and APIs that only worked on Drupal 11. The Restore Drupal 10 compatibility and repair incomplete beta3 upgrades fix was merged, addressing attribute-based hook registration failures, missing revision pointers after failed upgrades, and PHP 8.1 incompatibilities. This clears the path for a beta4 release.
Work continues on decoupling scope plugin descriptions from context item form text, with MR !239 open for review. A literal <br> tag is appearing as text in the Global context checkbox description, tracked in "Global context" checkbox description renders a literal <br> instead of a line break.
The architecture is shifting: plugin-based generic context consumers will replace agent-specific configuration, treating agents as one consumer type among many. Documentation efforts are underway to clarify scope eligibility, ranking, and limits, add the Scheduler module to the Extensions page, and explain RAG integration patterns. Access control hardening is planned in Harden CCC context item access checks. Large open MRs for DX cleanup (!211) and scope plugin renaming (!195) remain under review.
How can I help on this project?
Review MR !239 for scope description decoupling. Pick up the <br> rendering bug or add Scheduler to the Extensions page—both are unassigned quick wins with clear scope.
Contributors: Juan Correa (jucs7), Reinhold Schachner (reinimax) [1], Tamas Balog (tbalog), Tekla Aivazashvili (aivazashvilit)
AI translate
Development activity this period centered on addressing gaps in entity translation workflows and performance optimization. A merge request was opened to implement Auto-translate referenced taxonomy terms (and other translatable entities) when translating a node. The proposed solution introduces a batch operation that scans entity reference fields and automatically translates referenced entities (such as taxonomy terms) that lack translations in the target language. This should eliminate the manual step of translating each referenced term individually on multilingual sites.
Work also began on Translation result caching and cross-field deduplication, which aims to reduce redundant LLM calls by caching previously translated field values and deduplicating identical strings across multiple fields or components. This feature is currently assigned and flagged for the 2026Sprint15.
A bug was reported affecting media entity translation: InvalidArgumentException: Invalid translation language (und) when translating media entities. The batch operation fails when attempting to translate media items due to incorrect language handling. This issue is tagged as a Quick Win and awaits implementation.
How can I help on this project?
- Review MR 35 implementing batch translation for referenced entities.
- Pick up the unassigned media translation bug and provide a patch addressing the language code handling issue.
LiteLLM AI Provider
Two model detection fixes were merged during the reporting period. The video generation model detection fix and the moderation model detection fix both landed, addressing gaps in the provider's capability discovery.
Two new merge requests remain open. The translateText method addition introduces translation support to the LiteLlmAiProvider class, spanning 72 lines of changes. A separate model retrieval enhancement adds fallback logic for admin key access when retrieving models, a 42-line change aimed at improving reliability when the provider configuration may be incomplete or inaccessible.
How can I help on this project?
Review the open translation support MR or the model retrieval fallback MR to help move these features forward. Test the merged model detection fixes against your LiteLLM configuration to verify capability discovery works as expected.
Contributors: Carlos Romero (o0Charly0o), Darren Oh (darrenoh) [2]
AI powered Search Block
The module saw progress on code quality during this period. The task: #3609906 Fix pre-existing PHPCS/PHPStan violations and the PHPUnit --verbose CI failure merge request was merged on 2026-08-03, addressing code standards violations and resolving a CI failure related to PHPUnit verbosity. This maintenance work brings the codebase into compliance with Drupal coding standards and ensures the continuous integration pipeline runs cleanly.
How can I help on this project?
Review the project's issue queue for open bugs or feature requests that don't yet have merge requests. Consider testing the module with different AI provider configurations to identify edge cases. Help improve documentation by clarifying setup steps for developers integrating custom search providers.
Contributors: Sergiu Nagailic (Nikro)References
[1] AI Automator Token Replacement with removing unresolved Tokens (Checkbox?)
[10] ai_ckeditor: streamGenerateContent causes 400 Bad Request with Gemini 2.x models
[11] Issue #3586535: AI Automators strip unresolved tokens from prompts
[22] Make it possible to pick providers per agent
[27] Issue #3535760: Provider picker
[39] #3591905: `drush config:import` can fail to update a Component whose `active_version` changed
[47] bug: #3591839 Preserve the query string when stripping the language prefix; a...
[52] #3591885: Add `document` object $ref for linking locally hosted documents
[55] Harden CCC context item access checks and document the authoring trust model
[68] Switch CCC documentation link to clean version
[94] Issue #3586361: Decouple context item form descriptions from scope plugin descriptions.
[96] Feature: Translation result caching and cross-field deduplication
[97] feat: Add batch translation for referenced translatable entities in AiTranslateController
[100] fix: #3614721 Models supporting video generation are not detected