feature: Disable Chat History #1158

New Issue

2025-11-11T14:38:54-06:00

GiteaMirror commented

2025-11-11 14:38:54 -06:00

Originally created by @StammesOpfer on GitHub (Jun 6, 2024).

I host a small instance with a couple shared users and auto login (single user mode). I would like to ensure that users are not seeing each others chats. Separate logins is not an option currently

I would like an option to either globally set chat history to off, or set the default behavior to off, or for chat history setting to be stored server side (it appears to be stored client side).

I am not terribly concerned about chat history getting reenabled, but an environment variable that disables chat history completely would be ideal.

Originally created by @StammesOpfer on GitHub (Jun 6, 2024). I host a small instance with a couple shared users and auto login (single user mode). I would like to ensure that users are not seeing each others chats. Separate logins is not an option currently I would like an option to either globally set chat history to off, or set the default behavior to off, or for chat history setting to be stored server side (it appears to be stored client side). I am not terribly concerned about chat history getting reenabled, but an environment variable that disables chat history completely would be ideal.

GiteaMirror closed this issue

2025-11-11 14:38:55 -06:00

GiteaMirror commented

2025-11-11 14:38:55 -06:00

@justinh-rahb commented on GitHub (Jun 6, 2024):

Single user mode is exactly that, meant for a single local user. Seperate logins and chat history storage is the default behavior that's been disabled here. I think the default setting is more appropriate for your use case. A password is not a high barrier to use, you can enter it one time and as long as you set WEBUI_SECRET_KEY environment variable to a static value, your session will stay logged in forever, in between container restarts or replacement.

@justinh-rahb commented on GitHub (Jun 6, 2024): Single user mode is exactly that, meant for a single _local_ user. Seperate logins and chat history storage is the **default** behavior that's been disabled here. I think the default setting is more appropriate for your use case. A password is not a high barrier to use, you can enter it one time and as long as you set `WEBUI_SECRET_KEY` environment variable to a static value, your session will stay logged in forever, in between container restarts or replacement.

GiteaMirror referenced this issue

2026-04-19 19:15:51 -05:00

[GH-ISSUE #1158] RAG breaks on larger pdf/txt/doc file #12366

GiteaMirror referenced this issue

2026-04-25 02:38:41 -05:00

[GH-ISSUE #1158] RAG breaks on larger pdf/txt/doc file #27894

GiteaMirror referenced this issue

2026-05-05 11:47:21 -05:00

[GH-ISSUE #1158] RAG breaks on larger pdf/txt/doc file #51031

GiteaMirror referenced this issue

2026-05-12 23:15:21 -05:00

[GH-ISSUE #1158] RAG breaks on larger pdf/txt/doc file #66970