In order, every time
Steps run one after another, each in the project’s folder, with your shell.
The ritual, as one button.
Rebuild the database, seed it, then start the dev server. Clean, fetch packages, then run. Sequences are the steps nobody remembers in the right order — saved under one name.
Free for everyone · macOS 14 Sonoma or later · Apple silicon and Intel
Your projects
- acme-storemain
- billing-apifeature/invoices
- field-appmain
- studio-journalmain
- menubar-kitmain
- ops-dashboarddevelop
- tide-mobilerelease/2.4
Add a project…Settings
Filter these commands…
Recent
WorkersRunning
Start dev
Tests
Run and serve
Start dev
Full dev stack
Queue worker
Scheduler
Tail logs
Tinker
Database and caches
Migrate
Migration status
Fresh and seed
Clear all caches
3 keys missing from .env
Search all commands… ⌘K
Fresh startsequence · 4 stepsRun
Stop at the first failure
1
pkill -f "vite"
May fail Done
2
composer install
Done
3
php artisan migrate:fresh --seed
Running
4
composer dev
Waiting
+ Add a step
Stops at the first failure
On by default — because carrying on after composer install fails just wastes four minutes proving it.
Some steps may fail
Mark a step “may fail” — a pkill that finds nothing, a clean of a folder that isn’t there — and the rest carry on.
One press
Pin it, give it a hotkey or start it from the menu bar.
01
Build the list
Add steps, put them in order and name the whole thing.
- Any command line as a step
- Stop at first failure, or not
- Per-step “may fail”
Filter these commands…
Recent
WorkersRunning
Start dev
Tests
Run and serve
Start dev
Full dev stack
Queue worker
Scheduler
Tail logs
Tinker
Database and caches
Migrate
Migration status
Fresh and seed
Clear all caches
3 keys missing from .env
Search all commands… ⌘K
Fresh startsequence · 4 stepsRun
Stop at the first failure
1
pkill -f "vite"
May fail Done
2
composer install
Done
3
php artisan migrate:fresh --seed
Running
4
composer dev
Waiting
+ Add a step
02
Watch it go
The sequence runs in one tab, step by step, and stops the moment one fails — unless you said it could.
- Clear output per step
- Exit codes shown
- Restart from the top with ⌘R
Filter these commands…
Recent
WorkersRunning
Start dev
Tests
Run and serve
Start dev
Full dev stack
Queue worker
Scheduler
Tail logs
Tinker
Database and caches
Migrate
Migration status
Fresh and seed
Clear all caches
3 keys missing from .env
Search all commands… ⌘K
Workers
Start dev
Workers
php artisan queue:work redis --queue=critical,default,low --memory=512
Running
Restart
Kill
info Processing jobs from the [critical,default,low] queues.
22:14:02 App\Jobs\SendInvoice 41ms done
22:14:02 App\Jobs\SyncStock 118ms done
22:14:05 App\Mail\OrderShipped 203ms done
22:14:09 App\Jobs\ResizeImage running
03
Works for every stack
flutter clean, pub get, run. swift package resolve, build, test. wp maintenance-mode, update, flush.
- Flutter, Swift and WordPress too
- Shareable with import and export
- Safety checks apply to every step
Filter these commands…
Recent
Run on iPhoneRunning
Hot reload
Run and serve
Run on iPhone
Run on Chrome
Hot reload
Hot restart
build_runner watch
Build
Build apk
Build ios
Build web
Flutter doctor
Packages not fetched
Search all commands… ⌘K
Fresh startsequence · 4 stepsRun
Stop at the first failure
1
flutter clean
Done
2
flutter pub get
Done
3
dart run build_runner build
Running
4
flutter run -d "iPhone 17 Pro"
Waiting
+ Add a step
The small things
Details that add up.
Named
Sequences show by name, or by their first step if you don’t name them.
Stop on failure
A switch, on by default.
Ignores failure per step
For the steps that are allowed to fail.
Hotkeys
Any sequence can have a global shortcut.
Menu bar
Start one without opening the window.
Scripts
open -a devCommand --args --run "Fresh start"
Keep exploring
Works well with.
Free, and ready when you are.
No account, no licence key. Point devCommand at ~/Sites and press your first command.
macOS 14 Sonoma or later · Apple silicon and Intel · Version 1.0