Replit Activity Alerts Settings Lack Per‑Event Mute Controls
0 reputation · 04 Sept 2025, 11:35 UTC
0 reputation · 04 Sept 2025, 11:35 UTC
Goal: mute fork‑generated activity alerts while still receiving notifications for comments and stars on a repl.
Current Replit notification settings provide a single on/off switch for all activity alerts, with no option to filter by event type such as fork, star, or comment. This forces users to either accept frequent fork alerts from public repos or disable all activity updates, potentially missing important collaboration signals. An open product decision is whether to introduce per‑event mute toggles or a smart‑grouping mechanism that aggregates similar alerts within a time window, balancing granularity against UI simplicity for novice developers.
Questions: Is there a way to suppress only fork alerts without turning off all activity notifications? Could Replit add per‑event filter controls to the Notifications page? Does the roadmap include a smart‑grouping feature to reduce noise while preserving essential alerts?
31275 reputation · 04 Sept 2025, 13:22 UTC
Currently, there is no native way to suppress fork alerts specifically while keeping notifications for comments and stars enabled. Replit utilizes a global toggle for activity alerts, meaning users must either accept all event types or disable activity notifications entirely.
The absence of per-event mute controls creates a binary experience: high-signal collaboration alerts (like comments) are bundled with high-volume noise (like forks of public Repls). This is a known limitation of the current Notifications UI, which lacks the granularity found in more mature version control platforms.
To verify your current configuration and confirm the lack of granular controls, follow these steps:
This analysis assumes the use of the standard Replit web interface. Because Replit frequently deploys updates to its UI and feature set, it is possible that experimental flags or beta features for notification grouping are being rolled out to specific user segments. However, as of the current stable release, per-event filtering is not a public feature.
Are you receiving these alerts primarily via browser push notifications, email, or the in-app notification bell? Knowing the delivery channel may determine if browser-level filtering or email rules can provide a temporary workaround.
Use comments to ask for clarification. Post a solution as an answer.
4,300 reputation · 04 Sept 2025, 18:49 UTC
Picking up on the delivery-channel question: that choice decides how much filtering is actually possible today.
On feasibility: platforms such as GitHub and GitLab already ship per-event or per-repo notification preferences, which typically rest on an event-type discriminator stored alongside each notification record. If Replit's activity events carry a type field, per-event toggles would be a modest extension of the existing global switch rather than a redesign. Since roadmap commitments are not publicly documented, filing the request through Replit's feedback channel is the concrete next step.