github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 10:58:17 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #22553] issue: @mentions in channels do not work with direct connections #19744

New Issue
Closed
opened 2026-04-20 02:15:06 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-20 02:15:06 -05:00
Owner
Copy Link

Originally created by @mattserrano on GitHub (Mar 11, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22553

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.8.10

Ollama Version (if applicable)

No response

Operating System

macOS Sequoia (client) / Debian 13

Browser (if applicable)

Firefox

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

A user with a direct connection configured should be able to "@mention" a model in a channel after selecting it from the model list.

Actual Behavior

Models that are setup as direct connections do not reply in channels when they are mentioned.

A 404 XHR request is visible, but no request appears to be sent from the browser to the configured endpoint.

Steps to Reproduce

  1. Start with clean Debian install.
  2. Install Docker
  3. Run OpenWebUI as a docker container with channels docker run -d -p 3000:8080 -v open-webui:/app/backend/data --name open-webui ghcr.io/open-webui/open-webui:main -e USER_PERMISSIONS_FEATURES_CHANNELS=True -e ENABLE_DIRECT_CONNECTIONS=True
  4. Run ollama or llama-server with at least one model served
  5. Setup a direct connection for the user (verifying the connection & confirming models appear and can be prompted outside of channels)
  6. Create a new channel and "@mention" the model configured as a direct connection, observe no response

Logs & Screenshots

Image

Additional Information

No response

Originally created by @mattserrano on GitHub (Mar 11, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22553 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.8.10 ### Ollama Version (if applicable) _No response_ ### Operating System macOS Sequoia (client) / Debian 13 ### Browser (if applicable) Firefox ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior A user with a direct connection configured should be able to "@mention" a model in a channel after selecting it from the model list. ### Actual Behavior Models that are setup as direct connections do not reply in channels when they are mentioned. A 404 XHR request is visible, but no request appears to be sent from the browser to the configured endpoint. ### Steps to Reproduce 1. Start with clean Debian install. 2. Install Docker 3. Run OpenWebUI as a docker container with channels docker run -d -p 3000:8080 -v open-webui:/app/backend/data --name open-webui ghcr.io/open-webui/open-webui:main -e USER_PERMISSIONS_FEATURES_CHANNELS=True -e ENABLE_DIRECT_CONNECTIONS=True 4. Run ollama or llama-server with at least one model served 5. Setup a direct connection for the user (verifying the connection & confirming models appear and can be prompted outside of channels) 6. Create a new channel and "@mention" the model configured as a direct connection, observe no response ### Logs & Screenshots <img width="1796" height="1147" alt="Image" src="https://github.com/user-attachments/assets/0a755a02-a450-4cab-9c02-e5c5bf3ed0d9" /> ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-20 02:15:06 -05:00
GiteaMirror commented 2026-04-20 02:15:07 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Mar 11, 2026):

either intended or a feature request, not a Bug.

CC @tjbck

<!-- gh-comment-id:4037359594 --> @Classic298 commented on GitHub (Mar 11, 2026): either intended or a feature request, not a Bug. CC @tjbck
GiteaMirror commented 2026-04-20 02:15:08 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Mar 11, 2026):

Intended, should be filtered out.

<!-- gh-comment-id:4041634701 --> @tjbck commented on GitHub (Mar 11, 2026): Intended, should be filtered out.
GiteaMirror commented 2026-04-20 02:15:08 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Mar 11, 2026):

Addressed in dev.

<!-- gh-comment-id:4041719419 --> @tjbck commented on GitHub (Mar 11, 2026): Addressed in dev.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#19744
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?