The Rust agent harness, fullscreen TUI, and tool layer behind xAI's coding CLI are now on GitHub — model-flexible and self-hostable — after reporting that the earlier CLI uploaded users' directories to xAI's cloud.
2026-07-16 · by Moe Ameen
On July 15, 2026, xAI released Grok Build — its terminal-based coding agent, the CLI rather than the model — as open source under an Apache 2.0 license at github.com/xai-org/grok-build. The published codebase is the whole tool: a Rust agent harness, a fullscreen TUI with an inline diff viewer, the standard read/write/edit/shell tool layer, a workspace layer for filesystem and version control, and an extension system covering skills, plugins, hooks, MCP (Model Context Protocol) servers, and subagents, plus a headless mode for scripting and CI. Grok Build first launched as an early beta on May 14, 2026.
A notable part of the release is model flexibility. Grok Build ships pointing at xAI's Grok models — it defaults to its own Grok Build coding model (grok-build-0.1) — but configuration lives in a `config.toml` that can aim the agent at a different endpoint, including a local inference server. That lets developers run it air-gapped or against the model of their choice, rather than being tied to the xAI API.
xAI framed the move around transparency and control, citing security auditing, internal forks, air-gapped deployment, and CI automation as intended uses. The timing matters: the open-sourcing followed reporting from security researchers that the earlier Grok Build CLI had uploaded large portions of users' local directories to xAI's cloud storage without clear consent. Publishing the full source lets anyone verify exactly what the tool sends and self-host it to keep code on their own machines.
There are two ways a creator acts on this today, and neither is "use Grok Build to make content" — because it still cannot. The first is editorial, and it is the faster win: the open-source release, and the privacy story behind it, is exactly the kind of timely, high-intent topic your audience is talking about right now. Drop your take — what Apache 2.0 and self-hosting mean for developers, whether open-sourcing repairs the trust the directory-upload reporting dented — into Kompozy as a source, and it fans that single point of view into a blog explainer, a comparison carousel, a few captioned short clips, and platform-native posts for X and LinkedIn, then schedules and publishes them across your channels. Being early and clear on a release like this is how one opinion becomes a week of content.
The second is structural, and the open-sourcing makes it cleaner than before: Grok Build ships software, Kompozy ships the marketing for it. Because the CLI now has inspectable hooks and a headless mode, a builder can have the agent emit a changelog on release and feed it into Kompozy as a source — and Kompozy turns each release into launch shorts, feature carousels, and a newsletter in your brand voice via a Persona Brief, published across nine platforms plus email and blog. Grok Build handles the engineering and the automation; Kompozy handles the audience.
Yes. On July 15, 2026, xAI published Grok Build — 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.
Largely, yes. It ships pointing at xAI's Grok models (its grok-build coding model), but its config.toml can target a different endpoint, including a local inference server, so you can run it against the model of your choice or fully air-gapped.
No. Open-sourcing changed who can run and inspect the tool, not what it does. It is a coding agent with no image, video, or publishing layer. 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.