-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[Question]: RAG-Graph Generate-Answer with history message in chat api #1472
Comments
Could you paste the picture of canvas here? |
thanks,i have added "回答时请考虑聊天历史" . Could you please add a 'number of previous messages included' setting, similar to other GPT conversation tools (e.g., NextChat)?
|
its still has problem after 12 times conversations,i have set max window size to 64,but it looks like still 12. My conversation has repeated after 12. |
@KevinHuSh,excuse, in your commit,it seems just update UI design rather than really request body? |
…nfiniflow#1487) ### What problem does this PR solve? fix: add message_history_window_size to GenerateForm infiniflow#1472 ### Type of change - [x] Bug Fix (non-breaking change which fixes an issue)
Describe your problem
"I have a very complex graph model, and in one of the processes, I connect an answer generation component with a human-computer interaction component. In this stage, I need to continuously ask the user questions, and each conversation requires the complete history of the dialogue to ensure that the next question does not repeat previous ones. Therefore, I want to know how many past conversations are appended with each API call? And whether any summarization is performed? Additionally, how can I append historical information? My prompt works fine with GPT-4o and can complete multi-turn questioning as required. However, in the ragglow-graph, after several rounds of dialogue, it starts asking repetitive questions. I am also using the GPT-4o model, but I cannot see the detailed OpenAPI POST body, so I cannot determine where the problem is."
The text was updated successfully, but these errors were encountered: