devCommand is a native macOS menu bar companion. Pick a project, press a command, and get a real terminal running it — in the right folder, with your own login shell.
Free · macOS 14 Sonoma or later · Apple silicon and Intel
php artisan queue:work redis --queue=critical,default,low --memory=512
Running
Restart
Kill
Four stacks, one list
125 built-in actions across four project kinds, each offered only when your project can use it. No phpstan.neon, no static analysis button.
33 built-in Laravel actions
Spotted by artisan and composer.json. devCommand reads the Laravel version, PHP constraint, package manager, test runner, Pint and PHPStan, database and queue connection, APP_URL and git branch — without starting a single process.
Detected by artisan + composer.json
php artisan queue:work redis --queue=critical,default,low --memory=512
Running
Restart
Kill
35 built-in WordPress actions
Found by wp-config.php and friends, and run through WP-CLI. Core, plugin and theme updates, checksums, database housekeeping, cache and transient flushes, cron and maintenance mode — each one a button.
Detected by wp-config.php
wp plugin update --all
Running
Restart
Kill
28 built-in Flutter actions
Found by pubspec.yaml. Pick a device from the ones Flutter can actually see — iPhone, Android, Mac, web — and devCommand adds the -d for you. Hot reload and hot restart send r and R straight into the running app.
Detected by pubspec.yaml
flutter run -d "iPhone 17 Pro"
Running
Restart
Kill
29 built-in Swift actions
Found by Package.swift, .xcodeproj or .xcworkspace. Build, test and archive from one list. Run + Hot Reload relaunches on save, or injects changes live with InjectionIII or InjectionNext so your app keeps its state.
Detected by Package.swift · .xcodeproj · .xcworkspace
xcodebuild -scheme MenubarKit -configuration Debug build
Running
Restart
Kill
Why it earns a place in your menu bar
Queues, tests, logs, health checks and the commands you forget — all in the window you already have open.
⌘K searches all of them — 164 on a stock Laravel 13 app — by name and description, so “clear cache” finds what you meant. Your own commands sort first, and each one gets a form built from its own arguments and options.
Explore every artisan commandmigrate:fresh, db:wipe and friends make you type the database name first. It checks the command line itself, so buttons, searches and scripts are all covered.
Explore safe by defaultSave a profile of queues, priorities, limits and worker count. One row starts the lot; one button stops the group. It nudges you when app/ changes, because workers hold old code.
Explore queues and workersStack traces fold away, repeats collapse into one line, and clicking a frame opens your editor at the right line.
Explore log viewerNo vendor folder, no .env, debug on in production — spotted from files alone, fixed in one click.
Explore health checksThe menu bar lists what’s running by project, with Stop everything one click away.
Explore menu bar and hotkeysFull ANSI colour, interactive prompts and full-screen programs, one tab per command with scrollback kept. Stop takes the whole process tree with it — no orphaned vite still holding a port.
Explore real terminals16 aurora palettes or 16 solids. Each project keeps its own colour, so you know where you are at a glance.
Explore projects it understandsPest, PHPUnit, Flutter widget tests and Patrol, grouped and searchable. Run one test, one file, the suite or just the failures.
Explore tests, with a proper interfaceA proper macOS app with config in a hand-editable JSON file. Nothing is sent anywhere.
Nothing to set up
There’s no config to write before it’s useful. Show it where your projects live and it does the reading.
Nominate a folder and devCommand looks one to three levels down for Laravel, WordPress, Flutter and Swift projects.
Choose the ones you want. Each is read from its files — versions, scripts, database, branch — with no processes started.
It opens in its own terminal tab, in the right folder, with your login shell and your PATH. That’s it.
Logs, without leaving the window
Huge log files read from the tail, grouped, filtered and searchable — including inside the stack traces.
Five search modes Contains, does not contain, any of, whole word or wildcard.
Repeats collapse Forty-eight timeouts become one line, with when it last happened.
Traces fold away Click any frame to open that file at that line in your editor.
Health, beside your commands Missing .env keys flagged, with a one-click fix.
Keyboard first
Every everyday move has a shortcut. Give any command a global hotkey and it works from any app — no Accessibility permission needed, with clash detection built in.
The difference
Free for everyone
devCommand costs nothing. There’s no account to make, no licence key, no trial that runs out and nothing held back for a paid tier. Use it at work, at home, on one project or fifty — however suits you.
It isn’t open source, but from where you sit it behaves like it: free to download, free to use, free to share with your team.
Every feature, for everyone. No pro version waiting in the wings.
Suggestions are genuinely welcome. The next stack, the next pane, the small thing that annoys you — say so and it goes on the list.
No telemetry, no sign-in. Your projects stay on your Mac.
If it saves you time, a coffee keeps it going. Entirely optional — it’s free either way.
Questions
The short answers to what people ask first.
Yes. Free to download and free to use, for anything — personal projects, client work, your whole team. There’s no paid tier. If you’d like to say thanks, there’s a Buy me a coffee link, and that’s entirely optional.
Not formally — the source isn’t published. But you’re free to use it however you like, and suggestions from the people using it decide what gets built next.
Any Mac on macOS 14 Sonoma or later, Apple silicon or Intel. It’s a native app, not a web page in a wrapper.
No. Nothing is sent anywhere. Your projects are read from files on your Mac, and settings live in a JSON file you can open and edit yourself.
No. The Laravel version, PHP constraint, package manager, test runner, database, queue connection and git branch are all read from files. It starts no processes to do it.
It’s a companion. Each command runs in a real terminal with ANSI colour, prompts and full-screen programs, using your own login shell — so php, node and composer resolve just as they do in your terminal.
Yes — per project or globally, with placeholders it asks for before running, optional confirmation messages and a working subfolder. Chain steps into sequences that stop at the first failure, and import or export them.
Yes: open -a devCommand --args --run "Start dev". The same destructive-command checks apply, however a command is started.
PhpStorm, VS Code, Cursor, Sublime Text, Xcode and Zed — at the right line, from a failing test or a stack trace frame.
Point devCommand at ~/Sites, tick your projects and press your first command. No config to write first.
Free for everyone · macOS 14 Sonoma or later · Apple silicon and Intel · Version 1.0
