Module blockstats_detail 

What a terminal’s stats badge tooltip shows beyond the badge’s own CPU and memory (blockstats.detail), and the badge’s peak memory.

The badge (sysinfo::run_sysinfo_loop, through sampler::panes) counts the pane’s processes as Tower groups them: its Job Object or cgroup, else its shell’s tree. The tooltip describes the shell and every process under it: their names, when the shell started, and two more memory figures from one agentmux_procstats snapshot, private and committed. A process that left the shell’s tree is in the badge’s figures but not in the tooltip’s. A snapshot costs tens of milliseconds, so it is taken only while a tooltip is open, never on the badge’s every-second tick.

A remote pane (SSH, WSL) is measured on the machine it is connected to, by AgentMux’s helper there (PaneProcs); remote turns its answer into the badge’s figures, with a peak kept here. SPEC_TERMINAL_STATS_BADGE_REMOTE_PANES_2026_10_12.md.

Structs

Peaks

The highest memory each pane’s badge has shown since AgentMux started watching its shell. A new shell in the same pane (a restart) starts over.

RemotePeaks 🔒

Constants

REMOTE_PEAK_IDLE 🔒

Functions

detail

The tooltip’s numbers for the process tree under root_pid, at most max processes (the badge’s own cap). None when the shell isn’t in the snapshot (it exited).

display_name 🔒

An executable’s name as a person calls it: pwsh, not pwsh.exe.

remote

A remote pane’s helper answer as the badge’s figures, with its peak.

remote_peaks 🔒

Remote panes’ peaks, by pane and shell (its start: the PID is the other machine’s). A pane not asked about for REMOTE_PEAK_IDLE is forgotten.

remote_unavailable

A remote pane whose machine couldn’t be asked, and why.

Type Aliases

Shell

Which shell a peak is for: its PID and start time, so a restarted shell that got the old one’s PID back is still a new shell.