-
Notifications
You must be signed in to change notification settings - Fork 66
Desktop notification on Linux when an agent is done or blocked #426
Copy link
Copy link
Open
Labels
area: agentsAgent detection, lifecycle, resume, fork, hooks, and skillsAgent detection, lifecycle, resume, fork, hooks, and skillsarea: settingsConfiguration and settings interfaceConfiguration and settings interfaceplatform: linuxLinux-specific behaviorLinux-specific behaviorstatus: needs triageNeeds maintainer review and classificationNeeds maintainer review and classification
Description
Activity
Metadata
Metadata
Assignees
Labels
area: agentsAgent detection, lifecycle, resume, fork, hooks, and skillsAgent detection, lifecycle, resume, fork, hooks, and skillsarea: settingsConfiguration and settings interfaceConfiguration and settings interfaceplatform: linuxLinux-specific behaviorLinux-specific behaviorstatus: needs triageNeeds maintainer review and classificationNeeds maintainer review and classification
What problem would this solve?
When the server runs headless (driven over UHP, with no TUI attached), nothing tells the desktop that an agent has finished or is blocked. On 0.14.2,
dbus-monitorwatchingorg.freedesktop.Notifications.Notifysaw 0 calls across a whole task cycle, and also forui notification push --level success, which shows only a TUI toast.On
main, the only desktop path is OSC 9, written to an attached client's terminal. It fires for automation outcomes and PR checks, but not for agentdoneorblocked. Thenotificationsconfig has onlysound_on_doneandsound_on_blocked, both off by default.What would you like to happen?
notifications.desktop_on_doneandnotifications.desktop_on_blocked, off by default, using the existing OSC 9 path when a client is attached.notify-sendif it is installed (ororg.freedesktop.Notifications.Notifyover D-Bus). The title would be the pane name and agent, and the body theblocked_hint.Area
agents, settings
Platform
linux
Alternatives
This fits a module well. An
[[events]] on = "pane.agent_status_changed"hook that runsnotify-sendworks today, following the same pattern asexamples/modules/agent-ping. If you would rather keep this out of core, shipping it as an example module would be enough.Related: #424. Client-side context: atqamz/hand#708 runs
notify-sendfrom its own event watcher for now.