Rebuilding Git for AI Agents and The Future of Developer Tools | Deep Dives with a16z

Video summary

GitButler CEO Scott Chacon says agent-ready Git needs parallel branches, better code review, and stronger writing.

GitHub cofounder Scott Chacon returned to version control after finding Git’s user interface largely unchanged since 2005. GitButler keeps Git’s underlying storage and protocols but adds interfaces tailored to people and AI agents: a GUI, TUI, and CLI with human-readable output, JSON, and agent-focused context. Its parallel-branch workflow lets multiple agents work in one directory, see changes, and stack branches when they need to edit the same files—unlike isolated worktrees. Chacon says GitHub may not be the next-generation developer platform; new workflows are still emerging. He also argues that pull requests and branch-based reviews invite “commit slop,” and that local, patch-based review with agents testing code could work better. As implementation gets cheaper, he believes clear specifications, communication, and writing will become developers’ key skills. Agents could also help teams coordinate, while storing their transcripts and tool calls creates new metadata and usability challenges.

Chapters

1. 0:00Intro: Scott Chacon on agent code review and developer communication
2. 1:11Why Scott came back to version control after GitHub: GitButler rethinks Git’s interface
3. 6:18How Git was actually built: Unix plumbing, Pasquy’s Perl porcelain, and backward compatibility
4. 11:32Designing GitButler’s CLI for agents: shared interfaces, status output, and planned Markdown
5. 18:05Parallel branches: GitButler lets agents share a working directory and stack branches
6. 23:33What happens to GitHub in an agentic world: the next platform may be unlike SourceForge or GitHub
7. 27:00Code review needs a rethink: patch-based review, agent testing, and possible prompt review
8. 32:19Writing and communication: clear specifications become the next developer superpower
9. 34:52Writing and communication: GitButler prototypes specs and agents coordinate across teams
10. 39:11Writing and communication: Git metadata must balance agent context, history, and usability
11. 42:43Writing and communication: agent progress raises the human questions of intent and judgment