mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 03:18:23 -05:00
[GH-ISSUE #1068] feat: Notification System for JWT Token Expiration, Model Availability Updates, & Model Deprecation Updates #27849
Reference in New Issue
Block a user
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?
Originally created by @silentoplayz on GitHub (Mar 6, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/1068
Is your feature request related to a problem? Please describe.
Currently, there is no way for users to be notified if their JWT token is about to expire or when models become available or unavailable due to admin-initiated model updates. This can lead to unexpected session terminations and missed opportunities for user engagement.
Describe the solution you'd like
I would like for Open WebUI to include a notification system that alerts users if their JWT token is about to expire, notifies them when new models become available due to admin-initiated model updates, and informs them if a model is no longer available. This feature would enhance the user experience by providing timely information and reducing the need for manual checks.
Describe alternatives you've considered
I have considered manually checking for JWT token expiration and model availability, but this would not provide a scalable or automated solution and would require manual intervention. Users may often forget what models were available for them to use in the first place, due to the nature of model naming schemes. User's can not also check when their JWT token is about to expire.
Additional context
I propose implementing a notification system for JWT token expiration and model availability to enhance the user experience and encourage engagement with new models and features. This feature would include:
Benefits
This feature would provide a more user-friendly experience that respects user preferences and encourages engagement with new models and features. It would also reduce user frustration due to unexpected session terminations and increase user engagement through timely notifications of new model availability and model deprecation.