# How to run several Claude Code sessions in parallel

Running Claude Code sessions in parallel means giving several agents separate tasks at the same
time, each in its own conversation, while you watch and steer them. In a terminal, that's a window
or tab per session and a lot of switching. In Moontors, an agentic development environment (ADE),
each session is a card on one board, and the ones that need you say so.

## What goes wrong in terminals

- You can't see which session is waiting for an answer until you switch to it.
- Two sessions in the same folder edit the same files, and one's changes land in the other's work.
- Closing a terminal ends the session in it.

## Run them side by side

1. Choose **Create session**, pick the folder, and pick Claude Code as the provider. Give the
   session a title that says its task: it names the card, and the branch if you use a worktree.
2. Repeat for each task. Every session starts on the board, in the top row.
3. Write each session's first prompt. Each card streams its session's work as it happens.

Sessions in different folders or repositories need nothing more. For several sessions in one
repository, give each its own worktree (below).

## Keep their changes apart

When the folder is in a git repository, turn on **Run in a new worktree** as you create the
session. The session then works on its own branch, in a folder of its own, so no two sessions edit
the same copy of a file. You review and merge each branch as you would anyone's. See
[Worktrees](/docs/worktrees/).

## See which one needs you

Each card shows its status. **Waiting** means the session is waiting for you: a question, or a
permission request you can answer right in its transcript. Moontors also sends a desktop
notification when a session needs you; see [Notifications](/docs/sessions-and-board/#notifications) for when they arrive with the
window closed.

Sort the board into your own sections, such as one for review and one for what's next, and drag
cards between them as their work moves on. See [Sessions and the board](/docs/sessions-and-board/).

## Things to know

- Every session is a full Claude Code session on your account, so parallel sessions share your
  plan's usage limits. The Status tab shows them, and when they reset. See
  [Insight and code workflows](/docs/insight-and-code-workflows/).
- Each session's permission mode is its own. A session you trust with a well-defined task can run
  with fewer questions; see [Permission modes](/docs/permission-modes/).
- Closing the window doesn't stop the sessions. See
  [How to keep coding agents running when the window closes](/docs/how-to/keep-agents-running-when-the-window-closes/).

## Questions

### How many Claude Code sessions can run at once?

As many as you create. They all use your Claude plan, so they share its usage limits; the Status
tab shows them, and when they reset.

### Can parallel sessions work in the same repository?

Yes. Sessions in the same folder share its files, so give each session its own worktree when their
tasks might touch the same files.

### Will I know when a session needs me?

Its card shows **Waiting**, and a desktop notification says so while Moontors is open. The session
waits for you, so answer it to keep its work going.

## Related

- [What is an agentic development environment (ADE)?](/docs/what-is-an-ade/)
- [How to use git worktrees for AI coding agents](/docs/how-to/git-worktrees-for-ai-agents/)
- [A Claude Code Desktop alternative with Codex and Gemini CLI](/docs/compare/claude-code-desktop/)
- [A Conductor alternative for Windows and Linux](/docs/compare/conductor/)