github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 14:39:31 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #3728] feat: Data purging Parameters #13364

New Issue
Closed
opened 2026-04-19 20:07:37 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-19 20:07:37 -05:00
Owner
Copy Link

Originally created by @Zarkhator03 on GitHub (Jul 9, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/3728

Description

This feature request aims to introduce granular control over chat lifetime and data purging parameters, both at the system-wide and user-specific levels. By providing configurable quotas, open chat limits, and chat lifetimes, we can minimize storage of unused data, optimize resource utilization, and improve overall system performance for use at scale.

Proposed Features

  • UI Fields and Database:

    • Add configurable fields to the user interface and database for:
      • Quota: Maximum allowed chat length (e.g., number of messages)
      • Open Chats: Maximum number of concurrently open chats per user
      • Chat Lifetime: Duration after which a chat is automatically deleted

  • Default Values:

    • Establish default values for automatic deletion:
      • Max Chat Length: Define a standard maximum chat length
      • Max Open Chats: Set a default limit for concurrent open chats
      • Chat Lifetime: Specify a default duration for chat expiration
    • default values editable by administrators

  • User-Specific Overrides:

    • Allow administrators to override default values for individual users, providing flexibility in managing specific user requirements or addressing resource constraints.
    • If multiple user roles are added in the future, one value can be selected per user role.
Originally created by @Zarkhator03 on GitHub (Jul 9, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/3728 ## Description This feature request aims to introduce granular control over chat lifetime and data purging parameters, both at the system-wide and user-specific levels. By providing configurable quotas, open chat limits, and chat lifetimes, we can minimize storage of unused data, optimize resource utilization, and improve overall system performance for use at scale. ## Proposed Features - **UI Fields and Database:** - Add configurable fields to the user interface and database for: - **Quota:** Maximum allowed chat length (e.g., number of messages) - **Open Chats:** Maximum number of concurrently open chats per user - **Chat Lifetime:** Duration after which a chat is automatically deleted - **Default Values:** - Establish default values for automatic deletion: - **Max Chat Length:** Define a standard maximum chat length - **Max Open Chats:** Set a default limit for concurrent open chats - **Chat Lifetime:** Specify a default duration for chat expiration - default values editable by administrators - **User-Specific Overrides:** - Allow administrators to override default values for individual users, providing flexibility in managing specific user requirements or addressing resource constraints. - If multiple user roles are added in the future, one value can be selected per user role.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#13364
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?