github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 10:58:17 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

feat: AI workflows #2259

New Issue
Open
opened 2025-11-11 15:03:29 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-11 15:03:29 -06:00
Owner
Copy Link

Originally created by @tjbck on GitHub (Oct 1, 2024).

Originally assigned to: @tjbck on GitHub.

Orchestration layer

Originally created by @tjbck on GitHub (Oct 1, 2024). Originally assigned to: @tjbck on GitHub. Orchestration layer
GiteaMirror added the enhancementcore labels 2025-11-11 15:03:29 -06:00
GiteaMirror commented 2025-11-11 15:03:29 -06:00
Author
Owner
Copy Link

@g4challenge commented on GitHub (Oct 16, 2024):

Nice Idea and probably very useful - yet have you thought about incorporating langgraph? This would maybe help reuse the probably most frequently used graph/multiagent tooling to be used for workflows.

@g4challenge commented on GitHub (Oct 16, 2024): Nice Idea and probably very useful - yet have you thought about incorporating `langgraph`? This would maybe help reuse the probably most frequently used graph/multiagent tooling to be used for workflows.
GiteaMirror commented 2025-11-11 15:03:30 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Oct 16, 2024):

Will not be using any third party implementation here, this will also have to be accompanied by a node based editor.

@tjbck commented on GitHub (Oct 16, 2024): Will not be using any third party implementation here, this will also have to be accompanied by a node based editor.
GiteaMirror commented 2025-11-11 15:03:30 -06:00
Author
Owner
Copy Link

@PlebeiusGaragicus commented on GitHub (Nov 5, 2024):

You don't have to incorporate langgraph - they seem to be piggybacking on the Assistants API 'standard.' If that is the orchestration layer you're talking about, then it could enable a whole category of third party implementations.

I'm not sure that pipelines in their current form are well-suited for the Assistants API.

What are your thoughts on this "orchestration layer?"

@PlebeiusGaragicus commented on GitHub (Nov 5, 2024): You don't have to incorporate `langgraph` - they seem to be piggybacking on the Assistants API 'standard.' If that is the orchestration layer you're talking about, then it could enable a whole category of third party implementations. I'm not sure that pipelines in their current form are well-suited for the Assistants API. What are your thoughts on this "orchestration layer?"
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label core enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#2259
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?