ProvidersGrok

Grok

Install, authenticate, verify, and run xAI's Grok CLI through Tejus on Windows.

Tejus connects to xAI's Grok CLI (Grok Build) through the grok executable and its Agent Client Protocol (ACP) mode over standard input and output. Grok owns authentication, models, tools, and provider behavior; Tejus supplies the task, repository environment, transcript, approvals, review surfaces, and Git lifecycle around the session.

Install

Install the CLI with xAI's official Windows installer from PowerShell:

irm https://x.ai/cli/install.ps1 | iex

Tejus looks for grok on your PATH. Verify the installation from a new PowerShell window:

grok --version

Authenticate

In Tejus, open Settings → Agent providers, expand Grok under Provider tools, and click Sign in; Tejus runs grok login in a terminal window. Complete the browser sign-in or the authorization steps shown. Or run it yourself:

grok login

You can use an xAI API key instead. Tejus passes XAI_API_KEY (or GROK_CODE_XAI_API_KEY) to Grok. Set it as a Windows user environment variable and restart Tejus, or add it to Grok's Environment section under Provider tools with the secret switch on.

When an API key is set, Tejus signs Grok sessions in with the key; otherwise it uses the cached grok login session. Remove the key if you want to use your account login.

Do not place the key in a repository, prompt, screenshot, or documentation file.

Verify

From a disposable repository:

grok --version
grok models

Then run grok and ask a harmless read-only question. Confirm that the expected model catalog is available and that authentication succeeds before opening Tejus.

Connect to Tejus

Enable Grok

Open Settings → Agent providers, keep Grok enabled under Provider activity, and click Refresh status. The status shows xAI API Key or Grok Account once Tejus finds a key or a cached login.

Confirm the executable

Leave Grok binary path blank to use grok from your PATH, or point it at the installed executable.

Select model and reasoning

Confirm that Tejus shows the expected model and reasoning-effort options before starting the task. Effort options depend on the model: Grok Build offers None through High, while newer Grok models offer Low through High and, on some models, a higher level.

Run a test task

Use a small repository and a bounded objective. Review the active mode and permissions before allowing edits or commands.

Capabilities in Tejus

Grok sessions can expose:

  • Grok model selection and reasoning-effort controls
  • Plan mode, in which Tejus allows only read-only tools
  • Tool calls, command output, file changes, and assistant text
  • Authentication through a cached login or an xAI API key
  • Context compaction with /compact
  • Usage limits for a signed-in Grok account (with only an API key, Tejus shows the key's identity, not credits)
  • Tejus's terminal, browser, diff, checkpoint, worktree, and Git delivery surfaces

Grok applies the model and reasoning effort when its process starts. Changing them, or changing the permission mode, restarts the Grok session for the next turn.

Tejus does not support live steering of a running Grok turn.

Updating

Use xAI's official installer or release mechanism to update Grok, then restart Tejus so provider health and model discovery use the new executable. Tejus does not run Grok updates for you.

After an update, start a new task when the change affects ACP behavior, model options, permissions, or session negotiation.

Troubleshooting

Grok is not detected

Tejus shows “Grok CLI (grok) is not installed or not on PATH.”

  1. Run grok --version from a new PowerShell window.
  2. Confirm the installer folder is on PATH.
  3. Check the Grok binary path in Tejus.
  4. Restart Tejus after installation or environment changes.

Grok is detected but authentication fails

Run grok login directly, or use Sign in in Tejus. Typical messages:

  • “Grok is not authenticated for headless ACP. Run grok login (or launch grok) and retry.”
  • “Grok ACP requires API-key authentication, but XAI_API_KEY is not set.” Set the key, or run grok login to create a cached login.
  • “Grok did not advertise API-key authentication even though XAI_API_KEY is set.” Update Grok or check its login policy, then restart Tejus.

The model or reasoning setting is ignored

Confirm the setting in a newly created Tejus session. Grok applies these selections when its process starts.

Compaction is unavailable

Update Grok and start a new session.

Official documentation

Continue with Your first task or Provider handoffs.

Last updated on