grokodex-setuplisted

# Grokodex Setup Check that the **local Grok CLI** is installed and logged in so other Grokodex tools can run. ## When to use - First time using Grokodex in a session or machine - Any tool returns `GROK_NOT_FOUND` or `GROK_NOT_LOGGED_IN` - User asks to install / login / verify Grok for Grokodex (Codex, Claude Code, etc.) - Before heavy `grok_run` / `grok_imagine` / `grok_x_search` work if setup looks broken ## Tool preference 1. **Always call the MCP tool `grok_setup` first** (logical name; Claude may show an `mcp__…__grok_setup` prefix — use `/mcp` list). 2. Do **not** use a terminal/shell tool to run `grok` for diagnostics when `grok_setup` is available. 3. **Exception:** after `grok_setup` fails or reports missing binary / bad auth, you may guide the user to run **install** and **`grok login`** in their own terminal (see below). That is the only case where shell/`grok` is appropriate, and only as user-facing install guidance—not as a bypass for other tools. ## How to call ```text grok_setup ``` Optional (currently ignored by the bridge, reserved): ```text grok_setup fix=true ``` No other parameters are required. ## Interpret the result Envelope shape (text content is JSON): - `ok: true` → report `text` and/or `meta`: - `meta.grok_path` — binary path - `meta.version` — CLI version if known - `meta.auth_ok` — whether login looks healthy - `ok: false` → surface `error.code`, `error.message`, and `error.hint` - Common codes: `GROK_NOT_FOUND`, `GROK_EXIT_N