feat: option to mute messaging-gateway chat notifications
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 57/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- full-stack
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.
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_bridgeflag, 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.
- Dominant language
- Python
- Stars
- 620
- Forks
- 85
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from open-webui/computer
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-webui/computer#293 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-webui/computer#286 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
open-webui/computer#276 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-webui/computer#271 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/computer#269 · 1 comment ·
All issues in open-webui/computer
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
raullenchai/Rapid-MLX#4042 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
LearningCircuit/local-deep-research#7067 ·
Maintainers usually reply within 1 day
-
#bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
apache/superset#44923 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
lawndoc/stack-back#123 ·