/setup
Check whether the local Grok CLI is installed and authenticated
> /plugin marketplace add VasiHemanth/grok-build-plugin > /plugin install grok@grok-build-plugin
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/setup
Context preview
What this command does when you run it.
Check whether the local Grok CLI is installed and authenticated
Command definition
setup.mddescription: Check whether the local Grok CLI is installed and authenticated argument-hint: "" allowed-tools: Bash(node:*)
Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-companion.mjs" setup --jsonThen present a short, friendly summary of the result to the user:
- If `available` is false: tell them the Grok CLI was not found and to install it from https://docs.x.ai (or set `GROK_BIN` to the binary path), then rerun `/grok:setup`.
- If `available` is true but `loggedIn` is false: tell them Grok is installed but not signed in, and to run `!grok login`, then rerun `/grok:setup`.
- If both are true: confirm Grok is ready and report the account and default model.
Do not run any other commands.
Want Claude Code, Codex, or Cursor to drive Grok Build? If you already pay for a Grok subscription, this gives any of those agents live X search and data right in their context. A couple of ways to wire it up.
Repo: VasiHemanth/grok-build-plugin
Other commands on grok-build-plugin.
rescue
Delegate a coding or investigation task to Grok (write-capable by default)
review
Run a read-only Grok code review of your uncommitted changes or a branch
search
Search X (Twitter) and the web in real time with Grok, then summarize with sources

