CommandQ is a macOS utility that intercepts the ⌘Q shortcut and requires you to hold it down briefly before an application actually quits — eliminating the single most maddening source of accidental data loss on a Mac.
What is CommandQ?
CommandQ is a lightweight Mac app that adds a deliberate delay to the ⌘Q quit shortcut, so your browser, code editor, or design tool never closes the moment your fingers slip. Instead of quitting instantly on keypress, the app waits for you to hold the shortcut for a customisable duration — typically a second or so — before it fires. Miss the threshold, and nothing happens. Hit it intentionally, and the app quits just as you expected.
It sits quietly in the menu bar, consuming almost no resources, and you'll forget it's even there — until the day you accidentally brush ⌘Q in the middle of a 90-tab browser session and absolutely nothing bad happens. That's when you'll want to send the developer a thank-you note.
What does CommandQ do best?
CommandQ's headline strength is its near-zero friction: it doesn't change how you quit apps, it just makes accidental quits physically impossible without slowing down intentional ones by more than a heartbeat.
The delay duration is fully configurable, so you can dial it to match your typing rhythm. Heavy keyboard users often set it to around 0.8–1.0 seconds — fast enough that a deliberate ⌘Q never feels sluggish, slow enough that a mis-key during a ⌘W session (closing a tab) never nukes the whole window.
Beyond the raw delay, CommandQ can display a visual overlay as you hold the shortcut, giving you a satisfying progress arc that confirms you're on your way to a clean quit rather than a catastrophic one. There's also a per-app exclusion list: if you want Terminal or Activity Monitor to quit instantly, you can whitelist them.
- Hold-to-quit delay — configurable duration, feels natural within days
- Visual progress indicator — optional arc overlay so you know the quit is registered
- Per-app exclusions — bypass the delay for apps where instant quit makes sense
- Menu-bar presence — no Dock icon, no window clutter
- System-level integration — works across virtually every app without any per-app setup
How much does CommandQ cost?
CommandQ is available as a paid download from the Mac App Store, priced accessibly for a utility at this level of polish. There's no subscription — you buy it once and it's yours. Given that a single prevented accidental quit of a long-running Xcode build or a halfway-finished Figma file more than pays for it, the value proposition is almost embarrassingly strong.
A free trial is available directly from the developer's website so you can feel the difference before committing.
Who should use CommandQ?
Anyone who spends serious time at a Mac keyboard is a candidate, but CommandQ earns its keep fastest for a few specific groups. Developers switching rapidly between a terminal, an editor, and a browser are the obvious fit — the gap between ⌘W (close tab) and ⌘Q (quit app) is exactly one finger-slip wide. Writers working in Ulysses or iA Writer who haven't saved in a while will appreciate the safety net. And anyone who has ever rage-quit a long compile or a multi-hour video export by accident will install this and never look back.
If you primarily use a mouse and rarely touch ⌘Q by accident, CommandQ offers less. But if your hands live on the keyboard, this is the kind of utility that feels retroactively obvious — the sort of thing Apple really should have shipped in macOS itself.
What are the best CommandQ alternatives?
The closest conceptual alternative is Keyboard Maestro, which can replicate the hold-to-quit behaviour through a macro, but requires meaningful setup time and adds far more overhead than CommandQ's surgical focus. Raycast and Alfred don't address this problem at all — they're launchers, not input guards. Some users bind ⌘Q to a no-op via System Settings → Keyboard Shortcuts, but that breaks intentional quitting entirely. CommandQ is the only dedicated, polished solution I've found for this specific problem, and the specificity is exactly why it works so well.
How does CommandQ compare to macOS's built-in protections?
macOS offers almost nothing here natively. The closest thing is the "Warn before quitting" option built into certain apps like Terminal, but that's an opt-in per-app feature that developers must implement themselves — it doesn't exist system-wide. CommandQ intercepts at the shortcut level, so it works the same way in Safari, Chrome, VS Code, Figma, Sketch, and any other app without requiring the developer to do anything. It's the system-wide solution that macOS never shipped.
