GitHub notification badge not showing? Here are the 6 real causes

Updated August 2026 · 5 min read

You know notifications exist — you can see them on github.com — but the badge count on your app icon or menu bar stays empty, or never appears at all. Work through this list: one of these six things explains almost every missing GitHub notification badge.

1. Web notifications are disabled in your GitHub settings

Badges are driven by GitHub's notification settings, not by the app you're looking at. Go to Settings → Notifications on github.com and make sure "Web and mobile" is enabled for the events you care about (Participating, Mentions, etc.). If everything is set to email only, there is nothing for any badge to count.

2. You're watching too few repos

A badge only counts threads you're subscribed to. If you only watch repos you own, activity in your team's shared repos will never light it up. On each repo page choose Watch → All Activity, or use the Watching dashboard to bulk-adjust what you follow.

3. macOS: the app isn't allowed to show badges

On a Mac, open System Settings → Notifications, select the app in question, and check that Badges is toggled on and notification style isn't set to "None". Also check Dock & Menu Bar settings if you expect the count in the menu bar rather than on the Dock icon.

4. Browser tab badges need permission

Browser extensions and web apps that show a count on the tab or toolbar icon typically need both of these:

1. A valid Personal Access Token with the notifications scope (fine-grained tokens must include Notifications permissions).
2. Permission to run on the current site, if the badge lives on the github.com tab itself.

If you recently regenerated your token, the old one is revoked silently — the badge goes dark without an error message. Generate a new token and paste it into the extension or app's settings.

5. The count is cached and stale

Many clients poll on an interval and cache results. A badge that shows an old number (or zero) long after you've handled things is usually just a stale cache. Force a manual refresh in the app; if that doesn't clear it, sign out and back in so it re-reads your unread list from the API.

6. You read them on another device

Marking a notification as read anywhere — phone, browser, another machine — marks it read everywhere. If you skim notifications in your email or on github.com during the day, the badge on your desktop will legitimately show zero when you get home. That's correct behavior, not a bug.

Still no badge?

Check whether notifications arrive at all by visiting github.com/notifications directly. If items appear there but nowhere else, the delivery chain between GitHub and your client is the problem — almost always item 1, 3 or 4 above. If items don't appear there either, the problem is upstream in your watching and subscription settings (items 1–2).