Skip to content

Getting started

RADAR runs entirely on your machine. Setup is four steps and none of them involve creating an account.

1. Install

Download the Windows installer from the download page and run it. No admin rights are required and nothing is installed as a service — RADAR is a normal desktop app.

Start RADAR. On first run it opens Settings so you can connect a source control provider and a model.

2. Connect source control

RADAR reads pull requests through a personal access token (PAT) that stays on your machine, stored encrypted with Windows DPAPI.

Azure DevOps

  1. Create a PAT in Azure DevOps (User settings → Personal access tokens) with Code: Read & write scope. Read & write is only needed if you want to post comments from RADAR; Code: Read is enough for review packs.
  2. In RADAR Settings, choose Azure DevOps, enter your organisation URL (https://dev.azure.com/your-org) and project, and paste the PAT.

GitHub

  1. Create a fine-grained token with Pull requests: Read access to the repositories you want to review.
  2. In RADAR Settings, choose GitHub, enter the owner and repositories, and paste the token. GitHub support is read-only today: review packs, no comment posting.

3. Connect a model

Any of these works:

  • LM Studio — start the local server (Developer → Start server), then point RADAR at http://localhost:1234 and pick the loaded model.
  • Ollama — ollama serve is usually already running; point RADAR at http://localhost:11434 and choose a model such as qwen3:32b.
  • Any OpenAI-compatible endpoint — enter the base URL and, if the endpoint requires one, an API key. This is how you use a model host elsewhere on your network — or an external provider, in which case RADAR warns you and asks for explicit confirmation before every run.

4. Generate your first review pack

  1. Open the Pull Requests page — your open pull requests are listed.
  2. Pick a PR, choose a review profile (general senior C# review is the default) and a depth.
  3. Generate. RADAR builds a bounded context from the diff, runs your model, and writes a structured review pack — findings with severity, confidence, and evidence from the actual diff — as Markdown in your output folder.

Read the pack, copy the comments you agree with, and post the ones you choose — each post requires explicit confirmation. RADAR never approves, rejects, or merges.

5. Optional: let RADAR watch your PRs

The Inbox is RADAR’s home page. Turn on monitoring there and, while the app is open, RADAR polls your source provider every few minutes and detects new and updated pull requests. With auto-review enabled, matching PRs are reviewed automatically — one at a time — and finished packs land in the Inbox with a Windows notification.

The auto-review rules (the gear on the Inbox monitoring row) control exactly what runs unattended: per-repository toggles, skip drafts, a PR size cap, and re-review when new commits are pushed. Both monitoring and auto-review are opt-in and off by default, so a paid endpoint never runs without being asked — on a local model, unattended reviews cost you nothing. Automatic runs are labelled in Review History, and nothing is ever posted automatically.

Troubleshooting

  • The model host isn’t reachable — check the server is running and the port matches; RADAR shows the exact URL it tried.
  • Review packs aren’t written — if your output folder is under Documents or OneDrive, Windows Controlled Folder Access may block writes. Choose a folder outside protected locations in Settings → Output, or allow RADAR through the protection.