@avidwriter @allozaur @ServeurpersoCom

I finally found time to finish this feature. Here are the changes I made to the first version. I need your feedback before I write the e2e tests.

We now have two options:

• Automatic width.
• Custom width.

When Automatic width is checked, the custom field is disabled.

When Automatic width is not checked, the custom field is enabled and the app defaults to 48rem.

If you open the dropdown, you will find two types of options:

• Predefined widths.
• A Set pixel value option.

Selecting a predefined width is simple. If the user selects Set pixel value, an input field appears below the dropdown. They can type a number between 300 and, 10000.

Does this make sense? I’m happy to hear your feedback.

Yes, in automatic mode, everything is fully responsive!

I keep discovering new things every time I look at the code 😅. I checked the interface on the master branch and noticed that the user message width is always set to 80%, while the AI message is 100%. That confused me at first because I was not sure if it was a problem in my branch, but I confirmed it is the default behavior.

Now that the custom mode is removed, the code is much simpler and easier to review.

I also found and fixed a bug in agentic mode.

Here is how the content looks after the fix:

Since the "responsive" option works equally well whether enabled or disabled on a smartphone and a PC, I would personally enable it by default all the time (with the front-end default configuration JSON feature that I have to improve), but being able to disable it is also good because short lines are easier to read

So maybe (@allozaur would have to confirm too) we can have just 2 options, responsive for everything, and responsive for the CoT and Thinking sections?

@allozaur @ServeurpersoCom Do I need to include the build artifacts?

The PR is ready for review.

I have also noticed a few bugs while testing the app.

Duplicate PDF files in the dropdown.

Selecting individual tools is not possible

When you close the overlay, everything is deselected.

I wanted to mention these issues here so that I don't forget. I can create issues if you are not already working on fixing them.

@allozaur @ServeurpersoCom Do I need to include the build artifacts?

The PR is ready for review.

Yes, we add a commit "chore: update webui build output" at the end, in which you have "tools/server/public/bundle.js"

I always do the following:

cd tools/server/webui
npm run format
npm run lint
npm run check
npm run build

Good catch on the menu bugs. There's also a parasitic "-" inside the checkbox if you look closely (requires an MCP server configured to be seen) another PR to simplify the logic of this menu (KISS) is needed. I opened a ticket so I wouldn't forget : #22895

Btw soon we won't need the static builds in the source anymore

Btw soon we won't need the static builds in the source anymore

That's great news!

@ImadSaddik let's come back to this after we've merged #22937 as this will get us free from any potential merge conflicts thanks to removing the static output

@allozaur I will keep an eye on that PR and update this one accordingly.