Solo can send native macOS notifications when events happen while you're away from the app. macOS requires you to grant notification permission before those alerts will appear.
Checking permission status
- Open Settings. The default macOS shortcut is
Cmd+,; a custom Hotkeys binding for Open settings takes precedence. - Go to Notifications.
- The System notifications row shows your current status.
Enabling notifications
- If notifications haven't been requested yet, click Enable notifications.
- If notifications were previously denied, click Open system settings and enable Solo there.
- Use Send test to verify delivery after granting permission.
macOS controls the final presentation style after permission is granted.
When notifications appear
Native notifications are most useful when Solo isn't the active window. Common examples include terminal or script notifications, crash alerts, auto-restart paused alerts, and solo.yml sync-needed alerts.
Under the normal focus-aware policy, Solo relies on in-app toasts while the app is focused. Explicit native-channel actions such as Send test still use native delivery while Solo is focused. If you're already viewing the process that emitted a terminal notification, Solo suppresses that terminal alert entirely. See In-app toast notifications.
Notification Center settings
Alert style, lock-screen behavior, and Notification Center presentation are configured in macOS System Settings > Notifications > Solo, not inside Solo. Normal Solo native notifications request no system notification sound; configure Bell sound in Solo's Settings > Notifications for separate audible event feedback.
Privacy
Native notifications may include project or process context and a short message body, depending on the event type.