Skip to content
Fix sign-in and access readiness
On this page
DocumentationTroubleshooting

Fix sign-in and access readiness

Identify the first failed readiness stage before changing credentials or reinstalling a provider. A CLI can be installed and signed in while its selected route or model remains unavailable.

Match the symptom

Symptom Check first Next action
Missing CLI Installation and executable detection Follow the provider’s manual-install recovery
Signed out The selected CLI account route Complete that provider’s sign-in flow
Wrong account or route Subscription versus API selection Select the intended route; change shared login only deliberately
Could not verify status Status freshness and displayed error Refresh if offered before assuming the credential is invalid
Ready but no model Model discovery, deployment, entitlement Inspect Models and the route-specific catalog
Cursor connected but disabled Usage connection and setup gate Complete Cursor setup

Recheck in Rudr

  1. Open Settings → Code Harnesses and select the affected harness.
  2. Confirm the intended access route, then read the precise status message.
  3. If controls are present, use Refresh status and inspect the updated result.
  4. For API access, check the matching connection under Models, save changes, and return to the harness.
  5. Inspect Settings → Usage → Diagnostics for the executable version, readiness, and capability reasons.

The missing-CLI panel can hide normal access controls; a universal Refresh button is not available in every state. For a manual installation, fully quit and restart Rudr so it can inherit the updated environment.

Avoid unintended account changes

Claude Code and Codex login actions can change credentials also used outside Rudr. Cancelling Settings is not an undo for those changes. Grok Build requires its external login flow; OpenCode uses provider-specific connection setup. An API key saved for Chat does not automatically establish a coding subscription.

Follow Claude Code, Codex, Grok Build, OpenCode, or Cursor for the actual account steps. Share sanitized errors, never tokens or credential files.

Rudr account requirements

Rudr supports guest use. See what requires Rudr sign-in for the cloud account features that are unavailable while signed out, and how they differ from AI-provider credentials.

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 sign-in and access readiness — Rudr