If you’ve spent any significant time automating workflows on macOS, you’re probably familiar with the maddening issue of permissions randomly resetting on reboot. Whether you’re using tools like Keyboard Maestro, Hammerspoon, Shortcuts, or AppleScript, there’s a high chance that your finely tuned automation setup runs into sudden, inexplicable blocks. One day everything works smoothly. After a reboot? Your scripts hit a wall, asking repeatedly for permissions they’ve already been granted.
This isn’t just annoying—it disrupts productivity, kills reliability, and makes advanced scripting on macOS feel like walking a tightrope. After much trial and error, a relatively obscure but powerful fix has surfaced: the TCC Reset Trick. This article explains what the problem is, why it keeps happening, and most importantly, how to fix it permanently.
TL;DR
macOS automation tools can lose their permission settings after every reboot due to conflicts or corruption in the TCC (Transparency, Consent, and Control) database. This leads to repetitive prompts asking for control of apps like Finder, System Events, or Terminal. Using a safe TCC reset method—and reapplying permissions only once—can resolve this issue for good. Read below to learn step-by-step how to stabilize your automation workflows.
Understanding Why macOS Keeps Forgetting Permissions
macOS uses the Transparency, Consent, and Control (TCC) framework to manage access to sensitive services like accessibility, Full Disk Access, screen recording, and automation permissions. Apps or scripts requesting actions like “control another application” or “record screen” must be authorized through TCC on an app-by-app basis.
But here’s the catch: sometimes that database gets corrupted, overwritten during updates, or misconfigured—especially when your tools are installed outside of typical app directories or you use things like SIP-disabled boot modes, Homebrew installations, or symlinked services. The result? Your device “forgets” you’ve already given permission.
This is most commonly observed in:
- Accessibility permissions not sticking (e.g., Hammerspoon stopping mouse input)
- AppleScript commands triggering authorization errors
- Keyboard Maestro failing to control other apps
- Frequent popups asking for access to Finder or System Events
In short, if your automations work once and then stop after a reboot, you’re probably suffering from a messy TCC state.
The Solution: The TCC Reset Trick
After banging heads with plist files, reboot orders, re-authorizations, reinstallations and even SIP toggles, advanced users discovered a more reliable fix: resetting TCC properly and reauthorizing freshly—all before any app tries (and fails) to run automation scripts.
Here’s a step-by-step outline you can follow:
1. Back Up Your System and Scripts
This process affects system-level permissions, so having a Time Machine backup or bootable clone isn’t optional. Also, back up your automation scripts and configurations in case you need to reimport workflows after the reset.
2. Boot into Recovery Mode
- Shut down your Mac.
- Turn it on and immediately hold Command + R to enter Recovery.
3. Launch Terminal from Recovery
- From the top menu, select Utilities > Terminal.
4. Disable SIP Temporarily (if Needed)
If you plan to reset system-wide TCC databases, you might need to disable System Integrity Protection (SIP).
csrutil disable
Don’t forget: re-enable SIP later to keep your system secure.
5. Reset TCC Permissions
Next, you’ll be using the tccutil command or removing the database directly.
Option A: Use tccutil
tccutil reset All
This will remove all previously granted permissions for all apps. On reboot, any app that needs permission will ask again.
Option B: Manually Delete the TCC.db
This is more aggressive and is typically done if tccutil doesn’t solve the issue.
rm /Volumes/Macintosh\ HD/Library/Application\ Support/com.apple.TCC/TCC.db
Or, for user-specific permissions:
rm /Volumes/Macintosh\ HD/Users/YOURUSERNAME/Library/Application Support/com.apple.TCC/TCC.db
Be careful. Deleting this database will wipe every app’s permission state clean.
6. Reboot Normally and Reapply Permissions
After rebooting, open each automation tool and manually re-grant all required permissions through System Settings > Privacy & Security:
- Accessibility
- Automation
- Full Disk Access
- Screen Recording (if capturing UI elements)
Make sure the checkbox stays ON for each permission you enable. It’s advisable to test autorun scripts immediately after setup to ensure everything works as expected.
7. Enable SIP Again (Optional But Recommended)
- Reboot into Recovery Mode again.
- Open Terminal and run:
csrutil enable - Reboot as normal.
Make It Stick: Best Practices Going Forward
Now that your automations are back in stable territory, use these tips to keep them running smoothly:
- Avoid moving script or executable locations after granting permissions. macOS tracks the path; moving a tool breaks the link.
- Be cautious with system updates—they can tweak the TCC database. After major updates, double check your automation settings.
- Use officially bundled formats where possible (e.g., DMG installers > moving raw .apps around)
- Stay SIP-compliant for everyday use; only disable it during maintenance or TCC repair procedures.
What to Do If It Still Doesn’t Work
If your permissions still reset despite resetting TCC, the issue may be rooted in:
- Corrupt
launchdstartup scripts interfering with permissions - Third-party antivirus or security tools resetting database states
- Cloud-sync folders (like iCloud or Dropbox) used to store scripts or app bundles
In these cases, try storing your tool in /Applications, using local-only data sources for automation, and disabling other startup apps temporarily to isolate the problem.
Final Thoughts
Stability and reliability are the cornerstones of good automation. macOS’s TCC framework is powerful but notoriously fickle, and it can silently undermine your best-laid workflows. If you’re tired of reapplying permissions after every reboot, the TCC reset trick offers a robust solution that can finally give you peace of mind.
With just a little precaution and a one-time reset, you can regain total control over your scripting environment—and finally make your Mac the autonomous machine it was meant to be.