> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mossx.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Grok

> Detect and use local grok. The extension only detects. It does not install for you.

Grok uses local `grok`. Credentials and models stay in Grok's own config (usually `~/.grok/`).

Open **Settings → Provider management → CLI** and confirm Grok CLI shows **Installed**. The extension does **not** install it for you, and it does not change `config.toml`.

<img src="https://mintcdn.com/mossx-docs/kz4nt5KFSKzkAZwe/images/vscode/provider-cli.png?fit=max&auto=format&n=kz4nt5KFSKzkAZwe&q=85&s=5db25777376fb6428e73b4b9c0ae471e" alt="CLI detection page" width="100%" data-path="images/vscode/provider-cli.png" />

## Install

```bash theme={null}
curl -fsSL https://x.ai/cli/install.sh | bash
grok --version
```

Grok has no npm release. On Windows, run this command in WSL or Git Bash.

Docs: [https://x.ai/cli](https://x.ai/cli)

After install, go back to the CLI page and click **Detect again**. If the command is not found, set `GROK_BIN` / `GROK_PATH` / `GROK_CLI_PATH`, or add `~/.grok/bin` to the system `PATH`.

## Capability differences

Compared with Claude Code:

* No plan mode
* MCP / Skills / some settings pages are centered on Claude Code
* Stop ends the `grok` child process
* Image attachments use Grok's own path (for example `--prompt-file`)
* History is isolated by runtime and has a local history index

## If detection fails

See [Detect and install](/en/vscode/providers/cli).

## Next steps

* [Provider overview](/en/vscode/providers/overview)
* [Send the first message](/en/vscode/start/first-task)