§ conductor · multi-session safety
Multiple Claude sessions? Mooter coordinates them so you don't break git.
Filesystem locks. Heartbeats every 5 seconds. Stale recovery only with your confirm. No race conditions. No deleted commits.
~/repo·wave33-ultimateholds lock
$ git commit -m "wave33: final pass"
🔒holds .git/index.lock· heartbeat5s
~/repo·wave34-expqueued #1
$ git rebase main
○ waiting for lock · position 1 in queue
~/repo·hotfix/billingqueued #2
$ git commit -m "hotfix: null guard"
○ waiting for lock · position 2 in queue
this is what stops 2 sessions
from pushing simultaneously
from pushing simultaneously
worktree conductor · lock state
.git/index.lock● held
holder
wave33-ultimate· pid 48213
queue
1.wave34-exp
2.hotfix/billing
heartbeat
every 5s · alive
Stale lock detected? Conductor never force-breaks it. Recovery happens only with your confirm.
how it stays safe
01Filesystem lockOne session at a time holds .git/index.lock. The others queue in order — no race, no clobbered commit.
02Heartbeat every 5sThe holder pings every 5 seconds. A live holder keeps the lock; a missed beat is what flags a stale one.
03Recovery on your confirmConductor never force-breaks a stale lock on its own. It surfaces the situation and waits for you to confirm.