block / block/buzz

macOS notification clicks do not route to the target message

Open
#3,509 3 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Rust
Stars
32.7k
Forks
4.3k
Avg merge
1d 13h
Merged PRs (30d)
253

Description

**Describe the bug**
On macOS, clicking an actionable notification (eg. new message in a chat) re-focuses Buzz but does not route the UI properly to the specific message. Buzz remains in the channel that was open before the click.

**Steps to reproduce**
1. Prompt an agent in channel X.
2. Switch to channel Y before generation completes.
3. Focus another macOS application.
4. Wait for the completion notification.
5. Click the notification body.

**Expected behavior**
Buzz should activate, open channel X, and navigate to the generated message.

**Version and platform**
Buzz version: 0.4.26
OS: macOS 27.0.0

**Logs / additional context**
No error is shown. The notification target is sent as Tauri extra metadata, but the macOS notification backend does not return that metadata with the click action.

Contributor guide

Open the contributing guide

Research direction

Start by tracing the Tauri extra metadata from notification creation through the macOS notification click-action handling. Reproduce the channel-switch scenario and verify that clicking the completion notification activates Buzz, opens channel X, and navigates to the generated message.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust, tauri
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.