# Why Is knowledge-agent Using High CPU on My Mac?

> knowledge-agent records app usage for suggestions. What wakes it up, where its knowledgeC and Biome data live, and why deleting them is not a fix.

Published: 2026-11-11 | Updated: 2026-11-14

knowledge-agent is a macOS background process that records how you use your Mac, such as which apps you open and which actions you take in them, and answers other system services that ask about that history for suggestions, usage history and contact predictions. It runs from `/usr/libexec/knowledge-agent` under your own account and is idle almost all the time. A burst of CPU usually means it is catching up after login, a macOS update, a contacts change or a newly paired device. If it stays high, restart once and install pending updates; do not delete its databases.

## What it does

There is no manual page for it, so the evidence is the binary itself and its launchd job. `otool -L /usr/libexec/knowledge-agent` shows it is built on CoreDuet, BiomeFoundation and PeopleSuggester, Apple's private frameworks for usage context, activity streams and people suggestions. Its job file, `/System/Library/LaunchAgents/com.apple.knowledge-agent.plist`, publishes services named `com.apple.coreduetd.knowledge.user` and `com.apple.coreduetd.people.user`, plus suggestion services for calendar, reminder and FaceTime interactions.

On the Mac used for this page, it had used 13 seconds of CPU in almost four days:

```text
tw93  672  0.0% CPU  23 MB  /usr/libexec/knowledge-agent
```

You may see neighbours with similar names. `knowledgeconstructiond` runs from the IntelligencePlatformCore framework, and the `spotlightknowledged` processes, as the name suggests, are tied to Spotlight, so check which name is actually busy before reading advice written for another one.

## When it gets busy

The launchd job lists what wakes it up, and each item is a plausible reason for a burst:

- an interaction is recorded or deleted, for example after you clear history;
- your contacts database changes, because it reacts to an address book change notification;
- another Apple device appears through Continuity (`CompanionLinkDeviceAdded`) or iCloud sync for Siri data changes;
- an app reports an action through App Intents;
- login, when it is started with `RunAtLoad`.

After a macOS update or a migration, several of these happen at once.

| You see | Likely cause | Try |
| --- | --- | --- |
| A short spike after login or wake | Normal catch-up | Nothing |
| Busy after you edit or import many contacts | It reacts to contacts changes | Let the import finish |
| Busy after setting up a new iPhone or Mac | Syncing usage context between devices | Give it time on power |
| High CPU for hours after a macOS update | Rebuilding after the update | Restart once, then install any point update |
| High CPU every day with no change | A stuck job or a damaged record | Restart, update macOS, then contact Apple Support |

## What it stores

It keeps a SQLite database at `~/Library/Application Support/Knowledge/knowledgeC.db` and reads activity streams under `~/Library/Biome`. On this Mac they were small:

```text
35 MB   ~/Library/Application Support/Knowledge
554 MB  ~/Library/Biome
```

`lsof` showed `knowledgeC.db` held open by knowledge-agent and by a second process, `ContextStoreAgent`, at the same time. Biome stream files, such as `App.Activity` and `App.Intent`, were open too. Some of the data also lives in system locations such as `/private/var/db/CoreDuet` and `/private/var/db/biome`, which belong to system accounts and are largely closed to a normal account.

To see what it is doing right now:

```bash
ps -axo user,pid,%cpu,time,args | grep '[k]nowledge-agent'
/usr/bin/log show --last 10m --predicate 'process == "knowledge-agent"' | tail -40
```

Use `/usr/bin/log` rather than `log`, which zsh treats as a built-in command.

## What is safe to do

- Restart the Mac. launchd starts the agent on demand, so a fresh start clears a job that was stuck.
- Install macOS updates. Runaway background processes are fixed in point releases more often than by any setting.
- Reduce what it learns. In **System Settings › Siri**, click **Suggestions** and turn them off for the apps you choose. On earlier versions, click **Siri Suggestions & Privacy…** instead, choose an app and turn off **Learn from this application** (on macOS Tahoe the pane is **Apple Intelligence & Siri** on Macs that support it). This narrows what Siri learns from or suggests in that app; it is not a documented switch for the process.
- Ending it in Activity Monitor is harmless as a test, but it will come back the next time something asks.

## What not to do

Some guides tell you to run `sudo killall knowledge-agent` and then delete `~/Library/Application Support/Knowledge` or `~/Library/Biome`. Apple does not document either step, and there are good reasons to skip them:

- The database is open in two processes while you delete it, so the result depends on timing.
- It holds the history that suggestions and usage reports read. Removing it does not just clear a cache; that history is gone, and whatever rebuilds it starts from nothing.
- If the cause is a bug, the CPU returns once the agent starts recording again.

No Apple document, and no measured before-and-after found while writing this page, shows what deleting these folders fixes or breaks. The guides that recommend it describe a rebuild over the following days, but none of them shows one, so restart and update first.

## Is it malware

The real file is `/usr/libexec/knowledge-agent`, on the sealed system volume, and it is signed by Apple:

```bash
codesign -dv /usr/libexec/knowledge-agent 2>&1 | grep Identifier
```

It should print `com.apple.knowledge-agent`. A process with this name running from your home folder or `/tmp` deserves a closer look.

## Where Mole fits

[Mole](https://mole.fit/) lists `knowledge-agent` in **Status** with its CPU and memory when it is busy, and the table's search finds it when it is not. **Why is this running?** in its menu shows the executable, the launchd service and what started it, which helps when it is busy and you want to know which event woke it. Because it runs from a system folder, Mole shows no **Terminate** or **Force Quit** for it. Clean does not list `knowledgeC.db`, the Biome folder or anything else this agent keeps, and Mole does not change Siri or suggestion settings. For other system processes, see [Mac processes explained](https://mole.fit/blog/mac-processes-explained) and [Activity Monitor on Mac](https://mole.fit/blog/activity-monitor-mac).

## FAQ

### What is knowledge-agent on Mac?

It is a macOS process that records app usage and interactions in a local database and serves that history to suggestions and other system features. It runs from `/usr/libexec/knowledge-agent`.

### Why is knowledge-agent using high CPU?

It is usually catching up after login, an update, a contacts change or a new device. If it stays busy, restart once and install pending macOS updates.

### Can I delete knowledgeC.db or the Biome folder?

Apple does not document it, both are in use while the Mac runs, and they hold the history suggestions depend on. Restart and update first; deleting them is not a supported fix.

### Can I disable knowledge-agent?

There is no supported switch. You can turn Siri suggestions off per app under **Siri › Suggestions**, or on earlier versions with **Learn from this application** under **Siri Suggestions & Privacy…**.

### Is knowledge-agent a virus?

The real one runs from `/usr/libexec` and is signed by Apple as `com.apple.knowledge-agent`. Check the path and signature if in doubt.

---

Canonical HTML page: https://mole.fit/blog/knowledge-agent-high-cpu-mac
Blog index for agents: https://mole.fit/blog/llms.txt
Site index for agents: https://mole.fit/llms.txt
