docs/docs/en/api/cli/app/autostart/run.md
Start every env that has application autostart enabled.
This command is typically called after the host system boots, through your own startup mechanism. The CLI reads all saved envs, filters the ones that have autostart enabled, and then tries to start them one by one.
nb app autostart run [flags]
| Flag | Type | Description |
|---|---|---|
--verbose | boolean | Show raw startup output from the underlying local or Docker command |
nb app autostart run
nb app autostart run --verbose
If no env has autostart enabled, the command prints No environments have app autostart enabled..
During execution, the CLI processes each enabled env one by one:
startedskippedfailedInternally, this command calls nb app start --env <name> --yes. If you pass --verbose, that flag is forwarded to the underlying startup flow as well.
If any result is failed, the command exits with an error and prints Some app autostart envs failed to start.. This makes failures visible in systemd, CI, or other host startup mechanisms.