pdombkins shuts off Rose Lawyer's notification email

This fork moves reminders and other alerts entirely inside the product, ending notification emails altogether.

workflowintegration

pdombkins made a clear call on notification volume: task and deadline reminders first stopped going to email, then email became opt-in by notification type, and finally all notification email was switched off.

For users, the practical change is simple. Alerts still appear in the product, but Rose Lawyer no longer adds another message to the inbox. That can make the experience less noisy for teams already managing a heavy flow of legal and operational email, while placing more importance on users checking the application itself.

The intermediate approach is also worth a look for teams that want tighter control without a full shutdown: decide which kinds of alerts, if any, genuinely deserve an email.

So what Legal teams trying to reduce inbox fatigue without losing visibility of work should see how pdombkins has drawn the line.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

3 commits from pdombkins/rose_lawyer, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`3691981d`	Stop emailing task and deadline reminders; keep them in-app	Peter Dombkins	2026-08-02	↗ GitHub
commit body The daily sweep now passes skipEmail, so an overdue task raises the bell in Rose and nothing else. This is a teaching cohort of 36 working a case study that ships 49 tasks all deliberately past due, so an emailing reminder would put daily chasing mail in students' inboxes about work that is overdue by design. Done here rather than by unsetting user_profiles.email_notifications, which anyone could opt back into, and rather than LISTS_REMINDERS_DISABLED, which would take the in-app reminder with it.
`0cb4d92b`	Make notification email deny-by-default, per kind	Peter Dombkins	2026-08-02	↗ GitHub
commit body Agent run and tabular review completions are now in-app only, alongside deadline reminders. Rather than adding skipEmail at each call site, notify() now consults EMAILABLE_KINDS, so a kind added later cannot quietly start mailing 36 students because somebody forgot a flag. Emailable: regwatch (a real out-of-band alert about a regulatory change) and system (budget warnings a user wants when not signed in). Both low volume. Everything else raises the bell and stops there - a Week-8 session is several runs and reviews per student across the cohort.
`9e681f67`	Rose no longer emails any notification	Peter Dombkins	2026-08-02	↗ GitHub
commit body EMAILABLE_KINDS is now empty, so every kind - regwatch and system included - raises the in-app bell and stops there. Nothing Rose notifies about is urgent enough to be worth an inbox for a cohort of 36. The mechanism stays: re-enabling a kind is adding it back to that one set. Invitations and password setup are untouched - they go through lib/email.ts directly rather than notify(), and must keep sending, since that is how a student gets into Rose at all.

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-947.md from inside the repo you want the changes in.

⬇ Download capture-thread-947.md