feat: Add a button to save a conversation to chats when in "temporary conversation" #5925

New Issue

GiteaMirror · 2025-11-11T16:39:01-06:00

GiteaMirror commented

2025-11-11 16:39:01 -06:00

Originally created by @HannesStrohkopp on GitHub (Jul 31, 2025).

Check Existing Issues

I have searched the existing issues and discussions.

Problem Description

Cheers,

first of all I would like to express my sincere gratitude for this project. It is beyond awesome and I use it daily.

In OpenWebui, Admins can thankfully force temporary conversations as a standard mode, leading to no data being saved in the database. For new chats, users can still turn this mode of to save their upcoming chat. However, if the function is not actively turned off before starting a chat, the upcoming chat will inevitably be lost for future reference (as intended).

Desired Solution you'd like

In a lot of cases, I witness that the assessment of whether a chat is save-worthy or not may change over the course of chatting.
Usually, users like to start with a temporary chat, as they just want to get a quick answer to some superficial question or bounce some quick ideas. Here, they do not consider the potential outcome as noteworthy but just as quick throw-away info.
However, sometimes those temporary chats yield answers that are surprisingly information-rich or that might prove to be surprisingly valuable for future reference. However, in this situation, there is no way to preserve them (expect using external tools via copy+paste of course).

It would be awesome to have a button in temporary chats that allows to "Save Conversation" to the usual workspace for these (in my view quite common) cases. This should increase flexibility for users and decrease database-clutter by making it more likely for admins to force temporary chats by default.

I would love to hear your view on this, thanks. :)

Alternatives Considered

No response

Additional Context

No response

Originally created by @HannesStrohkopp on GitHub (Jul 31, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description Cheers, first of all I would like to express my sincere gratitude for this project. It is beyond awesome and I use it daily. In OpenWebui, Admins can thankfully force temporary conversations as a standard mode, leading to no data being saved in the database. For new chats, users can still turn this mode of to save their upcoming chat. However, if the function is not actively turned off before starting a chat, the upcoming chat will inevitably be lost for future reference (as intended). ### Desired Solution you'd like In a lot of cases, I witness that the assessment of whether a chat is save-worthy or not may change over the course of chatting. Usually, users like to start with a temporary chat, as they just want to get a quick answer to some superficial question or bounce some quick ideas. Here, they do not consider the potential outcome as noteworthy but just as quick throw-away info. However, sometimes those temporary chats yield answers that are surprisingly information-rich or that might prove to be surprisingly valuable for future reference. However, in this situation, there is no way to preserve them (expect using external tools via copy+paste of course). It would be awesome to have a button in temporary chats that allows to "Save Conversation" to the usual workspace for these (in my view quite common) cases. This should increase flexibility for users and decrease database-clutter by making it more likely for admins to force temporary chats by default. I would love to hear your view on this, thanks. :) ### Alternatives Considered _No response_ ### Additional Context _No response_

GiteaMirror closed this issue

2025-11-11 16:39:02 -06:00

GiteaMirror commented

2025-11-11 16:39:02 -06:00

@HannesStrohkopp commented on GitHub (Aug 18, 2025):

Thanks a lot for putting up a PR for this, @Rain6435! <3

@HannesStrohkopp commented on GitHub (Aug 18, 2025): Thanks a lot for putting up a PR for this, @Rain6435! <3

GiteaMirror commented

2025-11-11 16:39:03 -06:00

@tjbck commented on GitHub (Aug 18, 2025):

Addressed in dev!

@tjbck commented on GitHub (Aug 18, 2025): Addressed in dev!