How do I choose which tools Radar recognizes or add my own?

Enable or disable the built-in tools

1. Right-click Radar's icon, choose Settings…, and open Detection.
2. Find a tool in the list and change its switch.
3. Reopen the server panel to request a scan and check the result.

All built-in rules start enabled. Their switches save across launches. Switching a rule off changes recognition; it does not stop its server. Another enabled rule may still recognize the same process under a different label, or it may appear as Other if the unrecognized-server option is on.

The current built-in list is ordered as follows. Each rule also requires a listening TCP socket. A process-name entry is a case-insensitive prefix; each command entry is a case-insensitive substring. Alternatives within a column are joined by “or.”

The first complete enabled match wins. Custom rules are checked before built-ins. Specific built-ins precede broad ones; Node server is last. This list explains recognition, not a promise that every way of launching a framework will match. If your command differs, create a custom rule.

Show services Radar does not recognize

In Settings… → Detection, turn on Show unrecognized localhost servers. It is off by default. Radar then also lists accessible same-user TCP listeners that do not match an enabled rule, with the tool label Other.

The option can reveal databases and other local services that are not web servers. Despite the “localhost” label, Radar records listening sockets on any interface, including wildcard and specific IP addresses. It does not scan other computers. Other needs an explicit Address choice in Details before Radar constructs a browser URL or checks readiness.

Turning the option off hides unmatched groups on a later scan. It does not stop them or delete custom rules. The custom-tool editor can discover unrecognized listeners even when this option is off.

Start a custom rule from a running server

Use either entry point:

1. Open Settings… → Detection and click Add Custom Tool…. In Start from a running server, select the intended listener.
2. Or, enable unrecognized servers, find an Other card, then click its plus button or right-click it and choose Add as Custom Tool…. Radar opens Detection and a prefilled Add Custom Tool window.

Selecting a listener fills Name, Process name, and Command line contains. It suggests a name from the working folder and a distinctive command token, such as a script filename. Check the suggestion rather than treating it as a finished rule.

The discovery list refreshes about every 3 seconds while the editor is open. It shows only listeners not claimed by an enabled profile. More than five results appear in a scrollable area, with Start from a running server (N found) as the heading. Rows show process name, first port, and a shortened redacted command.

If the list says No unrecognized servers running right now — start your tool, or fill in the details below., you can start the server and wait or enter a rule manually. A server already recognized as Bun or Node server may be absent from this list even though you want a more specific custom label. Manual entry can override a built-in.

If the server exits during a card-to-editor transition, the editor may have only a suggested Name. Fill in the matching fields yourself. Selecting another listener replaces the three suggested text fields, so select first, then make your final edits.

Fill in the matching fields accurately

Name is the tool label shown in the Detection list and on matching cards. The card's main project name still comes from its working folder.

Process name is a program-name prefix, such as node, bun, or python3. Match the actual listening process, not necessarily the command you typed into a shell. For example, npm run dev may launch a listener whose process name is node.

Command line contains is a literal substring from the full command arguments. Use a script name, package path, or distinctive flag. It is case-insensitive and does not interpret regular expressions or wildcard syntax. It can match the executable path as well as later arguments.

Both matching fields accept comma-separated alternatives. node, bun means either process prefix. catalog-api.js, catalog-api.ts means either command substring. A server must satisfy both fields and have a listening TCP endpoint; alternatives do not require all listed words at once.

Use a distinctive token instead of broad words such as dev when you want one specific tool. A rule applies to every matching listener, not just the process you selected or a particular project folder. There is no project-path or port-range field in the editor. See worked custom-tool examples.

Choose an appearance, check the match and save

1. Under Details, finish Name and choose an Icon and Color.
2. Fill Process name and Command line contains with real, nonempty matching terms.
3. Review the live verdict. Currently matches: [process] on :[port] shows the first listener this rule would claim now. Nothing running matches yet — that's fine if your server is stopped. means the current discovery found no eligible match.
4. Click Add Tool to create the rule. Return to the panel and check the card's tool label.

The default appearance is a wrench icon and blue. The palette has 12 symbols and 10 colors. Color choices are blue, green, orange, red, purple, indigo, cyan, brown, yellow, and the standard primary color. Icon buttons show the symbol; their accessibility names identify it.

Add Tool requires nonblank Name, Process name, and Command line contains. It does not require a currently running match, so you can save a rule for a stopped server. Use actual words rather than commas alone. A green verdict shows one matching listener; it does not certify that no other process matches the same rule.

New rules start enabled and save immediately when you click Add Tool. Cancel or closing the editor discards its unsaved changes. Opening another Add/Edit request replaces the current editor and its unsaved draft.

Edit, disable or delete a saved custom tool

Custom rows in Detection have a Custom badge and Edit button.

1. Click Edit beside the intended custom tool.
2. Change its fields, Icon, or Color.
3. Click Save to keep the changes, or Cancel to discard them.

Editing preserves whether the rule was enabled. Saving a disabled rule does not enable it; turn on its Detection switch when you want it active. An edited rule keeps its position among the custom rules.

To pause recognition without losing the rule, turn off its switch. To remove it, open Edit and click Delete. Delete acts immediately, closes the editor, and has no confirmation or undo control. It does not stop the server. A later scan may classify that server with another enabled rule or as Other.

Built-in rows have switches but no Edit or Delete. You can add a custom rule for a more specific label instead.

Resolve empty matches, overlapping rules or lost changes

If there is no live match, check that the server is listening, use its actual process prefix, and choose a substring present in its command. Only unrecognized listeners are offered as starting rows, but the live verdict checks eligible discovered listeners more broadly.

Earlier enabled custom rules take precedence over later ones. A broad earlier rule can hide the draft's live match. Temporarily disable that rule or make it more specific, then check again. The UI has no reorder control. A disabled rule being edited also produces no live match until it is enabled after saving.

Changing General or Alerts preferences saves immediately; typing in the custom editor does not save until Add Tool or Save. Opening a second editor can discard the first draft. Save before switching to a different custom tool.

If custom rules or disabled built-ins disappear after reopening Radar, see missing or changed rules. Radar stores them in a local profile file and falls back to built-ins when that file cannot be decoded.