One task, one branch, every repo
Why every ORRERION task cuts a git worktree in each repository it touches, and what that means for your main checkout.
The first thing you notice when you run two coding agents on the same repository is that they share a working directory. One runs the formatter, the other’s diff explodes. One switches branches, the other is suddenly editing the wrong code.
The fix is old and boring, which is exactly why we like it: git worktree.
What a task does
When you create a task in ORRERION, you pick the repositories it touches. For each one, ORRERION:
- creates a branch named after the task, like
feature/SL-7, - checks it out into its own worktree, next to (not inside) your main checkout,
- starts every agent for that task inside those worktrees.
Your main checkout never moves. You can keep coding there, run the app from it, or switch branches, while three agents work on the task in parallel.
Why every repo, not just one
Real changes rarely live in one repository. A new checkout flow touches the API, the storefront and the shared design library. With ORRERION the task is the unit of work, so the same branch exists in all three, and one review window shows every diff together.
When the task is done
Review the changes with ⇧⌘R, commit, and open a pull request per repo without leaving the app. Archive the task and ORRERION cleans up its worktrees. The branches stay until you merge them, like any other branch.
The details we sweated
- Dependencies. Each worktree is a real directory, so
npm installorcomposer installruns per task. Long-running commands, like a dev server, are saved per task so they come back when you return. - Disk space. Worktrees share the repository’s object database, so a new one costs your working files, not another full clone.
- Escape hatch. It’s all plain git. Open the worktree in your editor, run
git status, and nothing is hidden.
Read more in the docs, or see it on the features page.
— The ORRERION team