xAI published Grok Build’s source code on GitHub this week, two months after the coding agent’s May launch and weeks after it priced the underlying grok-build-0.1 model in June. The new fact is not the agent. It is that developers can now inspect how the tool-calling, sandboxing, and editor-embedding layers actually work. That access comes with a condition the launch announcement did not mention.
The repository sits under the xai-org organization on GitHub and carries an Apache 2.0 license. Its own metadata frames the project as an agent runtime paired with a full-screen terminal interface. It has drawn more than 10,000 stars and over 1,600 forks within two days of going public, according to the repository’s own GitHub statistics. A fast star count on a freshly public repository measures attention, not adoption. xAI has not paired the code release with any usage or retention figures for Grok Build.
xAI’s README frames the repository as a periodic export from its internal SpaceXAI monorepo, not a project developed out in the open. Its CONTRIBUTING.md draws a hard line: the project does not take pull requests from outside engineers. That puts Grok Build in a different category from community-maintained agents such as Aider, the open-source terminal coding tool. The code is readable, but every change still originates inside xAI, and outside engineers have no channel to submit fixes.
The documentation shipped with the code is where the real update lives. The pager crate’s user guide now covers MCP servers, custom skills, plugins, hooks, sandbox configuration, and headless operation. Headless mode lets Grok Build run unattended inside a CI pipeline rather than only as an interactive terminal session. Editor integration runs through the Agent Client Protocol, which lets a third-party editor host the agent as an embedded process instead of shelling out to a separate terminal window. Both capabilities existed in some form at the May launch. What changed is that engineers can now read the implementation directly instead of relying on release notes.
One detail in the release did not make it into xAI’s own framing. The project’s third-party notices reveal that its tool layer includes code ported from OpenAI’s Codex and from opencode, the open-source coding-agent project maintained by sst. Grok Build’s tooling, in other words, was not built from a blank page. Pieces of it are adapted from two rival open coding agents under their original licenses, a lineage the May coverage did not surface.
Teams that adopted Grok Build for CI work based on June’s pricing announcement should read the sandboxing and headless-mode documentation directly rather than the marketing page. Any team planning an ACP-based editor integration should confirm the protocol version against this repository before committing to it for the rest of 2026.
Source: xAI’s GitHub repository for Grok Build (github.com/xai-org/grok-build), reviewed July 15, 2026.
