Replies: 1 comment
|
I support this. System notification (macos in my case) doesn't allow customizations so it uses a generic system, so herdr notification is the best alternative for me, but it needs more customization options |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
idea / problem
I’m using
ui.toast.delivery = "herdr"because it’s the only notification mode that can take me to the exact workspace/tab/pane.What feels awkward today is:
open_notification_targetonly works for the currently visible notification targetA lot of the time I notice the toast, move to click it, and it’s already gone. And if several background notifications arrive
close together, there isn’t a good keyboard-first way to work through them in order.
requested change
I’d like Herdr to support two things:
open_notification_targetnavigationFor the toast duration, something like this would help:
A sticky mode would also be useful, so the toast could stay until clicked or dismissed.
For open_notification_target, I’d like it to walk through retained notification targets in the order they appeared.
Example:
Then repeated open_notification_target presses would go:
Exact config or action naming is not important. The main request is:
why you want this
delivery = "herdr"is much better thansystemnotifications because it can jump to the right pane, but the current toastlifetime is short and there’s no good sequential way to triage multiple background notifications.
This would make multi-agent workflows much smoother, especially when several agents finish or block around the same time.
All reactions