# ivar vs Orca: multi-repo features and parallel agents
> Orca runs many coding agents in parallel in a desktop app; ivar turns one change across repos into one feature. As of 2026-10-06.
Source: https://ivar.run/compare/ivar-vs-orca

Orca is a desktop app for running many coding agents in parallel. `ivar` is a CLI that mounts every repo a change touches, on one branch, into one session of the harness you already use. You can use both.

## At a glance

Claims about Orca are as of 2026-10-06 and come from its [worktrees documentation](https://www.onorca.dev/docs/model/worktrees).

| | Orca | `ivar` |
|---|---|---|
| Form | desktop app | CLI |
| Unit | a worktree of one repo | a feature across N repos |
| Several repos | project groups: several repos under a parent folder in the sidebar; a folder workspace ties a task to one of those repos | one view directory with every promoted repo |
| Branches and PRs | per repo | one branch name across repos, one PR per repo via `gh`, on GitHub |
| Common branch across repos | not documented | yes |
| Write scope per repo | not documented | repos you haven't promoted are guarded; kernel-enforced on Linux ([Limitations](/docs/reference/limitations)) |
| Coordinated PRs | not documented | `ivar feature deliver` opens one per repo, via `gh`, on GitHub |

## How each handles a change across three repos

The change touches `api`, `web` and `shared-types`.

In Orca, you group the three repos under a parent folder. The folder workspace ties the task (an issue or a PR) to one of them. Worktrees, branches and PRs stay per repo.

In `ivar`, you create one feature, promote the three repos and start one session:

```sh
ivar feature create avatar-url
ivar feature promote avatar-url api
ivar feature promote avatar-url web
ivar feature promote avatar-url shared-types
ivar session start avatar-url
```

All three sit in one directory on the `avatar-url` branch. Deliver opens one PR per repo, via `gh`, on GitHub.

## Where Orca is the better choice

You want many agents in parallel, each in its own worktree, from a graphical app. Choose Orca when a GUI matters more to you than a single branch across repos.

## Where `ivar` is the better choice

The change crosses repos and needs one branch name, writes guarded to the repos you promote (kernel-enforced on Linux; see [Limitations](/docs/reference/limitations)), and one PR per repo (via `gh`, on GitHub). Choose `ivar` if you work in the terminal.

## Using them together

Open an `ivar` session directory in an Orca terminal.

## FAQ

### Does Orca support multiple repos?

Yes, with project groups. The docs describe several repos grouped under a parent folder in the sidebar, with a folder workspace that ties a task to one of them. Worktrees, branches and PRs stay per repo. Whether Orca uses a common branch across those repos, limits writes per repo or coordinates PRs is not documented.

### Can I run Orca and `ivar` together?

Yes. Open the session directory in an Orca terminal.

### Which one should I pick for one repo?

For one repo with many parallel agents, Orca fits. `ivar` pays off once a change spans repos.

Back to [all comparisons](/compare), or see [ivar with Claude Code](/docs/with/claude-code) for a harness walkthrough.

## Sources

- [Orca worktrees](https://www.onorca.dev/docs/model/worktrees), accessed 2026-10-06.