Runrail Desktop
Install Runrail Desktop on Windows, macOS, or Linux.
Choose your computer, complete the disposable local sample, and turn read-only repository inspection into one readiness verdict, one next action, and a path-free receipt. No account or model key is required for the sample.
First local review
From download to evidence in three steps.
The exact verification commands remain available below, but the product path is intentionally short.
-
01
DownloadChoose the public preview package and its matching checksum. No account is required for the sample or your one preview review.
-
02
Verify and launchExtract the archive and open the named launcher in its top-level folder. Do not open desktop/index.html directly.
-
03
Review one real candidateComplete the safe sample, run the printed desktop --repo . command from your local Git worktree, select the base and candidate branches, then inspect the exact local evidence.
Start-file rule: use START-RUNRAIL-PREVIEW.cmd, Start Runrail Preview.command, or start-runrail-preview.sh. The internal HTML cannot create the private session that protects Desktop operations.
Shared requirements
Local runtimes only.
Windows, macOS, Linux, or WSL2; Node.js 20+; Python 3.11+ with venv; and Git. No DeepSeek key or account is required for the public-preview review. Repository content stays local; enrolled plans contact the subscriber service only for browser-authorized device enrollment and bounded entitlement renewal metadata.
First five minutes
Open the app. Follow one checklist.
Desktop keeps setup in one place and shows exactly what remains before your first repository review.
- 01
Confirm this deviceIntegrated doctor verifies the package and local runtime.
Automatic
- 02
Complete the safe sampleAfter doctor passes, Run safe sample is the only next action. A secondary rerun appears only after completion.
No enrollment
- 03
Review and hand offFrom your Git worktree, run desktop --repo ., select one candidate, inspect exact hunks, save attention, and copy the source-free correction brief. The preview keeps that one review inspectable; reruns require enrollment.
One review
What leaves the device: entitlement metadata only. Source, diffs, paths, findings, prompts, and test output remain local. There is no background daemon.