github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-10 07:43:10 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

Issue: Multi-model chats not taking up full width resulting in bad user experience #2782

New Issue
Closed
opened 2025-11-11 15:14:17 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-11 15:14:17 -06:00
Owner
Copy Link

Originally created by @hg0428 on GitHub (Nov 22, 2024).

Screenshot 2024-11-22 at 12 54 08 It would be a much better user experience if chats with more than one model could expand to take up the full width. With 2-3 models the width of each model's response is compacted to fit multiple. With 4+ models it has to scroll. However, it would be better to increase the width of these responses to take up the available space. Or, at least have the option to do so. Perhaps a customizable width, allowing you to scroll if you want would be best. So, you could use the full width to fit all 4 side by side, or have each one be full size individually and scroll through them.
Originally created by @hg0428 on GitHub (Nov 22, 2024). <img width="1507" alt="Screenshot 2024-11-22 at 12 54 08" src="https://github.com/user-attachments/assets/d4e0a6da-cb4a-4c41-b073-f550102478c2"> It would be a much better user experience if chats with more than one model could expand to take up the full width. With 2-3 models the width of each model's response is compacted to fit multiple. With 4+ models it has to scroll. However, it would be better to increase the width of these responses to take up the available space. Or, at least have the option to do so. Perhaps a customizable width, allowing you to scroll if you want would be best. So, you could use the full width to fit all 4 side by side, or have each one be full size individually and scroll through them.
GiteaMirror commented 2025-11-11 15:14:17 -06:00
Author
Owner
Copy Link

@hg0428 commented on GitHub (Nov 22, 2024):

@tjbck Could you let me know why this is not planned? Thanks.

@hg0428 commented on GitHub (Nov 22, 2024): @tjbck Could you let me know why this is not planned? Thanks.
GiteaMirror commented 2025-11-11 15:14:18 -06:00
Author
Owner
Copy Link

@hg0428 commented on GitHub (Nov 22, 2024):

It would be great if this was at least saved for the future, even if it is not currently planned.

@hg0428 commented on GitHub (Nov 22, 2024): It would be great if this was at least saved for the future, even if it is not currently planned.
GiteaMirror commented 2025-11-11 15:14:18 -06:00
Author
Owner
Copy Link

@etlweather commented on GitHub (Dec 11, 2024):

Definitely, would be much more usable to do comparison!

@etlweather commented on GitHub (Dec 11, 2024): Definitely, would be much more usable to do comparison!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#2782
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?