[GH-ISSUE #24495] feat: Per-folder/project valve overrides for Filter and Tools #74918

New Issue

GiteaMirror · 2026-05-13T07:47:21-05:00

GiteaMirror commented

2026-05-13 07:47:21 -05:00

Originally created by @akopper on GitHub (May 9, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24495

Check Existing Issues

I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

When using Folders/Projects as semantic workspaces (e.g. separate AI personas, project-scoped memory banks, domain-specific tools), there is no way to configure function/filter valves differently per folder.

Currently only two valve scopes exist:

Global (admin-set, instance-wide)
Per-user (UserValves, per individual user)

This means a memory filter like Hindsight must use the same memory bank for all folders, unless you resort to ugly workarounds like embedding a raw JSON UUID→bank mapping inside the valve itself, which requires knowing internal folder UUIDs (not exposed in the UI), has no admin interface, and breaks when folders are renamed or recreated.

Desired Solution you'd like

Add a per-folder valve override layer, configurable in the Folder settings UI, mirroring how model-level valve overrides work (see #11461 / #11553).

Merge priority (lowest → highest):

Global Valves → Folder Valves → UserValves

Alternatives Considered

UserValves: requires every user to manually reconfigure per chat session; not scalable for admin-managed workspaces.
JSON UUID map embedded in the global valve: current workaround; requires knowing internal UUIDs, no UI, fragile.
Per-model valves (#11461) — solves a related problem but doesn't map to folder-scoped workflows where the same model is used across multiple folders with different configurations.

Additional Context

Real-world scenario that motivated this request:

Using a Hindsight memory filter, each Open WebUI folder should write/read from a separate Hindsight memory bank (e.g. a "Project A" folder gets its own memory bank, a "Work" folder gets another).

Currently the only workaround is a folder_bank_map valve containing raw UUIDs. The user must find their folder UUID via the API (GET /api/v1/folders) because it is not shown anywhere in the UI.

Per-folder valves would make this a first-class, user-friendly configuration instead of a poweruser hack.

Related: #11461 (per-model valve overrides discussion), #11553 (per-model valves PR — reference implementation).

Originally created by @akopper on GitHub (May 9, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/24495 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description When using Folders/Projects as semantic workspaces (e.g. separate AI personas, project-scoped memory banks, domain-specific tools), there is no way to configure function/filter valves differently per folder. Currently only two valve scopes exist: - **Global** (admin-set, instance-wide) - **Per-user** (UserValves, per individual user) This means a memory filter like Hindsight must use the same memory bank for all folders, unless you resort to ugly workarounds like embedding a raw JSON UUID→bank mapping inside the valve itself, which requires knowing internal folder UUIDs (not exposed in the UI), has no admin interface, and breaks when folders are renamed or recreated. ### Desired Solution you'd like Add a **per-folder valve override** layer, configurable in the Folder settings UI, mirroring how model-level valve overrides work (see #11461 / #11553). **Merge priority (lowest → highest):** Global Valves → Folder Valves → UserValves ### Alternatives Considered - **UserValves**: requires every user to manually reconfigure per chat session; not scalable for admin-managed workspaces. - **JSON UUID map embedded in the global valve**: current workaround; requires knowing internal UUIDs, no UI, fragile. - **Per-model valves (#11461)** — solves a related problem but doesn't map to folder-scoped workflows where the same model is used across multiple folders with different configurations. ### Additional Context Real-world scenario that motivated this request: Using a Hindsight memory filter, each Open WebUI folder should write/read from a separate Hindsight memory bank (e.g. a "Project A" folder gets its own memory bank, a "Work" folder gets another). Currently the only workaround is a `folder_bank_map` valve containing raw UUIDs. The user must find their folder UUID via the API (`GET /api/v1/folders`) because it is not shown anywhere in the UI. Per-folder valves would make this a first-class, user-friendly configuration instead of a poweruser hack. Related: #11461 (per-model valve overrides discussion), #11553 (per-model valves PR — reference implementation).

GiteaMirror commented

2026-05-13 07:47:22 -05:00

@owui-terminator[bot] commented on GitHub (May 9, 2026):

⚠️ Missing Issue Title Prefix

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

Please update the title to lead with one of:

bug: bug report or error
feat: feature request or enhancement
docs: documentation issue
question: usage question
help: support request

Example: bug: Login fails when the password contains special characters

@owui-terminator[bot] commented on GitHub (May 9, 2026): # ⚠️ Missing Issue Title Prefix @akopper, your issue title is missing a categorising prefix (e.g. `bug:`, `feat:`, `docs:`). Please update the title to lead with one of: - **bug**: bug report or error - **feat**: feature request or enhancement - **docs**: documentation issue - **question**: usage question - **help**: support request Example: `bug: Login fails when the password contains special characters`

GiteaMirror commented

2026-05-13 07:47:23 -05:00

@owui-terminator[bot] commented on GitHub (May 9, 2026):

⚠️ Invalid Issue Title

@akopper, your issue title is too short, too few words, or a generic placeholder — it doesn't tell maintainers what's actually being reported or requested.

Please update the title to be at least 10 characters and 2 words, and to describe the actual issue. Bare placeholders like bug, feat:, or issue make triage difficult and slow down everyone.

Example: bug: Login fails when password contains special characters

@owui-terminator[bot] commented on GitHub (May 9, 2026): # ⚠️ Invalid Issue Title @akopper, your issue title is too short, too few words, or a generic placeholder — it doesn't tell maintainers what's actually being reported or requested. Please update the title to be **at least 10 characters and 2 words**, and to describe the actual issue. Bare placeholders like `bug`, `feat:`, or `issue` make triage difficult and slow down everyone. Example: `bug: Login fails when password contains special characters`

GiteaMirror commented

2026-05-13 07:47:24 -05:00

@owui-terminator[bot] commented on GitHub (May 9, 2026):

🔍 Related Issues Found

I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:

🟣 #11458 feat: override Valves per-model
This is the closest architectural match: it requests a new valve override layer with a merge priority and UI/backend support, just scoped to models instead of folders. The new issue explicitly cites it as the reference implementation and wants the same pattern applied to folders/projects.
by kaytwo
🟣 #17411 feat: valve overwrite per group
This feature asks for valve overrides per group, which is conceptually similar to per-folder overrides as another non-user scope. It supports the broader idea of adding a scoped override layer beyond global and per-user valves.
by Podden
🟣 #19179 feat: User-Specific Valves for Pipelines
This issue introduces a new scoped valve layer for pipelines at the user level, showing the project has already considered extending valves beyond the global/admin layer. While the scope differs, it is related because it addresses per-entity valve customization and the required UI/backend plumbing.
by hectorc98

💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.

This comment was generated automatically. React with 👍 if helpful, 👎 if not.

@owui-terminator[bot] commented on GitHub (May 9, 2026):  🔍 **Related Issues Found** I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions: 1. 🟣 [#11458](https://github.com/open-webui/open-webui/issues/11458) **feat: override Valves per-model** *This is the closest architectural match: it requests a new valve override layer with a merge priority and UI/backend support, just scoped to models instead of folders. The new issue explicitly cites it as the reference implementation and wants the same pattern applied to folders/projects.* *by kaytwo* 2. 🟣 [#17411](https://github.com/open-webui/open-webui/issues/17411) **feat: valve overwrite per group** *This feature asks for valve overrides per group, which is conceptually similar to per-folder overrides as another non-user scope. It supports the broader idea of adding a scoped override layer beyond global and per-user valves.* *by Podden* 3. 🟣 [#19179](https://github.com/open-webui/open-webui/issues/19179) **feat: User-Specific Valves for Pipelines** *This issue introduces a new scoped valve layer for pipelines at the user level, showing the project has already considered extending valves beyond the global/admin layer. While the scope differs, it is related because it addresses per-entity valve customization and the required UI/backend plumbing.* *by hectorc98* --- 💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead. *This comment was generated automatically.* React with 👍 if helpful, 👎 if not.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#74918