{"version":"2.1.232","anchor":"notification-dispatch-merged-into-one-helper","canonical_anchor":"notification-dispatch-merged-into-one-helper","heading":"Notification dispatch merged into one helper","tier":"notice","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/notification-dispatch-merged-into-one-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Notification dispatch merged into one helper\n\nTerminal notifications go through one path, and an unrecognised notification setting is reported as invalid.\n\n**What**\n\nThe separate branches for iterm2, kitty, ghostty and terminal-bell notifications were replaced by a single call. The `tengu_notification_method_used` event now records which notification type was used, and records the configured channel as \"invalid\" when the setting is not one of the known values.\n\n**Evidence**\n\n`tengu_notification_method_used`\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}