Grok Build Adds /tutorial: CLI Coding Agents Now Compete on the "First Ten Minutes After Opening"

At 08:25 this morning, Elon Musk shared a very short update: download Grok Build, then type /tutorial. One line. Taken literally, it is not a model breakthrough, nor even a formal release announcement.

But it reveals a product signal. The battlefield of AI coding is shifting from "can it edit code" to "will an ordinary developer figure it out within ten minutes of first opening it."

Grok Build is no longer a lone CLI. The official page lists a full stack: Plan mode, Skills, Plugins, Hooks, MCP, AGENTS.md, Memory, parallel subagents, standalone worktrees, headless mode, ACP integration, code review, sandboxing, and background tasks. With the model now switched to Grok 4.5, xAI is selling a complete terminal development workbench—code completion is just one cell in the grid. [1][2]

/tutorial fills the least glamorous but most off-putting layer: onboarding. As of July 22, the latest public version in the official changelog is still v0.2.111, which contains no /tutorial entry—so today's post reads more like an announcement first, documentation to follow. v0.2.111 turned Workflows on by default, let grok doctor fix run inside the TUI, and stopped silently rejecting actions when the permission classifier timed out or failed, falling back to a normal permission prompt instead. A few versions earlier, /resume gradually added recovery of sessions across directories, machines, and other coding tools. [3]

Piecing this together, xAI has recently been tackling three kinds of real friction:

1. Not knowing how to use it: /tutorial guides the way; 2. A broken environment with no idea where it broke: /doctor diagnoses; 3. Interrupted tasks, failed subagents, sessions moved to another machine: Workflows and /resume pick things back up.

That looks more like product engineering than another ten benchmark numbers. Long-running agents most often die not in the function bodies—which usually get written—but in permission pop-ups, environment variables, session recovery, background task states, and retry-after-failure. Whoever polishes these corners gets to move from "tried once" to "runs on my machine every day."

That said, don't read /tutorial as a sign the trust problem is solved. Grok Build's Rust CLI/TUI and agent runtime have been published on GitHub under Apache 2.0, but it is a periodically synced mirror from an internal monorepo at SpaceXAI, and external contributions are not currently accepted. Open-sourcing makes the local harness auditable; the hosted model, account services, telemetry, and data retention remain a separate chain. The repo's SECURITY.md only offers a vulnerability reporting channel, with no full explanation of runtime data policy. [4][5]

My take is simple: today's update is small but very "productized." The next round of competition for terminal agents is not just about who is smarter, but about who can teach users, diagnose themselves, explain permissions clearly, show progress, and keep going after failure. /tutorial is a small button—but behind it, CLI coding agents are starting to build a consumer-grade entry point.

Sources

1. Elon Musk: download Grok Build and type /tutorial 2. Grok Build official product page and docs · Docs 3. Grok Build official changelog 4. xAI Grok Build open-source repo 5. Repository security policy