[PR #17550] feat: support per-model RAG template override #47516

New Issue

GiteaMirror · 2026-04-29T22:46:56-05:00

GiteaMirror commented

2026-04-29 22:46:56 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/17550
Author: @athoik
Created: 9/18/2025
Status: 🔄 Open

Base: dev ← Head: model_rag_template

📝 Commits (1)

86f33de feat: support per-model RAG template override

📊 Changes

2 files changed (+26 additions, -4 deletions)

View changed files

📝 backend/open_webui/utils/middleware.py (+6 -1)
📝 src/lib/components/workspace/Models/ModelEditor.svelte (+20 -3)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

Before submitting, make sure you've checked the following:

Target branch: Please verify that the pull request targets the dev branch.
Description: Provide a concise description of the changes made in this pull request.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Have you written and run sufficient tests to validate the changes?
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
- BREAKING CHANGE: Significant changes that may affect compatibility
- build: Changes that affect the build system or external dependencies
- ci: Changes to our continuous integration processes or workflows
- chore: Refactor, cleanup, or other non-functional code changes
- docs: Documentation update or addition
- feat: Introduces a new feature or enhancement to the codebase
- fix: Bug fix or error correction
- i18n: Internationalization or localization changes
- perf: Performance improvement
- refactor: Code restructuring for better maintainability, readability, or scalability
- style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- test: Adding missing tests or correcting existing tests
- WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Add rag_template as a configurable parameter in model settings, allowing each model to define its own RAG template instead of always using the global default.

Middleware now selects the model-specific RAG template if provided.
Model editor UI updated to allow editing and saving rag_template.
Fallback to global RAG_TEMPLATE remains when no override is set.

Added

Support per-model RAG template override

Breaking Changes

BREAKING CHANGE: NONE

Screenshots or Videos

By default the model screen will have an empty template and global rag template will be used.

We can override the default by setting our customized rag template.

Here is an example rag template, based on default, without citations.

### Task:
Respond to the user query using the provided context.

### Guidelines:
- If you don't know the answer, clearly state that.
- If uncertain, ask the user for clarification.
- Respond in the same language as the user's query.
- If the context is unreadable or of poor quality, inform the user and provide the best possible answer.
- If the answer isn't present in the context but you possess the knowledge, explain this to the user and provide the answer using your own understanding.
- Do not cite any <source> tag
- Do not use XML tags in your response.

### Output:
Provide a clear and direct response to the user's query.

<context>
{{CONTEXT}}
</context>

<user_query>
{{QUERY}}
</user_query>

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/17550 **Author:** [@athoik](https://github.com/athoik) **Created:** 9/18/2025 **Status:** 🔄 Open **Base:** `dev` ← **Head:** `model_rag_template` --- ### 📝 Commits (1) - [`86f33de`](https://github.com/open-webui/open-webui/commit/86f33de9f36a33fdc97370b1bc661300d41ca3b9) feat: support per-model RAG template override ### 📊 Changes **2 files changed** (+26 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/utils/middleware.py` (+6 -1) 📝 `src/lib/components/workspace/Models/ModelEditor.svelte` (+20 -3) </details> ### 📄 Description # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request. **Before submitting, make sure you've checked the following:** - [x] **Target branch:** Please verify that the pull request targets the `dev` branch. - [x] **Description:** Provide a concise description of the changes made in this pull request. - [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [x] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [x] **Testing:** Have you written and run sufficient tests to validate the changes? - [x] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [x] **Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry Add `rag_template` as a configurable parameter in model settings, allowing each model to define its own RAG template instead of always using the global default. - Middleware now selects the model-specific RAG template if provided. - Model editor UI updated to allow editing and saving `rag_template`. - Fallback to global `RAG_TEMPLATE` remains when no override is set. ### Added - Support per-model RAG template override ### Breaking Changes - **BREAKING CHANGE**: NONE --- ### Screenshots or Videos By default the model screen will have an empty template and global rag template will be used. <img width="1468" height="401" alt="image" src="https://github.com/user-attachments/assets/62e818bc-5d36-4aa2-a50a-fc329dc53de8" /> We can override the default by setting our customized rag template. <img width="1432" height="790" alt="image" src="https://github.com/user-attachments/assets/b3b338c7-e99a-441e-bb88-16219097605d" /> Here is an example rag template, based on default, without citations. ``` ### Task: Respond to the user query using the provided context. ### Guidelines: - If you don't know the answer, clearly state that. - If uncertain, ask the user for clarification. - Respond in the same language as the user's query. - If the context is unreadable or of poor quality, inform the user and provide the best possible answer. - If the answer isn't present in the context but you possess the knowledge, explain this to the user and provide the answer using your own understanding. - Do not cite any <source> tag - Do not use XML tags in your response. ### Output: Provide a clear and direct response to the user's query. <context> {{CONTEXT}} </context> <user_query> {{QUERY}} </user_query> ``` ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-29 22:46:56 -05:00

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#47516