Grok
Run xAI's Grok Build agent inside Proliferate workspaces with review and governance.
Grok runs through xAI's Grok Build agent over its native ACP surface, in the same workspace model as every other agent.
Supported functionality
| Capability | Support |
|---|---|
| Repository workspaces | Run Grok against a local checkout or a worktree with full repo and branch context. |
| Permission modes | Not available. Grok runs a single way; there's no plan/read-only split like Claude Code's session modes or Codex's read-only/auto/full-access. |
| Model & reasoning | Switch models from the composer. Reasoning is picked by model (a reasoning and a non-reasoning variant), not a separate toggle. |
| Review | Inspect generated diffs, the transcript, and command output before merge. |
| Credentials | Grok's own sign-in, an xAI API key (XAI_API_KEY), or the Proliferate gateway. |
Authenticate Grok
Set Grok's authentication under Settings -> Agents -> Grok. Choose one method card at a time: Proliferate gateway, API key, or CLI login.
- Native sign-in. Sign in with your Grok account (
grok login, or thegrok.combrowser sign-in), which caches a login token on your machine. Authenticate appears when Grok needs that credential. - Your own xAI API key. Paste a key to save it to your vault, or bind one
already saved; Proliferate wires it in as
XAI_API_KEYfor you. - Proliferate gateway. Managed access to xAI models, with nothing to paste in and nothing to rotate.
The cards have radio behavior: choosing one disables the other configured source. Cloud workspaces and their separate authentication surface are coming soon.
Unlike Claude Code and Codex, Grok isn't bundled with the desktop app. It downloads automatically the first time a workspace needs it, so there's nothing to install ahead of time.
For how native sign-in and shared routes work across harnesses, see Authentication.