enricoros / big-AGI

Generative AI suite powered by state-of-the-art models and providing advanced AI/AGI functions. It features AI personas, AGI functions, multi-model chats, text-to-image, voice, response streaming, code highlighting and execution, PDF import, presets for developers, much more. Deploy on-prem or in the cloud.

Home Page:https://big-agi.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Beam: remove the "+" selector for adding another model

dandv opened this issue · comments

Why
By implementing the ability to remove the "+" model selector, users will be able to maximize the width of the existing model response columns.

Description
In the screenshot below, you can see that my browser window has space for 3 model response columns. I only use two models, so I would like to remove the third empty column.

image

PS: if this is already possible, it would help to have the Discussions feature in the repo enabled, so users could help each other in their use of big-AGI.

Agree, how can I remove that and still let users create new chats? What are good UI options?

Two ideas:

  1. Moving the button to add a beam to the Beam / Beam Count / Stop bar, maybe as a "+1" after "x8"
  2. If "Beam Count" doesn't actually get much usage, replacing it with that button to add one more model to the beam

One minor problem with this approach is that the user would have to scroll to the top to find that button. A solution would be to duplicate it at the bottom:

image

I personally haven't found a good use for the "x2/4/8" buttons. Maybe an intended use case is to get multiple answers from the same model, but that runs the risk of hitting concurrency quotas as in my screenshot. So the typical usage seems to load/use a Model Preset, or add models one by one (and likely choosing a different one each time).

@dandv this is great UX input. I'll add it as an option so we can try it out. I feel the need as well.

@dandv will be deployed once we merge the feature-multipart branch, but this is done.
image
Thanks again for the idea.

Thanks for implementing this! 🚀

Thanks for implementing this! 🚀

Not landed yet, it's on a big side branch with lots of cool changes.