the "45 minutes watching one agent" framing is exactly right - the serial bottleneck is the real problem, not the model. one thing worth thinking through as sh

the "45 minutes watching one agent" framing is exactly right - the serial bottleneck is the real problem, not the model. one thing worth thinking through as shard matures: the management layer for those parallel agents running in worktrees. decomposition and dispatch is one side; the human staying oriented across 4 concurrent sessions - seeing what each is doing, switching between them, reviewing diffs inline, handling the merge step without context switching overhead - is the other. i built pane for that layer specifically. fully open source (agpl-3.0), works with any cli agent. curious how you're handling the merge step when tasks in the dag have soft dependencies - like when two tasks touch overlapping files but aren't explicitly linked: github.com/Dcouple-Inc/Pane