Commands
Commands are the long-running pieces of your dev stack that Solo manages for a project, such as dev servers, workers, queues, and databases. Learn how to add and arrange them, control when they start or restart, read their status, and decide which commands to trust.
Adding and removing commands
Think of commands like your dev stack. Anything needed to make your app work locally:
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 canno…
Auto-start
Auto-start lets Solo launch eligible commands automatically for a project.
Auto-restart
Auto-restart relaunches a command after it exits unexpectedly.
File-watch Auto-restart
While a configured command is running, a matching on-disk file change triggers its restart. It's useful when your tool doesn't already have a good built-in watch mode.
Status Indicators
The sidebar shows visual indicators next to each command so you can see its current state at a glance.
Renaming commands
You can rename a command from its settings. Renaming changes the label Solo uses for the process and can also update solo.yml when the command is file-backed.
Reordering Commands
With the sidebar filter clear and no overlay open, you can drag and drop commands to reorder them within their section in the sidebar.
Lesser-used Commands
The Lesser used context-menu toggle marks quiet commands so they can be tucked out of the main command list without deleting or disabling them.
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.
Trust and Security
Solo blocks untrusted solo.yml commands from starting until you explicitly approve them. This prevents you from accidentally running unknown commands when a repo's solo.yml is adde…
Are you an agent? Read this doc via API: /api/v1/docs/commands