Process monitor

Running many agents means running many processes — agent CLIs, language servers, shells, renderers. The CPU-chip button in the toolbar shows the total RAM across Grove's whole process tree; clicking it opens a per-process breakdown.

What it shows

One row per process: a kind chip (agent, LSP, MCP, shell, renderer, …), a description, the PID, a usage bar, and MB. Sorted largest-first, refreshed every couple of seconds while open. The total is an upper bound — shared memory between helper processes is counted more than once.

Kill and jump

• Rows that belong to a terminal or chat are click-to-jump — find the runaway process, land in the surface that owns it.
• Non-system processes can be killed from the row (with an inline confirm). Grove refuses to kill anything that isn't its own descendant.
• LSP rows are special: killing one disables auto-spawn for that whole language — otherwise Grove would just respawn it. Disabled languages stay off across restarts; re-enable from the same popover. This is the main control surface for "rust-analyzer is eating my laptop." See LSP.

What it is not

Despite living behind a memory chip, this has nothing to do with agent context or CLAUDE.md — it's purely an OS process and RAM monitor.