Alfred is one of those magical productivity tools Mac users often swear by. Its Workflows—a customizable automation feature—can streamline even the most repetitive macOS tasks. But nothing halts that productivity spree faster than a Workflow that mysteriously stops functioning. If you’ve recently found your Alfred Workflows suddenly losing access to macOS features like file access, automation, or scripting, you’re not alone. And the culprit? A silent shake-up in macOS’s TCC database, which governs system permissions.
TL;DR: Workflows Broken? A TCC Reset Might Be the Fix
Some Alfred Workflows stopped working properly due to broken or missing permissions managed by macOS’s TCC (Transparency, Consent, and Control) database. Users noticed errors when automations tried to control other apps, access files, or execute scripts. The fix? Resetting permissions for Alfred via the TCC system forces macOS to re-request access and restores normal behavior. It’s a relatively safe process—but knowing why it happens and how to fix it makes life much easier.
What’s Going On Behind the Scenes?
macOS, especially from version 10.14 (Mojave) onwards, introduced a strict security model via Transparency, Consent, and Control (TCC). It ensures apps explicitly request and receive user permission before accessing sensitive features—think Full Disk Access, Screen Recording, Accessibility, etc.
Alfred Workflows often rely heavily on these permissions, particularly when:
- Running AppleScripts to automate app behavior
- Accessing specific folders on your Mac
- Communicating with other apps using scripting or plugins
Occasionally, a macOS update, backup restore, or system hiccup can silently corrupt or reset the TCC database. This causes previously granted permissions to vanish without warning. Suddenly, Alfred can’t control Finder or run a script that worked perfectly yesterday.
Signs Your Alfred Workflows Have Lost Permissions
It can be subtle at first, but telltale symptoms begin to show:
- Workflows involving AppleScript or shell scripts fail silently or return permission errors
- Alfred can no longer open files or applications it once could
- Error messages like “not authorized” or “not allowed to control System Events” appear
And perhaps the most confusing part? Going into System Settings → Privacy & Security shows Alfred is already listed and checked under Accessibility—and sometimes other sections like Automation. But things still don’t work!
Why Updating macOS Might Break Things
macOS updates often include changes to how permissions are handled. While the system usually attempts to preserve existing settings, inconsistencies can arise, especially if:
- You performed a Time Machine or third-party backup restore
- The system crashed or failed during an update
- You used migration assistant to set up a new Mac
TCC is stored in a SQLite database on your Mac, but it is not user-editable by conventional means. When this database becomes corrupted or misaligned with the actual app permissions, macOS behaves as though access was never granted—yet offers no visible prompt to fix it.
The Solution: Resetting Alfred’s TCC Permissions
Fortunately, there’s a tested remedy: forcibly resetting Alfred’s TCC permissions. This forces macOS to forget all previous grants and errors, allowing you to re-approve everything from scratch.
Safe Steps to Reset Alfred’s TCC Permissions:
- Ensure Alfred is closed (quit from the menu bar).
- Open the Terminal app.
- Enter the following command:
tccutil reset All com.runningwithcrayons.Alfred
What this does:
- tccutil reset All: Clears all saved permissions (Full Disk Access, Accessibility, etc.)
- com.runningwithcrayons.Alfred: Targets only the Alfred app (not a global wipe)
After running this command, it’s crucial that you:
- Reopen Alfred
- Launch any workflow that requires permissions (like opening a file or using AppleScript)
- Look out for the macOS permission prompts and click “Allow” when they appear
Double-Check Accessibility and Automation Permissions
Sometimes, simply resetting isn’t enough—you may need to manually toggle permissions in System Settings once Alfred has relaunched. Here’s where to check:
- System Settings → Privacy & Security → Accessibility
Ensure Alfred is listed and switched ON. - System Settings → Privacy & Security → Automation
Re-approve any apps Alfred is trying to control, such as Finder, System Events, etc.
Note that sometimes, Alfred may not reappear under Automation until a specific workflow tries to access another app. That’s when macOS will prompt you and insert it into the Automation section for approval.
When Else Should You Consider a TCC Reset?
The beauty of using tccutil is that it’s safe and reversible. If you’re experiencing similar issues with other apps—like Keyboard Maestro, Hazel, or even Terminal not having access—you can run the command using the appropriate bundle ID.
Examples:
- Reset Terminal permissions:
tccutil reset All com.apple.Terminal - Reset Keyboard Maestro permissions:
tccutil reset All com.stairways.keyboardmaestro.engine
Just make sure you know what you’re resetting. Resetting “All” system-wide, without specifying an app, can lead to a flood of permission prompts across many apps.
How to Prevent Workflow Interruptions in the Future
While you can’t control when macOS decides to act cranky, you can minimize the likelihood of TCC issues:
- Back up your Mac before major updates or migrations
- Review permissions periodically, especially after updates
- Keep Alfred and workflows up to date with recent patches
- Use named bundle IDs in your scripts for better compatibility
It’s also worth joining Alfred’s user forums or newsletters—developers often post alerts when they detect permission-related bugs following macOS updates.
Final Thoughts
Alfred remains one of the most powerful tools in the macOS automation arsenal. When Workflows mysteriously break, it can feel more like sabotage than a system safeguard. But understanding the inner workings of the TCC system and how to reset permissions puts the power back in your hands. Whether you’re an automation junkie or just someone who’s tired of clicking through repetitive tasks, mastering these fixes ensures Alfred keeps working the way it was meant to—efficiently and invisibly.
So the next time Alfred seems to “forget” what it once could do, don’t panic. A quick TCC reset may be all it needs to regain its voice.
