xAI's terminal coding agent — the Grok Build CLI — is now open source under Apache 2.0, so you can run it, read it, and self-host it.
Last verified · 2026-07-16 · by Moe Ameen
Grok Build is xAI's terminal-based coding agent — the CLI, not the model. On July 15, 2026, xAI published the whole thing as open source under an Apache 2.0 license at github.com/xai-org/grok-build. That means the agent harness, the fullscreen terminal UI, and the tool layer that reads, edits, and runs your code are now source-available: you can read exactly what it does, fork it, and run it yourself.
The codebase is written in Rust, organized into crates like the agent runtime, the tool implementations, the TUI/pager, and a workspace layer for filesystem, version control, and command execution. The tool layer is the standard agentic set — read, write, edit, apply-patch, glob, grep, list-dir, and shell — and the agent runs a plan-then-act loop over them. On top of that sits an extension system: skills, plugins, hooks, MCP (Model Context Protocol) servers, and subagents, plus a headless mode for scripting and CI and a sandboxing layer. Configuration lives in a `config.toml`.
Because it is now open, the model is no longer fixed to xAI. By default Grok Build runs on xAI's Grok models — it ships pointing at its own Grok Build coding model (grok-build-0.1) — but the `config.toml` lets you aim the agent at a different endpoint — including a local inference server — so you can run it air-gapped or on the model of your choice. xAI framed the release around transparency and control: security auditing, internal forks, air-gapped deployment, and CI automation. The context matters — the open-sourcing followed reporting that the earlier CLI had uploaded large parts of users' directories to xAI's cloud, and publishing the source lets anyone verify what leaves their machine.
One thing to be clear about: Grok Build is a developer tool. It writes and ships software. It generates no images, video, audio, captions, or social posts, and it publishes nothing. If you found it while looking for a way to make content, it is the wrong category — but it is a strong, now-free way to build the thing you then make content about.
The open-source release is what makes this pairing genuinely tight, because Grok Build now has a headless mode, hooks, and a fully inspectable config — the exact surfaces you need to wire it into a publishing pipeline. Grok Build ships the product; Kompozy turns each release into a week of content. The concrete workflow for a founder or indie builder: add a Grok Build hook (or a headless job in CI) that fires when you tag a release, have it emit a plain-language changelog, and feed that into Kompozy as a source — paste it in, or wire it to an input source. Kompozy takes that one input and fans it into a demo-style short, a feature carousel through HyperFrames, a launch thread for X, a LinkedIn post, and a blog article — all in your brand voice via a Persona Brief — then schedules and publishes them across the nine connected platforms plus email and blog from one queue.
The point that only holds now that Grok Build is open: you can build the integration yourself and read every line of it, so a builder who cares about what leaves their machine can keep the coding agent local and let Kompozy handle only the outbound content. Grok Build owns the engineering and the automation; Kompozy owns the audience. You are not wiring Grok into Kompozy's generation — Kompozy runs its own managed Claude and OpenAI models — you are using Grok Build's now-open hooks to hand Kompozy the raw material and letting the engine take it to finished, scheduled posts.
Yes. On July 15, 2026, xAI published the Grok Build CLI — its terminal coding agent, including the agent harness, TUI, and tool layer — as open source under an Apache 2.0 license at github.com/xai-org/grok-build. You can read, fork, and self-host it.
Not necessarily. It ships pointing at xAI's Grok models (its grok-build coding model), which need xAI API access, but the config.toml lets you aim the agent at a different endpoint — including a local inference server — so you can run it against the model of your choice or fully offline.
xAI framed it around transparency and control — security auditing, internal forks, air-gapped deployment, and CI. It followed reporting that the earlier CLI had uploaded large portions of users' directories to xAI's cloud; publishing the source lets anyone verify what the tool sends and run it locally to avoid that entirely.
No. It is a coding agent — it writes and ships software and produces no images, video, audio, or social posts. To turn what you build into published content, pair it with a content engine like Kompozy that generates the media and publishes across nine platforms plus email and blog.
Build the product itself — an app, a landing page, an internal tool, or the automations and webhooks around it. Then use Kompozy to generate and publish the marketing: launch shorts, carousels, threads, blogs, and newsletters. Grok Build's open hooks and headless mode make it easy to wire the two together.