Static AppName on the Linux daemon path groups all notifications in GNOME; entries collapse to icon-only
#130 建立於 2026年8月8日
倉庫指標
- 星標
- (759 顆星)
- PR 合併指標
- (PR 指標待抓取)
描述
Environment: plugin v1.40.1 (commit 74b9fba), Fedora 44, GNOME Shell 50.4 on Wayland, click-to-focus daemon path.
Symptom: in GNOME's notification list (calendar dropdown), plugin notifications collapse into one grouped source showing effectively icon-only entries — the rich per-event titles/bodies ("✅ Task Completed [session, project]") aren't visible until the group is manually expanded. Users read this as "notifications have no description".
Cause: the daemon path sends a constant identity on every call — AppName: "claude-notifications" (internal/daemon/server.go, handleNotification()), plus the same fixed desktop-entry hint — so GNOME Shell groups everything under one source. Notably, the beeep fallback path already avoids exactly this: it randomizes AppName per call, with the comment "Use unique AppName to prevent notification grouping/replacement, allowing multiple notifications to be displayed simultaneously" (internal/notifier/notifier.go). The daemon path — the one that actually runs whenever the daemon is healthy — never got the same treatment.
Suggested fix: apply the beeep path's uniqueness approach to the daemon path (or make grouping behavior configurable). If grouping is considered desirable GNOME UX, consider at least documenting the asymmetry between the two paths.