Skip to content
Fix installation and detection
On this page
DocumentationProviders

Fix installation and detection

A missing CLI, failed installer, signed-out account, and unavailable model are different problems. Resolve the first failing stage before repeating later steps.

Availability variesSource reviewed 2026-09-06 · Rudr 0.34.0

Use the in-app installer

  1. Open Settings → Code Harnesses and select the affected harness.
  2. If a missing-CLI panel appears, choose Install followed by that harness’s name and review the command, download host, and any alias warning.
  3. Choose Download and run it only when you intend to run that installer. Wait for completion or a displayed failure.
  4. Read the failure before Try again. Open install docs takes you to the provider’s installation guidance.

On a successful exit, Rudr refreshes executable detection, models, and access. That sequence is not proof that login or a paid first turn succeeded.

Recover with a manual installation

  1. Follow the native-platform instructions linked from the individual provider guide. Match your shell to the command, especially PowerShell versus CMD on Windows.
  2. Verify the provider executable in a new terminal: claude --version, codex --version, grok --version, or opencode --version, as appropriate. Cursor requires the provider-specific cursor-agent executable for Rudr; a generic agent command is ambiguous.
  3. Fully quit Rudr and launch it again. Return to Code Harnesses and check detection.
  4. Once access controls appear, complete sign-in or key setup, use Refresh status if offered, and Save settings.

Rudr searches the process PATH and known user/system installation locations. It does not scan the entire disk. An interactive-shell alias, an arbitrary custom directory, or a WSL installation may work in your terminal while remaining unavailable to native Rudr. Reopening Settings alone may not refresh the app’s inherited environment.

Diagnose the remaining failure

If detection still fails, inspect Settings → Usage → Diagnostics. Record OS, Rudr version, provider version, installation method/location, and sanitized error text. Never attach credential files or environment dumps.

If the executable is installed but the route is not ready, move to authentication recovery. Muse has no automated Windows plan and its upstream instructions remain unverified; do not invent a replacement installer.

Instructions have been reviewed against the application source; native setup and account walkthroughs remain to be verified. Platform and provider limitations are described above.

Fix installation and detection — Rudr