How do I read resource use and process details?
Read a server card, compare recent resources, find its project, and understand the processes Radar grouped together.
In this article
Read the server card
Each card shows the project folder's final name, the matched tool, the selected URL or Choose endpoint…, and since [time]. If the project folder is unavailable, the display name uses localhost:[port] instead. Cards are ordered by their first listening port, then a stable process identity.
The icon and color come from the detection profile. A shield means the project is protected from Stop All. Background describes a detached parent. Long-running reminders off and Memory reminders off show that the corresponding alert kind was silenced for this server.
The main text opens the server. The information button opens Details. The red stop button stops it. These are separate accessible controls. The card's context menu offers Details…, Open in Browser, Reveal in Finder, Stop, and Force Stop. Cards labeled Other also offer Add as Custom Tool… and a plus button.
A card represents a logical server group, not necessarily one process or one port. Related listeners, verified package-manager wrappers, and descendant workers can share a card. General-purpose launchers and different projects stay separate. Two cards with the same folder name may represent separate groups or different full paths; inspect Details before acting.
Use Recent resources to spot changes
- Click the information button or choose Details… from the card's context menu.
- Find Recent resources.
- Compare the current memory and CPU with the Memory · MB and CPU · % charts.
- Keep the server panel open when you want 2-second samples, or choose a suitable background interval in General.
Memory is the combined physical footprint of the processes in the card's group. The panel header and optional menu bar memory value total the visible groups. CPU is measured from changes in cumulative process CPU time between scans, not from the server's entire lifetime. More than 100% is possible when a group uses multiple CPU cores. Card CPU values above 50% are colored orange; that color does not itself trigger a notification.
CPU warming up means there is no comparison sample yet, such as just after discovery or wake. History appears after the next sample. means there are not yet enough samples to draw the charts.
Radar keeps up to 120 samples from the last 30 minutes for each currently monitored server. The count can shorten the visible time range: at 2-second sampling, 120 samples cover roughly 4 minutes. History is kept in memory, not saved as a log, and is discarded when the server leaves the monitored list or Radar quits. There is no chart export control.
For example, observe the memory before a rebuild and again afterward. A rise in this group is a useful clue, but Radar does not identify which application object allocated the memory. Use the process count and your development tools for a deeper investigation.
Identify the process and its detection rule
In Details, the header shows the tool and number of grouped processes. Under Process details, check:
| Field | How to use it |
|---|---|
| Executable | Name of the primary listening process, useful for a custom rule |
| Root PID | The process at the root of the group Radar can stop; it may be a package-manager wrapper |
| Project path | Full detected working folder, or Project folder unavailable |
| Detection explanation | Which profile matched, or Listening TCP socket; no enabled profile matched. |
| Command | Display of the primary listener's command arguments, with known credential forms redacted |
The primary listener and group root can differ, so Executable and the displayed command need not describe Root PID. The since time uses the group root's start time. It can begin before the listening process itself started.
The command display hides recognized token/password/secret/API-key/authorization/credential forms and URL credentials, query strings, and fragments. Review the text before sharing it: unusual secret formats are not guaranteed to be detected. Full command matching uses the original arguments, so redaction does not prevent the tool from being recognized.
An open Details window follows that server's current samples while it is monitored. If it disappears, the window retains its original details and may show Server stopped. Reopen the panel to distinguish an exited process from an ignored project or changed rule. Stop Server and Open are disabled when the server is no longer in the monitored list; an old URL may still be copied.
Understand Background and the parent chain
Background means the group's root now has the system process as its parent. The original parent is no longer attached. This can be intentional; it does not mean the server was abandoned or should be stopped.
Current parent chain lists the parents Radar can observe now, nearest first, with names and PIDs. If the parent detached after Radar saw it, Previously observed parent chain may retain that earlier observation. This is historical evidence, not a live launcher connection.
If Radar never observed the original chain, it shows Original launcher unknown. It cannot reconstruct an original terminal or AI tool from a detached process. The observed chain is limited to 20 parents and the processes available in Radar's same-user scan.
Find the project in Finder
Right-click the card and choose Reveal in Finder. Radar asks Finder to select the detected project folder. If the folder is unavailable, this action has no folder to reveal. Open Details to copy or inspect the path instead.
The path is the running listener's working folder. It may differ from the repository root you expected if you started the tool in a subfolder or it changed directories. Radar does not let you relabel or assign a project folder manually.