Preset Saving for Prompts and Settings #2422

New Issue

GiteaMirror · 2025-11-11T15:06:52-06:00

GiteaMirror commented

2025-11-11 15:06:52 -06:00

Originally created by @bgeneto on GitHub (Oct 21, 2024).

Feature Request

This feature request proposes the implementation of a preset saving system for prompts and custom settings in Open-webui, similar to the functionality found in LibreChat (see attached image). This would allow users to save and quickly load their preferred prompt configurations, including the system prompt and various advanced parameters.

Is your feature request related to a problem? Please describe.

Yes, the lack of a preset saving feature significantly limits the user experience in Open-webui.

Repetitive Input: Users currently need to manually re-enter their preferred prompts and adjust settings every time they use the application. This is time-consuming and inefficient, especially for complex prompts or frequently used parameter combinations.
Limited Experimentation: Without the ability to easily save and compare different prompt variations, users might be discouraged from experimenting with different settings and exploring the full potential of the model.

Describe the solution you'd like:

I propose implementing a "Save as Preset" button within the chat interface, similar to the one found in LibreChat. This button would:

Capture Current Configuration: Save the current system prompt, along with all selected advanced parameters (e.g., Temperature, Top K, Context Length) and their values.
Store Preset: Store the captured configuration as a named preset, allowing users to provide a descriptive name for easy identification.
Load Preset: Provide a mechanism for users to easily browse, select, and load saved presets, instantly applying the stored prompt and settings.

Describe alternatives you've considered:

Manual Copying and Pasting: While users can currently copy and paste prompts and settings, this is a cumbersome workaround and prone to errors. It also lacks the organization and ease of use provided by a dedicated preset system.
Waiting for Teams Feature: While the upcoming Teams feature might offer some form of preset saving, it's unclear if it will address the needs of individual users. Implementing a basic preset system now would provide immediate value to a wider user base.

Additional context:

The attached image (see bellow) illustrates a clean and user-friendly implementation of preset saving. A similar approach in Open-webui would greatly enhance the user experience by streamlining workflows, encouraging experimentation, and unlocking the full potential of the platform for all users.

Originally created by @bgeneto on GitHub (Oct 21, 2024). ## Feature Request This feature request proposes the implementation of a preset saving system for prompts and custom settings in Open-webui, similar to the functionality found in LibreChat (see attached image). This would allow users to save and quickly load their preferred prompt configurations, including the system prompt and various advanced parameters. **Is your feature request related to a problem? Please describe.** Yes, the lack of a preset saving feature significantly limits the user experience in Open-webui. * **Repetitive Input:** Users currently need to manually re-enter their preferred prompts and adjust settings every time they use the application. This is time-consuming and inefficient, especially for complex prompts or frequently used parameter combinations. * **Limited Experimentation:** Without the ability to easily save and compare different prompt variations, users might be discouraged from experimenting with different settings and exploring the full potential of the model. **Describe the solution you'd like:** I propose implementing a "Save as Preset" button within the chat interface, similar to the one found in LibreChat. This button would: 1. **Capture Current Configuration:** Save the current system prompt, along with all selected advanced parameters (e.g., Temperature, Top K, Context Length) and their values. 2. **Store Preset:** Store the captured configuration as a named preset, allowing users to provide a descriptive name for easy identification. 3. **Load Preset:** Provide a mechanism for users to easily browse, select, and load saved presets, instantly applying the stored prompt and settings. **Describe alternatives you've considered:** * **Manual Copying and Pasting:** While users can currently copy and paste prompts and settings, this is a cumbersome workaround and prone to errors. It also lacks the organization and ease of use provided by a dedicated preset system. * **Waiting for Teams Feature:** While the upcoming Teams feature might offer some form of preset saving, it's unclear if it will address the needs of individual users. Implementing a basic preset system now would provide immediate value to a wider user base. **Additional context:** The attached image (see bellow) illustrates a clean and user-friendly implementation of preset saving. A similar approach in Open-webui would greatly enhance the user experience by streamlining workflows, encouraging experimentation, and unlocking the full potential of the platform for all users. ![feature-request-openwebui](https://github.com/user-attachments/assets/9d8acb7a-9ed4-407e-a132-a90a4dffd16a)

GiteaMirror closed this issue