Do not include the css and js from the component generation agent in the response to speed up generation

Created on 28 August 2025, about 21 hours ago

Overview

Currently the response is overly verbose, unless this is on purpose. This means that the tokens that is needed for generating css and js are generated 3 times:

  • One time when the tools are being used.
  • One time when the component agent is generating its response to the orchestration agent.
  • One time when the orchestration agent is generating its response to the end user.

The only one of those that needs to be filled out is the tools, since they are used to fill out the form inside XB. The rest will create more costs and take more time.

I did a check on the following prompt using OpenAI:

Create a hero component with a title, subtitle and two buttons. Call it herosection

Over ten calls the average e2e time with the current output over 10 tries was 22.521.

With changes to not add this to the textual output it was 15.801

This is very unscientific, since it generates different tokens each time, and token generation on external apis are not consistent in time, but it will be faster: https://docs.google.com/spreadsheets/d/17UDhqo9UxKKuCOLNlxBw9ekjR88fFdIe...

Proposed resolution

Add to the component generation agent how to write out a textual response, when it has generated or edited a component

📌 Task
Status

Active

Version

1.0

Component

AI

Created by

🇩🇪Germany marcus_johansson

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

Comments & Activities

Production build 0.71.5 2024