GitHub DigestLog in

Your GitHub inbox, swept for what needs you.

GitHub Digest reads your notifications and sorts them by what is actually waiting on you. Review requests and failed builds come first. Everything else can wait.

Log in with GitHub

Free during early access. We only ask to read your notifications and basic profile, never your code.

What your morning looks like

ExampleA sample digest, not real dataLog in to see yours

Needs you now 2

  • Review requested: Fix login redirectacme/webWaiting 3d

    You were asked to review this pull request. Check the login redirect change.

    DoneMute
  • CI failed on feature/billingacme/api

    A check failed on the billing branch. Open the run to see what broke, then fix or re-run it.

    DoneMute

Worth a look today 1

  • Mentioned in Rate limit headersacme/api

    You were mentioned in this issue. No direct question is asked of you.

    DoneMute

Can wait 1

  • New comment on Update READMEacme/docs

    A thread you follow has activity. Nothing is asked of you.

    DoneMute

Built to cut the noise

See what is waiting on you

Reviews and mentions that sit untouched for 2 days or more get flagged.

Sorted by real priority

Review requests and failed builds rise to the top. Passive activity stays out of the way.

Plain-English summaries

Each thread gets a short note on what it is actually asking of you.

Mute a thread for good

One click and a thread you don't care about stops showing up. Unmute all whenever you like.

Why not GitHub's own inbox?

GitHub's inbox lists activity as it happens. GitHub Digest works out what is waiting on you and puts that first.

FeatureGitHub inboxGitHub Digest
OrderNewest activity first, plus filters you set up yourselfReview requests, questions and failed builds first
Left waitingNo flag for threads that sit untouchedFlagged after 2 days
What a thread wantsOpen it to find outA plain-English note on your most urgent threads
NoiseUnsubscribe or mark done one thread at a timeMute a thread, unmute everything in one click

What we access and what we keep

You log in with GitHub OAuth. Here is what happens with that access. The full policy is on the privacy page.

Permissions
read:user for your username and notifications to read your notification list. The Done button uses it to mark a thread done on GitHub. We never ask for repository access, so your code stays out of reach.
AI summaries
For your most urgent threads (up to 20), the title, type, reason and repo name go to Google Gemini. Never thread contents, your token or your email.
What we store
Your GitHub username, your access token (encrypted), the IDs of threads you mute, and your email if you save one. Notifications are fetched live and their content is not kept in our database.
Leaving
Revoke access any time in GitHub under Settings, Applications. To delete what we store, email us and it is removed.