Merge main into dev

Author: Classic298

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,17 @@
+## Summary
+
+<!-- Briefly describe what this PR changes and why it benefits Open WebUI users. -->
+
+## Related issue or discussion
+
+<!-- Link the issue or discussion this PR resolves, if one exists. -->
+
+## Checklist
+
+- [ ] I have reviewed the relevant documentation and matched the existing style.
+- [ ] This PR meets Open WebUI's contribution standards: it is accurate, relevant to users, narrowly scoped, maintainable, and not promotional content, advertising, lead generation, SEO placement, or a request to list a product, service, provider, integration, gateway, tool, or company primarily for visibility.
+- [ ] I understand that PRs that do not meet these standards may be closed without review and will not be merged. Repeated, low-quality, off-topic, promotional, or intentionally misleading submissions may result in the contributor being blocked from future participation in Open WebUI repositories.
+
+## Notes for reviewers
+
+<!-- Add screenshots, validation steps, or other context reviewers should know. -->

docs/features/chat-conversations/audio/text-to-speech/openai-tts-integration.md

@@ -112,6 +112,62 @@ services:
 | `AUDIO_TTS_MODEL` | TTS model (`tts-1` or `tts-1-hd`) | `tts-1` |
 | `AUDIO_TTS_VOICE` | Voice to use | `alloy` |
 
+## Using OpenRouter as a Text-to-Speech Provider
+
+Open WebUI's `OpenAI` TTS engine is compatible with any service that implements the OpenAI Audio API, including [OpenRouter](https://openrouter.ai). This section explains how to configure OpenRouter as your TTS provider and how to avoid a common `400 Bad Request` error.
+
+### Why the 400 Error Happens
+
+OpenRouter's [`/audio/speech` endpoint](https://openrouter.ai/docs/guides/overview/multimodal/tts) defaults `response_format` to `pcm` when the field is omitted. Open WebUI does not send `response_format` in its request payload, so OpenRouter returns raw PCM audio, which Open WebUI cannot play back — resulting in a `400 Bad Request`.
+
+The fix is to explicitly request MP3 by adding `{"response_format": "mp3"}` to the **OpenAI Params** field (extra parameters) in the TTS settings.
+
+### Quick Setup (UI)
+
+1. Click your **profile icon** (bottom-left corner)
+2. Select **Admin Panel**
+3. Click **Settings** → **Audio** tab → **Text-to-Speech Settings**
+4. Configure the following:
+
+| Setting | Value |
+|---------|-------|
+| **Text-to-Speech Engine** | `OpenAI` |
+| **API Base URL** | `https://openrouter.ai/api/v1` |
+| **API Key** | Your OpenRouter API key (`sk-or-...`) |
+| **TTS Model** | Any OpenRouter TTS model, e.g. `openai/tts-1` |
+| **TTS Voice** | Choose from available voices |
+| **OpenAI Params** | `{"response_format": "mp3"}` |
+
+:::important
+
+The **OpenAI Params** field must contain `{"response_format": "mp3"}`. Without it, OpenRouter defaults to `pcm`, and speech requests fail with a `400 Bad Request` error.
+:::
+
+5. Click **Save**
+
+### Environment Variables Setup
+
+If you prefer to configure via environment variables, add the parameters JSON via `AUDIO_TTS_OPENAI_PARAMS`:
+
+```yaml
+services:
+  open-webui:
+    image: ghcr.io/open-webui/open-webui:main
+    environment:
+      - AUDIO_TTS_ENGINE=openai
+      - AUDIO_TTS_OPENAI_API_BASE_URL=https://openrouter.ai/api/v1
+      - AUDIO_TTS_OPENAI_API_KEY=sk-or-...
+      - AUDIO_TTS_MODEL=openai/tts-1
+      - AUDIO_TTS_VOICE=alloy
+      - AUDIO_TTS_OPENAI_PARAMS={"response_format":"mp3"}
+    # ... other configuration
+```
+
+:::info
+
+OpenRouter supports `mp3` and `pcm` output formats. Always select `mp3` in Open WebUI — PCM output is intended for real-time streaming pipelines and cannot be played back by Open WebUI.
+:::
+
 ## Testing TTS
 
 1. Start a new chat

docs/features/extensibility/mcp.mdx

@@ -141,7 +141,7 @@ No configuration is needed on the Open WebUI side: the resource indicator is dis
 
 If an OAuth 2.1 tool is set as a default and the user hasn't previously authenticated (or their refresh token has expired), the tool call will fail with **"Failed to connect to MCP server"** because the backend cannot initiate the browser-based auth flow mid-request.
 
-**Workaround:** Users should manually enable OAuth 2.1 tools per-chat via the **➕** button in the chat input area. This triggers the auth flow before the tool is ever invoked. Token refresh works automatically once the initial authentication is complete.
+**Workaround:** Users should manually enable OAuth 2.1 tools per-chat via the **Integrations** menu in the chat input area. This triggers the auth flow before the tool is ever invoked. Token refresh works automatically once the initial authentication is complete.
 :::
 
 ### Connection URLs

docs/features/extensibility/plugin/tools/index.mdx

@@ -83,7 +83,7 @@ Never import a Tool you don’t recognize or trust. These are Python scripts and
 🔧 Once installed or connected, here’s how to enable them for your conversations:
 
 ### Option 1: Enable on-the-fly (Specific Chat)
-While chatting, click the **➕ (plus)** icon in the input area. You’ll see a list of available Tools, and you can enable them specifically for that session.
+While chatting, click the **Integrations** icon in the input area (the four-diamond icon next to the ➕ button), then select **Tools**. You’ll see a list of available Tools, and you can toggle them on specifically for that session.
 
 ### Option 2: Enable by Default (Global/Model Level)
 1. Go to **Workspace ➡️ Models**.

docs/features/extensibility/plugin/tools/openapi-servers/open-webui.mdx

@@ -151,15 +151,15 @@ If you've connected a Global Tool Server (i.e., one that's admin-configured), it
 Instead:
 
 - Global tools are hidden by default and must be explicitly activated per user.
-- To enable them, you'll need to click on the ➕ button in the message input area (bottom left of the chat box), and manually toggle on the specific global tool(s) you want to use.
+- To enable them, you'll need to click on the **Integrations** button in the message input area (bottom left of the chat box, next to the ➕ button), select **Tools**, and manually toggle on the specific global tool(s) you want to use.
 
 Here's what that looks like:
 
 ![Global Tool Server Message Input](/images/openapi-servers/open-webui/global-message-input.png)
 
 ⚠️ Important Notes for Global Tool Servers:
 
-- They will not show up in the tool indicator popup until enabled from the ➕ menu.
+- They will not show up in the tool indicator popup until enabled from the **Integrations** menu.
 - Each global tool must be individually toggled on to become active inside your current chat.
 - Once toggled on, they function the same way as user tools.
 - Admins can control access to global tools via role-based permissions.