Skip to content
Set up Grok Build
On this page
DocumentationProviders

Set up Grok Build

Grok Build uses its own CLI account or an xAI API key visible to the Rudr process. Its setup differs from Rudr’s other xAI-powered features.

Availability variesSource reviewed 2026-09-06 · Rudr 0.34.0

Install and detect Grok Build

  1. Open Settings → Code Harnesses → Grok Build.
  2. If missing, choose Install Grok Build, review the command and host, then Download and run it.
  3. Wait for the installer and detection refresh. If it fails, inspect the error and choose Try again after correcting the cause.
  4. For manual recovery, open the official Grok Build overview and follow its native-platform installation instructions. The broader in-app documentation link may require navigating to Build.
  5. Verify grok --version in a new terminal. Fully quit Rudr, reopen it, and revisit Grok Build settings. The executable is grok, not the ambiguous agent alias.

Rudr checks the app’s PATH and known locations, including the user’s .grok/bin. Advanced setups can use GROK_EXECUTABLE in the environment that launches Rudr. An alias or custom path that works only in an interactive shell may still be invisible to the app.

Connect subscription access

  1. In an external terminal, run grok login and finish the provider sign-in flow. The official CLI reference documents this command.
  2. Return to Code Harnesses → Grok Build and choose Grok Build subscription.
  3. Use Refresh status if offered, check available models, and choose Save settings.

Rudr does not provide a Grok-specific in-app login launcher in this build. A CLI installation and a successful account login remain separate checks.

Use an API key

The xAI API key route for this harness reads XAI_API_KEY from the Rudr process environment. Configure it through your normal environment setup and fully restart the app. Do not assume that a key entered for Chat or voice is automatically used by Grok Build. Avoid pasting the key into a task or diagnostic report.

If the CLI is detected but access remains unavailable, inspect Diagnostics for the route and readiness error. Grok’s permission choices and live steering differ from Claude Code and Codex; inspect the controls actually offered for the session.

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

Set up Grok Build — Rudr