Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-21 01:25:28 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #5431] [FEAT]: Request / UX Improvement Suggestions for Anything LLM #5088

New Issue
Closed
opened 2026-06-05 14:51:56 -04:00 by yindo · 3 comments
yindo commented 2026-06-05 14:51:56 -04:00
Owner
Copy Link
Copy Source

Originally created by @oioix on GitHub (Apr 14, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5431

Hi,
I appreciate the functionality of Anything LLM . However, I have noticed two points that I would like to submit as improvement suggestions to further enhance the user experience (UX).

1. Issue: Truncated Model Descriptions in the Left Dropdown Navigation Bar

Description:
In the left dropdown navigation bar where different models and their associated chats are configured, the text window for the dropdown is simply too cramped, causing the informative text about the model to be cut off. This descriptive text is crucial when dealing with multiple models, as it helps distinguish which model is being used, whether it's integrated locally or via the cloud, and so on.

This significantly hinders me as a user in quickly grasping the specific capabilities or characteristics of a particular model assigned to the dropdown menu because I cannot see the full context.

Proposed Solutions:
I suggest the following options to resolve this issue:

  • Option A (Minimalist): Slightly reduce the font size of the model descriptions to display more text on the same line.
  • Option B (Layout Change): Minimally widen the entire side panel to allow for better visualization.
  • Option C (Optimal – Multi-line Display): Expand the display to up to three lines. Ideally, this would function with a structure like this:
    • Line 1: Short headline/Model Name
    • Lines 2 & 3: More detailed description of the model's behavior

Option C is my absolute favorite here, as it would allow me to put the model's name in the first line and add specific details about that configuration in smaller text across one to three lines below.
See the difference in my screenshot.

2. Issue: Handling the "Default" Chat Thread

Description:
The currently existing "default" chat is very cumbersome for me to manage. Since this chat cannot be deleted as a whole, I have to painstakingly delete every single message manually during cleanup just to clear the thread. This represents a significant UX bottleneck and causes unnecessary frustration.

Proposed Solution:
I request the implementation of a feature that allows this entire chat thread to be cleared or deleted at once. Alternatively, since it is arguably unnecessary (given the "+ New Thread" option), the "default" chat could potentially be completely removed.

I hope these suggestions are helpful for the further development of Anything LLM! Thank you very much!

Image

Originally created by @oioix on GitHub (Apr 14, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5431 Hi, I appreciate the functionality of Anything LLM . However, I have noticed two points that I would like to submit as improvement suggestions to further enhance the user experience (UX). ## 1. Issue: Truncated Model Descriptions in the Left Dropdown Navigation Bar **Description:** In the left dropdown navigation bar where different models and their associated chats are configured, the text window for the dropdown is simply too cramped, causing the informative text about the model to be cut off. This descriptive text is crucial when dealing with multiple models, as it helps distinguish which model is being used, whether it's integrated locally or via the cloud, and so on. This significantly hinders me as a user in quickly grasping the specific capabilities or characteristics of a particular model assigned to the dropdown menu because I cannot see the full context. **Proposed Solutions:** I suggest the following options to resolve this issue: * **Option A (Minimalist):** Slightly reduce the font size of the model descriptions to display more text on the same line. * **Option B (Layout Change):** Minimally widen the entire side panel to allow for better visualization. * **Option C (Optimal – Multi-line Display):** Expand the display to up to three lines. Ideally, this would function with a structure like this: * Line 1: Short headline/Model Name * Lines 2 & 3: More detailed description of the model's behavior Option C is my absolute favorite here, as it would allow me to put the model's name in the first line and add specific details about that configuration in smaller text across one to three lines below. See the difference in my screenshot. ## 2. Issue: Handling the "Default" Chat Thread **Description:** The currently existing "default" chat is very cumbersome for me to manage. Since this chat cannot be deleted as a whole, I have to painstakingly delete every single message manually during cleanup just to clear the thread. This represents a significant UX bottleneck and causes unnecessary frustration. **Proposed Solution:** I request the implementation of a feature that allows this entire chat thread to be cleared or deleted at once. Alternatively, since it is arguably unnecessary (given the "+ New Thread" option), the "default" chat could potentially be completely removed. *** I hope these suggestions are helpful for the further development of Anything LLM! Thank you very much! ![Image](https://github.com/user-attachments/assets/bfda377b-b5de-46f1-8e92-7d774ee5d135)
yindo added the enhancementUI/UXfeature request labels 2026-06-05 14:51:56 -04:00
yindo closed this issue 2026-06-05 14:51:56 -04:00
yindo commented 2026-06-05 14:51:57 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Apr 14, 2026):

I have to painstakingly delete every single message manually during cleanup just to clear the thread.

You can just use the /reset slash command - you do not have to delete the messages.

For the first issue you outline, this is going to crowd the UI a ton - there has to be a better way to highlight or manage this. We could add a description field to workspaces that could enable something like this?

<!-- gh-comment-id:4246293093 --> @timothycarambat commented on GitHub (Apr 14, 2026): > I have to painstakingly delete every single message manually during cleanup just to clear the thread. You can just use the `/reset` slash command - you do not have to delete the messages. For the first issue you outline, this is going to crowd the UI a ton - there has to be a better way to highlight or manage this. We could add a description field to workspaces that could enable something like this?
yindo commented 2026-06-05 14:51:57 -04:00
Author
Owner
Copy Link
Copy Source

@oioix commented on GitHub (Apr 16, 2026):

Yes, an additional description field would be great! I think two lines under the heading would be perfect. However, I also think the font size of the heading should probably be a bit smaller. Thank you very much for considering this.

"You can simply use the /reset Slash command - You do not have to delete the messages."

Thank you for this valuable tip! Yes, it actually works with the /reset. However, you have to execute the command twice if you are still in agent mode because the first /reset only resets the agent initially. And thus you need to wait until the agent session is completed, which can take a few seconds using a local model.
Image
I probably did not found it that way. Wouldn't it be much simpler if a delete function was directly added to the default button. Then it would only take one single click. To distinguish this from "completely deleting threads" (the "default" button remains there), you could display a trash icon at the right side of the default-button instead of an X-icon.

<!-- gh-comment-id:4258163770 --> @oioix commented on GitHub (Apr 16, 2026): Yes, an additional description field would be great! I think two lines under the heading would be perfect. However, I also think the font size of the heading should probably be a bit smaller. Thank you very much for considering this. "_You can simply use the /reset Slash command - You do not have to delete the messages._" Thank you for this valuable tip! Yes, it actually works with the /reset. However, you have to execute the command twice if you are still in agent mode because the first /reset only resets the agent initially. And thus you need to wait until the agent session is completed, which can take a few seconds using a local model. <img width="1714" height="842" alt="Image" src="https://github.com/user-attachments/assets/d9da0203-e22e-40c2-82ac-ed573851e037" /> I probably did not found it that way. Wouldn't it be much simpler if a delete function was directly added to the default button. Then it would only take one single click. To distinguish this from "completely deleting threads" (the "default" button remains there), you could display a trash icon at the right side of the default-button instead of an X-icon.
yindo commented 2026-06-05 14:51:57 -04:00
Author
Owner
Copy Link
Copy Source

@nordwestt commented on GitHub (Apr 24, 2026):

Hey there @timothycarambat 👋 just chiming in here
I think the simplest and best for UX is just to do a fake delete, ie. the thread doesn't get removed, but just is wiped clean. To the user it's all the same, and this has been done so many times.
Think of how your computer doesn't actually delete files, it just marks the space as being available - although that's of course for efficiency reasons, the point is the same: it's okay to lie to users if it helps them get through their day 😉

<!-- gh-comment-id:4311801982 --> @nordwestt commented on GitHub (Apr 24, 2026): Hey there @timothycarambat 👋 just chiming in here I think the simplest and best for UX is just to do a fake delete, ie. the thread doesn't get removed, but just is wiped clean. To the user it's all the same, and this has been done so many times. Think of how your computer doesn't actually delete files, it just marks the space as being available - although that's of course for efficiency reasons, the point is the same: it's okay to lie to users if it helps them get through their day 😉
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label UI/UX enhancement feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#5088
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?