Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #2953] [FEAT]: Embed Widget limits chat history to workspace setting (or has customizable setting) #1883

New Issue
Closed
opened 2026-02-22 18:26:59 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:26:59 -05:00
Owner
Copy Link
Copy Source

Originally created by @Alminc91 on GitHub (Jan 8, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2953

Originally assigned to: @shatfield4 on GitHub.

What would you like to see?

Request / Solution:
I would like to be able to configure the chat history limit of my embed widgets. This could be either through:

  1. The embed widget simply adopts the setting of the corresponding workspace.
  2. There is an additional setting in the embed configuration. It can be a direct setting like "Max chats per day" or something like "Enable Chat history override".

Or if you advise me what the best approach could be, maybe I could try to fix it myself with a PR.

Problem:
I get more hallucinations when the chat history is set to a higher number. For example, I enable two history message in my workspace (in combination with RAG it is slow enough :D). This leads to substantially less hallucinations in the case of a longer, ongoing chat. Especially, if hallucinations happen because of ungrounded (bad RAG) data or a non-optimal prompt, the behaviour of hallucinations can accumulate. At least, so it seems,
Therefore, in order to benefit from this type of technique to reduce hallucinations, I would love to limit the chat history for the embed widget.

Example:
I ask 5 questions, always the same ones in order. Then, on the sixth question, the workspace set to two messages gives me correct information. And in general, when I continue asking about my documents (RAG), the results contain a lot less hallucinations. The quality is better.

As soon as I use the embed widget or set the chat history to 20, the chatbot starts making up additional information for the sixth question. Continuing the conversation leads to a lot of invented information.

Additional question:

  1. Is the chat history compressed, when more messages are allowed? In order to not slow down responses? Or how does it work? I have my LLM token context window set to 12.000 tokens.

Of course, I could maybe do something with prompt engineering in order to improve the behaviour with longer chat history. But I would need to experiment with that.

Thank you very much for all the amazing upgrades you do and for reacting so fast to issues! It is surely a lot of work, but the app is quite amazing. Blessings.

Originally created by @Alminc91 on GitHub (Jan 8, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2953 Originally assigned to: @shatfield4 on GitHub. ### What would you like to see? **Request / Solution**: I would like to be able to configure the chat history limit of my embed widgets. This could be either through: 1. The embed widget simply adopts the setting of the corresponding workspace. 2. There is an additional setting in the embed configuration. It can be a direct setting like "Max chats per day" or something like "Enable Chat history override". Or if you advise me what the best approach could be, maybe I could try to fix it myself with a PR. **Problem:** I get more hallucinations when the chat history is set to a higher number. For example, I enable two history message in my workspace (in combination with RAG it is slow enough :D). This leads to substantially less hallucinations in the case of a longer, ongoing chat. Especially, if hallucinations happen because of ungrounded (bad RAG) data or a non-optimal prompt, the behaviour of hallucinations can accumulate. At least, so it seems, Therefore, in order to benefit from this type of technique to reduce hallucinations, I would love to limit the chat history for the embed widget. **Example:** I ask 5 questions, always the same ones in order. Then, on the sixth question, the workspace set to two messages gives me correct information. And in general, when I continue asking about my documents (RAG), the results contain a lot less hallucinations. The quality is better. As soon as I use the embed widget or set the chat history to 20, the chatbot starts making up additional information for the sixth question. Continuing the conversation leads to a lot of invented information. **Additional question:** 1. Is the chat history compressed, when more messages are allowed? In order to not slow down responses? Or how does it work? I have my LLM token context window set to 12.000 tokens. Of course, I could maybe do something with prompt engineering in order to improve the behaviour with longer chat history. But I would need to experiment with that. Thank you very much for all the amazing upgrades you do and for reacting so fast to issues! It is surely a lot of work, but the app is quite amazing. Blessings.
yindo added the enhancementfeature request labels 2026-02-22 18:26:59 -05:00
yindo closed this issue 2026-02-22 18:26:59 -05:00
yindo commented 2026-02-22 18:26:59 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 10, 2025):

closed by https://github.com/Mintplex-Labs/anything-llm/pull/4114

@timothycarambat commented on GitHub (Jul 10, 2025): closed by https://github.com/Mintplex-Labs/anything-llm/pull/4114
yindo changed title from [FEAT]: Embed Widget limits chat history to workspace setting (or has customizable setting) to [GH-ISSUE #2953] [FEAT]: Embed Widget limits chat history to workspace setting (or has customizable setting) 2026-06-05 14:43:15 -04:00
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 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#1883
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?