Auto-restart mostly happens quietly in the background. The important notification path is when Solo pauses auto-restart because a command is crash-looping.
What you actually see
When a command has auto-restart enabled, Solo retries it, and each successful retry writes a restart banner in the terminal. Solo suppresses the normal crash notification when its cached process snapshot carries that setting. If the snapshot is not yet in the cache, a normal crash notification can still appear while the retry proceeds.
If the command crashes too many times in a short window, Solo writes an "Auto-restart paused" banner into the terminal. If the effective notification level allows important alerts, Solo also marks the process as exhausted in the UI and sends an "Auto-restart paused" notification. When Solo is focused, that notification is an in-app toast; when Solo is unfocused, it can be a native desktop notification.
Solo doesn't send a separate notification for every successful restart attempt.
Rate limiting
Auto-restart is rate-limited to 10 restarts within a 60-second sliding window. Once the retry limit is exhausted, Solo stops retrying and writes the paused banner instead of continuing forever. It also shows the exhausted UI state when the effective notification level allows important alerts.
Where to investigate
- Open the affected process to inspect its recent output.
- Check the terminal for the crash-loop message.
- Review the command's auto-restart setting if the process shouldn't keep retrying.
See Auto-restart for the feature itself.
Settings
There's no separate per-category notification toggle for auto-restart events today. Important and All levels allow the paused/exhausted alert; None suppresses it. If you don't want the restart behavior, disable auto-restart for that command.