Rethinking Git for the Age of Coding Agents with GitHub Cofounder Scott Chacon

What It Covers

GitHub cofounder Scott Chacon and a16z's Matt Bornstein examine why Git's 20-year-old interface — built by Linus Torvalds' Linux kernel team with no intentional UX design — fails both human developers and coding agents, and how GitButler's CLI rethinks version control primitives for agentic workflows.

Key Questions Answered

• •Agent-optimized CLI output: When GitButler added a `--json` flag expecting agents to prefer structured data, agents instead performed better with human-readable output, then piped it through JQ themselves. The practical fix: append status output automatically after every mutable command, since agents run `git status` after nearly every operation regardless.
• •Parallel branch architecture for multi-agent teams: Rather than using Git worktrees — which create isolated copies of the working directory, preventing agents from seeing each other's changes — GitButler's parallel branch model lets multiple agents operate on one shared working directory. Agents detect file conflicts and automatically stack branches, eliminating merge conflicts before they reach GitHub.
• •Communication overhead is the real multi-agent bottleneck: Running five or more agents simultaneously creates a management problem, not a compute problem. A more productive model has agents use idle cycles to communicate with teammates' agents — surfacing file conflicts, flagging relevant changes, and briefing the human developer — rather than maximizing parallel agent count.
• •Writing ability becomes the primary engineering skill: As implementation cost approaches zero, the constraint shifts entirely to specification quality. Developers who can write precise, detailed specs — describing desired behavior rather than implementation details — will outperform those who rely on technical execution alone. The "why" compounds in value as the "how" becomes automated.
• •PR-based code review is structurally broken: Surveys show roughly 80% of developers still use Git CLI over GUIs. Meanwhile, PR review has degraded to cursory checks because branch-based review divorces commit messages from merge context. Patch-based, local review — where agents can pull, compile, run tests, and return a prioritized findings list — addresses what PR review never reliably delivered.