0.6.42

.gitattributes

@@ -0,0 +1 @@
+* text=auto eol=lf

.gitignore

@@ -18,3 +18,7 @@
 npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
+
+# Local Node environment
+.local_node
+node.zip

docs/faq.mdx

@@ -39,22 +39,42 @@ The same principles apply in harsh terrestrial settings, including submarines, p
 
 ### Q: Why isn't my Open WebUI updating? I've re-pulled/restarted the container, and nothing changed.
 
-**A:** Updating Open WebUI requires more than just pulling the new Docker image. Here’s why your updates might not be showing and how to ensure they do:
+**A:** To update Open WebUI, you must first pull the latest image, then stop and remove the existing container, and finally start a new one. Simply pulling the image isn't enough because the running container is still based on the old version.
 
-1. **Updating the Docker Image**: The command `docker pull ghcr.io/open-webui/open-webui:main` updates the Docker image but not the running container or its data.
-2. **Persistent Data in Docker Volumes**: Docker volumes store data independently of container lifecycles, preserving your data (like chat histories) through updates.
-3. **Applying the Update**: Ensure your update takes effect by removing the existing container (which doesn't delete the volume) and creating a new one with the updated image and existing volume attached.
+**Follow these exact steps:**
 
-This process updates the app while keeping your data safe.
+1. **Pull the latest image:**
+   ```bash
+   docker pull ghcr.io/open-webui/open-webui:main
+   ```
+2. **Stop and Remove the current container:**
+   ```bash
+   docker stop open-webui
+   docker rm open-webui
+   ```
+3. **Start the new container with your data attached:**
+   ```bash
+   docker run -d -p 3000:8080 -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main
+   ```
+
+*(Note: If your container or volume has a different name, adjust the commands accordingly.)*
+
+For a deeper dive into update methods (including automated updates like Watchtower), check our full **[Updating Guide](/getting-started/updating)**.
 
 ### Q: Wait, why would I delete my container? Won't I lose my data?
 
-**A:** It's a common concern, but deleting a container doesn't mean you'll lose your data, provided you're using Docker volumes correctly. Here’s why:
+**A:** In Docker, containers are meant to be "disposable." Your data is safe **only if you have a Volume configured**. 
+
+:::danger Important: Data Persistence
+If you ran your container *without* the `-v open-webui:/app/backend/data` flag (or a similar volume mount in Docker Compose), your data is stored **inside** the container. In that specific case, deleting the container **will result in permanent data loss**. 
+
+Always ensure you follow our **[Quick Start Guide](/getting-started/quick-start)** correctly to set up persistent volumes from the beginning.
+:::
 
-- **Volumes Preserve Data**: Docker volumes are designed to persist data outside of container lifecycles. As long as your data is stored in a volume, it remains intact, regardless of what happens to the container.
-- **Safe Update Process**: When updating Open WebUI, removing the old container and creating a new one with the updated image does not affect the data stored in volumes. The key is not to explicitly delete the volume with commands like `docker volume rm`.
+When you use a Volume (typically named `open-webui` in our examples), your data stays safe even when the container is deleted. When you start a new container and mount that same volume, the new version of the app attaches to your old data automatically.
 
-By following the correct update steps—pulling the new image, removing the old container without deleting the volume, and creating a new container with the updated image and the existing volume—your application code is updated while your data remains unchanged and safe.
+**Default Data Path:** 
+On most Linux systems, your volume data is physically stored at: `/var/lib/docker/volumes/open-webui/_data`.
 
 ### Q: Should I use the distro-packaged Docker or the official Docker package?
 
@@ -84,6 +104,14 @@ Everything you need to run Open WebUI, including your data, remains within your
 
 **A:** If your Open WebUI isn't launching post-update or installation of new software, it's likely related to a direct installation approach, especially if you didn't use a virtual environment for your backend dependencies. Direct installations can be sensitive to changes in the system's environment, such as updates or new installations that alter existing dependencies. To avoid conflicts and ensure stability, we recommend using a virtual environment for managing the `requirements.txt` dependencies of your backend. This isolates your Open WebUI dependencies from other system packages, minimizing the risk of such issues.
 
+### Q: I updated/restarted and now I'm being logged out, or getting "Error decrypting tokens" for my tools?
+
+**A:** This happens because you haven't set a persistent `WEBUI_SECRET_KEY` in your environment variables.
+*   **Logouts:** Without this key, Open WebUI generates a random one every time it starts. This invalidates your previous session cookies (JWTs), forcing you to log in again.
+*   **Decryption Errors:** Essential secrets (like OAuth tokens for MCP tools or API keys) are encrypted using this key. If the key changes on restart, Open WebUI cannot decrypt them, leading to errors.
+
+**Fix:** Set `WEBUI_SECRET_KEY` to a constant, secure string in your Docker Compose or environment config.
+
 ### Q: I updated/restarted and now my login isn't working anymore, I had to create a new account and all my chats are gone.
 
 **A:** This issue typically arises when a Docker container is created without mounting a volume for `/app/backend/data` or if the designated Open WebUI volume (usually named `open-webui` in our examples) was unintentionally deleted. Docker volumes are crucial for persisting your data across container lifecycles. If you find yourself needing to create a new account after a restart, it's likely you've initiated a new container without attaching the existing volume where your data resides. Ensure that your Docker run command includes a volume mount pointing to the correct data location to prevent data loss.

docs/features/audio/text-to-speech/chatterbox-tts-api-integration.md

@@ -176,6 +176,8 @@ For local development, you can run the API and frontend separately:
 cd frontend && npm install && npm run dev
 ```
 
+> **Note:** If you encounter dependency issues, try running `npm install --force` instead of just `npm install`.
+
 Click the link provided from Vite to access the web UI.
 
 ### Build for Production
@@ -186,6 +188,8 @@ Build the frontend for production deployment:
 cd frontend && npm install && npm run build
 ```
 
+> **Note:** If the build fails due to dependency conflicts, try using `npm install --force`.
+
 You can then access it directly from your local file system at `/dist/index.html`.
 
 ### Port Configuration

docs/features/auth/scim.mdx

@@ -191,4 +191,4 @@ SCIM works best when combined with SSO (Single Sign-On). A typical setup include
 
 This ensures users are automatically created and can immediately authenticate using their corporate credentials.
 
-For SSO configuration, see the [SSO documentation](https://docs.openwebui.com/features/auth/).
+For SSO configuration, see the [SSO documentation](https://docs.openwebui.com/features/auth/sso/).

docs/features/auth/sso/index.mdx

@@ -17,11 +17,11 @@ Check out our [troubleshooting guide](https://docs.openwebui.com/troubleshooting
 
 :::
 
-:::danger
-
-Right now, you can only configure one OAUTH provider at a time.
-You cannot have Microsoft **and** Google as providers simultaneously.
+:::danger Only One OIDC Provider Supported
+Right now, you can only configure **one** OpenID Connect (OIDC) provider at a time via `OPENID_PROVIDER_URL`.
+You cannot have Microsoft **and** Google as OIDC providers simultaneously.
 
+*However, there is a community workaround for using both! See our [Dual OAuth Tutorial](/tutorials/tips/dual-oauth-configuration) for more details.*
 :::
 
 ## OAuth Configuration Overview
@@ -120,6 +120,7 @@ The following environment variables are used:
 1. `OAUTH_PROVIDER_NAME` - Name of the provider to show on the UI, defaults to SSO
 1. `OAUTH_SCOPES` - Scopes to request. Defaults to `openid email profile`
 1. `OPENID_REDIRECT_URI` - The redirect URI configured in your OIDC application. This must be set to `<open-webui>/oauth/oidc/callback`.
+1. `OAUTH_AUDIENCE` - Optional `audience` value that will be passed to the oauth provider's authorization endpoint as an additional query parameter.
 
 :::warning
 
@@ -130,6 +131,9 @@ The following environment variables are used:
 
 :::
 
+:::tip Community Workaround: Multi-Provider OAuth
+If you need to support both Microsoft and Google simultaneously, check out our **[Dual OAuth Configuration Tutorial](/tutorials/tips/dual-oauth-configuration)**. 
+:::
 ### OAuth Role Management
 
 Any OAuth provider that can be configured to return roles in the access token can be used to manage roles in Open WebUI.

docs/features/channels/index.md

@@ -9,6 +9,35 @@ title: "Channels"
 Channels is currently a **Beta** feature. Functionality is subject to change, and it must be explicitly enabled by an Administrator before it appears in the interface.
 :::
 
+## Channel Types
+
+Open WebUI supports three types of channels:
+
+| Type | Description |
+|------|-------------|
+| **Standard** | Traditional topic-based channels with public or private visibility |
+| **Group** | Membership-based channels where users explicitly join as members |
+| **Direct Message** | Private one-on-one or multi-user conversations |
+
+### Group Channels
+
+Group channels are collaboration spaces where:
+- Users explicitly join as members rather than accessing through permissions
+- Support public or private visibility
+- Can automatically include members from specified user groups
+- Channel managers can add or remove members through the channel info modal
+
+### Direct Message Channels
+
+Direct Message (DM) channels enable private conversations:
+- One-on-one or multi-user private messaging
+- Automatic deduplication for existing conversations
+- Optional channel naming
+- Display participant avatars instead of channel icons
+- Can be hidden from sidebar while preserving message history
+- Automatically reappear when new messages arrive
+- Show online/offline status indicator for participants
+
 ## Enabling Channels
 
 By default, the Channels feature may be hidden. An **Admin** must enable it globally for the instance.
@@ -22,12 +51,19 @@ By default, the Channels feature may be hidden. An **Admin** must enable it glob
 
 ## Creating a Channel
 
+:::note
+Channel creation is restricted to administrators only by default.
+:::
+
 1. Locate the **Channels** header in the sidebar.
 2. Click the **(+) Plus** icon next to the "Channels" header.
-3. **Name:** Enter a channel name (e.g., `general`, `python-dev`). Spaces should get converted to hyphens.
-4. **Access Control:**
-   * **Public:** All registered users on your Open WebUI instance can see and join this channel.
-   * **Private/Group Access:** Only you or users with permission can access this channel.
+3. **Select Channel Type:** Choose Standard, Group, or Direct Message.
+4. **Name:** Enter a channel name (e.g., `general`, `python-dev`). Spaces are converted to hyphens.
+5. **Access Control:**
+   * **Public:** All registered users can see and join this channel.
+   * **Private/Group Access:** Only you or users with permission can access.
+   * For Group channels, select which user groups to auto-include.
+   * For DM channels, use the user selection interface to choose participants.
 
 ## Using Channels
 
@@ -79,22 +115,33 @@ If a user **does not** have access to view a linked channel (e.g., `#admin-only`
 
 Hover over any message in the timeline to access interaction options:
 
-* **Add Reaction:** Click the **Smiley Face** icon to add a visual emoji eaction to a message.
-* **Reply:** Quotes the message within the main channel stream, linking your response to the original message while keeping it visible to everyone in the main flow.
-* **Reply in Thread:** Starts a separate, nested conversation thread centered on that specific message. This allows for focused discussions without cluttering the main channel history.
-* **Edit:** Click the **Pencil** icon to modify the content of your message.
-* **Delete:** Click the **Trash** icon to remove the message from the channel.
+* **Add Reaction:** Click the **Smiley Face** icon to add an emoji reaction. Hovering over reactions shows the names of users who reacted (up to 3 names plus a count for additional reactors).
+* **Pin Message:** Pin important messages for easy reference. Pinned messages are highlighted and accessible via a dedicated modal in the navbar.
+* **Reply:** Quotes the message within the main channel stream.
+* **Reply in Thread:** Starts a separate, nested conversation thread.
+* **Edit:** Click the **Pencil** icon to modify your message.
+* **Delete:** Click the **Trash** icon to remove the message.
 
 :::note
 Currently, reactions are purely visual and do not influence model behavior.
 :::
 
+### File Attachments
+
+Channels support file sharing:
+
+* **Paste from clipboard:** Images and files can be pasted directly using Ctrl+V / Cmd+V
+* **Drag and drop:** Drag files directly into the message input
+* **Image processing:** AI models in channels can view and analyze shared images
+
 ### Collaboration
 
 If your Open WebUI instance supports multiple users:
 
-* **Real-time updates:** Messages appear instantly for all users currently viewing the channel.
-* **Shared Context:** When a teammate asks an AI a question, the AI's response becomes part of the context for the *next* user's query. This allows teams to iterate on AI outputs together.
+* **Real-time updates:** Messages appear instantly using optimistic UI rendering.
+* **Shared Context:** AI responses become part of the context for subsequent queries.
+* **Unread indicators:** Visual badges show unread message counts in the sidebar.
+* **User list:** Click to view all users with access to the channel.
 
 ## Managing Channels
 
@@ -106,9 +153,17 @@ To manage an existing channel:
 2. Click the **Gear (Edit)** icon.
 
 :::info
-Only the Channel Creator or an Admin can delete a channel.
+Channel creators can edit and delete their own group and DM channels without administrator privileges. Standard channels require admin access.
 :::
 
+### Permissions
+
+Channels support granular access control:
+
+* **Write access:** Required for posting, editing, and deleting messages
+* **Read-only access:** Users can view content but cannot contribute
+* **Feature toggle:** Administrators can control channel access via `USER_PERMISSIONS_FEATURES_CHANNELS` environment variable or group permissions in the admin panel
+
 ## Use Cases
 
 ### 1. Team Development (`#dev-team`)

docs/features/chat-features/autocomplete.md

@@ -0,0 +1,70 @@
+---
+sidebar_position: 10
+title: "Autocomplete"
+---
+
+# ✨ Autocomplete
+
+Open WebUI offers an **AI-powered Autocomplete** feature that suggests text completions in real-time as you type your prompt. It acts like a "Copilot" for your chat input, helping you craft prompts faster using your configured task model.
+
+## How It Works
+
+When enabled, Open WebUI monitors your input in the chat box. When you pause typing, it sends your current text to a lightweight **Task Model**. This model predicts the likely next words or sentences, which appear as "ghost text" overlaying your input.
+
+- **Accept Suggestion**: Press `Tab` (or the `Right Arrow` key) to accept the suggestion.
+- **Reject/Ignore**: Simply keep typing to overwrite the suggestion.
+
+:::info
+**Performance Recommendation**
+
+Autocomplete functionality relies heavily on the response speed of your **Task Model**. We recommend using a small, fast, **non-reasoning** model to ensure suggestions appear instantly.
+
+**Recommended Models:**
+- **Llama 3.2** (1B or 3B)
+- **Qwen 3** (0.6B or 3B)
+- **Gemma 3** (1B or 4B)
+- **GPT-5 Nano** (Optimized for low latency)
+
+Avoid using "Reasoning" models (e.g., o1, o3) or heavy Chain-of-Thought models for this feature, as the latency will make the autocomplete experience sluggish.
+:::
+
+## Configuration
+
+The Autocomplete feature is controlled by a two-layer system: **Global** availability and **User** preference.
+
+### 1. Global Configuration (Admin)
+
+Admins control whether the autocomplete feature is available on the server.
+
+### 1. Configuring Autocomplete (Global)
+
+**Admin Panel Settings:**
+Go to **Admin Settings > Interface > Task Model** and toggle **Autocomplete Generation**.
+
+### 2. User Configuration (Personal)
+
+Even if enabled globally, individual users can turn it off for themselves if they find it distracting.
+
+- Go to **Settings > Interface**.
+- Toggle **Autocomplete Generation**.
+
+:::note
+If the Admin has disabled Autocomplete globally, users will **not** be able to enable it in their personal settings.
+:::
+
+## Performance & Troubleshooting
+
+### Why aren't suggestions appearing?
+1. **Check Settings**: Ensure it is enabled in **both** Admin and User settings.
+2. **Task Model**: Go to **Admin Settings > Interface** and verify a **Task Model** is selected. If no model is selected, the feature cannot generate predictions.
+3. **Latency**: If your Task Model is large or running on slow hardware, predictions might arrive too late to be useful. Switch to a smaller model.
+4. **Reasoning Models**: Ensure you are **not** using a "Reasoning" model (like o1 or o3), as their internal thought process creates excessive latency that breaks real-time autocomplete.
+
+### Performance Impact
+Autocomplete sends a request to your LLM essentially every time you pause typing (debounced).
+- **Local Models**: This can consume significant GPU/CPU resources on the host machine.
+- **API Providers**: This will generate a high volume of API calls (though usually with very short token counts). Be mindful of your provider's **Rate Limits** (Requests Per Minute/RPM and Tokens Per Minute/TPM) to avoid interruptions.
+
+:::warning
+For multi-user instances running on limited local hardware, we recommend **disabling** Autocomplete to prioritize resources for actual chat generation.
+:::

docs/features/chat-features/code-execution/artifacts.md

@@ -100,3 +100,15 @@ Example Project: Develop a prototype for a new e-commerce website using HTML, CS
 - Benefits: Create interactive stories with scrolling effects, animations, and other interactive elements. Open WebUI's Artifacts enable you to refine the story and test different versions.
 
 Example Project: Build an interactive story about a company's history, using scrolling effects and animations to engage the reader. Use targeted updates to refine the story's narrative and Open WebUI's version selector to test different versions.
+
+## Troubleshooting
+
+### Artifacts Preview Not Working (Uncaught SecurityError)
+
+If you encounter an issue where the code preview in the chat interface does not appear and you see an error like `Artifacts.svelte:40 Uncaught SecurityError` in the browser console, this is commonly caused by cross-origin iframe restrictions in certain environment configurations.
+
+**Solution:**
+
+1. Go to **Settings > Interface**.
+2. Toggle on **Allow Iframe Sandbox Same-Origin Access**.
+3. Save your settings.

docs/features/chat-features/index.mdx

@@ -15,4 +15,6 @@ Open WebUI provides a comprehensive set of chat features designed to enhance you
 
 - **[⚙️ Chat Parameters](./chat-params.md)**: Control system prompts and advanced parameters at different levels (per-chat, per-account, or per-model).
 
+- **[✨ Autocomplete](./autocomplete.md)**: AI-powered text prediction that helps you write prompts faster using a task model.
+
 - **[🗨️ Chat Sharing](./chatshare.md)**: Share conversations locally or via the Open WebUI Community platform with controllable privacy settings.

docs/features/chat-features/url-params.md

@@ -79,6 +79,7 @@ The following table lists the available URL parameters, their function, and exam
 - **How to Set**: Set this parameter to `true` for a temporary chat session.
 - **Example**: `/?temporary-chat=true`
 - **Behavior**: This initiates a disposable chat session without saving history or applying advanced configurations.
+  - **Note**: Document processing in temporary chats is frontend-only for privacy. Complex files requiring backend parsing (e.g., DOCX) may not be fully supported.
 
 ### 9. **Code Interpreter**