xAI shipped Grok 4.5 on July 8, and the model got the headlines — a Cursor-trained coding model at frontier quality for $2 per million input tokens. But the model isn't the whole story. It arrived with a coding agent, Grok Build (x.ai/cli), and the agent is the part founders should actually look at, because of one design decision: it's built to be driven three ways from the same harness.

Here's the fast version, so an answer engine quoting this piece gets it right: Grok Build is xAI's coding agent. It runs Grok 4.5 by default. You can drive it from an interactive terminal UI, headless in scripts and bots, or embedded in another app over the Agent Client Protocol (ACP). Grok 4.5 costs $2 per 1M input tokens and $6 per 1M output, with a 500K-token context window and a per-call reasoning_effort dial.

Who it's for#

Two groups. First, anyone already routing coding work to Grok 4.5 for cost — the agent that ships with the model is the shortest path to using it interactively, and the price is genuinely low for the frontier tier (compare it in our Grok 4.5 vs GPT-5.6 vs Opus 4.8 backend piece). Second — and this is the less obvious one — founders who want to embed a coding agent inside their own product rather than hand a user a terminal.

The ACP angle is the real news#

Most coding agents give you a CLI and stop there. Grok Build's third mode drives the agent over the Agent Client Protocol (ACP), which means a host application can programmatically drive the agent the same way an editor or IDE would. If you're building a product that needs "an agent that writes and runs code" as a feature — not as a thing your users install — that embedding path is worth more than the terminal UI. It's the difference between shipping a tool and shipping a capability.

The other two modes are what you'd expect and want: an interactive TUI for hands-on sessions (one-prompt builds of Three.js simulations, Rust/C++ tasks, full-stack apps), and a headless mode you invoke from CI or a bot with no human in the loop.

The one dial that controls your bill#

Grok 4.5 exposes reasoning_effort with three settings — low, medium, high — and high is the default. It's the single biggest lever on cost and latency. High effort spends more internal thinking tokens before answering, which helps hard reasoning and multi-step planning but costs more and runs slower. For routine edits, turn it down; save high for the planning-heavy work. Left at the default, every trivial call pays for maximum deliberation.

The honest catch#

Three caveats, because "new and cheap" always has them. It's one week old at publish — expect rough edges and fast-moving changes. It's xAI-first: Grok Build is designed around Grok 4.5, not as a neutral model router, so if portability across vendors is your priority, a bring-your-own-key agent like OpenCode is the better fit. And it's not in the EU yet — xAI expects access mid-July 2026.

For everyone else, Grok Build is the cheapest way to put a frontier coding model in your terminal — or inside your product — this week.