Our take
Newless than six months old and changing fast- Activity
- 42
- Community
- 4
- Issues
- 21
- Pull requests
- no data
- Fewer contributors than 92% of the projects we track
Grok Build is a capable, flexible coding-agent harness, but its very recent and highly concentrated development makes it a project to evaluate carefully before relying on it broadly.
Good fit if
- You want an interactive Rust-based coding agent with terminal, file-editing, and search tools.
- Headless scripting or ACP-based editor integration matches your workflow.
- You can work with a fast-changing project that currently has no release history in the measured period.
Look elsewhere if
- You need evidence of a broader contributor base or shared project ownership, since measured development is concentrated in one contributor.
- Your team needs established release history or demonstrated issue-resolution activity before adopting a coding agent.
- You need a Windows build known to be tested from this source tree, which the README says is not currently the case.
All health signals
| Last commit | 2026-09-29 (9 days ago) |
|---|---|
| Commits, last 90 days | 51 |
| Releases, last 12 months | 0 |
| Contributors | 1 |
| Issues closed, last 90 days | 0 |
| Project age | 3 months |
Checked on 2026-10-09 with the GitHub API.
Overview
Grok Build is a terminal-based coding agent for developers who want an agent to work in their existing codebase. It combines a full-screen, mouse-interactive interface with tools for editing files, running shell commands, searching the web, and managing longer-running tasks.
It can also run headlessly for scripts and CI, or integrate with editors through the Agent Client Protocol (ACP). The repository is periodically synced from SpaceXAI's monorepo, so it is a source tree for the CLI and runtime rather than an independently maintained upstream project.
Key Features
- Full-screen terminal interface with scrollback, prompts, and modals.
- Agent tools for file editing, terminal commands, and search.
- Headless entry points for scripting and CI workflows.
- Agent Client Protocol support for editor integration.
- Workspace support for filesystem access, version control, execution, and checkpoints.
- User-guide coverage for configuration, MCP servers, skills, plugins, hooks, and sandboxing.
Use Cases
- Developers can ask an interactive agent to understand and modify an existing codebase.
- Teams can run coding tasks from scripts or CI using the headless mode.
- Editor users can connect the agent through ACP instead of working only in its terminal interface.
- Developers who need configurable agent tooling can explore its MCP, skills, plugins, and hooks support.
What you need
Detected in the repository
- Rust (from Cargo.toml)
License in plain words
Apache-2.0permissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Install the released binary on macOS, Linux, or Windows using the official installation instructions:
curl -fsSL https://x.ai/cli/install.sh | bash
See the repository README for source-build requirements, platform-specific installation, and documentation links.
Alternatives
- openinterpreter: Open Interpreter targets low-cost language models and supports multiple agent harnesses and Codex SDK clients, while Grok Build emphasizes interactive, scripted, and ACP editor use.
- prime-agent: Prime Agent focuses on long-running coding and research tasks with a persistent Python environment, recursive subagents, and durable context.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| grok-build | Rust | Apache-2.0 | 27.3k | New |
| openinterpreter | Rust | Apache-2.0 | 68.5k | Active |
| prime-agent | Rust | Other | 21.5k | New |
Considerations
The project is new and changing quickly. The measured activity shows recent commits, but no releases in the measured period, and all measured contributor activity comes from one person. The repository reports no open issues, but no issues were closed in the measured period, so there is little issue-handling history to assess. Building from source requires Rust and DotSlash, with protoc available through DotSlash or the environment; macOS and Linux are supported build hosts, while Windows source builds are best-effort and untested. The repository is periodically synced from a monorepo, and external contributions are not accepted.
Found this useful?
Share it with someone who would like grok-build.