A break reminder that knows when you’re shipping

Why every break timer fires at the worst moment

You install a break app on Monday with good intentions. By Wednesday it has popped a full-screen overlay two keystrokes into a tricky refactor, fired in the middle of a deploy, and demanded twenty seconds of stretching while you watched a flaky test finally go green. So you hit Skip, then Skip again, and by Friday it’s uninstalled. The app wasn’t wrong that a break was due — it was wrong about the moment. A fixed-interval timer counts minutes and nothing else; to a stopwatch, reading docs and landing a fix you’ve chased all afternoon look identical.

What developer-aware Smart Pause does

Opt in, and Pausebar treats a running build, test, deploy, or AI-agent run as “busy” — it holds a due break while the run is going, then eases it back in the moment it finishes. It reads this the same calm way it reads a meeting: a small local signal that now is a bad time. Curated patterns already tell a one-off build from a long-running dev server, so a quick build holds a break while your dev server doesn’t — and you add the build and agent commands you actually run, so it matches your stack.

For AI agents, Cursor and Aider are recognized out of the box, and you can point Pausebar at any other agent command you drive (for example, a codex exec command) so a long agent session is never chopped in half by a rest overlay. You choose every signal — nothing here is on until you turn it on.

It still respects the rest of your day

The developer signals sit on top of everything Pausebar already does: a due break holds while you’re typing and slips in at the next natural pause, and Smart Pause stays quiet during calls and meetings, screen sharing, full-screen and presenting, video, screenshots, and dictation. The net effect is one quiet nudge when stepping away would genuinely help, instead of an ambush ten times a day.

The privacy developers actually check

If you read app permissions for a living, the obvious question is how a break app knows you’re busy. The answer is deliberately boring: Pausebar checks the names and commands of your own running processes locally — the same permission-free macOS information Activity Monitor uses — plus small yes/no signals like whether your mic is active or a window is full-screen. It never reads your code, your screen, your keystrokes, or your terminal output. Everything stays on your Mac: no account, no cloud, no telemetry.