Managing Kata Worktrees

Architecture

kata-mono uses a multi-worktree layout where each worktree maps to a monorepo app:

Why standby branches exist: Git prohibits checking out the same branch in multiple worktrees. Since all worktrees need to track main when idle, each has a local "standby" branch that mirrors origin/main. No work happens directly on main in any worktree.

Standby branch tracking

Each standby branch must track origin/main so git pull works:

git branch --set-upstream-to=origin/main wt-cli-standby

If git pull reports "no tracking information," re-run that command. Tracking can be lost if a branch is recreated.

For initial setup of a new standby branch, set tracking and then pull from within the worktree to sync both the ref and working tree:

git branch --set-upstream-to=origin/main wt-<name>-standby
git -C /Volumes/EVO/kata/kata-mono.worktrees/wt-<name> pull

Starting work on a ticket

1. Verify the worktree is on its standby branch and current with main:
   bashCopy

   git -C /Volumes/EVO/kata/kata-mono.worktrees/wt-<name> log --oneline -1
   # Should match: git log --oneline -1 main
   

2. If behind, sync first (see below).
3. Create and check out a feature branch:
   bashCopy

   git -C /Volumes/EVO/kata/kata-mono.worktrees/wt-<name> checkout -b feat/my-feature
   

Returning to standby after a PR merge

After merging a PR on GitHub:

# In the worktree (or using -C from anywhere)
git checkout wt-<name>-standby
git pull

git pull works because the standby branch tracks origin/main. This fast-forwards the standby branch to include the newly merged PR.

If pull fails with conflicts: This means the standby branch diverged from main (e.g., commits landed on standby that weren't in the PR). If the PR contained all the work, reset is safe:

git checkout wt-<name>-standby
git fetch origin
git reset --hard origin/main

Only use reset when you're certain the PR captured all the work. If unsure, inspect with git log wt-<name>-standby..origin/main and git log origin/main..wt-<name>-standby to see what each side has.

Diagnosing worktree drift

To check if all worktrees are current:

git worktree list

All entries should show the same commit hash when idle. If any differ:

# See what main has that the standby doesn't
git log --oneline wt-<name>-standby..main

# See what the standby has that main doesn't (should be empty)
git log --oneline main..wt-<name>-standby

Sync all worktrees after a merge

After merging a PR, pull main from the root repo. Worktrees share the same git object store, so they see the updated refs automatically. Then pull from within each worktree to fast-forward its standby branch:

# From the main repo root
git checkout main && git pull

# Then from each worktree (or using -C)
for wt in wt-cli wt-context wt-desktop wt-orc wt-symphony; do
  git -C /Volumes/EVO/kata/kata-mono.worktrees/$wt pull
  echo "$wt: $(git -C /Volumes/EVO/kata/kata-mono.worktrees/$wt log --oneline -1)"
done

Do not use git update-ref or git reset --hard to sync worktrees. These operate on refs or working trees in isolation and cause dirty state. Use git pull from within the worktree, which updates both the branch pointer and working tree together.

Health check (all worktrees)

Quick verification that everything is in sync:

MAIN_SHA=$(git rev-parse main)
for wt in wt-cli wt-context wt-desktop wt-orc wt-symphony; do
  WT_SHA=$(git -C /Volumes/EVO/kata/kata-mono.worktrees/$wt rev-parse HEAD)
  if [ "$WT_SHA" = "$MAIN_SHA" ]; then
    echo "$wt: current"
  else
    echo "$wt: BEHIND (at $(git log --oneline -1 $WT_SHA))"
  fi
done

Common pitfalls

• Standby branch loses tracking: Happens if the branch is deleted and recreated. Fix: git branch --set-upstream-to=origin/main wt-<name>-standby
• Add/add merge conflicts on sync: Happens when the standby branch has commits that also reached main via a PR (same content, different history). Safe to git reset --hard origin/main if the PR captured everything.
• Working on the wrong worktree: Always verify pwd resolves to the intended worktree, not the main repo. See memory: feedback_worktree_paths.md.