mirror of
https://github.com/open-webui/pipelines.git
synced 2026-11-05 01:37:24 +00:00
[GH-ISSUE #49] feat: Keeping Threads of Conversatiosn separate in interactions #36
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-webui/pipelines#36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @MarlNox on GitHub (Jun 3, 2024).
Original GitHub issue: https://github.com/open-webui/pipelines/issues/49
It seems that the pipes, will take any input from any of the chat windows, and will "merge" the content in the backend.
We need to keep the conversation threads separate, so that there's no cross sending of messages or mixup of threads.
We need a method to identify the conversation threads, and keep them separate.
@tjbck commented on GitHub (Jun 3, 2024):
Not entirely understanding your use case but
chat_idgets sent by Open WebUI!@MarlNox commented on GitHub (Jun 3, 2024):
I was using the OpenAI pipeline in the examples and it wasnt sending any data on the chat_id.
Using the api does, im currently streamlining the responses to the frontend.
EDIT: Just noticed the OpenAi Manifold does hold chatid.