Your first scan

Under the heading, Pip tells you the state of the machine in one line — how many dev servers are running, what they are using between them, and which one is the heaviest. On a normal working day that sentence is the entire answer, and you can close the window again.

Below it, the card carries the combined figure and a tick meter of 40 dots. Each contiguous run of colour is one process's share of the total, ordered largest first, with the legend underneath naming the ports those colours belong to.

The CPU / MEM toggle on the right switches which resource the card and the meter are measuring. It is a view switch, not a filter — the list below is unaffected.

The search box matches on projects, ports and branches at the same time, so 5173, storefront and main are all valid ways to find the same row. Press / to jump straight into it.

Project

The repository or folder the server was started from — not the process name.

Memory share

Percentage of the machine's memory, with the absolute figure beside it. Amber once a process is running hot.

Load bar

The comb meter. Colour is a property of position along the track, so a bar reads the same way every time.

Port and branch

The listening port, and the git ref read straight from .git — more on branches.

CPU

Current usage, sampled every 1.5 seconds.

The Servers guide covers what you can do to a row once you have found it.

The dock floats at the bottom of the window. Servers is the curated list of your dev servers; Network is every listening port on the machine and who can reach it; Storage is on its way.