I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
0.6.15
Ollama Version (if applicable)
n/a
Operating System
Ubuntu 22.04
Browser (if applicable)
Firefox 139.0.4
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
UserValves to be rendered for a 'Pipe' class for any login.
Actual Behavior
UserValves are not rendered for a 'Pipe' class, while Valves work fine when logged in as admin. The same code works for a 'Tool'.
Steps to Reproduce
Here's a snippet:
`
class Pipe:
class Valves(BaseModel):
"""System administrator-level configuration."""
a_debug: bool = Field(default=True, description="Enable or disable debug mode.")
pass
class UserValves(BaseModel):
"""User-level configuration (overrides Valves if set)."""
MCP_API_KEY: str = Field(
default="none",
description="API key for authenticating requests to the MCP endpoint.",
)
pass
`
In the above anything under UserValves is not rendering in the UI.
Logs & Screenshots
No errors are logged
Additional Information
Unless I am missing something about the UI/features, it appears that UserValves in general do not work for 'Pipe' as it is treated as a model and not a Tool or a function. Users don't appear to have the ability to modify 'Pipe' valves.
If this is the case:
The documentation needs to be updated so that it accurately reflects these limitations and not conflate Tools with Pipe.
It is a significant oversight in the design and should be addressed as it limits the usefulness of OwUI for use-cases more complex than playing around with a few LLMs.
Originally created by @git2212 on GitHub (Jun 28, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15379
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
0.6.15
### Ollama Version (if applicable)
n/a
### Operating System
Ubuntu 22.04
### Browser (if applicable)
Firefox 139.0.4
### 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
UserValves to be rendered for a 'Pipe' class for any login.
### Actual Behavior
UserValves are not rendered for a 'Pipe' class, while Valves work fine when logged in as admin. The same code works for a 'Tool'.
### Steps to Reproduce
Here's a snippet:
`
class Pipe:
class Valves(BaseModel):
"""System administrator-level configuration."""
a_debug: bool = Field(default=True, description="Enable or disable debug mode.")
pass
class UserValves(BaseModel):
"""User-level configuration (overrides Valves if set)."""
MCP_API_KEY: str = Field(
default="none",
description="API key for authenticating requests to the MCP endpoint.",
)
pass
`
In the above anything under UserValves is not rendering in the UI.
### Logs & Screenshots
No errors are logged
### Additional Information
Unless I am missing something about the UI/features, it appears that UserValves in general do not work for 'Pipe' as it is treated as a model and not a Tool or a function. Users don't appear to have the ability to modify 'Pipe' valves.
If this is the case:
1. The documentation needs to be updated so that it accurately reflects these limitations and not conflate Tools with Pipe.
2. It is a significant oversight in the design and should be addressed as it limits the usefulness of OwUI for use-cases more complex than playing around with a few LLMs.
GiteaMirror
added the bug label 2026-05-15 12:48:27 -05:00
I can't reproduce this issue either. UserValves for pipe functions are accessible via the Valves section in the Chat Controls sidebar.
<!-- gh-comment-id:3019506668 -->
@silentoplayz commented on GitHub (Jun 30, 2025):
I can't reproduce this issue either. UserValves for pipe functions are accessible via the `Valves` section in the `Chat Controls` sidebar.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @git2212 on GitHub (Jun 28, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15379
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.6.15
Ollama Version (if applicable)
n/a
Operating System
Ubuntu 22.04
Browser (if applicable)
Firefox 139.0.4
Confirmation
README.md.Expected Behavior
UserValves to be rendered for a 'Pipe' class for any login.
Actual Behavior
UserValves are not rendered for a 'Pipe' class, while Valves work fine when logged in as admin. The same code works for a 'Tool'.
Steps to Reproduce
Here's a snippet:
`
class Pipe:
class Valves(BaseModel):
"""System administrator-level configuration."""
`
In the above anything under UserValves is not rendering in the UI.
Logs & Screenshots
No errors are logged
Additional Information
Unless I am missing something about the UI/features, it appears that UserValves in general do not work for 'Pipe' as it is treated as a model and not a Tool or a function. Users don't appear to have the ability to modify 'Pipe' valves.
If this is the case:
@tjbck commented on GitHub (Jun 30, 2025):
Cannot reproduce, It's there.
@silentoplayz commented on GitHub (Jun 30, 2025):
I can't reproduce this issue either. UserValves for pipe functions are accessible via the
Valvessection in theChat Controlssidebar.