An orphaned process is one that's still running after Solo loses its active management state — for example, if Solo crashes or is force-quit while commands are running.
Launch recovery
On the next launch, Solo prunes stale orphan records and tries to adopt running commands that are still in its project list. Solo checks that each running process is the same one it launched, not an unrelated program that later reused its process ID. A surviving command is adopted again even if you changed its configured command in the meantime.
Only commands are adopted. Agents and terminals aren't, but agents with a saved session can be resumed after Solo quits or crashes.
On macOS, processes recorded before a system restart are cleaned up at launch instead of being reported as still running.
When adoption succeeds, Solo removes the orphan record and manages that process again.
Dialog options
If running orphans remain, Solo shows an orphaned-processes dialog with two choices:
- Kill Process / Kill All stops the orphaned process records Solo found.
- Leave running dismisses the orphan records without killing the OS processes.
If you leave them running, they are no longer managed by Solo from that dialog. Use system tools if you later want to inspect or stop them manually.
Important
Adoption depends on the project and command still existing in Solo and on the running process still being the one Solo started. Historical terminal output from while Solo was disconnected may not be fully recoverable.