I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
Verify Feature Scope
I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
Problem Description
When a message is sent to a channel you are a member of, and you have the Open WebUI window minimised or are on a different tab, if you miss the notification or have them disabled, you will not be alerted of the new message.
Desired Solution you'd like
A change in the window icon (favicon) or in the window title, visible even when minimised, would alert the user of a new message. This feature may be optional, controlled by a specific configuration setting that users can enable.
Alternatives Considered
Making the window blink would be even better, though I'm unsure if that is possible.
Additional Context
No response
Originally created by @daniporr on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21581
### Check Existing Issues
- [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request.
### Verify Feature Scope
- [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
### Problem Description
When a message is sent to a channel you are a member of, and you have the Open WebUI window minimised or are on a different tab, if you miss the notification or have them disabled, you will not be alerted of the new message.
### Desired Solution you'd like
A change in the window icon (favicon) or in the window title, visible even when minimised, would alert the user of a new message. This feature may be optional, controlled by a specific configuration setting that users can enable.
### Alternatives Considered
Making the window blink would be even better, though I'm unsure if that is possible.
### Additional Context
_No response_
@pr-validator-bot commented on GitHub (Feb 19, 2026):
⚠️ Invalid Issue Title
Hey @daniporr, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues.
Please update the title to reflect the content of your issue.
⚠️ Missing Issue Title Prefix
@daniporr, your issue title is missing a prefix (e.g., bug:, feat:, docs:).
Please update your issue title to include one of the following prefixes:
bug: Bug report or error you've encountered
feat: Feature request or enhancement suggestion
docs: Documentation issue or improvement request
question: Question about usage or functionality
help: Request for help or support
Example: bug: Login fails when using special characters in password
<!-- gh-comment-id:3924332635 -->
@pr-validator-bot commented on GitHub (Feb 19, 2026):
# ⚠️ Invalid Issue Title
Hey @daniporr, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues.
Please update the title to reflect the content of your issue.
---
# ⚠️ Missing Issue Title Prefix
@daniporr, your issue title is missing a prefix (e.g., `bug:`, `feat:`, `docs:`).
Please update your issue title to include one of the following prefixes:
- **bug**: Bug report or error you've encountered
- **feat**: Feature request or enhancement suggestion
- **docs**: Documentation issue or improvement request
- **question**: Question about usage or functionality
- **help**: Request for help or support
Example: `bug: Login fails when using special characters in password`
@Classic298 I don't see anywhere in #8050, and didn't see when I searched before opening this issue, the feature I mentioned in this issue.
Are you going to add it there?
<!-- gh-comment-id:3935723715 -->
@daniporr commented on GitHub (Feb 20, 2026):
@Classic298 I don't see anywhere in #8050, and didn't see when I searched before opening this issue, the feature I mentioned in this issue.
Are you going to add it there?
@daniporr i didn't close it because it necessarily already existed there but because we use those main feature tickets to track ideas related to that feature under one central issue.
Feel free to post it there.
Therefore this was marked as duplicate
<!-- gh-comment-id:3935801272 -->
@Classic298 commented on GitHub (Feb 20, 2026):
@daniporr i didn't close it because it necessarily already existed there but because we use those main feature tickets to track ideas related to that feature under one central issue.
Feel free to post it there.
Therefore this was marked as duplicate
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @daniporr on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21581
Check Existing Issues
Verify Feature Scope
Problem Description
When a message is sent to a channel you are a member of, and you have the Open WebUI window minimised or are on a different tab, if you miss the notification or have them disabled, you will not be alerted of the new message.
Desired Solution you'd like
A change in the window icon (favicon) or in the window title, visible even when minimised, would alert the user of a new message. This feature may be optional, controlled by a specific configuration setting that users can enable.
Alternatives Considered
Making the window blink would be even better, though I'm unsure if that is possible.
Additional Context
No response
@pr-validator-bot commented on GitHub (Feb 19, 2026):
⚠️ Invalid Issue Title
Hey @daniporr, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues.
Please update the title to reflect the content of your issue.
⚠️ Missing Issue Title Prefix
@daniporr, your issue title is missing a prefix (e.g.,
bug:,feat:,docs:).Please update your issue title to include one of the following prefixes:
Example:
bug: Login fails when using special characters in password@daniporr commented on GitHub (Feb 20, 2026):
@Classic298 I don't see anywhere in #8050, and didn't see when I searched before opening this issue, the feature I mentioned in this issue.
Are you going to add it there?
@Classic298 commented on GitHub (Feb 20, 2026):
@daniporr i didn't close it because it necessarily already existed there but because we use those main feature tickets to track ideas related to that feature under one central issue.
Feel free to post it there.
Therefore this was marked as duplicate