One task, one branch, one pull request: how Ember organizes parallel agents
In shortEmber gives every task its own branch and pull request, and puts parallel work in git worktrees, because that is the only arrangement we found where each change can be reviewed, tested by CI, reverted and merged by itself, and two agents never edit the same checkout.
The rule
Claude never commits on your base branch in Ember. It makes a branch before its first commit, and parallel work goes in a git worktree of its own under .claude/worktrees. Your own tab stays exactly as you left it.
When a branch is done you choose what happens: open a pull request, bring its changes into your checkout as an uncommitted squash merge, or check it out in your main worktree.
What our first design got wrong
Our first version of this model did not survive its own review, and the corrections shaped the product. We had said a chat belongs to a branch. That is wrong: a chat belongs to a worktree, and the branch is read live from git. If you switch from master to a feature branch in your main worktree, your chat should stay with you, which is how a terminal behaves.
We had also said every branch opens in a tab. Tabs are real windows, and a five-branch plan build would have meant five windows. So background worktrees get no tab until you ask for one, and every tab of a repository lists all of that repository's chats, grouped by branch.
The first design had six different ways to move a chat between places. The shipped design has none. The tab you type in drives the chat; a running chat simply says where it is running and offers to take you there.
Git is the record
Ember keeps no shadow copy of your work. Bringing changes over is git merge --squash, undoing that is git reset --merge, and conflicts are git's own. Everything Ember does, you can see and redo in a terminal, and the claude CLI sees the same state.
The base of new work is the branch of the tab you start from, always fetched first and always shown. You start from where you are, the same as git switch -c.
One state, one next step
Once every task is a branch, every branch can be described the same way. In Ember a branch is Needs you, Working, Waiting, Ready, Merged or Idle, and it offers one next step: Answer, Merge #41, Open PR, Remove worktree, Delete branch.
The Dashboard, the board, the tab dot, the title bar, the dock badge and your phone all read that one list, so their numbers always agree. Needs you is ranked by what each item frees up: a question holding up three stacked branches comes before a pull request that only waits for you.