---
title: "How to run several Muse Code agents in parallel"
url: https://helicon.sh/guides/run-parallel-agents
description: "Use isolated git worktrees so parallel agents never collide, then watch all of them from one sidebar that shows which threads are running and which are blocked."
updated: 2026-09-19
site: Helicon
---

# Run several Muse Code agents at once

Create an isolated git worktree per task so the agents never touch the same files, add each one to Helicon as its own project, and start a thread in each. The sidebar then shows every run in one list, marked by whether it is running, finished, or blocked on your approval.

## Why worktrees rather than branches

Two agents on one checkout will fight over the same files. A git worktree gives each one its own directory with the same repository behind it, which is the cheapest real isolation available without cloning.

```sh
git worktree add ../proj-auth -b feat/auth
git worktree add ../proj-search -b feat/search
```

## Adding them to Helicon

Add each worktree directory as a project. Helicon keys projects by working directory, so each one gets its own entry with a badge marking it as a worktree, and its sessions live underneath.

## Watching them

- Running threads are marked while they run.
- Threads waiting on an approval are marked, so you know which one needs you.
- Stop one call, background it, or stop everything, without ending the session.
- The usage page shows what the parallelism cost, by thread.

> Each workspace gets its own `muse serve` host, the same process the CLI would start. Parallelism is bounded by your machine and your plan, not by Helicon.

## Run several Muse Code agents in parallel with git worktrees

1. **Create a worktree per task** Each agent gets its own directory.
   ```sh
   git worktree add ../proj-auth -b feat/auth
   ```
2. **Add each worktree as a project** Helicon lists them separately with a worktree badge.
3. **Start a thread in each** Threads are grouped under their own project.
4. **Triage from the sidebar** Running, finished and blocked threads are marked, so you can see who needs you.

## Frequently asked questions

### How many agents can I run?

As many as your machine and your Muse Code plan allow. Each workspace gets its own muse serve host.

### Do worktrees show as separate projects?

Yes, each with a badge, because each is its own working directory.

### How do I know which one is waiting on me?

Blocked threads are marked in the sidebar, so the approval queue is visible without opening each one.

## Related

- [Projects and worktrees](https://helicon.sh/features/projects-and-worktrees): Helicon groups every Muse Code thread under the directory the agent worked in, isolated git worktrees included, so parallel work across repositories has one place to live.
- [Background work](https://helicon.sh/features/background-tasks): Send a running tool call to the background, stop one, or stop them all. Cancel a workflow run, or skip and retry its agents, without abandoning the thread.
- [Running agents in parallel](https://helicon.sh/use-cases/parallel-agents): Isolated worktrees, one sidebar, and clear marks for which thread is running, finished, or blocked on you. Plus the cost of all that parallelism, per thread.

---

Helicon is a free, MIT licensed, unofficial community client for Meta's Muse Code CLI. Not made, sponsored or endorsed by Meta. Source: https://helicon.sh/. Machine readable index: https://helicon.sh/llms.txt