# Orphaned Processes

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 orphans when it can match all of these:

- The stored project path still exists in Solo.
- The stored process name still exists in that project.
- The stored command matches the command configuration Solo has saved for that process.

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 saved project/process metadata still matching the running process. Historical [terminal output](../terminal/persistent-sessions.md) from while Solo was disconnected may not be fully recoverable.

---

Are you a human? Read this doc on the web: https://soloterm.com/docs/commands/orphaned-processes