How this relates to Grok Build

Layers

Layer	What it is	Where it lives
Agent (models, tools, skills, MCP, auth)	Official Grok Build CLI	Installed `grok` binary + `~/.grok`
Desktop GUI	This project	Electron + React ACP client

Grok Build already supports embedding via:

grok agent stdio

This app is a graphical client on that interface. It does not replace or patch the agent monorepo UI.

Useful if you want to read ACP behaviour or rebuild the CLI yourself:

git clone https://github.com/xai-org/grok-build.git
# place next to this repo, e.g. ../grok-build

You do not need a local clone to run Grok Desktop if the official grok binary is installed.

The agent project is maintained separately; this is a product shell around ACP.
Replacing the terminal UI inside that tree is a large effort; ACP is the supported boundary for alternate clients.
Keeps this UI’s license (MIT) clean of vendored agent source.

GUI product layer · reuse the agent process.