Introduce AI Agents and tools to Build Pages from Single Directory Components

Created on 18 June 2025, 6 days ago

Overview

🐛 External AI Chatbot Functionality Active introduced AI capabilities for Experience builder in whichcode components can be created and updated using AI.
This issue is for creating AI agents and tools to build entire pages using Single Directory Components, through the chatbot widget added in that issue

Proposed resolution

User interface changes

Feature request
Status

Active

Version

0.0

Component

AI

Created by

🇮🇳India Akhil Babu Chengannur

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @Akhil Babu
  • 🇮🇳India Akhil Babu Chengannur
  • Pipeline finished with Failed
    5 days ago
    Total: 1198s
    #526196
  • Pipeline finished with Failed
    5 days ago
    Total: 728s
    #526232
  • Pipeline finished with Failed
    5 days ago
    Total: 1294s
    #526240
  • 🇮🇳India Akhil Babu Chengannur
  • 🇮🇳India Akhil Babu Chengannur
  • 🇮🇳India Akhil Babu Chengannur
  • Pipeline finished with Failed
    4 days ago
    Total: 1171s
    #526841
  • 🇮🇳India Akhil Babu Chengannur
  • 🇮🇳India Akhil Babu Chengannur

    Currently there are 2 issues

    1. The messages from the page_builder_agent are not rendering in the chatbot window.
    2. Once a component is selected from the canvas, the screen automatically refreshes while typing the next message. It seems that a request is somehow being triggered to the endpoint /xb/api/v0/form/content-entity/{entity_type}/{entity}/{entity_form_mode}

  • Pipeline finished with Running
    4 days ago
    Total: 1366s
    #526894
  • 🇮🇳India narendraR Jaipur, India

    I think we can limit scope of this issue to only create page using existing components.
    Eg. "Create a page for our university website featuring a heading, a hero section, featured content, and news sections." should create the page with existing components.

    Creating/editing of components using AI already exists and we should use those tools wherever required.

    I tried testing the current MR, but the changes are not reflected on my local. Could I be missing something? Please see below.

  • 🇮🇳India Akhil Babu Chengannur

    The changes aren’t about creating or editing components. They’re focused on adding already existing components (Only SDC as of now) to the canvas with dynamic content to help build pages. For example: “Create a section showing three key features of Drupal” or “Add a button with the text ‘Read more.’”
    In my opinion, creating entire page templates (with header, body, footer, etc.) can be handled in a separate issue after the current approach is reviewed and accepted, since we’ll need to reuse a lot of the existing logic for that.

    Also, have you run npm run build after pulling the latest changes? If yes, are you seeing any errors in the console?

  • 🇮🇳India narendraR Jaipur, India

    Forgot to run npm commands , now it is working as shown in Demo, Thanks.
    We need to decide whether considering only the SDC component for now is acceptable.
    Also, I have a question: What is the purpose of using 'default_information_tools' here instead of using the tool directly?

  • 🇮🇳India Akhil Babu Chengannur

    The page builder AI agent needs both the curent layout structure (Provided by the get_current_layout tool) of the page and the details of avaialble SDCs (Provided by get_sdc_info tool). Default information tools option helps to send these direct;y along with the Agent instructions as context. So it saves two extra AI calls.

Production build 0.71.5 2024