Solo can display live CPU and memory usage right in the sidebar for both project headers and individual process rows. This makes it easy to spot resource issues without leaving the app.
What gets shown
- Project headers show aggregated CPU and memory across running items in that project.
- Process rows show CPU and memory for that specific process tree.
Stopped items don't show live stats. Process rows can also show port information and active subprocess counts next to CPU and memory when those are available.
Port badges
When Solo detects a listening port for a running process, the row shows the port next to its stats; if it detects several, the first port is shown with a +N count for the rest. Hovering the row shows the full URL in a tooltip and replaces the stats with quick actions, including an open-link button — click it to open the bound URL in your default browser.
Configuring stats visibility
In Settings -> Sidebar, you'll find independent threshold controls for:
- Project CPU usage
- Project memory usage
- Process CPU usage
- Process memory usage
Each control uses preset buttons. Current defaults are 25% for project CPU, 1GB for project memory, 30% for process CPU, and 500MB for process memory. A separate Show subprocess count control sets when the +N subprocess badge appears (default 2+).
For process rows, a stat appears when its current value meets or exceeds the chosen threshold. Always displays the requested stat and uses a dash when its value is missing; Never hides it. Project-header totals use their configured thresholds only after at least one running-process stat is available. Before that, the project header keeps its placeholder blank even under Always.
Why you might use this
- Debugging resource issues — find out which command or project is eating CPU during a slow development session.
- Monitoring long-running workers — see if a background job is growing in memory over time.
- Comparing processes — spot the difference in resource usage between similar commands.
Accuracy
Process-row stats use Solo's live process monitor for that row, including child-process data when available. Project-header stats aggregate all running processes in the project, not just rows currently visible after filtering.
Solo samples stats every two seconds. Displayed values may lag behind actual usage spikes.