Run Grok CLI in parallel — Tallos

What is Grok CLI?

Grok CLI is xAI's AI coding agent for the terminal, run with the grok command. It works on the project in your current folder — reading code, editing files and running commands — and signs in with your Grok account or uses an xAI API key.

Tallos is a desktop agent development environment that installs, signs in and launches the real Grok CLI, runs many sessions of it in isolated workspaces, and puts it next to Claude Code, Codex and your other agents.

How do I set up Grok CLI in Tallos?

Open Settings → Connections, install Grok CLI from its card, sign in, and set it as your default agent. An existing grok on your PATH is detected automatically.

1. 1

   Install

   Click Install. Tallos shows the official command before running it: npm install -g @xai-official/grok or curl -fsSL https://x.ai/cli/install.sh | bash on macOS, and npm install -g @xai-official/grok on Windows (Node.js required).

2. 2

   Sign in

   Click Sign in to run grok login in a terminal. Or click Use API key: Tallos keeps an XAI_API_KEY in your computer's secure storage and passes it only to Grok CLI each time it starts it.

3. 3

   Check the models

   Open Models on the card. Tallos reads the list from your signed-in Grok CLI, so the list matches what the CLI offers you.

4. 4

   Make it the default and start

   In Settings → Agents, set Grok as the Default agent. Add a repository, click + for a workspace and describe the task; Tallos starts grok in a fresh worktree with your prompt.

Setting up several agents at once? Follow connect your agents.

How do I run multiple Grok CLI sessions in parallel?

Create one workspace per task. Each workspace is a separate git worktree with its own branch, files and terminals, so parallel Grok sessions never write to the same working directory.

• Watch them together. Split panes in any direction; Tallos's Grok hooks report working, waiting and done in the sidebar.
• Prompts arrive intact. Tallos passes your task to grok as an argument, after a -- separator, so a prompt that starts with a word like “help” is not read as a Grok command.
• Review per branch. Each workspace has its own diff; comment on lines and send the feedback back to that session.
• Resume later. Grok sessions appear in Agent Session History; Resume runs grok --resume <id> in the right folder.

The isolation model is explained in parallel workspaces.

Connect Grok CLI and run it in parallel.

Get Tallos →

Does Grok CLI open in a chat view or a terminal?

In a chat view, by default, for sessions on your computer. Tallos reads Grok's transcript and shows messages and tool calls for reading, while the Grok CLI keeps running underneath.

• Model pill. Choose the model before the first message (passed as -m at launch) or change it mid-session (sent as /model). The list comes from your signed-in Grok CLI.
• Effort pill. Set reasoning effort at launch (--reasoning-effort) or mid-session (/effort). The choices follow the selected model.
• View terminal / Back to chat switch to the raw Grok interface and back at any time.
• Want the terminal every time? Set Settings → Agents → Agent View to Terminal.

Read more in native chat.

How do I use Grok CLI alongside other agents?

Add Grok to a squad — a leader agent plus members — or run it in its own workspaces next to other agents. In a squad, each slot picks its own agent, model and effort, and Tallos applies Grok's model and effort when it launches that member.

• One of three attempts. In *3 attempts, pick the best*, Grok can try the same objective as Claude Code and Codex; the leader recommends one result.
• Builder or reviewer. In *Build + review*, Grok can build while another agent reviews, or the other way round.
• Leader. Any detected agent can lead, including Grok. It plans, dispatches and reports within your limits: 5 rounds and 4 members at once by default, up to 20 rounds and 12 members.

Every member works in its own worktree, and nothing merges without your approval.

What does Tallos add to Grok CLI?