Start, Stop, and Restart

Solo lets you start commands and control the lifecycle of command processes that it owns. A command adopted from a previous Solo session is still tracked as running, but Solo cannot stop or restart it through the normal controls because it does not own an authoritative process handle.

Start#

Starts a command if it's allowed to run. Command processes must be trusted and within applicable limits before Solo launches them. Terminals and agents are trusted by design and use their own process kind rules.

Stop#

Stops an ordinarily managed running command. After a successful stop, Solo releases any todo locks held by that process and removes the process from crash-recovery tracking. An adopted command cannot be stopped through the normal Solo controls.

Restart#

Restarts the selected command by stopping its Solo-managed process and, after that stop succeeds, starting it again with the latest saved command configuration and terminal size. Restart is blocked for untrusted commands, and it cannot replace an adopted command whose stop Solo refuses.

Bulk Actions#

Project-level lifecycle actions are command-only:

• Start auto-start starts trusted commands with auto_start enabled.
• Start all starts all trusted commands in the project.
• Stop all attempts to stop every command process in the project. An adopted command can remain running because Solo cannot stop it through the normal controls.
• Restart running attempts to restart currently running trusted commands whose processes Solo owns. An adopted command can fail during the stop step instead of restarting.
• Restart all attempts to restart every trusted command in the project, including commands that are currently stopped. Untrusted commands are skipped, and an adopted command can remain running if its stop is refused.

Notes#

• The available actions depend on the current process state. A stopped command shows "Start", a running one shows "Stop" and "Restart".
• Stop and restart from hotkeys or command-palette actions can show a confirmation for managed commands. You can suppress future stop/restart confirmations for that command.
• Context-menu start/restart actions for untrusted commands are disabled and labeled as requiring trust.