Run Grok with your whole team, in the cloud

Published October 28, 2026 · by the AQ team

AQ runs Grok (xAI's Grok CLI) in cloud workspaces your whole team shares: the same live terminal, editor and app preview in everyone's browser. Grok runs on a machine that is yours, each work item gets its own isolated git worktree, and you sign in with your own xAI account. AQ never marks up usage on your own subscription.

Two ways to use Grok in AQ

• As an AQ thread. Pick Grok in the composer and talk to it like any AQ conversation: messages queue, follow-ups reach it mid-turn, and the transcript, Changes panel and pull request card sit beside it. It runs on your own xAI account.
• As a terminal tab. Open Grok itself in a tab of the work item, exactly as it runs on your laptop, in a real terminal teammates can watch and type into.

Grok also works as a teammate outside AQ: the Grok bot can create and message AQ work items through AQ's MCP server (see connect the Grok bot to AQ).

What running Grok in AQ adds

• Sessions that outlive your laptop. Grok runs on the machine, so a closed lid or a lost connection does not stop it.
• Parallel tasks, zero collisions. One isolated git worktree per work item.
• Review and merge in the tab. The Changes panel, line comments and a merge that waits for checks (see review and merge).
• A crew around it. Use Grok as a builder in a crew and have another vendor review its work (see Crews).
• Your team in the loop. Teammates open the same work item, watch live and take the keyboard when you hand it over.

How setup works

Connect Grok once in Settings, Connections, with its normal sign-in. You can connect more than one account and pick which one a thread uses. Then connect a repository and start a work item. Related reading: Grok 4.7 for coding agents.

Grok alongside every other agent

AQ runs Grok next to Claude Code, Codex, Cursor, Kimi Code, Grok, Antigravity, Devin, Muse Code, OpenCode, Command Code and plain shells, on the same repository. See every agent AQ runs.