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 #1442] [BUG]: Discontinuous conversation #923

New Issue
Closed
opened 2026-02-22 18:22:13 -05:00 by yindo · 3 comments
yindo commented 2026-02-22 18:22:13 -05:00
Owner
Copy Link
Copy Source

Originally created by @chalitbkb on GitHub (May 17, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1442

How are you running AnythingLLM?

All versions

What happened?

Some issues were found: The conversation is not aligned or continuous with the previous dialogue. It seems this might be related to compiling the conversation history for the model. I checked the knowledge base, and it should provide answers based on the knowledge I have gathered.

*The first question was answered correctly, but the second question does not align with the answer to the first.

image

image

image

Are there known steps to reproduce?

No response

Originally created by @chalitbkb on GitHub (May 17, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1442 ### How are you running AnythingLLM? All versions ### What happened? Some issues were found: The conversation is not aligned or continuous with the previous dialogue. It seems this might be related to compiling the conversation history for the model. I checked the knowledge base, and it should provide answers based on the knowledge I have gathered. *The first question was answered correctly, but the second question does not align with the answer to the first. ![image](https://github.com/Mintplex-Labs/anything-llm/assets/32437546/b100dba8-23bf-4245-8fb9-463e44a3711a) ![image](https://github.com/Mintplex-Labs/anything-llm/assets/32437546/f9ff7c14-f16b-4aa5-a5a5-56220d965747) ![image](https://github.com/Mintplex-Labs/anything-llm/assets/32437546/6f328b59-b954-40f1-8368-b7718d28283e) ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:22:13 -05:00
yindo closed this issue 2026-02-22 18:22:13 -05:00
yindo commented 2026-02-22 18:22:13 -05:00
Author
Owner
Copy Link
Copy Source

@man2004 commented on GitHub (May 17, 2024):

Seems you have selected query mode? I think if you want to have previous dialogue, you need to choose conversation mode.

@man2004 commented on GitHub (May 17, 2024): Seems you have selected query mode? I think if you want to have previous dialogue, you need to choose conversation mode.
yindo commented 2026-02-22 18:22:13 -05:00
Author
Owner
Copy Link
Copy Source

@chalitbkb commented on GitHub (May 17, 2024):

Seems you have selected query mode? I think if you want to have previous dialogue, you need to choose conversation mode.

Using the "query" mode should allow for asking related questions continuously to maintain coherence. I understand that this mode queries information solely from the knowledge base. If no information is found, the response will attempt to decline and inform the user that no data was found. However, what use is it if it cannot learn from previous questions? Therefore, this mode should be improved. For example, in the attached image, I discussed the same topic but it seems that the conversation did not integrate the first question with the second one, even though they are on the same subject and asked consecutively.

Thus, in this mode, rejection will occur if no information is found as usual. But there is a condition that previous conversation data must be combined with new questions to ensure coherence about what is being discussed. Rejection should only happen after checking from the conversation that when combined with the latest question, no information can truly be found in the knowledge base. Only then should it respond to users indicating that no data was found. On the other hand, choosing "Chat" mode will attempt to find other information beyond predefined knowledge and will not reject providing any information. This would make more sense.

@chalitbkb commented on GitHub (May 17, 2024): > Seems you have selected query mode? I think if you want to have previous dialogue, you need to choose conversation mode. Using the "query" mode should allow for asking related questions continuously to maintain coherence. I understand that this mode queries information solely from the knowledge base. If no information is found, the response will attempt to decline and inform the user that no data was found. However, what use is it if it cannot learn from previous questions? Therefore, this mode should be improved. For example, in the attached image, I discussed the same topic but it seems that the conversation did not integrate the first question with the second one, even though they are on the same subject and asked consecutively. Thus, in this mode, rejection will occur if no information is found as usual. But there is a condition that previous conversation data must be combined with new questions to ensure coherence about what is being discussed. Rejection should only happen after checking from the conversation that when combined with the latest question, no information can truly be found in the knowledge base. Only then should it respond to users indicating that no data was found. On the other hand, choosing "Chat" mode will attempt to find other information beyond predefined knowledge and will not reject providing any information. This would make more sense.
yindo commented 2026-02-22 18:22:13 -05:00
Author
Owner
Copy Link
Copy Source

@Propheticus commented on GitHub (May 18, 2024):

Currently, in query mode, no historical messages are sent.
Each query is handled in isolation.

It sound like you're looking for a feature enhancement where there's a hybrid form between query and chat modes.
e.g. Query mode for the first prompt and then chat mode for subsequent messages.

@Propheticus commented on GitHub (May 18, 2024): Currently, in query mode, no historical messages are sent. Each query is handled in isolation. It sound like you're looking for a feature enhancement where there's a hybrid form between query and chat modes. e.g. Query mode for the first prompt and then chat mode for subsequent messages.
yindo changed title from [BUG]: Discontinuous conversation to [GH-ISSUE #1442] [BUG]: Discontinuous conversation 2026-06-05 14:37:58 -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 possible bug
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#923
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?