Notifications
Choose how EvoX lets you know when work needs your attention.
EvoX Desktop
Notifications bring you back when work needs you to return. The channel depends on whether the window is in the background, whether the desktop pet is enabled, and whether the operating system allows EvoX notifications.
Configure desktop notifications
On macOS, open Settings > Appearance to inspect notification permission. If denied, use Open System Settings to authorize it. Windows does not provide this in-app permission diagnostic; check EvoX, banners, and Do Not Disturb in Windows notification settings.
EvoX does not repeat a completion alert when you are already looking at the current window. When a reply finishes in the background, the system can show a desktop notification; a background approval or confirmation request uses a stronger attention cue. If an organization disables desktop banners, the in-app activity list and badge continue to update.
Follow chat activity in the activity view
Select the Activity icon in the top bar to see conversations that still need attention in the current work surface. The list can include Chat, Code, and Cowork conversations, together with their status and unread state.
Selecting a conversation returns you to the session that produced the activity; opening the activity list does not create a new conversation. Once everything is handled, the list says All handled.
Follow chat activity with the desktop pet
When the desktop pet is present, evo can show a bubble beside it when a reply is ready or when your confirmation is needed, such as Reply's ready or Need your go-ahead. Selecting the bubble returns to the conversation that produced the state.
The pet bubble is an alternative presentation channel to system notifications: when the pet is enabled and available, it takes priority; when pet bubbles are disabled, completion and approval reminders use system notifications instead. The conversation and run record remain the source of truth for the full result. For messaging channels, generating a reply and delivering it are separate outcomes. A conversation notice that delivery failed or is unconfirmed does not mean the task never ran. Inspect the retained reply and channel records before deciding what to do, so the task is not triggered twice.
Related documentation
EvoX Docs · Features · Workflows