Type to confirm
migrate:fresh, migrate:refresh, migrate:reset, db:wipe and key:generate need the database name typed.
The worst commands make you type the database name. The risky ones ask first, showing the exact command, the folder and the database. However the command was started.
Free for everyone · macOS 14 Sonoma or later · Apple silicon and Intel
php artisan queue:work redis --queue=critical,default,low --memory=512
Running
Restart
Kill
This drops every table in acme_store and runs all migrations again.
php artisan migrate:fresh --seed
migrate:fresh, migrate:refresh, migrate:reset, db:wipe and key:generate need the database name typed.
migrate, rollback, db:seed, queue:flush, queue:forget, composer update and artisan down ask before running.
migrate asks; migrate:status doesn’t. The check is on what will actually run.
Button, search, pin, your own command or --run from a script — the same rules apply.
The confirmation shows the full command, the project folder and the database it will touch.
php artisan queue:work redis --queue=critical,default,low --memory=512
Running
Restart
Kill
This drops every table in acme_store and runs all migrations again.
php artisan migrate:fresh --seed
Found migrate:fresh with ⌘K? Same question, same typed name.
Debug on in production, a missing .env or keys missing from it — flagged before they bite.
The small things
Read from the project’s .env, so you know which one.
Turn on confirmation with your own message.
Every step is checked.
Plain sentences, not warnings in capitals.
The same check, however the command was started.
Read-only commands like migrate:status never ask.
Keep exploring
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