Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From grok
Diagnose the Grok plugin — CLI presence, auth, resolved config, and Node version
How this command is triggered — by the user, by Claude, or both
Slash command
/grok:setup [--json]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Run: Present the report to the user. `--json` emits the same report as structured JSON. The dispatcher exits nonzero when the Grok CLI is missing; missing auth and an old Node version are reported as warnings and next steps without changing the exit code. If it reports that grok is **not installed**, the fix is the curl bootstrap (do NOT suggest `npm install` — grok is installed via curl): If grok is installed but **not authenticated**, tell the user to run `grok login` (or `grok login --device-auth`) or set `XAI_API_KEY`. The setup check validates the live CLI state, so a stale `~/...
Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/grok.mjs" setup $ARGUMENTS
Present the report to the user.
--json emits the same report as structured JSON. The dispatcher exits nonzero when the Grok CLI is missing; missing auth and an old Node version are reported as warnings and next steps without changing the exit code.
If it reports that grok is not installed, the fix is the curl bootstrap (do NOT suggest npm install — grok is installed via curl):
curl -fsSL https://x.ai/cli/install.sh | bash
If grok is installed but not authenticated, tell the user to run grok login (or grok login --device-auth) or set XAI_API_KEY. The setup check validates the live CLI state, so a stale ~/.grok/auth.json file does not count as authenticated. Never print the key value or any other credential value.
npx claudepluginhub trevoraspencer/grok-plugin-cc --plugin grok/setupInitializes or resumes Conductor project setup by creating foundational documentation (product definition, tech stack, workflow, style guides) through interactive Q&A.
/setupChecks whether the local Codex CLI is ready and optionally toggles the stop-time review gate. If Codex is not installed, prompts the user to install it via npm.
/setupWalks an enterprise admin through configuring the Claude Office add-in to call their own cloud (Vertex/Bedrock/Foundry/gateway), producing a customized manifest.xml for M365 deployment.
/setupDetects and cleans up ghost installations of the claude-hud plugin in Claude Code, checking cache, registry, and temp files across macOS/Linux and Windows.
/setupInteractive setup wizard that detects installed AI providers, configures auth, and optimizes token usage for the Octopus ecosystem. Runs on first install or manual invocation.