How to Clear the macOS CoreSuggestions Daemon Cache via Terminal

The Proactive Intelligence Engine

When you open the Apple Mail app on your Mac and receive an email saying, “Let’s meet for coffee on Thursday at 3 PM,” macOS will often automatically underline the date and time. If you click it, the system instantly offers to add an event to your Calendar. If a friend texts you an address in Messages, macOS will suggest opening it in Apple Maps. This seamless contextual awareness is powered by the CoreSuggestions daemon (suggestd).

The suggestd process constantly runs in the background, scanning the plaintext of your emails, iMessages, and Safari browsing history. It uses local machine learning models to identify entities like dates, flight numbers, package tracking codes, and contact information. It stores these extracted entities in a massive SQLite database so it can instantly present them to you across the operating system.

However, if this database becomes corrupted—or if the local ML models get stuck in an infinite processing loop while trying to parse a massive, malformed email thread—the symptoms are severe. The suggestd process will suddenly consume 100% of your CPU, your MacBook battery will drain in less than an hour, and Mail/Messages will become incredibly sluggish. To stop this runaway intelligence loop, you must forcefully purge the CoreSuggestions cache via the Terminal.

Locating the Suggestions Cache

Because CoreSuggestions scans highly sensitive personal data (your private text messages and emails), its cache is strictly isolated within your specific user profile. It is located deep inside the user Library, specifically within the Suggestions directory.

Purging the Cache via Terminal

While you do not strictly need sudo to delete files in your own user profile, using it ensures that we can forcefully terminate the locked background daemon without permission errors.

1. Open the Terminal application.
2. First, you must forcefully terminate the suggestd daemon. This immediately stops the runaway CPU usage and releases the file locks on the SQLite database:

sudo killall suggestd

Press Enter, type your Mac’s administrator password (the characters will remain invisible), and press Enter again.

3. Next, aggressively delete the primary Suggestions database directory. We use the -rf flag to recursively delete the folder contents without asking for confirmation:

rm -rf ~/Library/Suggestions/*

4. Additionally, clear the personalized language models and entity extraction caches associated with the daemon:

rm -rf ~/Library/Caches/com.apple.suggestd
rm -rf ~/Library/Containers/com.apple.corerecents.recentsd/Data/Library/Caches/*

The Recalibration

macOS relies on launchd to manage its background services. The moment you executed the killall suggestd command, the operating system detected that the daemon had died and immediately respawned a fresh, uncorrupted instance of it.

This new daemon will initialize against an empty ~/Library/Suggestions/ directory. The CPU usage will instantly drop back to a normal baseline (typically 0%), and the massive system lag will be permanently resolved.

What happens next? Over the next 24 to 48 hours, the suggestd process will slowly, quietly, and efficiently re-scan your recent emails and messages to rebuild the contextual entity database. You might temporarily lose the “automatic calendar invites” feature for a day, but the system stability will be completely restored without the crippling overhead of a corrupted machine learning loop.