GROK BUILD CLI / INDEPENDENT FIELD GUIDE
Command the terminal frontier.
Source-checked, terminal-first manuals for installing, controlling, extending, and automating Grok Build across real repositories.
$ grok inspect --json
RULES · SKILLS · HOOKS · MCP / DISCOVERED
$ grok --cwd ./repository
› /plan review the change before editing
PLAN → REVIEW → APPROVE → VERIFY
AZ 277.42 / EL 18.06
CARRIER: GROK WORLD
NOISE FLOOR: −112 dB
FIELD NOTE / 00
Agent operations, not prompt folklore
Inspect the repository before editing. Plan consequential changes. Bound tools with permissions and a sandbox. Verify every result with the project’s own checks.
TRANSMISSION ARCHIVE
Grok Build core course
Install and verify Grok Build
Install the official grok executable, prove which binary your shell resolves, and establish a repeatable update check before opening a repository.
MANUAL / 02 · CORE CLIAuthenticate without spreading credentials
Choose interactive, device-code, or API-key authentication for the environment you are actually running, then verify and revoke it cleanly.
MANUAL / 03 · CORE CLIRun a disciplined first repository session
Open Grok at the repository boundary, inspect what it discovered, and turn a vague first prompt into evidence, acceptance criteria, and verified changes.
MANUAL / 04 · CORE CLIEncode project rules and verify Claude Code compatibility
Give every session durable repository instructions, layer monorepo rules by directory, and audit the Claude Code assets Grok says it can discover.
MANUAL / 05 · CORE CLIPlan, review, and approve before editing
Use Plan Mode for ambiguous or high-impact work, annotate the proposed path, and keep approval as a meaningful engineering gate.
MANUAL / 06 · CORE CLILayer permissions and sandboxing
Control whether a tool call may run, then separately constrain what an approved process can read, write, and reach.