Grok Build quickstart

Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.

Grok Build is xAI's coding-agent CLI (`grok-build` in AIWG). Grok Bot is a separate desktop integration; the Grok web Build experience is not this CLI. Start with the AIWG install, connect, and verify guide if AIWG is not yet installed in the project. Install a reviewed released binary from the upstream instructions, then check `grok the version option`. In a project with AIWG installed:

Use AIWG to complete this documented outcome: Grok Build is xAI's coding-agent CLI (grok-build in AIWG). Grok Bot is a separate desktop integration; the Grok web Build experience is not this CLI. Start with the AIWG install, connect, and verify guide if AIWG is not yet installed in the
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Open a new Grok Build session after deployment. AIWG stores shared project guidance in `WORKSPACE.md`; generated `AGENTS.md` loads it before `AIWG.md`. Kernel skills land in `.grok/skills`; inspect the live discovery with `grok inspect the json option`. For user-scope skills, inspect the target with a dry run of the agent-owned use operation first. Operator-owned `.grok` files and text outside managed context blocks must survive refreshes.

See native extensions for MCP/hooks, sessions, models, the CI guide, and the Grok Build migration guide. The qualification matrix documents scope, recovery, and the evidence still needed for stable promotion.