How to Force Yourself to Take Breaks on Mac

Why dismissible reminders don't work

I built StandLock because every break reminder I tried was too easy to ignore. I used Time Out, Stretchly, and the macOS timer. All of them did the same thing: showed a notification, I clicked dismiss, and went right back to work. The break never happened. This went on for months. I knew I should be standing up more. I had the apps installed. They were running. None of it mattered because the moment I was deep in code, nothing short of a fire alarm was going to pull me away.

This is not a willpower problem. It is a design problem. Notifications on macOS slide into the corner of your screen. They sit there for a few seconds and disappear. If you are in a fullscreen app, you might not see them at all. Even when you do see them, dismissing a notification is so automatic that your hand moves to the X before your brain registers what the notification said. You have done it thousands of times with spam emails and Slack pings. The muscle memory is baked in.

Research backs this up. A 2004 study by Czerwinski, Horvitz, and Wilhite at Microsoft Research found that after a notification interruption, it took workers an average of 25 minutes to return to their original task. But that assumes the person actually stopped. When the notification is a break reminder you can dismiss in one click, most people dismiss it and stay on task. The interruption cost is zero because no interruption actually occurred.

What screen lock enforcement means

Screen lock enforcement means the app does not ask you to take a break. It takes the break for you. When your work interval ends, StandLock puts something on your screen that you cannot trivially dismiss. How hard it is to get past depends on which discipline level you choose. There are three, and they are designed to match different temperaments and stages of habit formation.

Gentle: overlay with a skip button

Gentle mode covers your screen with an overlay that shows your break timer counting down and a skip button. One click and you are back to work. No lock, no friction. This is training wheels. It is there to establish the rhythm of regular breaks without forcing anything. If you have never used a break reminder with any enforcement at all, start here. The overlay is visible enough that you notice it, but it does not prevent you from doing anything. I found that even this small nudge made me take about 40% of my breaks, up from roughly zero with notification-only apps. The overlay is harder to ignore than a notification because it sits on top of your work, not in a corner.

Firm: type to dismiss

Firm mode shows the break screen and requires you to type a short phrase to dismiss it early. Something like "I'm ready to go back." You can still skip the break, but you have to be deliberate about it. That extra 3-4 seconds of typing is enough to make you pause and question whether you actually need to skip or whether you are just being reflexive. In practice, I found that I almost never typed the phrase. The act of reaching for the keyboard to type a dismissal message made me realize I should just take the break. Behavioral economists call this a "friction cost." A tiny barrier that changes behavior disproportionately. It is the same reason requiring an extra click before an online purchase reduces impulse buying.

Strict: full input lock

Strict mode locks your keyboard and mouse for the full break duration. No dismiss button. No typing your way out. Your Mac is off-limits until the timer reaches zero. This is the mode I use daily. The break screen fills your display, shows the remaining time, and does not respond to input. You stand up because there is literally nothing else to do.

There is always an emergency escape. Hold Control, Option and Command together for about ten seconds and StandLock releases the lock. The hold is deliberately long enough that you cannot do it by reflex. I have used this maybe five times in the past year, always for something genuinely time-sensitive like a production incident. The bar is intentionally high. It is not "let me just finish this function." It is "the server is on fire."

This mode requires Accessibility and Input Monitoring permissions. StandLock asks for these the first time you select Strict. It never accesses anything beyond what is needed to capture and release keyboard and mouse input during breaks. Until both are granted, a Strict schedule runs as Firm.

Setting up forced breaks step by step

The entire setup takes about two minutes. StandLock runs from the menu bar after that, no dock icon and no window to keep open.

1. Install StandLock via Homebrew (brew install yagizdo/tap/standlock) or download the .dmg from the homepage.
2. Launch StandLock from your Applications folder. It shows up as a small icon in your menu bar.
3. Click the menu bar icon and go to Schedules.
4. Create a new schedule. Set your work interval (how long between breaks). 30 to 60 minutes is a good starting range.
5. Set your break duration. 5 minutes is enough to stand, stretch, and walk to the kitchen and back.
6. Choose your discipline level. Start with Gentle if this is your first time, Firm if you know you will dismiss anything optional, or Strict if you want zero negotiation.
7. Grant the permissions StandLock asks for. Only Strict needs any: Accessibility and Input Monitoring. You can find these in System Settings > Privacy & Security.
8. Toggle the schedule on. StandLock will lock your screen on the interval you set, starting now.

You can configure your schedule with 4 short breaks followed by a long one for Pomodoro-style cycles. And if you want to add 20-20-20 eye breaks instead, use a 20-minute interval and 30-second duration. Keep it in a separate active time window from any other schedule: overlapping schedules do not run as independent clocks, and a shorter interval can keep taking priority over a longer one.

Meeting awareness: when StandLock gets out of the way

A forced break reminder is worse than useless if it locks your screen while you are presenting to your team on Zoom. StandLock has three detection mechanisms that prevent this.

• Calendar integration. If you grant Calendar read access, StandLock checks for events that overlap with your next scheduled break. If it finds one, it defers the break until the event ends. It reads only the time range of events, never their titles or descriptions.
• Camera and microphone detection.StandLock checks whether any app is currently using your camera or mic. If either is active, it assumes you are on a call and holds the break. It does not access the camera or microphone streams. It only checks the system-level "in use" flag that macOS exposes.
• Screen sharing detection. If macOS reports that screen sharing is active (through an app like Zoom, Google Meet, or any other app using the screen capture API), StandLock waits. Nobody wants a break overlay appearing in a client presentation.

All of these are optional. You enable each one individually. If you never have meetings, you can skip them all and StandLock will always fire on schedule with no exceptions.

The health case for forced breaks

The reason this matters goes beyond productivity habits. Prolonged sitting is directly linked to health problems that most desk workers do not think about until they appear.

A 2015 meta-analysis published in the Annals of Internal Medicine analyzed 47 studies and found that prolonged sedentary time was associated with higher rates of cardiovascular disease, type 2 diabetes, and all-cause mortality, even among people who exercised regularly. Going to the gym in the morning does not undo 8 hours of uninterrupted sitting. What helps is breaking up sitting time throughout the day.

According to the World Health Organization, physical inactivity is the fourth leading risk factor for global mortality. Replacing just a few minutes of sitting per hour with standing or light walking is one of the simplest interventions available. The hard part is remembering to do it, which is exactly what StandLock automates.

Frequently asked questions

Can I always exit a forced break in an emergency?

Yes. Hold Control, Option and Command together for about ten seconds (the default; configurable, and longer if progressive enforcement has escalated) and StandLock releases the lock. This applies to Strict mode, the only mode that blocks input.

Will StandLock lock my screen during a meeting or presentation?

No. StandLock checks your calendar for events, detects active camera and microphone use, and detects screen sharing. If any of these are active, it defers the break until you are done. Each detection method is optional and can be enabled individually.

What permissions does StandLock need for screen locking?

Gentle and Firm need no special permissions. Strict requires Accessibility (to block input) and Input Monitoring (for the hold-to-escape combo). Calendar awareness requires Calendar read access. StandLock asks for each permission only when you turn on a feature that needs it, and a Strict schedule runs as Firm until both are granted.

Is StandLock free?

Yes. Free and open source under the MIT license. No paid tiers, no accounts, no analytics by default. The full source code is on GitHub. See how it compares to other break reminder apps.