# Run Cline CLI in parallel

> Run several Cline CLI sessions side by side in diri, each in its own git worktree, with live status, alerts when it needs you, and review in one place.

diri runs `cline` exactly as you would in a terminal, with your own install and sign-in. What it adds is everything one terminal window can't give you: several Cline CLI sessions at once, each in its own git worktree, a sidebar that shows which ones are working and which need you, and one place to review what they changed.

## What diri adds for Cline CLI

| | |
| --- | --- |
| Live status | Read from the screen with rules written for its interface. |
| Needs-you alerts | A notification and an amber mark when Cline CLI asks a question or wants permission. |
| Own worktree | Optional per session, so parallel runs never edit the same checkout. |
| Review | Diffs, staging, commits and pull request checks beside the session. |
| Survives restarts | Yes. Each session is owned by its own process, so quitting diri never stops it. |
| Resume after exit | Not automatically. |
| Fork a conversation | Not supported. |
| Approve from a notification | Yes. Permission prompts get an Approve button on the notification. |
| Starts other agents | No built-in connection. Claude Code, Codex and Cursor can start Cline CLI sessions for you. |

## Set up

1. Install Cline CLI with npm install -g cline. See the [Cline CLI install guide](https://docs.cline.bot/getting-started/installing-cline).

2. Run cline auth and choose a provider or API key.
3. Install diri with `brew install --cask cristicretu/diri/diri`, or [download it](https://github.com/cristicretu/diri/releases/latest).
4. Open **New Agent** in the sidebar and choose **Cline CLI**. If you installed Cline CLI while diri was open, click **Refresh** in **Settings → Agents** first.

The [quickstart](/docs/quickstart/) covers the rest: picking a folder, giving a task and answering questions.

## Run several at once

Start more sessions from **New Agent** with a fresh worktree each, or let an agent do it. Claude Code, Codex and Cursor get diri's [MCP server](/docs/mcp/) automatically and can start Cline CLI sessions (kind `cline`). Ask one of them:

> Start two Cline CLI agents in their own worktrees: one fixes the failing tests, the other updates the docs. Tell me when both are done.

Each session shows up in the sidebar under the agent that started it. [Worktrees and review](/docs/worktrees/) explains how to bring the work back.

## Questions

### Does diri need its own Cline CLI account?
No. diri starts the `cline` you installed, which uses its own sign-in. diri has no account of its own and never sees your password.

### Can I pick a Cline CLI session up again later?
Not automatically. The terminal and its history survive restarts, but a session that exits starts a fresh conversation. Quitting diri never ends a session in the first place.

### Can Cline CLI run on a server?
Yes. Install and sign in to Cline CLI on any machine you reach with `ssh`, then pick it as the machine in **New Agent**. diri needs no tmux, sudo or service there. See [Remote hosts](/docs/remote-hosts/).

### What does diri cost?
Nothing. diri is free and open source under Apache 2.0. You pay for Cline CLI as you do today.

## Other agents

[Claude Code](/agents/claude-code/) · [Codex](/agents/codex/) · [Antigravity](/agents/antigravity/) · [Cursor](/agents/cursor/) · [Gemini](/agents/gemini/) · [Aider](/agents/aider/) · [Amp](/agents/amp/) · [Copilot CLI](/agents/copilot/) · [All agents](/agents/)