You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When chatting with local docs using API server, it is not aware of what the previous question
I have a frontend UI where users can make conversation with the chatbot. I am using local API server, but discovered a critical bug, the model are not able to provide answers based on what was talked about including the local docs.
Also, the local doc that I have is just a simple text file. You can notice the local doc is retrieved only once when processing the first query regardless query content. However, the following conversation is not able to semantically bind the content from this text file.
I assume each time you send a query to the server, it is a brand new chat session so that's why no history can be preserved. Any solutions?
The text was updated successfully, but these errors were encountered:
Same problem here using here using GPT4All v3.6.1: Only the first request after startup and enabling the LocalDocs takes the reasoning from the local document. The next request takes it from the model.
This bug report describes the same issue as #3210
When chatting with local docs using API server, it is not aware of what the previous question
I have a frontend UI where users can make conversation with the chatbot. I am using local API server, but discovered a critical bug, the model are not able to provide answers based on what was talked about including the local docs.
Also, the local doc that I have is just a simple text file. You can notice the local doc is retrieved only once when processing the first query regardless query content. However, the following conversation is not able to semantically bind the content from this text file.
I assume each time you send a query to the server, it is a brand new chat session so that's why no history can be preserved. Any solutions?
The text was updated successfully, but these errors were encountered: