[BUG]: Differences in Behavior Between Threads API and Workspace in AnythingLLM #2526
Labels
possible bug
Bug was reported but is not confirmed or is unable to be replicated.
question
Further information is requested
How are you running AnythingLLM?
Docker (remote machine)
What happened?
Hello everyone,
I have been implementing a system over the past few months and noticed some peculiarities in the API's behavior. The main issue is that the API does not respond exactly the same way as it does within the workspace on the platform, even when using the threads API. It seems the handling is different.
Specifically, I believe the difference may be related to not considering document checks with embeddings. My system is a chat accessed externally via API. Initially, I used the workspace API (/chat), but I realized that all users were communicating in the same conversation. I solved this by creating a separate thread for each user.
However, the behavior is still not the same as inside AnythingLLM. My workspace is configured in query mode and contains documents in RAG. Another point is that the API returns too many emojis in conversations, which doesn't happen within the system.
My main question is: does the API actually handle things differently? Initially, I thought using the threads API would result in the exact same behavior, but it seems that's not the case.
Thanks in advance for any help or clarification.
Are there known steps to reproduce?
a thread in workspace with file embedded, a app calling the workspace api threads. same question, different answers.
The text was updated successfully, but these errors were encountered: