open-webui / open-webui/computer

feat: option to mute messaging-gateway chat notifications

Open
#255 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
569
Forks
79
PR merge metrics
No merged PRs in 30d

Description

feat: option to mute messaging-gateway chat notifications

Feature description

Conversations that arrive via messaging gateways (Discord, WhatsApp, Telegram)
generate in-app toasts, browser notifications, sidebar unread badges, and
tab-bar unread dots. When the user is already reading (and replying to) those
conversations in the platform UI itself, the mirrored gateway notifications
are pure noise.

Proposed solution

A user preference (toggle under Settings → Notifications) that silences
notification surfaces for gateway chats when the user reads them in the UI:

  • no in-app toast, no browser notification
  • no sidebar unread badge
  • no tab-bar unread dot

The chats themselves remain fully visible and functional — only the
notification mirroring is suppressed.

Implementation notes
  • Unread counting accepts an exclude_bridge flag, driven by the user's persisted preference.
  • The chat's "done" socket event can carry a flag for gateway chats so the client can skip toasts for chats it hasn't loaded.
Additional context

Implemented on a fork; can share implementation notes.


Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Settings → Notifications preference, unread counting with the exclude_bridge flag, and the chat "done" socket event described in the issue. Done means gateway chats can be read normally while their toasts, browser notifications, sidebar badges, and tab-bar dots are suppressed according to the persisted preference.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
57/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.