Docs

Auto-commands

Run Horizon, queues, schedulers, npm dev, and any other command automatically when a project starts.

Service vs once mode

Auto-commands fire every time a project starts. Two run modes:

Service mode runs detached with -d and stays alive until containers stop. Use this for long-running things: Horizon, queue workers, the schedule worker, Vite dev server, Reverb, Pulse worker.
Once mode runs blocking, waits for it to exit, and continues. Use this for one-off setup: extra migrations, storage:link, cache:clear, etc.

Service-mode commands get killed cleanly when you stop the project, so you don't need to babysit them.

Built-in presets

The Add menu has presets grouped by purpose. Click any to add it pre-configured. You can still edit the label, command, or mode after.

Workers: Horizon, Queue worker, Schedule worker, Reverb, Pulse worker.
Frontend: Vite dev server, Bun dev.
Tooling: Pail (live logs), Telescope publish.
Maintenance: Storage link, Cache clear, Optimize clear.

Custom commands

You can add anything. The app accepts sail artisan ..., ./vendor/bin/sail ..., or raw shell strings; it strips the Sail prefix and executes the rest with docker compose exec laravel.test bash -lc. Each command has its own log tab so you can see output independently.

Per-command fields

Label. Shown in the list and the log tab.
Command. The shell string. sail artisan prefixes are normalized.
Run mode. Once or service.
Enabled. Skip without deleting.
Order. Drag to reorder; once-mode commands run in the order shown.

Run all now

The "Run all now" button triggers the full auto-command sequence on demand without restarting the project. Disabled commands are skipped. Useful when you want to kick off Horizon and Vite without bouncing the containers.