github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-17 17:02:01 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #21952] bug:Workspace Tools (Custom Plugins) fail to inject into model context in v0.8.5 (Docker on Ubuntu 25.10) #74227

New Issue
Closed
opened 2026-05-13 06:56:04 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-05-13 06:56:04 -05:00
Owner
Copy Link

Originally created by @MCQSJ on GitHub (Feb 28, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21952

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.5

Ollama Version (if applicable)

未使用

Operating System

Host: Windows 11 | Container OS: Ubuntu 25.10

Browser (if applicable)

Microsoft Edge 145.0.3800.82

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

After importing custom Python tools (either self-written or from the Community Library) and enabling them in the Model settings or Chat interface, the tool definitions should be injected into the LLM's context. The model should recognize these tools, list them when asked, and successfully invoke them during conversation. This functionality worked correctly in previous versions of Open WebUI before my recent update.

Actual Behavior

Since updating directly to v0.8.5 (from an older working version), Workspace Tools (Custom Plugins) are completely missing from the model's context, despite being successfully imported and enabled.

Import Status: Both self-written Python tools and multiple recently updated tools downloaded from the Community Library import successfully without any errors.
Visibility: When enabling these tools via the Workspace > Models editor or the chat input toolbar, they appear toggled "ON" in the UI.
Model Awareness: However, when chatting, the model claims it only has access to the built-in Code Interpreter. It does not see or list any of the custom Workspace Tools.
Execution Failure: Consequently, the model cannot call any custom tools.
Scope: This issue occurs across multiple different models (tested with various frontier and local models).
Logs: There are no error messages in the Docker logs or Browser Console. The system silently fails to inject the tool schemas.
Regression: This feature was fully functional in my previous Open WebUI installation prior to this update.

Steps to Reproduce

Environment Setup:
Host OS: Windows 11 running Ubuntu 25.10 (via WSL2).
Docker Installation: Open WebUI v0.8.5 (Updated directly from a previous working version).
Browser: Microsoft Edge 145.0.3800.82.
Tool Import:
Navigate to Workspace > Tools.
Action A: Create and save a simple custom Python tool (e.g., a "Hello World" function).
Action B: Go to the Community Library, select multiple recently updated tools, and click "Get" / "Import".
Observation: All tools import successfully with no error messages.
Enable Tools:
Method A (Global): Go to Workspace > Models, edit a target model, scroll to the "Tools" section, and enable the newly imported custom tools. Save changes.
Method B (Per-Chat): Start a new chat, click the + icon in the input bar, and toggle the custom tools to "ON".
Verification & Testing:
Start a conversation with the configured model.
Prompt: "What tools do you currently have access to? Please list them all."
Result: The model responds stating it only has access to the Code Interpreter. It makes no mention of the custom Workspace Tools.
Prompt: "Use the [Name of Custom Tool] to perform [Task]."
Result: The model refuses or states it cannot find the tool, proceeding to answer without tool usage.
Cross-Model Testing:
Repeat steps 3-4 with multiple different models (e.g., gemini-3-pro, glm-5, qwen3.5-plus).
Result: The behavior is identical across all tested models; custom tools are never recognized.

Logs & Screenshots

No errors or exceptions found in docker logs

Image

Additional Information

No response

Originally created by @MCQSJ on GitHub (Feb 28, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/21952 ### 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.5 ### Ollama Version (if applicable) 未使用 ### Operating System Host: Windows 11 | Container OS: Ubuntu 25.10 ### Browser (if applicable) Microsoft Edge 145.0.3800.82 ### 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 After importing custom Python tools (either self-written or from the Community Library) and enabling them in the Model settings or Chat interface, the tool definitions should be injected into the LLM's context. The model should recognize these tools, list them when asked, and successfully invoke them during conversation. This functionality worked correctly in previous versions of Open WebUI before my recent update. ### Actual Behavior Since updating directly to v0.8.5 (from an older working version), Workspace Tools (Custom Plugins) are completely missing from the model's context, despite being successfully imported and enabled. Import Status: Both self-written Python tools and multiple recently updated tools downloaded from the Community Library import successfully without any errors. Visibility: When enabling these tools via the Workspace > Models editor or the chat input toolbar, they appear toggled "ON" in the UI. Model Awareness: However, when chatting, the model claims it only has access to the built-in Code Interpreter. It does not see or list any of the custom Workspace Tools. Execution Failure: Consequently, the model cannot call any custom tools. Scope: This issue occurs across multiple different models (tested with various frontier and local models). Logs: There are no error messages in the Docker logs or Browser Console. The system silently fails to inject the tool schemas. Regression: This feature was fully functional in my previous Open WebUI installation prior to this update. ### Steps to Reproduce Environment Setup: Host OS: Windows 11 running Ubuntu 25.10 (via WSL2). Docker Installation: Open WebUI v0.8.5 (Updated directly from a previous working version). Browser: Microsoft Edge 145.0.3800.82. Tool Import: Navigate to Workspace > Tools. Action A: Create and save a simple custom Python tool (e.g., a "Hello World" function). Action B: Go to the Community Library, select multiple recently updated tools, and click "Get" / "Import". Observation: All tools import successfully with no error messages. Enable Tools: Method A (Global): Go to Workspace > Models, edit a target model, scroll to the "Tools" section, and enable the newly imported custom tools. Save changes. Method B (Per-Chat): Start a new chat, click the + icon in the input bar, and toggle the custom tools to "ON". Verification & Testing: Start a conversation with the configured model. Prompt: "What tools do you currently have access to? Please list them all." Result: The model responds stating it only has access to the Code Interpreter. It makes no mention of the custom Workspace Tools. Prompt: "Use the [Name of Custom Tool] to perform [Task]." Result: The model refuses or states it cannot find the tool, proceeding to answer without tool usage. Cross-Model Testing: Repeat steps 3-4 with multiple different models (e.g., gemini-3-pro, glm-5, qwen3.5-plus). Result: The behavior is identical across all tested models; custom tools are never recognized. ### Logs & Screenshots No errors or exceptions found in docker logs <img width="1850" height="1863" alt="Image" src="https://github.com/user-attachments/assets/17b7f093-f13b-4f73-b60c-04d635ad5878" /> ### Additional Information _No response_
GiteaMirror added the bug label 2026-05-13 06:56:04 -05:00
GiteaMirror commented 2026-05-13 06:56:15 -05:00
Author
Owner
Copy Link

@pr-validator-bot commented on GitHub (Feb 28, 2026):

⚠️ Missing Issue Title Prefix

@MCQSJ, your issue title is missing a prefix (e.g., bug:, feat:, docs:).

Please update your issue title to include one of the following prefixes:

  • bug: Bug report or error you've encountered
  • feat: Feature request or enhancement suggestion
  • docs: Documentation issue or improvement request
  • question: Question about usage or functionality
  • help: Request for help or support

Example: bug: Login fails when using special characters in password

<!-- gh-comment-id:3976246654 --> @pr-validator-bot commented on GitHub (Feb 28, 2026): # ⚠️ Missing Issue Title Prefix @MCQSJ, your issue title is missing a prefix (e.g., `bug:`, `feat:`, `docs:`). Please update your issue title to include one of the following prefixes: - **bug**: Bug report or error you've encountered - **feat**: Feature request or enhancement suggestion - **docs**: Documentation issue or improvement request - **question**: Question about usage or functionality - **help**: Request for help or support Example: `bug: Login fails when using special characters in password`
GiteaMirror commented 2026-05-13 06:56:15 -05:00
Author
Owner
Copy Link

@MCQSJ commented on GitHub (Feb 28, 2026):

Tested it; external tools cannot be used properly even after import.

Image
<!-- gh-comment-id:3976367130 --> @MCQSJ commented on GitHub (Feb 28, 2026): Tested it; external tools cannot be used properly even after import. <img width="720" height="1045" alt="Image" src="https://github.com/user-attachments/assets/da602c9f-2370-43a7-8f71-ab8f98697bd6" />
GiteaMirror commented 2026-05-13 06:56:15 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Feb 28, 2026):

This is the tenth duplicate issue.

PLEASE
USE
THE
SEARCH
!

this is fixed in dev

<!-- gh-comment-id:3976731036 --> @Classic298 commented on GitHub (Feb 28, 2026): This is the tenth duplicate issue. PLEASE USE THE SEARCH ! this is fixed in dev
GiteaMirror commented 2026-05-13 06:56:15 -05:00
Author
Owner
Copy Link

@MCQSJ commented on GitHub (Feb 28, 2026):

Sorry, I tried searching several times but couldn't find any related feedback, so I created this issue.

<!-- gh-comment-id:3976751426 --> @MCQSJ commented on GitHub (Feb 28, 2026): Sorry, I tried searching several times but couldn't find any related feedback, so I created this issue.
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#74227
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?