A collection of 2 posts

1. Parallel agent workflows often use Git worktrees: one checkout per task, one branch per agent. That improves isolation, but it also creates a subtle permissions problem. A child agent running in one worktree may still try to read or edit sibling worktrees, parent directories, or shared files outside its assigned

2. Git worktrees make it easy to run several coding agents in parallel. They do not make the resulting branches compatible. If three agents edit the same files, the merge queue becomes the first place you discover the collision. A lightweight "clash predictor" can catch overlapping edits earlier by