Separate check from install
Use grok update --check or --check --json to inspect availability without changing the installation. The released command can select --stable, --alpha, or a specific --version; switching channel is a deliberate policy choice.
Record grok version information and read release notes before installation. Avoid --force-reinstall unless repairing a known installation problem.
grok update --check --json
grok --versionDiagnose before fixing
grok doctor checks terminal, clipboard, color, input, notification, and sandbox support; --json makes the diagnostic machine-readable. grok inspect covers discovered configuration and extensions, a different evidence surface.
Review grok doctor fix before applying changes. --yes removes confirmation and belongs only in a procedure that has already audited the proposed local modifications.
- Review debug-file output before sharing.
- Fix the first failing layer before changing unrelated settings.
- Re-run doctor after a repair.
Generate completion code deliberately
grok completions requires a shell and prints its completion script. Write it to a temporary file, inspect it, and install it using the conventions of that shell rather than appending unknown text directly to a startup file.
The TUI /doctor command is source-preview in the captured source ledger, while the grok doctor shell command is runtime-confirmed. Keep availability labels attached to the surface you teach.
grok completions zsh > /tmp/_grok
sed -n "1,40p" /tmp/_grok