Skip to content

Notifications: no late summary when a cooldown ends - #332

Merged
fylorn merged 1 commit into
devfrom
notices-no-late-summary
Oct 13, 2026
Merged

fylorn merged 1 commit into
devfrom
notices-no-late-summary

Conversation

@fylorn

@fylorn fylorn commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

A one-off event (a blocked tool call, a security rule match) pops once, then cools down for five minutes. At the end of the cooldown, repeats from that window were summed up in a second notification, which arrived minutes after the request or session it described had finished.

Now repeats during the cooldown only update the in-app list (count, unread) and the delivered notification in place, quietly. Nothing is sent when the cooldown ends; the next occurrence after it pops at once. The sum_up timer, the unsaid counter and summed_up are removed, and the tests that asserted the late summary now assert that nothing comes late.

🤖 Generated with Claude Code

A one-off event (a blocked tool call, a security rule match) pops once and
then cools down for five minutes. When the cooldown ended, any repeats in
that window were summed up in a second notification, which arrived minutes
after the request or session it described had finished. Repeats now only
update the in-app list (count, unread) and the delivered notification in
place, quietly; once the cooldown is over, the next occurrence pops at once.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@fylorn
fylorn merged commit b92cded into dev Oct 13, 2026
6 checks passed
@fylorn
fylorn deleted the notices-no-late-summary branch October 13, 2026 09:53
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 13, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant