Version Control and Agent Workflows
Synthesis
Parallel agent work needs visible boundaries between experiments, reviewable changes, and recovery. Daniel San's terminal-first workflow uses multiple panels and Git worktrees to keep several Claude Code instances separated while retaining an operator's view of their state. It is a personal workflow report, not a comparative evaluation of terminals or agents. [src]
Jujutsu offers a related recovery-oriented model: mutable commits, automatic snapshots, an operation log, lightweight bookmarks, and conflict handling that lets unrelated work continue. Its tutorial emphasizes Git interoperability and explains a particular mental model; teams still need shared conventions for review, publication, and conflict ownership. [src]
Working model
Isolation is useful when it preserves reversibility. Give each agent or task an explicit workspace and branch-like identity, make handoff artifacts inspectable, and retain an operation history that helps a person undo a bad merge or recover a useful partial result.