New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chat history is not included in the prompt (model is not aware of previous interactions) #393
Comments
Hello, I am currently facing the exact same issue. It looks
|
Anyone come up with a solution to this? |
anyone have a solution? |
Hi, @Dlas1212 I'm helping the gpt4-pdf-chatbot-langchain team manage their backlog and am marking this issue as stale. The issue involves the Could you please confirm if this issue is still relevant to the latest version of the gpt4-pdf-chatbot-langchain repository? If it is, please let the gpt4-pdf-chatbot-langchain team know by commenting on the issue. Otherwise, feel free to close the issue yourself, or it will be automatically closed in 7 days. Thank you! |
I believe this is still active right? |
@mayooear Could you please assist with the issue involving the
|
@Dlas1212 yeah the solution is to not use langchain bc it's trash. My system improved dramatically by removing langchain. |
The issue persists with this. Ticket should be re opened. When using
ConversationalRetrievalQAChain
the history if your message does not persist.Detail: I am using Externally Managed Memory, which clearly states
you can also pass the chat history in explicitly by omitting the memory option and supplying a chat_history string or array of HumanMessages and AIMessages directly into the chain.call method
When you pass in your history and ask it something along of lines of "My name is Joe", then AI will usually respond with "Hi Joe, how are you?" and if your follow up question is "What is my name?" Even when passing in the
chat_history
the AI will respond withI do not have access to that information
.The closed ticket that should be re-opened because this is not solved: #65
The text was updated successfully, but these errors were encountered: