A git workflow for several agents

This page builds on Git with repose.

Each task gets its own worktree and branch on the machine. Your laptop is where branches get reviewed and merged.

#1. Sync once, in the morning

repose sync

Your main goes up.

#2. One agent per task, each in a worktree

repose run -d --worktree -p "rate-limit the public API"
repose run -d --worktree -p "parse dates with date-fns"
repose run -d --worktree --agent codex -p "audit_log migration"

-d keeps your shell. Each run prints its worktree and window:

Worktree: ~/todo-app-worktree-1 on branch worktree-1
Window: claude
Worktree: ~/todo-app-worktree-2 on branch worktree-2
Window: claude-2
Worktree: ~/todo-app-worktree-3 on branch worktree-3
Window: codex

repose ps shows who's still busy, and in which worktree:

$ repose ps
WINDOW       COMMAND  STATE        TREE        ACTIVE
0:shell*     bash     -            checkout    2h ago
1:claude     claude   working      worktree-1  now
2:claude-2   claude   needs input  worktree-2  4m ago
3:codex      codex    working      worktree-3  now

repose ps todo-app claude-2 prints that agent's last lines without attaching.

A notification reaches you when an agent asks you something, waits for permission, or reports its work done. repose questions and repose reply handle the asking without an attach.

#3. Fetch and review on your laptop

$ git fetch repose
From todo-app.repose:~/todo-app
 * [new branch]      worktree-1      -> repose/worktree-1
 * [new branch]      worktree-2      -> repose/worktree-2
 * [new branch]      worktree-3      -> repose/worktree-3

Review each branch:

git log --oneline main..repose/worktree-1
git diff main...repose/worktree-1
git diff main...repose/worktree-1 -- test/

Run the tests on the machine without attaching:

repose exec --workdir worktree-1 npm test

Or open the checkout in your editor over SSH with repose code; the worktrees sit beside it.

#4. Merge what's good

git merge repose/worktree-1
git merge repose/worktree-3

A branch that isn't good enough gets a second round. repose attach -w claude opens the agent of that worktree, and you tell it what to change. It commits on the same branch; you fetch again. Or ask for a pull request and review on GitHub: "push the branch and open a PR" works in a prompt.

#5. Send the merged result back up

repose sync

The third agent, still working, isn't touched (Several agents, separate trees).

#6. Tidy

On the machine, or through repose exec:

repose exec -- git worktree remove todo-app-worktree-1
repose exec -- git branch -D worktree-1

On your laptop, git branch -rd repose/worktree-1 drops the fetched copy. Worktrees you leave in place cost only disk.

#The rules that make this work

• Agents commit. Put it in the prompt: "commit as you go" or "commit when the tests pass". An uncommitted change on the machine is what gets in the way of a sync.
• Nobody works on the machine's main. Then repose sync never stops on a file the machine changed, and a branch is always a clean diff against something you know.
• Review on the laptop. There git diff main...branch reads a copy the agent can't touch.
• Risky experiments get a fork. repose fork copies the machine's disk, worktrees, database and all, so an agent can try something destructive on the copy.