From a80ce9b5feafa3891b1694587b45a14d0e312f8f Mon Sep 17 00:00:00 2001 From: Timothy Jaeryang Baek Date: Tue, 18 Mar 2025 07:15:57 -0700 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 22c11db..b08a7d4 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!** +> **Do NOT use 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.