Bulk tools run best-effort operations on command processes in the effective project. Start operations consider only trusted commands; stop operations consider every running command regardless of trust.
Tools
start_all_commands— Attempt to start every trusted command process in the effective project scope.stop_all_commands— Attempt to gracefully stop every running command process in the effective project scope, regardless of trust.restart_all_commands— First attempt to stop every running command process in the effective project scope, regardless of trust, then attempt to start every trusted command process in that scope. If the project has no trusted commands, nothing is stopped or started and untrusted commands are reported as skipped. Agents and terminals are never touched.
Notes
Bulk start and the start phase of bulk restart respect command trust. The stop phase of bulk restart does not filter by trust, so a running untrusted command can be stopped and then skipped during the start phase. Results report per-process failures and trust skips; successful operations are not rolled back when another process fails.
Before stopping anything, restart_all_commands checks your license's process limit. If you're already over it, the call fails and nothing is stopped. See Free tier.
Bulk tools are useful for restoring a project after opening Solo, restarting a full dev stack, or stopping project commands before a large change.