Another week, another terminal that writes your code. xAI has pushed Grok Build into early beta — a coding agent and CLI for SuperGrok and X Premium Plus subscribers, installable with one command, per the company’s own x.ai announcement. It runs plan mode (approve, comment on, or rewrite the steps before anything executes), shows every change as a clean diff, and reads your AGENTS.md, hooks, plugins, and MCP servers out of the box. For larger jobs it spins up specialised subagents in parallel, some in their own git worktrees.

If that feature list reads like a checklist you have seen four times this year, you are not wrong. That is the point worth sitting with.

The reason it is possible now and not in 2022 is boring and important: the plumbing got standardised. AGENTS.md is becoming the README for machines, MCP is becoming the wall socket every tool plugs into, and a headless -p flag means the same agent that helps you interactively can run unattended inside a script. MarkTechPost reports xAI shipped a plugin marketplace alongside the beta — MongoDB, Vercel, Sentry, Cloudflare — and basenor notes that by v0.1.212 the CLI even renders diagrams inside the terminal. None of these are revolutions. They are the agent ecosystem agreeing on file formats. Which, for our trade, is the whole ballgame.

On a working architect’s desk this week the relevance is narrow but real. Most of us are not writing web apps; we are maintaining the ugly four-hour-saving Python that stitches an Archicad export to a Speckle stream to a Bonsai check. A terminal agent that respects a plain-text AGENTS.md and emits a reviewable diff is exactly the right shape for that work — small, inspectable, repairable. The danger is the opposite shape: letting an agent generate a tangle you cannot read, owned by a subscription you may not have in 2030.

←TODAY: June 2026 — Grok Build joins a crowded field of terminal agents that all speak AGENTS.md and MCP. →3012: in the Zurich-3012 horizon, the building’s repair manual is its plain-text config, not its vendor login. Fulcrum: the agent is disposable; the conventions file it reads is the asset — only obvious when you can see both the hype and the half-life.

Here is the part my generation learned the hard way. The buildings that aged badly were not the ugly ones — they were the ones nobody could repair because a proprietary format went dark in 2041. The same logic now applies to your toolchain. An agent that reads a plain Markdown conventions file and writes a plain unified diff is one a 25-year-old can still understand after the vendor is gone. An agent whose decisions live only inside a closed cloud is a future repair you are quietly forbidding. Pick accordingly this quarter.

Atelier: In the PAZ Archicad↔Speckle↔Bonsai pipeline twelve practices quietly run, the rule is simple — every machine-made change lands as a versioned text diff before it touches the model. Drop an AGENTS.md at the repo root describing your IFC-export conventions, and any compliant agent inherits your house style instead of guessing it.

Hack: This Hack teaches you to keep every AI-generated change as a plain-text patch you can open in 2050, not a vendor blob. The medium is your shell; the domain is Workflow.

# run the agent without letting it commit
grok-build -p "tidy the IFC export script" --no-commit
git add -p                      # stage only hunks you actually read
git diff --cached > changes.patch   # archival-safe unified diff
git apply --check changes.patch     # prove it still applies later

Read the diff, keep the patch, version the conventions file. The agent you use next year will be different; the patch will still open. Try Grok Build, or any agent you like — but make the plain-text artefact, not the subscription, the thing you depend on.

Source: HN Funny