Find what is keeping your Mac busy

Identify a process contributing to load without launching, stopping or changing any process. Start with Fleet Console installed and running on macOS 14 or later. Leave builds, editors and background services as they are while you inspect them.

Read Quick View

1. Find the Fleet Console cluster in the menu bar. It shows CPU, memory and disk use, connection state, and an attention count when something needs a look.
2. Click it to open Quick View: CPU and memory dials, a disk-capacity map and upload/download bars.
3. Note the resource that appears busy. One reading is one sample, not proof of sustained load or a fault.

Follow the load

1. Open the dashboard from the menu-bar controls, or press Command 0.
2. Begin in Overview, where resource histories and large process consumers provide context.
3. Choose CPU or Memory and compare the 15-second, 30-second, 1-minute and 2-minute ranges. Read the actual observation times; a sampling gap is not measured inactivity.
4. Open Processes with Command 2 and select the process you want to inspect. Keep its identity separate from another row with a similar name.

Search with Command K filters the current destination. Changing destinations clears that filter, so search again after switching rather than assuming a missing row has exited.

Check your finding

You should be able to name a process and say whether its resource use was brief or sustained over the observed window. If a service record accompanies it, inspect owner, purpose and lease. Work launched outside the controller can be unmanaged; a claimed record adds attribution without controller signalling authority.

Do not report an unavailable sensor as idle, or an existing process as healthy. If the process exits before you inspect it, choose a current row rather than treating its old PID as an enduring identity. If the controller is disconnected, current service status needs fresh evidence before any control action.

Continue with timed charts or the fleetctl reference.