# Run Cursor in parallel

> Run several Cursor 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 `cursor-agent` 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 Cursor 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 Cursor

| | |
| --- | --- |
| Live status | Read from the screen, plus a hook when it stops. |
| Needs-you alerts | A notification and an amber mark when Cursor 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 | Yes, the exact conversation. |
| Fork a conversation | Not supported. |
| Approve from a notification | Yes. Permission prompts get an Approve button on the notification. |
| Starts other agents | Yes. diri's MCP server is added at launch. |

## Set up

1. Follow Cursor's CLI installation guide. See the [Cursor install guide](https://docs.cursor.com/en/cli/installation).

2. Run cursor-agent and complete authentication when prompted.
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 **Cursor**. If you installed Cursor 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. Cursor gets diri's [MCP server](/docs/mcp/) automatically, so you can ask it in plain words:

> Split this into three parts and start a Cursor agent for each, in its own worktree. Wait for them, review each diff, and merge the ones that pass the tests.

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 Cursor account?
No. diri starts the `cursor-agent` you installed, which uses its own sign-in. diri has no account of its own and never sees your password.

### Can I pick a Cursor session up again later?
Yes, the exact conversation. diri records its id at launch and reopens that one. Quitting diri never ends a session in the first place.

### Can Cursor run on a server?
Yes. Install and sign in to Cursor 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 Cursor as you do today.

## Other agents

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