From 10662e224c2bde94ffd9cc56208c8d9d1c70f2ae Mon Sep 17 00:00:00 2001 From: Timothy Jaeryang Baek Date: Thu, 20 Feb 2025 11:33:33 -0800 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index eea6f65..22c11db 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@ # Pipelines: UI-Agnostic OpenAI API Plugin Framework > [!TIP] -> You probably **don't** need Pipelines! +> **You probably don't need Pipelines!** > > 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.