Why is my server missing or not updating in Radar?

Check the running server and monitoring choices

1. Confirm the server is still running in the terminal or development tool where you started it. A command that has not begun listening, has exited, or only makes outbound connections will not produce a server card.
2. Open Radar's panel to request a fresh scan. All clear means no visible monitored groups matched; it does not prove that every local process stopped.
3. Open Settings… → Detection and check that the intended rule is enabled.
4. Check Ignored (N) in the panel footer. Choose Restore [folder name] if you previously hid the project.
5. Turn on Show unrecognized localhost servers to look for an accessible listener not claimed by the current rules.
6. If it appears as Other, inspect Details… and use Add as Custom Tool… if you want a saved recognition rule.

The built-in rule name is not enough by itself: its process prefix and command text must match. For example, a Python process needs the http.server command term to match Python HTTP. A different server module may need a custom tool even though Python is a supported runtime.

Radar inspects processes owned by the same macOS user. A server running as another user or in a guest environment is outside that native process view. Radar has no remote, Docker, or VM process integration. A host-side forwarding process may be visible if it is a same-user TCP listener, but it is not a view of the guest's internal process tree.

Handle Scan unavailable or an orange scan warning

With no retained rows, a failed process-table scan shows Scan unavailable and Radar will retry. Process controls are paused. If a previous successful sample exists, its rows remain and the header has an orange warning. Its help text is Last scan failed. Showing the last successful sample.

Wait for the next successful scan. You can close and reopen the panel to request another attempt. Stop, Force Stop, notification Stop it, and Stop All cannot override an unavailable scan. Treat the retained resource numbers and endpoints as old observations until the warning clears.

If failures persist across several scan intervals, quit and reopen Radar, then record whether the same symptom returns. The app provides no special permission-granting or administrator button for this error. Report the message, the last successful sample time, and the macOS/app version rather than treating an empty list as proof of no servers.

Check refresh timing and retained details

The open server panel refreshes every 2 seconds. With the panel closed, Radar uses Check for servers every from General: 5, 15, 30, or 60 seconds. Opening Details closes the panel, so a Details window alone follows the background cadence.

The header's relative timestamp updates as time passes, but that changing text is not itself a new scan. Use the time since the last successful sample and the scan warning together. Radar pauses during sleep and requests a scan on wake. CPU needs a new comparison sample after wake.

If an old Details window says Server stopped but you believe the process is running, reopen the panel and find its current card. A restarted process has a new identity; the old window does not switch to that new server automatically. A changed detection rule or Ignore setting can also make the old identity absent from the visible list.

History is bounded to 120 samples within 30 minutes and is not a saved log. An empty history after a restart, ignore, rule change, or quit can be expected. Readiness has its own scheduling limit; it does not refresh every 2 seconds with the card.

Check changed tool labels or missing custom rules

If the label changed, inspect Detection for an overlapping custom rule or disabled built-in. The first enabled complete match wins. All custom rules precede built-ins; earlier custom rules precede later ones. Disabling a specific rule may expose Node server or another fallback instead of hiding the server.

If a custom tool appears in Detection but never matches, open Edit and check its fields and enabled switch. Save preserves a disabled rule's disabled state. Make sure you clicked Add Tool or Save; Cancel, closing the editor, or opening another editor discards a draft.

Radar stores custom rules and disabled built-in choices in:

~/Library/Application Support/Radar Dev Monitor/profiles.json

If the file exists but cannot be decoded, Radar attempts to move it to profiles.json.bad and falls back to fresh built-ins. That can explain why custom tools are gone and previously disabled built-ins are enabled again. If the file cannot be read at all, Radar also starts from built-ins, without a specific recovery dialog.

For support, use Finder's Go → Go to Folder… with ~/Library/Application Support/Radar Dev Monitor and check whether profiles.json or profiles.json.bad exists. Preserve the files before any repair, and review their contents before sharing. The app has no profile Import, Export, Reset, or recovery button; do not delete or hand-edit the files as a first troubleshooting step.

Profile saving does not show an in-app write-error message. A rule can work in the current session yet fail to persist if the file could not be written. If the problem only appears after quitting and reopening, include that distinction in your report.

Gather useful details for support

Include the app version/build if available from Finder's app information, macOS version, expected tool, exact symptom, and whether it began after sleep, a restart, or a settings change. This UI has no About/version command.

If a card exists, include its tool label, full project path, Executable, Root PID, endpoints, detection explanation, and whether the chain is current or previously observed. Review the command text for secrets and personal paths before sharing it.

If no card exists, include whether the tool is enabled, whether Show unrecognized is on, whether the project is ignored, and whether the terminal still reports a listening server. Note any scan warning, failed-stop warning, or saved-rule persistence problem. Radar has no built-in diagnostic export button, so collect only the relevant visible details.