Daily Digest
Daily Digest – 18 June 2026
2026 Capabilities Progress
- Page generation — Significant progress on data model reliability with fixes for entity references and translation handling that ensure Canvas can safely generate pages in multilingual contexts [57][56], plus work on full-screen extension support for page-level tools [46][71]. Next milestone is completing symmetric translation propagation [30][53].
- Context management — Strong progress with improved documentation [84][99], new validation rules to prevent configuration errors [80][95], Document Loader submodule for importing PDFs and URLs [81][96], and UX improvements to the context listing interface [87][98]. Project governance infrastructure is now in place [82][85][97][104].
- Background agents — Active work on error handling to make agents more resilient when tools fail [24][26], allowing agents to continue operation even when permission issues occur. Menu organization improvements completed [22][25]. Risk: error handling changes still under review and not yet merged.
- Design system integration — Progress on component data consumption with optimized reference field handling [36][64] and improved support for content-entity-reference properties [38][61][62]. Work continues on ensuring Canvas AI can safely render previews [42][66]. Translation fixes ensure components render correctly across languages [34][57].
- Content creation and discovery — Progress on AI-powered content tools with fixes for taxonomy automators handling encoded characters [4] and work to enable summary field automation [10]. Language-aware indexing for Canvas content added [41][55]. Inline prompt validation bug addressed [3][13]. User experience issues remain around CKEditor AI Assistant [11][12].
- Advanced governance — Conflict detection work advancing with merged code for detecting conflicts during publishing [59] and client-side prevention [65], plus active development on resolution UI [58][69]. Translation governance improved with validation of configuration overrides [33][56] and proper handling of auto-saved changes [29][54]. Risk: conflict resolution UI still in draft status.
- Intelligent website improvements — Foundational work with the AI Cost & Usage module proposal [17] to track token usage and spending patterns, which would enable data-driven optimization decisions. This is early exploration with no code yet; community validation of demand is the immediate next step.
- Multi-channel campaigns — No direct progress today.
Shipped
- AI module regression fix — Missing features from version 1.3.3 were restored to the 1.4.x release line, preventing feature loss during upgrades [1].
- Canvas translation and data model fixes — Four critical issues were resolved: entity references are no longer incorrectly marked as translatable [57], translation configuration overrides now validate properly [56], a full-screen extension type was added for workflows that don't require page context [71], and query optimization was implemented for components consuming nested object data [64].
- Context Control Center governance and UX improvements — The project added GitLab templates [97], security reporting procedures [104], updated help documentation [99], and fixed a visual alignment issue on Drupal 11 [105].
- Gemini Provider error handling — A fix was submitted to handle content blocking by safety filters gracefully instead of causing technical errors [20].
- AI Agents menu consistency — The administrative interface was updated to align with the AI 1.4.x categorization standards for Tools and Automation [25].
Ongoing
- AI chatbot performance optimization — Work continues to defer session creation until the first message is sent, reducing unnecessary cache invalidation and improving site speed for anonymous users [15].
- Canvas symmetric translation — Active development is underway to propagate component updates across all language versions, with multiple critical issues and merge requests in progress [30][53].
- Context Control Center feature expansion — A Document Loader submodule for PDF and URL imports is under development [96], along with improved listing page filters [98] and configuration validation rules [95].
- AI Agents error handling improvements — Development continues on allowing agents to configure whether individual tool errors should halt execution or be handled gracefully, reducing support overhead for permission-related failures [26].
- Field Widget Actions configuration UX fix — A merge request is under review to filter unavailable action options from configuration menus, preventing users from encountering setup dead ends [107].
AI (Artificial Intelligence)
The AI module team closed a regression issue affecting the 1.4.x release line where features present in version 1.3.3 had not been carried forward to 1.4.2. A merge request restored missing functionality, bringing the 1.4.x branch back in line with user expectations. This ensures consistency across supported versions and prevents feature loss during upgrades.
Development continued on several fronts. Contributors opened a merge request to address a validation bug where forms with multiple prompt selectors could validate inline prompts against the wrong configuration, causing legitimate prompts to be rejected. Separately, work began on improving chatbot performance for anonymous users by deferring session creation until the first message is sent, which should reduce unnecessary cache invalidation and improve site speed.
Several user experience issues were reported. These include taxonomy automators discarding valid AI-generated terms when language models return HTML-encoded characters, a confusing dual-permission system for chatbot access, and errors when using AI Assistant features in the content editor without a properly configured user session. A feature request was raised to allow AI automators to fill both the main content field and its summary when working with formatted text fields.
How can I help on this project?
- Prioritize the chatbot permission simplification work to reduce administrator confusion and support burden.
- Ensure quality assurance resources are available to validate the inline prompt validation fix before release.
Drupal AI Initiative
The AI Initiative team opened a new exploration around cost visibility and community insights. The proposal for an AI Cost & Usage module addresses a recurring request from site owners: better understanding of AI spending. The module would provide a local dashboard showing token usage, daily costs, and which models or features are driving spend, helping organizations budget and optimize their AI investments.
The proposal also includes an optional, privacy-conscious community telemetry component. Sites could choose to share anonymized usage patterns with the Drupal AI Initiative, creating a feedback loop that would help the team understand real-world adoption patterns, identify which providers and models are most popular, and prioritize development efforts based on actual usage rather than assumptions.
This is an early-stage concept opened by Marcus Johansson (Marcus_Johansson). No code has been written yet, and the idea is currently gathering input from the community to validate demand and shape requirements.
How can I help on this project?
- Validate demand by surveying your teams or peers: would cost visibility tools change how you budget or govern AI features?
- Connect the initiative with procurement or finance stakeholders who can articulate what cost reporting capabilities would support vendor evaluation or budget planning.
Gemini Provider
The Gemini Provider module saw focused progress on error handling during the past 24 hours. When the Gemini service blocks content due to safety filters, the module currently encounters a technical error rather than handling the situation gracefully. A proposed solution has been submitted to address this issue through #3588223: Resolved value error, contributed by Ishani Patel (IshaniPatel). This work will improve the user experience by allowing the system to respond appropriately when content is blocked, rather than failing unexpectedly.
Separately, work continues on expanding the module's capabilities to process multiple pieces of content at once for efficiency gains, with Joshua Fernandes (joshua1234511) assigned to Add support for batch embeddings.
How can I help on this project?
- Expedite review and testing of the error handling fix to unblock a more stable release and improve user experience when content is moderated.
- Consider allocating testing resources to validate batch processing functionality once implementation is complete, as this will impact performance at scale.
Huggingface Provider
The Huggingface Provider module saw one new development proposal during the reporting period. Ahmad Khader (Ahmad-Khader) opened a merge request to add extractive question functionality, which would expand the module's capabilities to support question-answering features based on provided text. This enhancement would allow site owners to implement automated question-answering tools that extract precise answers from documents or content, potentially improving user self-service and reducing support overhead.
The proposal is currently under review. No issues were updated and no code was committed to the repository during this period, indicating a quiet day for maintenance and issue resolution.
How can I help on this project?
- Ensure maintainer capacity is available to review the pending merge request so the extractive question feature can move toward completion.
- Clarify strategic priorities for AI capabilities to help contributors focus on the most valuable features for your organization's needs.
AI Agents
The AI Agents project saw focused maintenance activity over the past 24 hours, with work addressing consistency and user experience in administrative interfaces.
Two issues were updated relating to menu organization. The first ensures the module aligns with newer categorization standards introduced in the core AI framework, where administration options are now grouped into thematic sections such as "Tools & Automation" and "AI Infrastructure." A merge request to implement this change has been submitted by Ahmad Khader. The second addresses a minor labeling inconsistency in the administration menu, making terminology more consistent across the interface.
Additionally, work continued on improving system reliability when agents encounter errors while using tools. Currently, if an agent lacks permission to execute a tool, the entire process stops, requiring manual intervention. The active development aims to allow creators to configure whether individual tool errors should halt execution or be handled gracefully, enabling agents to serve users with different permission levels more effectively. This capability would make agents more resilient and reduce support overhead.
How can I help on this project?
- Prioritize testing resources to review the error handling improvements, which could significantly reduce support costs for permission-related failures.
- Clarify product positioning on whether AI Agents should support multi-role deployments to guide feature prioritization decisions.
Tool API
The Tool API project supports AI agents in performing operations, including file handling. During this period, work continued on File Input Handling, a research and proof-of-concept effort exploring how tools should securely accept and process file inputs from AI agents. This work is examining input formats, file loading methods, and schema normalization to ensure safe file operations.
No code was merged or committed in the last 24 hours, which is typical for early-stage research work. The project is currently in the discovery phase, laying groundwork for future implementation decisions and potentially new issues or modules once the research concludes.
How can I help on this project?
- Ensure the team has access to security expertise to validate file handling approaches before implementation begins.
- Clarify strategic priorities for AI agent capabilities to help the team focus research efforts on the most valuable use cases.
Drupal Canvas
The team made significant progress on translation and data model reliability over the past 24 hours, closing four critical issues that together ensure Canvas can support multilingual content workflows without data loss or corruption.
Two merged fixes address translation-related bugs. The first ensures that entity references (such as images) are no longer incorrectly marked as translatable, preventing rendering failures when content is translated. The second adds validation to translated configuration overrides—closing a gap where Drupal core does not validate translations, which could allow invalid data to be saved.
The team also optimized how Canvas queries and stores referenced content. When components consume entity data exclusively through nested objects (for example, pulling a user's email and name through an author reference), the system now consolidates multiple field expressions into a single, more efficient query. This improves performance and reduces database load.
A new extension type was merged that allows full-screen Canvas tools (such as translation dashboards or content audit interfaces) to run outside the sidebar, providing a better user experience for workflows that don't require page context.
Active work continues on symmetric translation (propagating component updates across all languages), conflict detection during publishing, and compatibility with Drupal 11.3. Several issues remain open, including test failures and edge cases involving deleted file references, but all have assigned contributors or open merge requests in progress.
How can I help on this project?
- Prioritize resources for the symmetric translation effort, which has multiple critical issues in flight and will unlock full multilingual publishing workflows.
- Support testing and validation of the conflict detection UI to de-risk the selective publishing feature before release.
Context Control Center (CCC)
The team completed four key deliverables in the past 24 hours focused on project governance and user experience. The project now has standardized GitLab issue and merge request templates to streamline contributor workflows, and a SECURITY.md file that establishes clear procedures for reporting security vulnerabilities. The overview page help text and documentation was updated to better communicate the purpose and functionality of the module to administrators. A visual alignment issue with the overview page checkbox on vanilla Drupal 11 was also resolved.
Active work continues on several fronts. Kristen Pol (kepol) is preparing presentations for Bluefly and the Learners Club to promote adoption. Significant feature work is underway including improved filters and column layout for the context listing page, a Document Loader submodule enabling PDF and URL imports, and validation rules to prevent configuration errors. The team is also addressing compatibility with Drupal 12 and refining extensibility hooks for downstream modules.
How can I help on this project?
- Facilitate connections with potential adopters or pilot sites who could benefit from the presentation materials being prepared for Bluefly and Learners Club.
- Support prioritization decisions on whether to invest in the extensible role architecture being discussed for future context item types.
Field Widget Actions
The Field Widget Actions module saw development activity focused on improving the user experience when configuring actions. A bug was identified where users are presented with action options in a configuration menu that cannot actually be used. This creates confusion: users see tools they cannot add, resulting in a poor experience when trying to set up their workflows.
The issue occurs because the system displays all compatible action types without checking whether the necessary components exist for that specific content structure. A solution has been proposed by contributor Artem Dmitriiev (a.dmitriiev) through an open merge request that would filter the available options to show only actions that can genuinely be used in each context. This is expected behavior for configuration interfaces and would prevent users from encountering dead ends during setup.
No commits were merged during this period. The work is part of a broader AI Initiative Sprint focused on product development and code quality improvements.
How can I help on this project?
- Ensure code review capacity is available to evaluate the pending merge request so the user experience fix can be completed and deployed.
- Confirm alignment with the AI Initiative Sprint priorities to maintain momentum on product quality improvements.
References
[1] Regression in 1.4x release vs 1.3.x
[4] Taxonomy automator clears valid term values when the LLM returns HTML-encoded entities (e.g. &)
[10] Fields with optional summary field, have no AI Automator option to fill it as well.
[11] Improve ai_ckeditor UX when no provider modules are installed
[12] Issue when creating content and click on AI Assistant on Ckeditor
[13] fix: Validates inline prompt against stale prompt type when multiple ai prompt elements exists
[15] Issue #3554797: Start session after first interaction
[17] Idea: AI Cost & Usage module — local cost dashboard + opt-in aggregated community telemetry
[20] #3588223: Resolved value error.
[22] AI Agents admin menu does not follow AI 1.4.x menu categorization (Tools & Automation)
[24] Add possibility to catch all errors on a tool
[26] Issue #3547994: Add per-tool error catching to prevent agent crashes.
[29] Only show default-language entities when reviewing auto-saved (pending) changes
[30] Symmetric translation: component instance version updates must propagate to all translations
[36] Coalesce reference fields whose values are consumed only through nested objects
[38] Support `content-entity-reference` props in CLI and Workbench
[41] Include language-aware indexing for ContentTemplate-rendered Canvas content
[42] Canvas AI: An unexpected error has occurred while rendering preview
[46] Add "page" extension type for full-screen Canvas extensions
[54] fix: #3591704 Hide non-default-translation auto-saves from the pending-changes GET response
[55] #3591695 Include language-aware indexing for ContentTemplate-rendered Canvas content
[57] fix(Data model): #3591699 Never expose entity-reference inputs (e.g. image src) as translatable
[59] feat(Conflict detection): #3587526 "Detect conflicts during publishing of changes to Page entity"
[62] Draft: feat(CLI Tool): #3591700 Support `content-entity-reference` props in CLI and Workbench
[64] feat(Data model): #3591678 Coalesce reference fields consumed only through nested objects
[65] feat(Conflict detection): #3587526 "Client side prevention of publishing"
[66] Issues/Canvas AI: An unexpected error has occurred while rendering preview
[69] Add conflict detection and resolution UI for selective publishing
[71] Add "page" extension type for full-screen Canvas extensions
[80] Add context settings validation: max_global_items must not exceed max_items
[81] Create Document Loader submodule for CCC
[82] Create GitLab issue and merge request templates for ai_context project
[84] Update overview page description and docs
[85] Create SECURITY.md file for AI Context (CCC)
[87] Possible UX improvements on new context listing page
[95] Issue #3586272: Add validation that max_global_items cannot exceed max_items
[96] Issue #3586275: Add ai_context_document_loader submodule for MDXEditor imports.
[97] Issue #3586155: Add GitLab issue and merge request templates
[98] Issue #3586274: Merge Use cases/Scope columns and add cascading scope filter
[99] Issue #3586252: Update overview page help text and docs.
[104] Issue #3586267: Added SECURITY.md file
[105] Resolve "Show this overview page checkbox is misaligned on vanilla Drupal 11"
[107] Issues #3536116: Omit unavailable plugins in field widget actions configuration field widget form
Shipped
- AI module 1.4.x regression fixed — Merged fix setting temp directory for encoderProvider, resolving crashes in the 1.4.x release [1][14].
- Gemini Provider ValueError handling — Merged fix preventing crashes when Gemini blocks prompts and returns zero candidates [18][20].
- Canvas entity-reference translation fix — Image src and similar entity-reference props no longer incorrectly exposed as translatable, fixing rendering failures in translated config entities [34][57].
- Canvas LanguageConfigOverride validation — Config schema validation now enforced on Canvas config entity translations, working around 12-year-old core bug [33][56].
- AI Context documentation and tooling — Merged GitLab issue templates, overview page help text updates, SECURITY.md file, and CSS alignment fix for Drupal 11 [82][84][85][92][97][99][104][105].
Ongoing
- AI module form validation for multiple prompts — Fix under review for AiPromptSubForm validating against stale prompt type when multiple ai_prompt elements exist [3][13].
- Canvas symmetric translation propagation — Component instance version updates must propagate to all translations, blocking Phase 1 release with 3207-line MR under review [30][53].
- Canvas translation auto-save filtering — Open MR hides non-default-translation auto-saves from pending-changes review to prevent discard/publish bugs [29][54].
- AI Agents menu categorization alignment — MR under review to align admin menu with AI 1.4.x Tools and Automation structure [22][25].
- AI Context cascading scope filter — Open MR merges Use cases/Scope columns and adds cascading scope filter based on UX review [87][98].
AI (Artificial Intelligence)
The past 24 hours saw focused work on bug fixes and permission improvements. A regression issue affecting the 1.4.x branch was resolved - Regression in 1.4x release vs 1.3.x was closed after MR !1685 was merged, cherry-picking a commit to set the temp directory for encoderProvider.
Several new issues emerged around form validation and permissions. Javier Destefanis (javierdestefanis) opened AiPromptSubForm validates inline prompt against stale prompt type when multiple ai_prompt elements exist and submitted MR !1686 with a fix for forms containing multiple prompt elements. Nicholas Stees (NicholasS) reported Taxonomy automator clears valid term values when the LLM returns HTML-encoded entities, affecting entity reference fields when models return ampersands as &.
Permission issues received attention with activity on Remove access deepchat api permission and Permissions to use AI Assistant are confusing. Additionally, Issue when creating content and click on AI Assistant on Ckeditor reached RTBC status.
How can I help on this project?
Review MR !1686 for the AiPromptSubForm validation fix and test with multiple prompt elements. Pick up the taxonomy HTML-entity bug, which has no MR yet. Help test MR !978 for session creation optimization with anonymous users.
Drupal AI Initiative
Activity in the AI Initiative over the past 24 hours was light, with discussion continuing around future module development. An AI Cost & Usage module concept was updated on June 18th. This proposed module would provide site owners with a local dashboard to track AI spending and usage metrics (tokens per request, daily costs, and breakdown by model/provider/feature), while optionally sharing anonymized, aggregated telemetry data back to the community. The goal is two-fold: giving site administrators visibility into their AI costs, and providing the AI Initiative with real-world usage data to inform future development priorities and provider recommendations.
No merge requests were merged and no commits were pushed during this reporting period. The discussion phase for the cost tracking module continues as the community evaluates technical implementation approaches.
How can I help on this project?
- Review the AI Cost & Usage module proposal and contribute technical feedback on architecture, privacy considerations for telemetry, or implementation approach.
- Explore existing AI provider cost tracking patterns and share insights that could inform the dashboard design.
Gemini Provider
The Gemini Provider module saw continued work on error handling and API improvements this period. Activity centered around two open issues addressing integration gaps with the Gemini API.
Progress was made on ValueError: The `GenerateContentResponse::parts()` quick accessor only works for a single candidate, but none were returned, which addresses a crash when Gemini blocks a prompt and returns zero candidates. Ishani Patel (IshaniPatel) opened #3588223: Resolved value error to fix the issue in GeminiProvider.php. The MR is awaiting review, with the issue currently marked as needs work.
Meanwhile, Add support for batch embeddings was assigned to Joshua Fernandes (joshua1234511). This feature would integrate Gemini's batchEmbedContents method to handle multiple embeddings efficiently, following up on earlier work in the AI module.
No commits were merged during this period, indicating both issues remain in active development.
How can I help on this project?
Huggingface Provider
Activity this period centered on an open merge request. Ahmad Khader (Ahmad-Khader) submitted Resolve #3584375 "Add extractive question", introducing extractive question answering functionality with 113 lines of changes. The MR remains under review with no commits merged during the reporting period.
No issues were updated, merged, or marked blocking within the last 24 hours, leaving the module in a relatively quiet state with the extractive question answering work awaiting feedback.
How can I help on this project?
AI Agents
Activity in the AI Agents module focused on menu organization and error handling improvements during this period.
Ahmad-Khader opened MR !286 to address AI Agents admin menu does not follow AI 1.4.x menu categorization (Tools & Automation), which was reported by Marcus Johansson (Marcus_Johansson). The AI module restructured its administration menu in 1.4.x to include themed sub-sections, and AI Agents needs to align with this new structure by placing its settings under the Tools & Automation category. The MR contains 114 lines of changes and is awaiting review.
Michael Anello (ultimike) reported a minor inconsistency in Change "AI Agent" to "AI Agents" in admin menu, noting that the Configuration | AI section incorrectly displays "AI Agent" instead of "AI Agents". This issue is marked as needs work.
Work continued on Add possibility to catch all errors on a tool, with Nicolae Procopan (thebumikgmail.com) maintaining MR !220 (480 lines). This aims to give agent creators control over error handling behavior, allowing agents to continue execution when tools fail due to permissions or other issues rather than crashing entirely.
How can I help on this project?
Review MR !286 for the menu categorization issue to verify alignment with AI 1.4.x structure. Test MR !220 for error catching functionality and provide screenshots or tests, as both are currently needed. Pick up the unassigned menu naming issue and submit a patch.
Tool API
The Tool API project saw limited technical activity in the past 24 hours, with one issue remaining in active discussion. The File Input Handling issue, originally reported by abhisekmazumdar (drupalbot), continues to focus on research and proof of concept work for enabling AI agents to securely process file inputs through the Tool API. The issue is exploring key areas including input formats, file loading, and normalization schemas, with the goal of determining whether file handling capabilities should be integrated into this module or a separate one. Related MR !73 is associated with this work.
No merge requests were merged and no commits were pushed during this reporting period. The File Input Handling issue remains unassigned and in the opened state, indicating an opportunity for contributors to engage with this research-oriented task.
How can I help on this project?
- Review MR !73 related to the File Input Handling issue and provide feedback on the proposed approach for secure file processing.
- Contribute to the research discussion on file input formats and security considerations for AI agent file operations.
Drupal Canvas
Canvas merged several critical fixes and features over the past 24 hours, focusing heavily on translation infrastructure and data model improvements.
Three significant MRs landed on June 18th. Christian López Espínola (penyaskito) merged fix for entity-reference inputs being incorrectly exposed as translatable, resolving rendering failures in translated config entities when components contained image src or similar entity-reference props. The fix ensures these references remain language-agnostic. He also merged coalescing improvements for reference fields consumed only through nested objects, building on earlier work to optimize FieldObjectPropsExpression handling.
Wim Leers (wimleers) shipped validation for LanguageConfigOverride entities, working around a 12-year-old core bug by enforcing config schema validation on Canvas config entity translations—critical for the symmetric translation rollout. Meanwhile, Lauri Timmanee (lauriii) added a new "page" extension type allowing full-screen Canvas extensions for standalone tasks like translation dashboards.
Several translation and conflict-detection issues remain in progress. Ted Bowman (tedbow) has an open MR to hide non-default-translation auto-saves from the pending-changes review UI, preventing discard/publish bugs until langcode-aware endpoints land. The symmetric translation component instance propagation work (MR !1163, 3207 lines) and canvas_dev_translation promotion (MR !1258) are both open and blocking the Phase 1 release. Matt Glaman (mglaman) is addressing Drupal 11.3 kernel test failures in ComponentInputsEvolutionTest and HostEntityPropSourceMatcherTest.
How can I help on this project?
Review Ted Bowman's pending-changes translation filter MR !1263 or Matt Glaman's Drupal 11.3 kernel test fixes in MR !1261. Tackle the unassigned critical bug discarding translations deletes wrong language, which needs a langcode-aware DELETE endpoint in ApiAutoSaveController.
Context Control Center (CCC)
The past 24 hours saw significant documentation and process improvements shipped for the ai_context module. Matt Glaman (mglaman) merged Issue #3586155: Add GitLab issue and merge request templates, restoring standardized templates for contributions. Kristen Pol (kepol) merged Issue #3586252: Update overview page help text and docs, clarifying the overview page's purpose following earlier UX refinements. Daniel Rodriguez (danrod) added a SECURITY.md file via MR !179 to establish security reporting procedures. Juan Correa (jucs7) fixed a CSS alignment bug on vanilla Drupal 11 via MR !180.
Active development continues on several features. Matt Glaman opened MR !184 implementing the cascading scope filter and merged Use cases/Scope columns from the UX review. Open merge requests await review for validation that max_global_items cannot exceed max_items (MR !181, Tamas Balog), Document Loader submodule integration (MR !176), and making Scheduler an optional progressive feature (MR !178). Ahmad Khader (Ahmad-Khader) is addressing hook_ai_context_scope_values_alter() not being honored in scope value forms via MR !177.
How can I help on this project?
Review MR !184 for the cascading scope filter UX changes. Test MR !177 for hook_ai_context_scope_values_alter() integration. Pick up extensible role architecture for context items, which has no assignee or MR yet.
Field Widget Actions
No code was merged during this period. Activity focused on an open bug report where Field Widget Actions show in the "Add New Action" unavailable tools. The issue addresses confusion in the plugin configuration UI: while Field Widget Actions plugins implement an isAvailable() method to determine compatibility (particularly for AI Automators checking entity type and field availability), the "Add New Action" dropdown does not respect this method. Instead, it only performs basic field type and widget checks, allowing users to select plugins that cannot actually be added. Artem Dmitriiev (a.dmitriiev) has submitted MR !21 with 696 lines of changes to omit unavailable plugins from the configuration field widget form, but this merge request remains under review.
How can I help on this project?
References
[1] Regression in 1.4x release vs 1.3.x
[13] fix: Validates inline prompt against stale prompt type when multiple ai prompt elements exists
[14] Issue #3582743: Set temp directory for encoderProvider.
[20] #3588223: Resolved value error.
[22] AI Agents admin menu does not follow AI 1.4.x menu categorization (Tools & Automation)
[29] Only show default-language entities when reviewing auto-saved (pending) changes
[30] Symmetric translation: component instance version updates must propagate to all translations
[54] fix: #3591704 Hide non-default-translation auto-saves from the pending-changes GET response
[57] fix(Data model): #3591699 Never expose entity-reference inputs (e.g. image src) as translatable
[82] Create GitLab issue and merge request templates for ai_context project
[84] Update overview page description and docs
[85] Create SECURITY.md file for AI Context (CCC)
[87] Possible UX improvements on new context listing page
[92] Show this overview page checkbox is misaligned on vanilla Drupal 11
[97] Issue #3586155: Add GitLab issue and merge request templates
[98] Issue #3586274: Merge Use cases/Scope columns and add cascading scope filter
[99] Issue #3586252: Update overview page help text and docs.
[104] Issue #3586267: Added SECURITY.md file
[105] Resolve "Show this overview page checkbox is misaligned on vanilla Drupal 11"