Uncle Bob Is Herding AI Agents Now
Robert C. Martin — Uncle Bob, the man who wrote Clean Code — has a repo on GitHub Trending today: swarm-forge, a simple tool for coordinating several AI agents (github.com/unclebob/swarm-forge). It is written in Clojure, sits at 1.8k stars, and has 258 commits, which for a 73-year-old spokesman of software craftsmanship is not a drive-by experiment.
The design is aggressively low-tech and that is the point. Each agent role gets its own isolated git worktree. Sessions run in tmux. Agents communicate through validated handoff files dropped in project directories — no message bus, no cloud platform, no orchestration service. It ships three preset crews: a two-pack for quick backend work, a four-pack for specification-driven development, a six-pack for the full workflow. Self-hosted, lightweight, runs on your machine.
Squint and you will recognize the ideology. Isolated worktrees are single responsibility. Validated handoffs are interface contracts. Preset role structures are the team disciplines he has preached for forty years, now applied to non-human programmers. While the industry builds increasingly elaborate swarm platforms, the Clean Code guy's answer is: files, contracts, and discipline are enough. His generation's whole argument was that software quality comes from constraints humans impose on themselves. Watching him impose the same constraints on agents — and finding that tmux plus git suffices where others deploy Kubernetes — is the most Uncle Bob thing imaginable, and honestly a useful data point for anyone overbuilding their orchestration layer.
← Back to all articles
The design is aggressively low-tech and that is the point. Each agent role gets its own isolated git worktree. Sessions run in tmux. Agents communicate through validated handoff files dropped in project directories — no message bus, no cloud platform, no orchestration service. It ships three preset crews: a two-pack for quick backend work, a four-pack for specification-driven development, a six-pack for the full workflow. Self-hosted, lightweight, runs on your machine.
Squint and you will recognize the ideology. Isolated worktrees are single responsibility. Validated handoffs are interface contracts. Preset role structures are the team disciplines he has preached for forty years, now applied to non-human programmers. While the industry builds increasingly elaborate swarm platforms, the Clean Code guy's answer is: files, contracts, and discipline are enough. His generation's whole argument was that software quality comes from constraints humans impose on themselves. Watching him impose the same constraints on agents — and finding that tmux plus git suffices where others deploy Kubernetes — is the most Uncle Bob thing imaginable, and honestly a useful data point for anyone overbuilding their orchestration layer.
Comments