---
title: "A desktop GUI for Grok Build agents | microManager"
description: "microManager is a free desktop GUI for SpaceXSI's Grok Build: it runs grok agent stdio over ACP, in parallel git worktrees beside Claude Code and Codex."
url: "https://micromanager.win/agents/grok"
updated: "2026-11-09"
---

# A desktop GUI for Grok Build

microManager is a free desktop GUI for Grok Build, the coding agent of SpaceXSI (formerly xAI), on macOS, Windows and Linux: it starts grok agent stdio and talks to it over the Agent Client Protocol, with no adapter in between. Each chat is a Grok session in its own git worktree, next to Claude Code, Codex or anything else you run.

Updated 9 November 2026

![A Grok chat on Grok 4.7 Fast in the workspace Add balanceText to accounts route: an edit card showing the test it added to test/app.test.ts as a diff, an Execute npm test card, a folded Thought, and its summary ending with npm test: 11 passed, 0 failed.](https://micromanager.win/screenshots/grok-chat.png)

Grok Build over ACP: its edits show as diffs, its commands as cards, and its thinking folds away.

## Is there a GUI for Grok Build?

Grok Build is a command-line agent. microManager gives it a desktop window: each Grok session is a chat with streamed replies, tool calls shown as cards, file edits as diffs, permission requests as buttons and its plan as a to-do list, and several sessions can run at once in separate worktrees. Because it speaks ACP, the protocol Grok Build supports for hosting apps, there is no wrapper script or shim to maintain.

## How does microManager run Grok Build?

The built-in profile, named Grok, runs:

```sh
grok agent stdio
```

and talks to it over the Agent Client Protocol on standard input and output. It uses the `grok` you installed and signed in to; if it is not on your login shell’s `PATH`, set its absolute path in Settings → Agents.

## What works with Grok Build?

Everything ACP offers: streamed replies and thinking, tool calls shown as cards, its plan as a to-do list while it works, permission requests whenever Grok asks (its own permission setting decides whether it does), model choice when Grok offers several, and its slash commands. Grok also gets microManager’s [MCP tools](https://micromanager.win/docs/mcp-tools), and every workspace feature applies: worktrees, checkpoints, diff review and pull requests.

## What happens to Grok chats when I import from Conductor?

ACP chats that Conductor ran with a Grok model become chats on the Grok profile, in the same workspace. If Conductor was set up to reach Grok through a separate harness program, microManager does not carry that path over, because it runs `grok agent stdio` itself; it turns the Grok profile on instead.

## What do I need?

Grok Build installed and signed in, so that `grok` works in your terminal.

## Where to go next

- [ACP agents](https://micromanager.win/features/acp-agents)
- [Agents and profiles](https://micromanager.win/docs/agents)

## Frequently asked questions

### Do I need a shim or adapter?

No. microManager starts grok agent stdio and speaks ACP to it directly.

### Are my Grok chats from Conductor imported?

Yes. ACP chats that Conductor ran with a Grok model are imported as chats on microManager's Grok profile.