How to orchestrate large coding tasks without context bloat

I have lately been experimenting with an agentic workflow where one agent coordinates a large coding task, while short-lived worktree agents implement isolated phases in their own branches. A tmux session with phased-implement workflow running. Each tab in the sidebar on the left is a worktree agent. # The orchestration layer It uses workmux's primitives as the control plane for spinning off work…