mirror of
https://github.com/open-webui/docs
synced 2025-05-19 02:42:15 +00:00
wording
Signed-off-by: thiswillbeyourgithub <26625900+thiswillbeyourgithub@users.noreply.github.com>
This commit is contained in:
parent
0ff06a7912
commit
46742a374c
@ -20,7 +20,7 @@ import { TopBanners } from "@site/src/components/TopBanners";
|
||||
# Pipelines: UI-Agnostic OpenAI API Plugin Framework
|
||||
|
||||
:::warning
|
||||
**DO NOT USE PIPELINES!**
|
||||
**DO NOT USE PIPELINES IF!**
|
||||
|
||||
If your goal is simply to add support for additional providers like Anthropic or basic filters, you likely don't need Pipelines . For those cases, Open WebUI Functions are a better fit—it's built-in, much more convenient, and easier to configure. Pipelines, however, comes into play when you're dealing with computationally heavy tasks (e.g., running large models or complex logic) that you want to offload from your main Open WebUI instance for better performance and scalability.
|
||||
:::
|
||||
|
Loading…
Reference in New Issue
Block a user