Solo uses small visual indicators to draw your attention to processes that raised a notification or alert while you were focused elsewhere.
Unread marker on process rows
A small unread marker appears next to a process when it needs your attention. Common examples:
- A terminal notification arrives (BEL or supported OSC notification sequences).
- The process crashes and Solo surfaces a crash alert.
- Auto-restart pauses after repeated crashes.
- PTY-backed agents and terminals create completion attention only when they emit a supported BEL or OSC notification.
Ordinary output by itself does not create an unread marker.
To clear the marker, select the process, dismiss the linked toast, or use the process row's unread-dismiss action.
When several processes need your attention, open Focus jump. It collects unread and favorited processes in one palette so you can jump straight to whatever needs you next.
Notification levels affect which events can create unread markers:
- All allows terminal alerts plus important process alerts.
- Important allows crashes and auto-restart exhaustion, but not terminal BEL/OSC alerts.
- None suppresses both terminal alerts and important process alerts for that scope.
Project and process levels are combined by taking the more restrictive setting.
Dot on project header
If any command within a project has an unread indicator, the project header shows a dot too. This lets you see at a glance which project has activity, even if its commands are scrolled out of view or the project is collapsed.
Clicking the project header doesn't automatically clear the project-level dot. Clear each unread child by visiting or dismissing it, or use the title-bar attention menu's Clear all action.
Title-bar attention indicator
The title bar also shows an attention count when one or more processes have unread notifications. Use it to jump back to processes that need attention or to dismiss the unread state.
App icon badge count
When Solo isn't the active window, the app icon can show a badge count for unread process notifications on supported platforms. The badge count is capped at 99+ and clears when Solo regains focus.
The operating system controls the exact badge appearance. Solo provides the count; the OS renders the badge.
Indicator colors
The unread marker uses Solo's theme primary interactive color. Other warning and failure colors you might see in the row are separate status indicators, not alternate unread-dot colors.
Clearing all indicators
Use the title-bar attention menu's Clear all action to clear all current unread process notifications. Indicators also clear per process by selecting that process or dismissing its linked alert.