Your GitHub work, in views you define.
Hush keeps your GitHub searches live as views. It groups them by your role, status, project, or your own sections, and pushes only the facts that you choose: a review request, failing CI, a reply.
Free while in beta · Open source, AGPL‑3.0
hush 
Updated 1m ago
Hush nowA working demo with real pull requests and issues from PostHog/posthog.com. Change Group by, click a row, or use J K to move and E to snooze.
A view is a search that stays live.
Write a search with GitHub’s words, such as review-requested:@me, and add
Hush’s own: size:<100, -author:bots, or a category. GitHub
runs its part, and Hush checks the rest.
The view stays current. When GitHub sends a notification about an item, Hush reads it
again. Write @today-14d and the date moves with you.
is:open review-requested:@me updated:>@today-14d 38 found -author:bots size:<100 9 kept - Keep community profile actions in the window bottom bar 67 lines
chore(pages): move components out of src/pages 23 lines
Replace avatar fallback with DrakeHog 4 lines- and 6 more
Group it your way.
Each view puts its list into sections: by your role, by where the review stands, by the columns of a project board, by a category, or by sections that you write yourself. Each row says whose turn it is, and work that waits too long turns amber.
How Group by worksA push for the facts that you choose.
Turn on the facts that matter to you. A view can push its new items too. Everything else stays quiet.
- Review requested (on)
- Mentioned (on)
- Replied (on)
- Approved (on)
- Changes requested (on)
- CI failed (on)
- Assigned (on)
- A snooze ends (on)
- Team review requested (off)
- CI passed (off)
- New in a view (off)
- One push for each item. An item pushes once, then waits until you open it.
- Snooze until it happens. Snooze until CI passes or a review comes in. Hush pushes when it does.
- Digests and limits. Collect pushes into one every 5 to 240 minutes, or cap how many can come in a set time.
- Quiet hours. Nights and weekends stay silent. One push in the morning lists what waited.
@rafaeelaudibert 
@rubychilds Approve, reply, merge. Without leaving.
Press Space to peek at a pull request or issue: the checks, the reviews, the files, and the conversation. Approve, request changes, comment with @mentions, # links, and :emoji, or merge. Your draft waits if you close it.
Not now? E snoozes until there is new activity, S until tomorrow, M mutes, and U marks it unread. They stay in Hush.
Hush writes to GitHub only when you do.
The peek, step by stepCategories, by rule or by Jev.
Give each item an effort and an impact, or any group of categories that you make. A
category takes a one-line rule, such as author:dependabot*, or a few words
that Jev, a decision model, reads to place your PRs and issues. Group a view by a
category, or use category: in a search.
Shape every part.
Every command has a key that you can change, and every menu and swipe is yours to order.
Views, categories, keys, and pushes all live in one settings.json that you can
edit, export, or hand to an agent.
Open source. Free while in beta.
The app, the server, and this site are on GitHub under AGPL‑3.0. Read what Hush does with your token, or run your own copy on your own Cloudflare account. Hush has no analytics. Apart from the services it runs on, only TypeSafe's Jev model reads your PRs and issues, for smart decisions, and you can turn those off.
Hush is free while it is in beta. Paid plans are not open yet.
Questions
What is Hush for GitHub?
Hush is a web app for the pull requests and issues that you work on. Each view is a GitHub search that stays live, grouped your way. Hush shows whose turn it is on each item, pushes only the facts that you choose, and lets you read, approve, comment, and merge in a side panel.
Is it free?
Hush is free while it is in beta. Paid plans are not open yet. See pricing for the plans that come after the beta.
What access does it need?
You sign in with GitHub. Hush asks for the notifications, repo, read:org, and project scopes, because GitHub’s Notifications API accepts only classic scopes. Hush stores the token encrypted, and it acts on GitHub only when you do. See GitHub access and security.
Does it change my GitHub notifications?
No. Hush reads your notifications only to see what changed, and it never marks them read or done. Snooze, mute, and unread stay in Hush. See views and GitHub notifications.
Does my org need to approve it?
Only if your org allows just the OAuth apps that an owner approved. Until an owner approves Hush, GitHub hides that org from it. Choose Request approval after you sign in, or, until then, give Hush a custom token, such as the one from gh auth token. See when an org is missing.
Does it work on my phone?
Yes. Hush is a web app that you can install, with push alerts on each device where you turn them on. On iPhone and iPad, push works only after you add Hush to the Home Screen (iOS 16.4 or later): Share, then Add to Home Screen. See notifications.
Is it open source? Can I host it myself?
Yes. All of Hush, the app, the server, and this site, is open source under AGPL‑3.0, at github.com/ianmatson/hush. You can run your own copy on your own Cloudflare account; the README tells you how.
How is it different from GitHub’s own inbox?
GitHub’s inbox lists notifications by time. Hush starts from your work instead: searches that you choose, grouped by your role, status, a project board, or your own sections, with whose turn it is on each item. It pushes only the facts that you turn on. Use both: Hush never changes GitHub’s inbox. See Hush vs. GitHub notifications and other tools.
joethreepwood opened this · 3h
Adds a customer case study for Juno, an AI health assistant for people who live with chronic illness, with cross-links from the customer pages.
👍 3🚀 1