[GH-ISSUE #900] feat: persist settings to local instance (not in browser's local storage) #27775

New Issue

GiteaMirror · 2026-04-25T02:32:47-05:00

GiteaMirror commented

2026-04-25 02:32:47 -05:00

Originally created by @mherrmann3 on GitHub (Feb 25, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/900

Describe the solution you'd like
I expected that once I define my settings (such as default model, system prompt, advanced parameters, title generation prompt, etc.), they apply to my user profile. But if I login to my user profile/instance from another device, they are gone and I have the set them anew—they are stored in the browser's local storage (settings key). I'm not sure if this is intended, but having already a user profile, I thought it's more intuitive and practical to save those settings on the instance.

Describe alternatives you've considered
If current behavior is intended, I could imagine having a "settings sync" button, which:

(over)writes current settings in/to the profile/instance (but shows a warning message/popup before doing so);
pulls those settings from the instance if no (local) settings are made yet (which the user can enforce by clearing site data with the browser).

Additional context
Possibly related: #619

Originally created by @mherrmann3 on GitHub (Feb 25, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/900 **Describe the solution you'd like** I expected that once I define my settings (such as default model, system prompt, advanced parameters, title generation prompt, etc.), they apply to my user profile. But if I login to my user profile/instance from another device, they are gone and I have the set them anew—they are stored in the browser's local storage (`settings` key). I'm not sure if this is intended, but having already a user profile, I thought it's more intuitive and practical to save those settings on the instance. **Describe alternatives you've considered** If current behavior is intended, I could imagine having a "settings sync" button, which: * (over)writes current settings in/to the profile/instance (but shows a warning message/popup before doing so); * pulls those settings from the instance **if** no (local) settings are made yet (which the user can enforce by clearing site data with the browser). **Additional context** Possibly related: #619

GiteaMirror closed this issue

2026-04-25 02:32:48 -05:00

GiteaMirror commented

2026-04-25 02:32:49 -05:00

@tjbck commented on GitHub (Feb 25, 2024):

You can utilise modelfiles feature to save the preset on the backend!

@tjbck commented on GitHub (Feb 25, 2024): You can utilise modelfiles feature to save the preset on the backend!

GiteaMirror commented

2026-04-25 02:32:50 -05:00

@mherrmann3 commented on GitHub (Feb 27, 2024):

Thanks, Timothy! Yes, I use model files to specify some model parameters for specific models.
But I believe that model files do not fully address this issue:

they do not store the default model, system prompt, title generation prompt, etc.;
if one prefers a general set of model parameters (temperature, top_p, etc.), one would need to create a model file for each model - possible, but tedious.

I just witnessed (accidentally) another reason for persisting the settings to the local instance: settings are lost when the browser clears the data.¹

Yes, one could set an exception for localhost - or the corresponding URL when accessing Open WebUI remotely - in the browser, but many users may not know this. ↩︎

@mherrmann3 commented on GitHub (Feb 27, 2024): Thanks, Timothy! Yes, I use model files to specify some model parameters for specific models. But I believe that model files do not fully address this issue: * they do not store the default model, system prompt, title generation prompt, etc.; * if one prefers a _general_ set of model parameters (temperature, top_p, etc.), one would need to create a model file for _each_ model - possible, but tedious. I just witnessed (accidentally) another reason for persisting the settings to the local instance: settings are lost when the browser clears the data.[^1] [^1]: Yes, one could set an exception for localhost - or the corresponding URL when accessing Open WebUI remotely - in the browser, but many users may not know this.

GiteaMirror commented

2026-04-25 02:32:52 -05:00

@tjbck commented on GitHub (Apr 12, 2024):

Closing in favour of #1022

@tjbck commented on GitHub (Apr 12, 2024): Closing in favour of #1022

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