Grok Build

Combine code editing, shell execution, and web search in one full-screen terminal agent

The official README describes Grok Build as a terminal-based AI coding agent that understands the codebase, edits files, executes shell commands, searches the web, and manages long-running tasks. It is presented as a mouse-interactive full-screen TUI rather than only a prompt-and-response command line, keeping investigation, modification, and execution in one session.

Sources: [1]

Reuse the same runtime for interactive TUI work, headless CI, and ACP editor integration

The README lists interactive use, headless execution for scripting and CI, and editor embedding through the Agent Client Protocol (ACP). This makes the project useful when the same coding-agent runtime needs to move between human-driven terminal work, automation, and an editor surface instead of maintaining separate tools for each environment.

Sources: [1]

Extend the coding-agent environment with MCP, skills, plugins, hooks, and sandboxing

The bundled user guide covers configuration and theming alongside MCP servers, skills, plugins, hooks, headless mode, and sandboxing. The repository layout also separates the agent runtime, terminal/file-edit/search tools, workspace and VCS handling, execution, and checkpoints into crates, exposing the execution substrate in addition to the TUI.

Sources: [1]

A strong fit for terminal-first coding-agent users who also need automation or editor embedding

Grok Build is relevant to developers who want code investigation, editing, and command execution in a terminal workflow, teams that want the same agent available headlessly in CI or scripts, and users of ACP-capable editors. The Rust implementation is also useful for studying agent harness, TUI, tool execution, and workspace-management architecture.

Treat the public tree as a synchronized source release, and account for auth, build tooling, and third-party licenses

This repository is periodically synchronized from the SpaceXAI monorepo, and CONTRIBUTING.md explicitly says that external pull requests and unsolicited patches are not accepted. Its contribution model therefore differs from a typical community-driven OSS project: the public tree is provided for source transparency and local builds.

Released binaries cover macOS, Linux, and Windows, but building from source requires Rust plus DotSlash; macOS and Linux are supported build hosts while Windows builds from this tree are best-effort. First launch opens a browser for authentication. First-party code is Apache-2.0, while vendored and third-party code retains its original licenses, so redistribution should also review the THIRD-PARTY-NOTICES files.

Sources: [1][2][3]