How to Use an Auto Clicker to Keep Your Mac Awake (Beats Caffeine and Amphetamine)
60-second answer. Set your auto clicker to fire one click every 60 seconds at a safe screen position (a dead corner of the menu bar or an empty desktop area), enable it before you walk away, and your Mac stays awake indefinitely. This beats Caffeine for configurability, beats Amphetamine for survival across reboots without a setup hassle, and beats caffeinate CLI for not requiring Terminal to stay open. It works during fullscreen video, long renders, downloads, compile jobs, and remote-work idle checks (the last one is an ethics call I cover below).
Why Your Mac Sleeps Even When System Settings Says “Never”
I learned this painfully. I had Battery > Options set to “Prevent automatic sleeping when the display is off” and assumed that covered everything. It didn’t. The Mac slept mid-render and I lost 25 minutes. Apple’s labels are misleading.
macOS has four separate idle systems running in parallel:
- Display sleep: screen-off timer. Defaults 10 min on power, 2 min on battery.
- System sleep: whole-machine low-power state. The “Prevent automatic sleeping” toggle covers only this.
- Screensaver: separate idle timer, can interrupt video playback.
- App Nap: per-app energy saver since Mavericks. Backgrounded apps throttle to 5% CPU regardless of sleep settings.
And then app-level idle. Slack flips your dot to away. Discord shows Idle. Teams reads the system’s HIDIdleTime counter, which only resets on actual input events. The IOPMAssertion framework that Caffeine and Amphetamine use covers the OS layer (five assertion types) but never touches app-level idle. An auto clicker bypasses assertions entirely by generating real input events, beating all five OS timers AND every app-level timer at once.
5 Ways to Keep a Mac Awake (Compared)
I’ve used every one of these on the same machine over the past two years. Here’s the side-by-side, scored on what actually matters when you’re trying to stop a render or download from getting interrupted.
| Method | Free | Open-source | Configurable | Survives reboot | Works during fullscreen | Generates input |
|---|---|---|---|---|---|---|
| Caffeine (Lighthead) | Free | Closed | Toggle only | Login item | Yes | No (assertion only) |
| Amphetamine (App Store) | Free | Closed | Triggers, schedules | Login item | Yes | No (assertion only) |
| autoclicker-mac.com | Free | GPL-2.0 | Interval, coords, hotkey | Manual relaunch | Yes | Real clicks |
| caffeinate (built-in CLI) | Free | Apple binary | Flags only | Terminal must stay open | Yes | No (assertion only) |
| Hardware mouse jiggler | $10-30 | N/A | Fixed pattern | Plugged in | Yes | Cursor jiggle only |
Source: hands-on testing May 2025 to April 2026 on the four Macs in the meta bar. Caffeine v1.1.3 (2017, still works), Amphetamine v5.3.2 (March 2024), Mahdi Autoclick v2.0.4, caffeinate man page on Sequoia 15.1.
Caffeine and Amphetamine both use IOPMAssertion assertions, telling the kernel “don’t sleep” without generating input events. They handle display and system sleep but do nothing for Slack, Discord, or Teams idle detection. The auto clicker hits all five assertion types AND fakes input events for app-level idle. The hardware jiggler I tested (Vaydeer, $19) handles cursor motion but skips click events, so VPN keepalives and certain remote desktop tools ignore it. Auto clicker covers both motion and click, which is a superset.
The Auto Clicker Approach: How It Actually Works
macOS tracks user activity via CGEventSourceSecondsSinceLastEventType. Every input event (click, keystroke, mouse move) resets the counter to zero. Screensaver, display sleep, system sleep, App Nap, Slack’s away timer, Discord’s idle setting, and HIDIdleTime all read variants of this source. A single click resets all of them simultaneously.
An auto clicker firing one event every 60 seconds pins the counter near zero. The Mac believes a human is at the keyboard. Display sleep never expires. Screensaver never engages. System sleep never triggers. App Nap doesn’t activate. Slack stays Active. Discord stays Online. Teams stays Available. Zoom doesn’t auto-leave. Final Cut, Logic, Xcode, and Docker keep grinding without the OS pulling the rug.
I tested 60-second vs 30-second vs 5-minute intervals. The 5-minute interval failed twice in 10 trials because Slack’s away timer is also 5 minutes and the click landed AFTER the away flip. 60 seconds is the sweet spot. If you want to set a 60-second click interval with millisecond precision, that’s its own walkthrough.
Set Up autoclicker-mac.com to Keep Your Mac Awake
Two minutes from installed-and-permissioned to running. If the app refuses to launch on Sequoia, run the auto clicker won’t launch on Sequoia override first.
Open the auto clicker app
Launch Autoclick.app from Applications. Main window shows click type, interval, location, and click count fields.
Set interval to 60 seconds
Interval field, enter 60000 ms (the field is milliseconds). Tested 30 and 90 too. 60 is the sweet spot, beats Slack’s 5-min and Teams’ 3-min timers without being noticeable.
Set click coordinates to a safe screen position
Pick the menu bar dead zone (between Help and the status icons) or an empty desktop area. Safe coordinates covered in detail in the next section. Avoid any active app window.
Set click pattern to single, left-click
Single click, Left button (right-click can trigger context menus). Click count: 0 for unlimited, or 99999 for a session limit.
Bind a hotkey and start
I always bind a Start/Stop hotkey, usually F6, so I can kill the loop instantly. Press F6 or click Start. First click fires 60 seconds later. Walk away.
Confirm it’s working: leave the Mac alone 12 minutes (longer than default sleep). If the screen is still on when you return, setup is correct. If it turned off, recheck coordinates and that Start was pressed.
Where to Put the Click Safely
Most guides skip this and it’s the most important part. A click in the wrong spot can minimize a window, delete text, scrub a timeline, or click a Send button you didn’t mean to.
Safe locations I’ve tested
- Menu bar dead zone: empty pixels between the right edge of the active app’s menu and the left edge of the status icons. On a 1440-wide display, around x=600-900, y=12. No clickable element. My preferred spot.
- Empty desktop area: any coordinate in the wallpaper area, like x=100, y=500. Finder receives the click but does nothing visible.
- Off-screen negative coordinates: Mahdi Autoclick accepts negative x/y. Setting x=-100, y=-100 fires off-screen. Works on every macOS version I tested.
- Screen corners: check System Settings > Desktop & Dock > Hot Corners and pick a corner with no action. Top-right is usually safe by default.
Don’t click inside an active app window. Even an “empty” spot inside Final Cut, Logic, or a browser can deselect a clip, lose your cursor position, scrub a timeline, or dismiss a dialog you needed. Stick to the menu bar dead zone or empty desktop. Avoid: any browser window, code editor, Zoom or Teams window, Notification Center, the Dock, and the Sequoia Stage Manager strip.
Use Cases That Need This
The eight scenarios where I reach for this trick most.
Long renders & exports
Final Cut, DaVinci Resolve, Premiere, Compressor. A 4K export runs 30-120 min. Sleep mid-render pauses the queue and sometimes corrupts output.
Remote-work idle status
Slack, Discord, Teams, Zoom flip status to Away after minutes of no input. Auto clicker resets the timer. (Read the ethics section first.)
Presentations & kiosk mode
Keynote loops or kiosk displays where the screen can’t turn off mid-show. Keeps it lit without manual trackpad waves.
Long downloads
50 GB Steam downloads, multi-hour git clone, browser downloads that pause when the Mac sleeps on battery. Click trick fixes all.
Compile & build jobs
Xcode, Docker builds, npm install on monorepos, Rust cargo. App Nap throttles backgrounded builds to 5% CPU. Real input events keep foreground priority.
Video playback pauses
YouTube’s “Are you still watching” at 30 min, Netflix’s similar gate, Plex auto-play queues. Click trick reads as continuous activity.
OBS streaming
Long Twitch sessions where you step away. OBS keeps the system awake but the screensaver still triggers. Auto clicker covers the gap.
Discord call status
Long calls or D&D sessions where you go quiet. Discord’s 10-min idle flip changes your friends’ view. Auto clicker keeps you Online.
The Remote-Work Idle-Status Caveat
Read this before using an auto clicker to stay “Available” on Slack or Teams during work hours. Employer monitoring tools (Hubstaff, Time Doctor, Insightful, Teramind) explicitly flag auto clickers as TOS violations and some companies treat them as misconduct grounds. Faking activity in a salaried output-based role is one thing, faking activity in an hourly or contract role where you’re paid for time can be wage fraud. I’m not your employment lawyer. Think twice before running this during billable hours.
Clearly fine: keeping Available during a coffee break, keeping a Zoom presentation running, preventing Slack from flipping you Away while reading a long PR diff. Iffy: walking away from the desk for an hour with status showing Active. I use this trick constantly for non-work scenarios (renders, downloads, Plex, Discord). For work I just close the laptop. A few minutes of Slack saying “away” doesn’t affect my reviews. Faking presence might.
Battery vs Power Adapter Behavior
Sleep timers change depending on whether the Mac is plugged in. My M3 Pro on battery defaults to 2 minutes display sleep and 10 minutes system sleep. On power adapter: 10 minutes display, never for system. The 60-second click rate beats both regardless.
Battery cost of the clicker: 0.4% additional drain per hour on M3 Pro at 60-second intervals. CPU sub-0.1%. The real cost is what it prevents, a lit display draws 4-6W, so total drain runs 8-10% per hour higher than letting the screen sleep. For multi-hour tasks, plug in. A 90-minute render at full brightness eats 35-50% of battery before the render draws its own power.
Apple Silicon Power Management Quirks
M-series Macs are more aggressive about sleep on battery than Intel was. M-chips’ efficiency cores plus unified memory let them suspend RAM to disk almost instantly, so Apple’s tuning prefers to sleep early. For sustained workloads that’s a problem.
Three Apple-Silicon-specific behaviors I noticed in testing: Standby mode drops in after 1 hour on M-chips (was 3 hours on Intel), with battery draw under 0.5W. App Nap throttles backgrounded apps harder on efficiency cores than Intel did, so a backgrounded Docker build slows further. Power Nap (mail fetch, Time Machine, iCloud) during sleep is essentially free on M-chips. Recommendation: for any session longer than 90 minutes on an Apple Silicon laptop, plug in. Power adapter mode shifts defaults toward “stay awake longer,” which combined with the auto clicker is the most reliable setup.
Troubleshooting
The five most common failure modes from a year of using this trick.
Clicker quits when screen sleeps. macOS sometimes pauses event delivery when the display goes dark. Fix: set Display Sleep to Never under System Settings > Lock Screen. Belt and suspenders.
Lock Screen still triggers. Auto-lock is independent of sleep. Fix: System Settings > Lock Screen > Require password “after screensaver begins or display is turned off” set to Never or 4 hours. Security tradeoff, only on a Mac you control physically.
Permission issues. UI says Started but no clicks happen. Fix: System Settings > Privacy & Security > Accessibility, ensure Autoclick is checked. Then Privacy & Security > Input Monitoring, check it there too. Sequoia 15.0+ added Input Monitoring as a separate gate, which many older guides miss.
Clicks register but Slack still flips Away. Slack v4.40+ sometimes uses focused-window check, not just HIDIdleTime. Fix: keep Slack in the foreground or click inside the menu bar so the active-window state is preserved.
Auto clicker stops after macOS update. Updates wipe Accessibility and Input Monitoring permissions. Fix: remove the auto clicker from each list, then re-add. Forces a fresh permission record that sticks until the next update.
Frequently Asked Questions
Will this drain my battery faster?
The clicker itself adds 0.4% per hour on M3 Pro, negligible. The real cost is the lit display (4-6W). An 8-hour run uses 25-50% more battery than letting the screen turn off. Plug in for multi-hour tasks.
Is it more reliable than Caffeine?
Yes for app-level idle (Slack, Discord, Teams, Zoom). Caffeine uses sleep assertions, which only handle display and system sleep. Auto clicker generates real input events, beating every idle timer at OS and app layer. For pure display-sleep, both work equally.
Will it survive a screensaver?
Yes if click interval is shorter than the screensaver activation timer. Default is 20 minutes; a 60-second click beats it 20-to-1. Caveat: the screensaver password gate, if active, still demands your password to dismiss any saver that already engaged.
Can I use it during a Zoom call?
Yes with care. Set click coordinates to the menu bar dead zone or empty desktop, NOT inside the Zoom window. Clicks inside Zoom can mute, leave, or trigger reactions. Used right, it keeps Zoom from auto-leaving during long quiet stretches.
Is it safe to use during work hours?
Depends on role and contract. Salaried output-based: brief use during a break is fine. Hourly or monitored: faking activity can be TOS violation or wage fraud. Hubstaff, Time Doctor, and Insightful flag auto clickers explicitly. Read your employment agreement first.
Does it work in fullscreen apps?
Yes. The click fires regardless of fullscreen state. Caveat: in fullscreen Final Cut or Premiere, clicks inside the timeline can scrub the playhead. Use the menu bar dead zone (still receives events at y=12) or off-screen negative coordinates.
Will my Mac still receive notifications?
Yes. Notifications are unaffected by sleep state and by the clicker. They arrive, stack in Notification Center, play sounds. Only concern: if your click coordinates land in the top-right Notification Center area, the click might dismiss one. Pick a different coordinate.
Can I schedule it to only run certain hours?
Mahdi Autoclick has no built-in scheduler. macOS does. Use Calendar.app with an Automator script, or launchd. Amphetamine has GUI triggers. For “run 2 hours and stop,” set click count to 7200 at 60-second intervals.
Does it work with macOS Sequoia 15.1 and 15.2?
Yes. Tested on Sequoia 15.1 (M3 Pro) in April 2026. Mahdi Autoclick v2.0.4 still works. Only friction is first-launch Open Anyway dialog, tightened to a 6-step flow. Once granted, it persists. 15.2 adds nothing that breaks this.
Does it work on Apple Silicon (M1, M2, M3, M4)?
Yes natively. Mahdi Autoclick v2.0.4 is a universal binary, runs arm64 on Apple Silicon without Rosetta. CPU sub-0.1% on M3 Pro, memory 22 MB. Every M-chip handles this workload identically.
How do I keep Mac awake without installing any app?
Use the built-in caffeinate command. Open Terminal, run caffeinate -di (-d prevents display sleep, -i prevents idle sleep). Leave Terminal open, Ctrl+C to stop. Limitation: no input events, so Slack and Teams still flip you Away. For that, use a real auto clicker.
Mouse jiggler vs auto clicker for this purpose?
A jiggler moves the cursor, a clicker generates click events. macOS treats both as input. But some apps (VPN keepalives, certain remote-desktop tools) only count clicks. Auto clicker is a superset. A $20 hardware jiggler is a viable alternative if you can’t install software.
Related Mac Auto Clicker Guides
If you came here for the keep-awake trick, these adjacent guides cover the rest of the setup. Each one walks a single config change end-to-end.