Work for the GSoC 2026 project, AI Knowledge Assistant for Drupal

The primary goal of this phase is to establish the core chat experience, integrate with Drupal AI providers, and implement conversational memory capabilities.

Features -

- to create the AI Knowledge Assistant custom module structure.
- to add administration configuration and Drupal AI provider integration.
- to implement the chat interface with AJAX-based interactions.
- to add support for AI responses through Drupal AI providers.
- to implement session-based conversational memory.
- to add sliding window context management for multi-turn conversations.
- to implement new chat and clear chat functionality.
- to add copy message functionality with user feedback notifications.
- to add speech-to-text (voice input) support.
- to improve the chat composer and overall chat UI/UX.
- to improve conversation management foundations for future chat history support.

Technical details -

Drupal session storage to maintain conversational state. A sliding window memory strategy is used to provide contextual continuity while keeping the amount of context sent to the LLM bounded and efficient.

Inspiration for the UI is taken from : link and link

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

sujal kshatri created an issue. See original summary.

sujal kshatri’s picture

Issue summary: View changes

azizos’s picture

@sujual_31 plz mention the inspiring chat ui lib

sujal kshatri’s picture

Issue summary: View changes
sujal kshatri’s picture

Issue summary: View changes

azizos changed the visibility of the branch gsoc-midterm to hidden.

azizos changed the visibility of the branch gsoc-midterm to active.

azizos’s picture

azizos’s picture

Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.