How do I stop servers, protect a project or hide it?

Stop one server

1. Open the panel and identify the correct project, tool, and URL.
2. Click its red stop button, right-click its card and choose Stop, or open Details… and click Stop Server.
3. Wait for the progress indicator and the next scan. A stopped server's card disappears.

Stop acts on the related process group represented by that card, including its tracked workers. Radar checks current ownership and process identities before signaling. It first asks the processes to terminate, allows up to 3 seconds for a graceful exit, then force-kills remaining processes. Normal Stop can therefore escalate automatically.

The controls act immediately; there is no confirmation dialog. Review the card before using them. Stopping ends that server session. Radar has no Start or Restart button; restart it using your usual development command.

Use Force Stop when needed

Right-click the card and choose Force Stop, or hold Option while clicking the red stop button. Force Stop sends the force-kill signal immediately, skipping the graceful period. It can interrupt cleanup work, so use normal Stop first when practical.

Force Stop still validates process identities and ownership. It cannot bypass a failed scan or unavailable process access. The Details Stop Server button uses normal Stop; it does not have a separate Force Stop option.

Protect a project before using Stop All

1. Open Details… for a server you want to retain.
2. Under Project preferences, turn on Protect this project from Stop All.
3. Return to the panel. A shield indicates Protected from Stop All.
4. Review the remaining cards, then click Stop All.

Stop All uses normal Stop concurrently for the visible, unprotected servers. Protected projects remain listed and running. Ignored projects are outside the visible list and are not Stop All targets. The button is disabled when the list is empty, every visible project is protected, or a scan is unavailable.

Protection is saved for the project folder and applies to its other cards and future server sessions. It only guards Stop All. A card's Stop, Force Stop, Details Stop Server, or a notification's Stop it can still stop that protected server.

For example, protect an API you still need, then use Stop All to clear the other visible servers. To include the API in a later Stop All, turn its protection switch off first.

Hide a project and restore it later

1. Open the server's Details… window.
2. Under Project preferences, turn on Ignore this project.
3. Return to the panel. The project's cards are hidden, and the footer offers Ignored (N).
4. To restore it, open Ignored (N) and choose Restore [folder name].

Ignoring does not stop the server. It removes the project from the visible monitored set, its counts and resource total, its alert evaluation, and its readiness checks. The saved ignore choice applies across restarts for the same project folder. An already-open Details window shows Ignored project, and you can turn Ignore this project off there too.

The restore menu can include an ignored project whose server is currently stopped. Restoring changes the preference; its card returns only when a detectable server is running. Restore entries use the final folder name, so two different paths with the same folder name can look alike. Use an open Details window or check the full project path if you need to distinguish them.

Know which servers share project preferences

Radar uses the detected listener's working folder as its project folder. Cards with the same folder share protection, ignore, the alert snooze end time, Address, Protocol, and HTTP readiness. The settings are saved as you change them.

Separate process groups can appear as separate cards while sharing those preferences. They do not share the temporary Long-running reminders off or Memory reminders off choice made from a notification; those apply to one server identity.

For example, two independent web and API servers started from /Projects/shop can have separate cards. Protecting or ignoring that folder applies to both. Changing Protocol to HTTPS applies to both too, so check that each server supports the choice. The saved Address includes its port; a card without that endpoint uses the fallback described in endpoint selection.

Moving a project or starting it from a different working folder gives it a different preference key. Radar does not migrate choices by display name. If Project folder unavailable is shown, the choices are tied to that process session instead, and should not be expected to follow a restart.

Handle a failed or unavailable stop

1. If the header has an orange warning or says Scan unavailable, wait for a successful scan. Radar retries automatically and refuses all stop requests while the scan is unavailable.
2. If a yellow warning appears beside a card after Stop, hover it to read the failure message. Recheck the current card and Details before retrying.
3. Try Force Stop only when you intend to interrupt the current server immediately. Normal Stop already attempts force-kill after its grace period.
4. If the process keeps returning, check the terminal or development tool that launches it. A supervisor may be creating a new server session. Compare Root PID and the running-since time to see whether the card is new.

A stop can fail when the process changed identity, cannot be inspected, or cannot be signaled. Current monitoring is limited to processes owned by your user; Radar does not offer an administrator elevation workflow. A failure warning clears after a later successful stop or when the server leaves the monitored list.

Stop All is also unavailable when every visible project is protected. Open Details to remove the protection you intend to change. Quitting Radar closes monitoring and leaves the servers running.