---
title: "Stats and gauges"
description: "The fleet summary, per-agent CPU and RAM across the whole process tree, and the machine gauges."
canonical: "https://agent-manager.dev/docs/stats/"
last-updated: "2026-08-21"
section: "Documentation"
source: "agent-manager"
---

# Stats and gauges

The header carries a fleet summary: per-status session counts, plus the CPU and memory every live agent's full process tree is using, shell and agent and children together.

`header`

```
agents total usage: cpu 12% · ram 8% · 6.2 GB
```

CPU is that tree's CPU time over the last poll as a share of total machine capacity, the same 0-100% unit the computer gauge uses. RAM is resident set as a share of installed memory, with the absolute size beside it. The selected session's detail line uses the same scale for that one session.

## The machine gauges

| Gauge | What it measures |
| --- | --- |
| cpu | Whole-machine utilization, 0-100%. |
| mem | Used over total. On macOS this matches Activity Monitor's Memory Used: resident RAM minus free, speculative and reclaimable file cache. On Linux it is `Total - MemAvailable`, so file cache is not counted as used. |
| swap | Used over the current swap allocation. On macOS the swap file grows under pressure, so the denominator is the live size from `vm.swapusage` rather than a fixed partition. |
| disk | Fill of the root filesystem, used over used plus available, with free space from the kernel's available figure. |
| net | Up and down rates on real NICs only. Loopback, utun, bridges and similar virtual interfaces are excluded. |
| temp | `cpu`, `gpu` and `soc` in °C, each the hottest sensor in its category, sampled every five seconds. |

> **Apple Silicon** Its dies report as one `soc` figure rather than separate CPU and GPU lines. A reading appears when the machine exposes that sensor.